Compliance you can prove, not just claim
Most payroll systems bury compliance inside opaque code, where correctness is asserted but never shown. Payroll Engine makes it explicit: regulations are declared as data, verified by tests, dated to the law in force, and recorded in an immutable audit trail.
The result is payroll whose correctness can be inspected, reproduced, and defended — by payroll experts and auditors, not only by developers.
- 01Verified — executable tests with calculation records
- 02Sourced — statutory reference on every value
- 03Dated — validFrom-dated regulation data
- 04Audited — annual check against official gazettes
- 05Accountable — immutable, reproducible audit trail
Every regulation is backed by executable tests
Each rule ships with integration tests that assert the legally correct result to the cent. Every test carries a calculation record documenting the statutory derivation — so an expected value is never a magic number, it is a traceable computation. The full suite runs in CI on every change.
- Statutory results asserted to the cent, re-run on every change
- Each test documents its legal calculation — the test is the audit record
- A change that breaks a known-correct result fails the build, not the payslip
Every value traces back to its legal source
Tax tariffs, contribution rates, thresholds, and allowances live in versioned data sets, each tied to its legal basis — the gazette, paragraph, or official table it comes from. Nothing is hard-coded or estimated: values are verified against official sources before they ever go live.
- Rates and thresholds carry their statutory reference
- No estimated or training-derived figures — official sources only
- Any figure on the payslip can be followed back to the law
The law that applied then still applies to then
Regulations and their data carry a validity start date. The engine resolves the version of the law that was in force for each pay period — so reprinting or recalculating a closed period yields exactly what it did originally. A new tax year is a new dated data set; prior years stay untouched and reproducible.
- Period results resolve against the law valid for that period
- New tax year = new dated regulation; old periods remain reproducible
- Two-axis time model (case-value time × regulation time) for full historical fidelity
Every statutory value re-verified before each tax year
Before a new tax year goes live, every regulation passes a structured compliance audit: each value is read, verified against the official source, reported, and corrected where needed. Passing local tests is not enough — statutory correctness is checked against the official gazettes themselves.
- A disciplined read → verify → report → fix cycle against official gazettes
- Catches carried-forward, swapped, or obsolete values before release
- Run for every supported country regulation, every year
An immutable audit trail, by design
Every case change and payroll result is timestamped and immutable — you can see who changed what, and when, and recompute any run to verify it. Beyond the trail, the platform enforces tenant isolation, static script-safety analysis, and GDPR-aligned data handling.
- Timestamped, immutable case and result history
- Reproducible payruns — recompute to verify any result
- Tenant isolation, script safety analysis, and GDPR-aligned data handling
Compliance at a glance
| Discipline | Mechanism | What it gives you |
|---|---|---|
| Verification | Executable tests + calculation records | Correctness you can prove |
| Traceability | Statutory reference on every value | Audit-ready lineage |
| Versioning | validFrom-dated regulations | Reproducible history |
| Annual audit | Verification against official gazettes | Up to date, every year |
| Retro corrections | Delta wage types + time segmentation | Legally correct recalculation |
| Forecasting | Same engine as the legal run | No estimation gap |
| Accountability | Immutable audit trail | Defensible payroll |