The short answer

An employee self-service portal is an internal system where staff request leave, check their leave balance and payslips, read and acknowledge policies, and ask for certificates or equipment, while managers and HR approve everything in one place instead of in email threads. For a larger organisation, the payback rarely comes from a nice home page. It comes from fewer routine questions landing on HR and a clear record of who approved what, and when.

At the end of 2026 this also becomes a compliance question in Lithuania. Under the Labour Code amendments that transpose the EU Pay Transparency Directive, every employer must approve or review its pay system by 31 December 2026 and make it available to all employees. From March 2027, employees can ask for data on their own pay and on average pay in their job group, and the employer has one month to reply in writing. For an organisation with hundreds of staff, that is a process worth running in a system rather than an inbox.

This guide is written for the buyer: which features matter, how to connect a portal to payroll and HR systems, when a packaged product is enough and when a custom build makes sense, and what the pay transparency rules change. We checked the sources on 17 November 2026. It is a practical guide, not legal advice.

Self-service portal vs intranet vs customer portal

These terms get mixed up, but they solve different problems:

  • An intranet is an internal information site: news, policies, contacts, the org chart. It informs, but it usually doesn't change anything.
  • An employee self-service portal lets people take action: submit a request, approve it, sign, view their own data. Behind every action there is a process with owners and deadlines.
  • A customer self-service portal serves external users such as customers, partners and distributors. We covered that separately in our guide to the B2B customer self-service portal.

A good employee portal usually has both layers, the information part and the action part. The value, though, sits in the second one. If the portal only shows news, people will open it once a month.

Why now: pay transparency in Lithuania

Lithuania transposed the EU Pay Transparency Directive (EU) 2023/970 through Labour Code amending law No XV-969, adopted on 21 May 2026. Most provisions took effect on 7 June 2026 and some take effect on 1 January 2027. The dates that matter for systems:

Date What changes What it means for your systems
By 31 Dec 2026 Every employer, regardless of size, approves or reviews its pay system. It must be available to all employees (Labour Code Art. 140(3)). You need one place where the pay system is published, the current version is clear, and you can see who has read it.
From 1 Jan 2027 Employers send a monthly pay transparency report (SDUP) to Sodra, the State Social Insurance Fund. The first one is due in February 2027 for January. It includes each employee's job group number under the pay system. Every role in your payroll or HR system needs a job group. The State Labour Inspectorate (VDI) says the data can also be sent straight from the employer's own system.
From March 2027 Employees can request, in writing, their annual and average hourly pay and the averages by gender in their job group. The employer must reply within one month, and any further explanations within two months of the request (Art. 148(4) and (5)). You need a request form, a logged receipt date, deadline tracking and an archive of replies.
Every year Employers must tell employees about this right and how to use it (Art. 148(4)). An annual notice with read confirmations.
1 Mar 2028 and 1 Mar 2031 Sodra delivers the first gender pay gap reports to employers with 150 or more insured employees (2028) and with 100 to 149 (2031). Employers must share them with employees and employee representatives within one month. Publishing to staff and representatives with tight access rights.

VDI itself urges employers to review and, where needed, update their accounting and information systems and do the necessary development work. According to VDI's guidance, failing to provide pay information to employees can bring fines on managers of EUR 460 to 700, rising to EUR 700 to 1,400 for a repeat offence.

One detail your developer needs to know: if a reply would directly or indirectly reveal the pay of another identifiable employee, that data goes not to the employee but to employee representatives, VDI or the Equal Opportunities Ombudsperson (Art. 148(7)). If a job group has only one woman in it, for example, the "average for women" is simply her salary. The system has to spot these cases rather than display the number.

It also helps to be clear about what a portal doesn't do. Sodra calculates the indicators from the data you report, and grouping roles is a decision for management and employee representatives. The portal is the channel where requests come in, deadlines are tracked, and replies are delivered and archived.

What to build, in three stages

The most common mistake is trying to build everything at once. Rank features by how much manual work they remove.

Stage 1: the biggest time savers

  • Leave and other requests. Employees see their balance and submit a request, managers approve it on their phone, and the approved request flows into payroll automatically. Cover arrangements and a team leave calendar sit alongside.
  • Payslips. The Labour Code allows information on calculated, paid and deducted amounts and hours worked to be provided at least monthly in writing or electronically (Art. 148(1)). A portal is a safer channel than a PDF attached to an email.
  • Policy acknowledgements. Work rules, the pay system, safety instructions, policies. What matters is not the file itself but the record of who read which version and when.
  • Certificates and requests. Employers must issue an employment certificate on request (Art. 148(3)). A tracked request beats a phone call to HR.
  • Contacts and structure. Who is responsible for what, and who covers for whom.

Stage 2: processes that span several teams

  • Onboarding and offboarding. A checklist with owners: IT sets up accounts, facilities prepares the desk, the manager assigns a buddy. Offboarding runs in reverse, with equipment returned and access revoked on the same day.
  • Equipment and assets. Who has which laptop, phone or car, and when the warranty runs out.
  • Business travel and expense claims with receipt photos and approvals.
  • Training and mandatory briefings with deadline reminders.
  • Shift schedules for organisations that run shifts.

Stage 3: pay transparency and reporting

  • Pay information requests with a logged receipt date, an automatic one-month deadline, reminders for the person responsible and an archive of replies.
  • The annual notice of the right to request pay data, with read confirmations.
  • Publishing gender pay gap reports to staff and representatives if you have 100 or more employees.
  • Surveys and management reports, for example how long leave approvals take on average.

With a 31 December 2026 deadline, a realistic plan looks like this: publish the pay system with read confirmations now, have the pay information request process ready by March 2027, and add everything else in order of value.

Integrations: where the portal gets its data

A portal should not become yet another place where people retype the same data. Each data type needs one source of truth:

Data Source of truth Direction
Employees, roles, departments, job groups Payroll and HR system Into the portal
Leave balances, payslips Payroll system Into the portal
Approved requests Portal Into payroll
Sign-in and accounts Your directory, for example Microsoft Entra ID or Google Workspace Single sign-on (SSO)
Documents to be signed Document management system Both ways

A few practical points:

  • Check first whether your payroll software has an API. If it does, requests and balances can sync automatically. If not, a scheduled export and import is often enough. We covered integrations with the accounting systems common in Lithuania in our article on Rivile, Directo and Agnum integrations.
  • Single sign-on is a must. One more password means lower adoption. And when someone leaves and their directory account is disabled, portal access should disappear with it.
  • Document signing and storage often already live in a document management system. In that case the portal just starts the document and shows its status. We looked at how to choose one in our guide to document management systems.
  • Staff without a desk. In manufacturing, logistics and retail, many people have no work email. The portal has to work on a phone, and signing in has to make sense to someone who only logs in once a month.

Packaged module, intranet or custom portal

Option Good fit when What to check
Self-service module in your payroll or HR software Needs are mainly leave and payslips, and processes are standard Does it work well on a phone? Can you add your own processes, such as pay information requests?
International HR platform (SaaS) You operate in several countries and want a standard HR process Does it handle Lithuanian specifics? How does it connect to payroll if payroll runs elsewhere? How does the price scale with headcount?
Intranet, for example SharePoint in Microsoft 365 The focus is information, documents and communication, and you already use Microsoft 365 Simple form workflows are possible, but more complex processes with integrations often need extra development.
Custom portal Processes are specific, several systems need connecting, and many staff work away from a desk Higher upfront cost. You need a clear specification and a maintenance plan.

For many organisations the right answer is a mix: payroll stays the source of truth for calculations, and a thin custom portal sits on top of it for the processes the packaged modules don't cover. Before you decide, cost it over five years: per-employee licences or subscriptions, implementation, integrations, maintenance and changes.

Security and personal data

An employee portal is one of the most sensitive systems you run. It holds salaries, medical certificates, personal ID numbers and family details.

  • Individual pay data may only be disclosed where the law requires it or with the employee's consent (Art. 148(2)). Managers should see their team's requests, not their salaries, unless their role genuinely needs it.
  • Data minimisation. The GDPR requires you to process only what is necessary for the purpose (Art. 5(1)(c)) and to ensure appropriate security (Art. 32). Don't collect what you won't use.
  • Two-factor authentication, especially for remote access and for admins.
  • An audit log of who viewed or changed what. It will also help if a pay dispute comes up.
  • Access reviews at least once a year, and automatic removal when someone leaves.

If NIS2 applies to your organisation, these requirements belong in your contract with the developer too. We went through what to include in NIS2 requirements for software suppliers.

Public sector: accessibility

Public sector bodies are covered by the EU Web Accessibility Directive (EU) 2016/2102. It exempts only intranet and extranet content published before 23 September 2019, and only until the site undergoes a substantial revision (Art. 1(4)(g)). In practice, a new or substantially rebuilt staff portal for a public body has to meet the accessibility requirements. Put that in the technical specification from day one, because retrofitting costs more. We covered the WCAG side in WCAG and the European Accessibility Act.

Example: a manufacturer running three shifts

This is a made-up example. "Amber Packaging" is a fictional company, and the figures are rough estimates meant to show the reasoning.

Amber Packaging has around 220 employees, 160 of them on the production floor across three shifts with no work email. Leave requests are filled in on paper and carried to HR by shift supervisors, and payslips go to personal email addresses. HR is two people.

The company runs the numbers like this: if HR gets about 40 routine questions a week (balances, certificates, payslips, request status) and each takes about 10 minutes, that is 6 to 7 hours a week, close to a full working day. On top of that, from March 2027 there will be pay information requests with a one-month deadline.

In stage one the company launched a mobile-friendly portal with sign-in by personal phone number and a one-time code: leave requests, balances, payslips, and the pay system with read confirmations. Approved requests are pushed to the payroll software every hour. Stage two added the pay information request process and an onboarding checklist. The company did not rebuild payroll or move HR records into the portal. The portal shows what the payroll software holds.

Common mistakes

  • Starting with design instead of processes. First list the 5 to 10 most common employee requests and who handles them today.
  • Duplicated data. If the leave balance in the portal doesn't match payroll, people will stop trusting the portal within a week.
  • Forgetting deskless staff. If the portal only works on the office network or with a work email, production and field staff are left out.
  • Overly broad permissions. Managers and admins see more than they need, which is especially risky with salary data.
  • Handling pay transparency by email. Once requests pile up, the one-month deadline slips easily and there is no archive of replies.

FAQ

Does a small company need an employee self-service portal?

Usually not. A company with a dozen or so employees can often get by with the self-service module in its payroll software and a shared document folder. Even so, every employer, whatever its size, must approve its pay system and make it available by 31 December 2026.

Can the portal answer pay information requests automatically?

Partly. Under Art. 148(5) the employer receives the indicators from Sodra, so the portal can prepare a draft reply from that data. But for the Art. 148(7) cases, where a reply would reveal another employee's pay, a person has to make the call.

Can payslips be available only in the portal?

The Labour Code allows this information to be provided electronically (Art. 148(1)). What matters is that every employee has real access, so people who can't use the portal need an alternative.

How long does it take to build an employee portal?

It depends on scope and integrations. A first stage with a handful of processes and one integration is usually a matter of months, not years. An accurate timeline and price are only possible once the processes are described and you know which systems need connecting.

Can the employee portal and the customer portal be one system?

Technically yes, but we usually advise against it. Users, permissions and security requirements are very different, so in most cases they are two separate systems that can share the same integrations.

Next steps

Start with two questions. First, where and how will employees read the approved pay system by 31 December, and how will you record that they did? Second, from March 2027, who will receive, log and answer pay information requests within a month, and how? If the answer is "by email", now is a good time to consider a portal.

DESAmedia builds web applications, including internal self-service portals, and connects them to the systems you already use through integrations and automation. In our driver communication and document system, for example, staff who never come into the office receive instructions and documents on their phones, and managers can see who has read them. For institutions, we work through our public sector services. If you'd like to talk through your situation, get in touch.

Sources