Employee self-service portal for small business: what to build

An employee self-service portal for small business is a secure login where each person on your team can view their own pay slips and tax forms, request leave, update personal details and find company documents, without asking HR for each one. For a team of 10 to 200 people, that usually means fewer emails, fewer paper forms and fewer "where is my pay slip?" questions. Vendors call it employee self-service software, an employee portal or an HR self-service portal, and the names overlap. Most standard tools cover the basics. Where they fall short is approval rules that match how your business actually runs, and that is where custom HR software development starts to make sense. This guide covers what staff can do, where approval rules matter and how buying compares with building.

1What can staff do in an employee self-service portal?

Most products share the same core features: pay documents, leave requests, personal details and a document library. The real differences lie in the rules behind each feature and in who can see what.

Pay slips and tax forms

Staff log in and download their own pay slips and, at year end, their tax slips. In Canada that is the T4. In the US it is the W-2.

Each person should see only their own records. HR should set that by role, so a payroll clerk can see pay for the whole company while an employee sees only themselves. Review those settings whenever someone changes role, because access tends to grow over time and rarely shrinks.

Leave and time-off requests

A good portal makes a leave request short. The employee picks dates, sees their balance, and submits. Their manager is notified, approves or declines, and the team calendar updates. HR sees the same request, and the employee gets a confirmation.

The balance display matters because it prevents the two most common leave emails. One is "how many days do I have left?" The other is a request for dates the employee cannot take. When staff can see their balance before they submit, managers refuse fewer requests and HR answers fewer questions.

Personal details and company documents

Staff can usually update a mobile number, home address or emergency contact themselves. Not every change should go live straight away. An address change can affect tax withholding or where a direct deposit goes, so it should go to HR for a check first. An emergency contact change can usually go live at once.

Company documents are the other half of the job: the handbook, policy updates and forms that need signing. A portal can record that each person has read a policy, with the date and time. That record matters if an employment dispute arises.

2Is an employee self-service portal for small business worth it?

Sometimes not. Below a certain size, the time a portal saves may not cover its cost. A small team can often manage with a shared folder and a well-kept spreadsheet.

Here is a hypothetical example. A 30-person firm in Raleigh spends about 10 hours a month on self-service tasks: answering pay queries, sending pay slips, chasing leave requests and typing address changes. With a portal, that falls to about 4 hours. The saving is 6 hours a month. At a hypothetical internal cost of $35 an hour, that is $210 a month.

Set that against a hypothetical subscription of $300 a month for 30 staff. On time saved alone, the subscription costs more than the saving. That does not make the portal a bad idea. It means the case has to rest on other things: fewer keying errors on pay-related changes, a record of who approved what, and staff getting answers outside office hours.

Run the test yourself. Count the hours your HR and office team spend on self-service tasks for one month. Then add up what your last few pay errors cost you. If the total falls well short of a tool's price, a simpler process may be enough.

3How do leave and payroll approvals work in a portal?

Many generic tools give you one approval step: the manager. That works for a day off. It does not work for a change to someone's salary or bank account, and most small businesses handle both kinds of request.

A sound design sends each request through the right chain and keeps the person who prepares a change away from approving it. The preparer should never approve their own payroll change. That rule is easy to state and easy to break when a small team is busy, so the system should enforce it rather than rely on memory. For the reasoning behind this rule, read payroll approval controls.

This is where a custom build can differ from a template. The chain follows your org chart and your limits, not a vendor's default settings.

Who approves what, and in what order?

The table below shows a simple chain for the requests most small firms handle.

Leave is about who has time off. Payroll is about who can move money. Keep the two chains separate in the system, not just in a policy document.

What happens when an approver is away?

Requests stall when the one person who can approve is on holiday. Set three rules and build them into the system:

• Delegation. An approver names a delegate for a set date range. The delegate cannot approve their own requests or payroll changes they prepared.
• Time limit. A request not acted on within a set period, two working days for example, passes to the delegate or the next person up.
• Escalation. If that also stalls, it reaches the owner or a named senior person, who sees a list of overdue items each morning.

Write these rules down. Don't leave them to memory.

4How much does employee self-service software cost per employee?

The employee self-service portal cost depends on whether you buy a subscription or pay for a build. Compare them on the same basis: cost over three years, what happens when you need a change, and who owns the data.

For Treevoxa figures, use our software development cost calculator and see our software development rates. Treat any third-party figure, including the ones in agency blog posts, as context rather than a budget.

What do off-the-shelf tools charge per employee?

Most employee self-service software is priced per employee or per user, and the two are not the same. Per employee means every person on payroll counts. Per user means every person who logs in counts, which can include managers who only approve requests and sometimes contractors. Read the definition before you read the price.

Three other traps catch small firms:

• Monthly minimums. Some vendors set a minimum fee for small teams, so a 10-person firm may pay more per head than a 200-person firm.
• Add-on modules. Approval chains, time tracking and recruiting are often sold separately.
• Price changes. Vendors revise pricing, sometimes mid-year. Check the vendor's current pricing page on the day you compare, not a roundup written last year.

Here is the arithmetic for a hypothetical 30-person firm. These figures are illustrative and are not a quote from any vendor:

• Hypothetical base fee: $10 per employee per month, so $300 a month or $3,600 a year.
• Hypothetical approval add-on: $150 a month, so $1,800 a year.
• Total: $450 a month, or $5,400 a year, before set-up.

The headline price was $10 a head. The real price was $15 a head. Always add up the full bill.

What drives the cost of a custom build?

A custom build is priced on scope. The main drivers are:

• The number of approval rules and how many exceptions they carry.
• Integrations with payroll, accounting and time clocks.
• Mobile access for staff who do not sit at a desk.
• Reporting, from simple exports to dashboards for owners.
• Data migration from spreadsheets and old systems.
• Security review, hosting and support.

Each extra integration or approval exception adds design and testing work, so ask any builder, including us, to price the rules you actually need rather than a generic portal. We agree a written scope and a fixed price before any work starts, so you know the number before you commit. For a wider view of HR and payroll build costs, see HRMS software development cost.

5Should a small business buy an off-the-shelf portal or build one?

Buy when your process is standard and a tool does what you need. Build when your approval rules are part of how the business works, and when the workarounds you would live with cost more than a build.

The table below uses a hypothetical 30-person firm over three years. Every figure is illustrative.

Assumptions: the subscription is $10 per employee per month plus a $150 monthly approval add-on. The build column assumes hosting and maintenance of $6,000 a year, about 13 per cent of the build cost, and that a build removes the manual workarounds. Change any of these and the totals move.

On these numbers, buying costs less at 30 staff. That is the honest answer for most small firms with standard leave and pay processes. The sums change when headcount grows, when workarounds multiply, or when a tool cannot connect to the payroll or time system you already use. Build cost also rises with each integration.

Treevoxa builds custom HR systems to a client's own rules, and it also runs MatrixHR, HR and payroll software as its own packaged product. That gives you two routes. A packaged tool is often the better one for a firm with standard processes, so compare both on the same three-year basis. For the wider trade-off between owning software and renting it, see custom software vs SaaS.

There is a middle path. Ready-made software with source code gives you a working base you can adapt, with full source code included.

Buying is usually the right answer when:

• Your approval chain is two steps or fewer.
• Your pay rules are standard.
• You need a working system within weeks, not months.
• You have no one in-house to manage a build.

6How secure is employee data in a self-service portal?

A portal holds the most sensitive records a small business keeps: bank details, home addresses, dependants, tax forms and pay history. One glossary entry on HR self-service portals notes that this mix makes these systems attractive to attackers. That is why security design matters as much as the screens.

A sound portal should do four things:

• Role-based access. Each role sees only what it needs. Employees see themselves, managers see their team, payroll sees pay, and nobody sees everything by default.
• Encryption. Data is encrypted as it travels between browser and server, and while it is stored. Ask your builder or vendor to show you how.
• Strong login for anyone with power. Anyone who can change pay or bank details signs in with a second factor, such as a code from an app.
• Same-day removal. When someone leaves, their access ends that day, not at the end of the month.

Can HR control what each employee sees in the portal?

Yes. HR sets access by role, so an employee sees only their own records, a manager sees their team, and payroll sees pay. Test it before go-live. Log in as a test employee and try to open a colleague's record by changing the number in the web address. If it works, stop and fix it. A portal that shows one person another's pay slip is a privacy breach, and the loss of trust lasts longer than the fix.

Who can change bank details, and how is it checked?

Bank details are the change most worth guarding. A reasonable rule looks like this:

1. The employee submits the new details in the portal. Nothing changes yet.
2. HR, who did not submit the change, checks it against a signed form or an in-person confirmation.
3. The system sends a confirmation to the contact details already on file, not the new ones. This stops someone who has taken over an employee's login from redirecting their pay.
4. The new account is used from the next pay run after those steps are complete, not before.

No one changes their own bank details without a second person, including the owner.

What gets logged, and who can see the log?

Every change to pay or personal data should create a log entry. Record who made the change, which field changed, the old value, the new value, and the date and time. Staff should not be able to edit or delete that log.

Someone outside payroll, usually the owner or a senior manager, should review bank and pay changes each month. A quick review that catches one unexpected change is worth more than a long report nobody reads.

7Do Canadian or US privacy laws apply to a self-service portal?

This section is an overview, not legal advice. The rules depend on where your business is regulated and where your staff work.

Canada. PIPEDA is the federal private-sector privacy law. The Office of the Privacy Commissioner of Canada says PIPEDA covers employee personal information only for federally regulated businesses, such as banks, telecoms and airlines. For a provincially regulated employer, employee data generally falls outside PIPEDA and under provincial law instead. Ontario has no general private-sector privacy law covering employees, so for most Toronto-area businesses the question is which provincial rules apply and how. Some commercial guides take a different view, so confirm your position with a Canadian privacy adviser before you rely on it.

Alberta and British Columbia have private-sector privacy laws that the OPC treats as substantially similar to PIPEDA. Quebec's Law 25 is stricter. It requires a privacy impact assessment for information system projects that involve personal information, so a portal that holds Quebec staff data needs one before it goes live.

Federal bills to replace PIPEDA have been before Parliament in recent years. Their status changes, so check where they stand before you plan around them.

United States. There is no single federal law that covers most private-sector employee records. Each state sets its own rules. California's privacy law has covered employee data since 2023, and New York requires employers to give notice before monitoring staff electronically. A firm with staff in New York, Austin, Raleigh and Denver may face a different set of rules in each place. Check each state before go-live.

On both sides of the border:

• Collect less. The OPC's guidance on privacy in the workplace says employers should limit employee information to what is necessary. Don't store a scan of a passport if the portal does not need one.
• Say where data lives. If a Canadian business hosts employee data in the US, Ogletree's guidance on transferring employee data points to telling staff about the transfer, its purpose, the risks and the safeguards in place.
• Write it down. Keep a short note of what the portal collects, why, who sees it and where it is held. It helps when you answer staff or a regulator, and it forces a useful question: do we really need this field?

8How long does it take to roll out a self-service portal?

The timing depends on how clean your records are and how many approval rules you need. The stages are much the same whether you buy or build:

1. Scope. Write down which processes the portal covers, which approval rules apply and what the first version leaves out.
2. Clean-up. Fix employee records before they move.
3. Configure. Set up approval chains and access by role.
4. Migrate and check. Move the data and compare it with the source.
5. Train. Run short sessions for staff and managers, with a one-page guide for each role.
6. Parallel pay run. Run one cycle in the old and new systems side by side and compare every line.
7. Go live. Name one person to handle questions through the first pay cycle.

For a custom build, we agree a written scope, a fixed price and a launch date before any work starts. You own the code and the accounts. Treevoxa has offices in Toronto, Thornhill, London and New York, so the team can work with owners on either side of the border. The written scope sets the timeline, and it is the first thing to check if a date slips.

How do you move data off spreadsheets?

Start with the employee list. Remove leavers, merge duplicates, and standardise job titles, pay codes and departments. Then check leave balances. The old spreadsheet and the new system should agree before anyone uses the new one. Where they differ, the person who owns leave, usually a manager or HR, checks the figures by hand.

Finish with a sign-off. Ask the owner or a senior manager to approve a one-page reconciliation covering headcount, total pay for the last run, leave balances and bank details. Go live only after that sign-off. If something is wrong, you find it there, not after the first payslips go out.

9How does attendance link to payroll?

If you already run time clocks, such as ZKTeco devices, attendance data can feed pay directly. Punches are collected, matched to employees and shifts, checked for missed or doubled entries, and then summarised into hours for the pay run.

The step that needs human judgement is the exception list. A missed clock-out, a shift swap or a late start should go to the supervisor for a decision before pay is calculated, not after. Rounding and overtime rules should be set once, written down and applied the same way to every person.

For a business that already runs time clocks, the step from attendance to pay is often where most of the manual effort sits. See ZKTeco attendance to payroll for how that works in practice.

10What should you write down before you buy or build?

Before you talk to any vendor or builder about an employee self-service portal for small business, write down three lists: your approval chain, the spreadsheets you are replacing, and the add-ons you think you need. Those lists settle most of the cost questions before a quote arrives.