Employee Self-Service
Payslips, annual tax statements, personal data, requests and documents in the employee’s hands — including on mobile. Every query resolved there is a ticket that never reaches HR.
We implement the HR system the client has contracted — we do not run their day-to-day operation. Payroll is the heart of that system and where we go deepest, but implementing payroll alone delivers half a solution: employees keep phoning HR, managers keep approving by email and finance keeps typing.
This is where an implementation error costs the most — in money, in labour liabilities and in trust. That is why it is the module we go deepest into, from configuring pay elements to the parallel run that proves the calculation before go-live.
These are the modules that decide whether HR spends the month answering tickets or actually managing. When they work, the volume of questions reaching HR falls on its own.
Payslips, annual tax statements, personal data, requests and documents in the employee’s hands — including on mobile. Every query resolved there is a ticket that never reaches HR.
Leave requests, personal data changes, job requisitions, expense approvals: each flow with a path, an approval limit, a deadline and an owner. A stalled request now has someone accountable instead of vanishing in an inbox.
These are the modules that back up decisions which have to be defended — in an audit, in union negotiations or in a difficult conversation with a manager.
Job architecture, job descriptions, salary bands and grading. Without this foundation, pay policy becomes case by case — and case by case becomes liability.
Workforce cost planning with scenarios, and budget-versus-actual tracking through the financial year.
Eligibility rules, policies by group, deductions and vendor reconciliation — tied to what payroll actually processed.
Headcount, turnover, absence and cost metrics, built to answer management questions — not to fill a screen with charts nobody looks at.
The bridge between payroll and accounting: cost centre allocation, integration with the finance ERP and the reconciliation that closes the month without manual keying.
Custom development, including FPw Reports and consuming the reporting API per environment. Written so that someone else can maintain them later.
Because in practice they are not independent. A badly configured benefit policy shows up as a discrepancy in payroll; a workflow without the right approval limit jams leave, job changes, absences and terminations — and each of them comes back as a retroactive adjustment in payroll; a wrong cost allocation in the finance integration is only found by the accountant, at period close. Implementing them together is what allows the validation of one module to catch the error in another.
You can start with one. But it is worth talking about how it talks to the others.