Payroll validation and reconciliation
Payroll decisions get made. Then they get lost.
Your payroll system has no idea.
A raise agreed on a call. A leaver named in a chat message that nobody turned into a file. None of it reaches the file your vendor actually runs. Korrigo reads every file you already send them, and checks it twice before the money leaves.
Nine systems that never spoke.
This is one monthly payroll run across 5 countries, as it exists today. Nothing here is connected to anything else, and all of it has to agree.
The teams that lose the most are the careful ones. The problem is not attention, it is structure.
Korrigo reads all of it. The files, the invoices and the payment confirmations, in whatever shape they arrive. Then it checks them against each other before you pay.
19 interviews. 20 countries. The same story every time.
The errors are already happening. Most just have not been found yet.
- 6 days every cycle, spent checking that what should have happened actually happened
- €83K median annual cost of payroll errors that were found and quantified
- 4 to 8 material errors a year in a multi vendor payroll operation
- 7 months average time before a ghost employee or a silent overpayment surfaces
-
Everyone ends up back on the dreaded master spreadsheet, no matter how sophisticated the set-up looks on paper.
Payroll director, mid market · 180 employees · 5 countries
-
A salary change runs in one region but not another. No red flag, because the number stays the same. Nobody catches it until audit.
Head of global payroll, pharma · 2,500 employees · 12 countries
-
EUR 77,000 lost to a ghost employee over seven months. Every individual check passed. The error had no signal.
Financial controller · 1,000+ employees · 15 countries
What a month actually looks like
The mess goes in. One register comes out.
Emails, a sticky note, a PDF and a spreadsheet nobody can open. Korrigo reads all of it and prints one register. Check 1 runs before the register is cut into the file each vendor expects. Check 2 runs on what comes back, against what you instructed, before the money leaves.
One entity, shown in full. The September run covers 1,947 payslips across five of them.
See it work
From 5 vendor files to one clean payroll run.
Consolidate Payroll Inputs
Upload multiple payroll input files to normalise, match and consolidate into one clean dataset.
Vendor files 5
| File | Vendor | Payslips | Pays via | Status |
|---|---|---|---|---|
| CSVPH_register_0926.csv | Manila bureau | 412 | PESONet | Normalised |
| XLSXES_nomina_0926.xlsx | Iberia bureau | 268 | pain.001 | Normalised |
| CSVDE_lohn_0926.csv | German provider | 351 | pain.001 | Normalised |
| XLSXMX_nomina_0926.xlsx | LatAm EOR | 307 | SPEI | Normalised |
| CSVUS_register_0926.csv | US processor | 609 | NACHA | Reading |
Column mapping 18
- Mitarbeiter-Nremployee_id
- Bruttolohngross_pay
- Sueldo brutogross_pay
- CLABEbank_account
- Basic Paygross_pay
- Routing / Accountbank_account
- Steuerklassetax_code
- Cost Centrecost_centre
10 more matched by the column agent. You confirm once, then it holds.
Pre-Payroll Validation
Review and clear every exception before the run is cut into vendor files.
Checks run 42
| Check | Scope | Found | Result |
|---|---|---|---|
| Duplicate bank accounts | All countries | 0 | Pass |
| Leavers flagged in the input | All countries | 0 | Pass |
| Net pay outside tolerance | Germany, Spain | 3 | Review |
| Ghost employees | All countries | 0 | Pass |
| Bank details changed this month | Germany | 2 | Review |
| Gross to net recalculation | 1,947 payslips | 0 | Pass |
Reconciliation & Discrepancies
Review and resolve discrepancies from vendor reconciliations.
Instructed against paid 5
| Country | Rail | Payslips | Instructed | Paid | Variance | Result |
|---|---|---|---|---|---|---|
| United States | NACHA | 609 | 3,775,800 | 3,775,800 | 0 | Matched |
| Germany | pain.001 | 351 | 1,632,150 | 1,632,150 | 0 | Matched |
| Spain | pain.001 | 268 | 948,720 | 948,580 | 140 | Variance |
| Mexico | SPEI | 307 | 279,370 | 279,370 | 0 | Matched |
| Philippines | PESONet | 412 | 255,440 | 255,440 | 0 | Matched |
| Total, EUR eq | 1,947 | 6,891,480 | 6,891,340 | 140 |
Step 1 of 3
Every vendor file is read and mapped to one column set, whatever shape it arrived in.
Included
What comes after the two checks.
-
Consolidated general ledger
A GL file and the records under it, broken down by cost centre.
-
Month on month variance
Drift and salary changes with no approved instruction, before cut-off.
-
Immutable audit log
Every upload, decision and vendor confirmation, timestamped and attributed.
Coming soon
Reading alongside the channels
Changes agreed in a thread or on a call, held against the files. Korrigo reads no inbox and no channel today.
No templates. No setup.
The engine was trained on thousands of real payroll runs, so it works out what a column means instead of being told. Try it.
Whatever your provider calls it, in whatever language.
Matched against a sample of the mapping table. The engine reads the values under the header as well, which is how it resolves the ones a header alone cannot.
No install, no IT ticket. The file you already send your vendor is the whole setup.
How your payroll data is handled.
Payroll files are the most sensitive data a company holds, so the answer to every question below is the same one: Korrigo holds less of it than you expect.
- Nothing to connect Korrigo works on files. It never touches your bank or your payroll systems, so there is no credential to hand over. File based
- Encrypted throughout Files are encrypted on the way in, in storage and on the way back out. In transit and at rest
- Access you control You decide who on your team sees which countries, and every action is logged. Per country
- Kept only as long as you want You set how long files are held, and we delete them when that time is up. Your retention rule
Before you ask
Four things Korrigo is not.
- A payroll processor Your vendors still run payroll, and we never touch the money.
- A post-close tool We work before the run, not after it.
- An integration project Korrigo works on files. Nothing to connect, nothing for IT to schedule.
- A vendor replacement Keep every provider you have, including the ones you are stuck with.
Join the waitlist. We will tell you if Korrigo is wrong for your run.
Leave your email and we will be in touch within 24 hours, with product updates and a note the day we go live.
Coming soon
The waitlist is not open yet. We'll be with you soon!
Or write to hello@korrigo.io.
- Nothing to installSend the file you already send your vendor.
- Your data stays in the EUEncrypted at rest and in transit, deleted on request.
- No sales callsProduct updates, and a note the day we go live.
Korrigo