One engine, two forecast models
A forecast in Payroll Engine is not an approximation layer bolted onto payroll — it is a real payrun, executed by the same regulation logic that produces the binding payslip and written to an isolated result store you can re-run as often as you like. There is no separate “estimation” codebase to drift out of sync.
That single property unlocks two distinct ways to put forecasts to work, shown below. They differ in whether an existing payroll is involved and what the result is used for — the calculation engine is identical in both.
Payroll Validation & Analysis
Validate and forecast against an existing production payroll (not Payroll Engine) — without switching systems first. Built for evaluation and migration.
- Validate an existing production payroll by running the same cases through Payroll Engine and comparing the results
- Produce forecasts relative to your existing production payroll
- A Payroll Adapter imports the source data from the existing payroll into Payroll Engine
- A dedicated verification step compares both result sets — for evaluation and migration sign-off
Payroll Engine Analysis
Everything runs inside Payroll Engine — production payslip and forward-looking planning on the same engine, with no external system involved.
- What-if simulation: model salary changes, promotions, and one-time payments before they happen
- Budgeting and cost projections across future periods
- Earned wage access: the exact net pay, computed by the real engine — not an estimate
- Combined production & planning: the legal payrun produces the payslip, a forecast payrun the analysis on the same data
Two models at a glance
| Scenario | External system | Job types | Output | Typical use |
|---|---|---|---|---|
| Payroll Validation & Analysis | Existing payroll (via Adapter) | Forecast + existing run | Verified results & forecast analysis | Evaluation, validation, migration |
| Payroll Engine Analysis | None | Legal + Forecast | Payslip + forecast analysis | What-if, budgeting, EWA, planning |