Payroll reconciled before it pays
A multi-country employer now catches around 85% of payroll exceptions before the run closes rather than after, has cut off-cycle corrections by around 70% per period, and spends around 60% less time on pre-close reconciliation with x101. Every close used to begin with days of manual reconciliation across four systems, and the errors that mattered were the ones found afterwards. x101 reads time, leave, benefits and contract data together ahead of each run, raises every exception with the records that produced it, and answers an employee's pay question from the governing policy.
Finance & HR
Last updated: 23 September 2026
The challenge
Payroll is judged on being both fast and exactly right, across a process spanning four systems and rules that vary by country, contract and tenure. Almost all of the effort went into finding the small number of records that were wrong before the run closed, and the ones that slipped through became off-cycle payments.
Reconciliation by hand, every cycle
Matching time, leave, benefits and contract data consumed the days before every close, and the same mismatches recurred each period.
Exceptions chased over email
An anomaly became a thread with a manager or an employee, and the reason it was raised had to be re-explained each time.
Answering a query meant digging
When someone asked why their pay changed, tracing the rule and the data behind it took a specialist and real time.
Corrections after the fact
Errors found after the run became off-cycle payments, which cost more to fix than to prevent and eroded confidence in the function.
Rules that vary by country
Entitlement and deduction logic differed by geography, contract and tenure, and lived partly in documents and partly in people.
Audit preparation as a project
Evidence for a payroll audit was assembled retrospectively from several systems rather than existing already.
What x101 does
x101 sits across the systems that feed payroll rather than replacing any of them. It reconciles the period before the run closes, raises each exception with the records and the rule behind it, completes approved corrections in the system of record, and answers employee pay questions from the governing policy, within that employee's own permissions.
Every source read together
HR records, time and attendance, leave balances, benefits elections and contract terms are read as one picture for the period being run.
Reconciled before close
Mismatches, outliers and missing inputs are raised as exceptions ahead of processing, each carrying the records that produced it.
Every deduction has its clause
Anything unusual on a payslip traces to the governing policy or contract term, quoted with its source, without a specialist in the loop.
Corrections completed, not just flagged
Once approved, the fix is applied in the system of record and confirmed back, so the exception closes where it was raised.
Employees answered directly
Routine pay questions are answered from policy and the employee's own record, within their permissions, in plain language.
The audit pack builds itself
Every check, exception, approval and correction is recorded as it happens, so the evidence exists before it is asked for.
Governance on every record. Each person sees only their own entitlements, every correction carries an approver and a reason, and the full trail is signed and replayable. Payroll data never leaves the customer's perimeter, and no customer data is used to train the underlying models.
The impact
The close stopped being a search. Exceptions surface while there is still time to fix them, corrections happen inside the cycle rather than after it, and the questions that used to reach a specialist are answered at source.
- ~85%
Caught pre-close
Exceptions surfaced while there is still time to correct them.
- ~70%
Fewer off-cycle runs
Errors handled inside the cycle rather than after it.
- ~60%
Less reconciliation time
Returned to the team from repetitive matching work.
- 100%
Deductions traceable
Every one tied to the clause that governs it.
| Dimension | Before | After · with x101 |
|---|---|---|
| Reconciliation | Days of manual matching across four systems each cycle | Reconciled automatically ahead of close, exceptions raised with evidence |
| Exception handling | Email threads, context re-explained each time | Each exception carries the records and the rule that produced it |
| Employee queries | Specialist time to trace a rule and its data | Answered from policy and the employee's own record, in minutes |
| Corrections | Off-cycle payments after the run | Applied in the system of record inside the cycle, under approval |
| Country rules | Split between documents and individual knowledge | Read from the governing documents and applied consistently |
| Audit evidence | Assembled retrospectively from several systems | Recorded as work happens, available on request |
Payroll never had a data problem, it had a timing problem. Everything needed to catch an error existed somewhere before the run closed. Reading it together, ahead of the close, is what turned corrections into exceptions.
Solution summary · x101 payroll operations deployment
The parts of x101 this uses
Nothing here was built for one customer. Each capability below is standard platform behaviour, applied to this problem.
Unify
HR, time, benefits, contract and finance data read as one picture for every run.
Explore UnifyCompany Knowledge
Pay policies, contract terms and local rules become the grounding for every explanation.
Explore Company KnowledgeFrom Answer to Action
An approved correction is applied in the system of record and confirmed back in the same thread.
Explore From Answer to ActionAI Explainability
Every exception and deduction carries the data and the clause behind it.
Explore AI ExplainabilityGoverned by Design
Each person sees only their own entitlements, and every correction carries an approver.
Explore Governed by DesignInstant Analytics
Cost, headcount and variance questions answered from live payroll data.
Explore Instant Analytics
About this case study. The customer's identity is withheld at their request. Improvement figures reflect the target and expected outcomes of the deployment and are indicative; actual results vary with payroll complexity, country coverage and data quality.
Close payroll on evidence, not on nerves.
Reconciliation before the run, exceptions explained in plain language, corrections completed under approval, and the audit trail built as you go.