Client profile
Kestrel Pay, a UK cross-border payments company.
Challenge and scope
The payroll team interprets 11 sets of tax rules. A 4.2% error rate creates more than 40 corrections in a monthly cycle.
A late hire, updated bank instruction, or retroactive pay change can carry a different meaning across local payroll calendars. The harder cases are changes that appear valid within one system but differ from the approved HR record. Resolving them after payroll runs increases corrections and leaves unclear ownership of the final figure.
Delivery workflow
Validate inputs for 1,900 employee payroll records across six jurisdictions. Country specialists work the recurring exceptions and quality reviewers compare the run with the prior payroll before it goes to the client for approval.
Prepare a country-level checklist for the recurring inputs and freeze times. Compare joiners, leavers, variable pay, deductions, and approved changes from HiBob with the relevant Deel or local records. Store each exception with its effective date, approval trail, and the pay period it affects.
Review totals against the prior period and investigate outliers before the employer signs off. Give each correction a reason code so reviewers can identify recurring data gaps. Keep a country-specific handoff with the draft register, unresolved questions, and a timestamp for final approval.
Delivery team
Bulgaria, about 6 FTE. 1 payroll lead, 3 country specialists and 2 QA reviewers.
Systems and tools
HiBob, Deel, local tax portals.
Client decision rights
The employer decides compensation and equity treatment and approves the final payroll.
Early milestone
By week 4, correction tickets fall to 22 per cycle.
Outcomes
Company-reported results, with the baseline, measurement window and supporting record described for each measure.
| Measure | Baseline | Result | Window | Supporting record |
|---|---|---|---|---|
| Payroll error rate | 4.2% | 0.3% | 5 months | Payroll register |
| Correction tickets per cycle | 44 | 3 | 5 months | HRIS report |
| Cycle completion | Day 4 | Day 2 | 5 months | Payroll register |
Interpreting the results
The drop from 44 to three correction tickets per cycle is easier to interpret with staffing and pay frequency held comparable. Separate errors discovered before release from post-payroll adjustments. Define the cycle clock from the agreed cutoff to a reviewed register and record any wait for employer approval separately.
Recommendations for new clients
For fintech operators running payroll in at least four countries, compare corrections and on-time completion by jurisdiction. Include off-cycle changes in the pilot so the QA process is tested against exceptions.
Start with countries that have different calendars and at least one with frequent off-cycle changes. Give the delivery team an approved input checklist, sample payroll files, and named country decision owners. Review a comparison run against expected outputs and require every material variance to have a reason, supporting record, and approval.