Service notepre-implementation-reading
Pre-implementation suite reading
Before a new payroll processing suite goes live, we read the configuration workbooks and the parallel-run differences as an independent financial check.
Quoted after we see the parallel-run calendar and the chart of wage types.
A vendor implementation is not a financial audit. The project team is paid to make the suite run. We are asked, usually by the CFO or the audit committee, to read the same workbooks with a different question: will this configuration pay people and the statutory bodies correctly on day one?
We sit with the parallel-run exceptions, not the slide deck. We sample joiners, leavers, and the ugliest allowance combinations in the old system, and we ask the new suite to produce the same net and the same contribution files.
What this engagement is not
We do not select the vendor. We do not manage the project. We do not sign a go-live certificate. We issue a letter of findings on the financial configuration, with items ranked as must-fix before first live pay, or watch in month two.
If the parallel run has not yet started, we can still review wage-type mapping and statutory screens, and we will say clearly that calculation testing remains outstanding.