The engine

Statutory rules are data, not code.

Adding a country to most HR systems means a release. Here it means rows. That single decision is what lets one platform be correct in more than one place at once — and it is the reason a payslip from last year still shows last year’s rules.

What lives in the tables

  • Employee and employer contribution rates, each with its wage ceiling and floor
  • Progressive tax bands, per year and per regime
  • Statutory leave entitlements, how many days, and who pays for them
  • Public holidays, including ones that move with the calendar each year
  • Required identifiers, each with the validation pattern it needs
  • Currency, locale, timezone, fiscal year start, week start, working days

What that buys you

History stays true. When a government revises a rate, a new set of rows is added. Nothing already run is altered, so a payslip produced eighteen months ago still reflects the rules in force at the time — which is exactly what an auditor expects to find and exactly what a recalculated figure destroys.

Quotes and payslips cannot drift. The calculator and the payroll run read the same rows. The number you give a candidate in March is the number they see on their payslip in June.

A new country is scoping, not rebuilding. No new deployment, no forked payroll logic to keep in step, no second codebase quietly diverging.

The step most systems skip

Tax is not calculated on gross pay.

In most countries, social contributions come off before income tax is worked out — sometimes with a cap on how much is deductible. Apply the tax bands straight to gross and you overstate the tax and understate the take-home, every single month, for every single employee.

We know the size of that mistake because we made it. Correcting exactly this step in our own engine moved a mid-range salary by around €120 a month. Nobody would have noticed for a year.

The engine now handles ceilings, deductibility caps, standard deductions, rebates and marginal relief where a country has them — and the public calculator uses the same code, so you can check it yourself before you ever speak to us.

Check it yourself →
0.00Variance between the public calculator and a real pay run
Per yearRules versioned, so a reprint of an old payslip is still correct
Both sidesEmployee deductions and full employer cost, always
FlaggedAny forward-year rate carried forward pending confirmation

Running a month

What actually happens on the 25th.

1 · Open the run

Create the run for the month. Everyone with a current salary structure is picked up automatically.

2 · Deductions computed

Statutory lines are calculated from the country and year tables — not from anything typed into the run.

3 · Review the totals

Gross, deductions, net and headcount, next to last month. A figure that moved without a joiner, leaver or revision is worth understanding before it is paid.

4 · Approve

Approval is a deliberate act by a person with the authority, and it is recorded with their name against it.

5 · Pay and publish

Mark as paid once the transfer is made. Payslips become visible to employees immediately, each reconciling line by line.

6 · It stays put

The run keeps the rules that produced it. Later rate changes do not reach backwards and quietly restate it.

Bring us a salary and a country.

We will show you the derivation, not just the total.