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.

Any payroll vendor Any country Nothing to integrate Two checks every cycle

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.

Messy payroll inputs become one clean payroll file Emails, notes, chat messages, PDFs and broken spreadsheets are pulled into a checking engine and printed as a validated payroll register, which is then formatted into separate files for the payroll vendor, the EOR company, the local accountant and internal finance, and sent. The system then verifies that each payroll run matches the register and that everyone was paid, and as a last step the returned deductions and net pay fill into the register. RE: RE: FW: bonus??add 500 for Ana...or was it 550?? Tom OT12h?? askSara? Luis started the 14th,not the 1st!! PDFexpenses_FINAL_v3 (2).pdf date amount03/04/26 1.200,502026-04-03 1,200.50? grosstaxnet184104951,713.4k=SUM(??#REF!! Payroll register Sep 2026 pay cycle EmployeeGrossDeductionsNet pay Ana Reyes4,200.001,134.003,066.00 Tom Becker3,960.001,069.202,890.80 Luis Ortega1,850.00462.501,387.50 Mia Santos5,100.001,428.003,672.00 Jo Whitfield3,300.00858.002,442.00 Total18,410.004,951.7013,458.30 Payroll closed 13,458.30 net pay recorded Payroll vendorvendor_import_0926.csv EMP_ID;PAY_CODE;AMOUNT1001;BASE;4200.00 Payslips match register2 of 2Paid out6,738.00 Verified EOR companyeor_variable_pay_0926.xlsx Worker Item AmountL. Ortega Pro-rata 1,850.00 Payslip matches register1 of 1Paid out1,387.50 Verified Local accountantpayroll_changes_0926.xlsx Overtime T. Becker 12 hBase pay J. Whitfield 3,300.00 Payslips match register2 of 2Paid out5,332.80 Verified Internal financegl_accrual_0926.csv 6000 Salaries 18,410.002300 Payroll accrual 18,410.00 Bank debits13,458.30Difference to register0.00 Verified

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.

korrigoOperational intelligence simon@korrigo.io Ready

Consolidate Payroll Inputs

Upload multiple payroll input files to normalise, match and consolidate into one clean dataset.

Vendor files 5

FileVendorPayslipsPays viaStatus
CSVPH_register_0926.csvManila bureau412PESONetNormalised
XLSXES_nomina_0926.xlsxIberia bureau268pain.001Normalised
CSVDE_lohn_0926.csvGerman provider351pain.001Normalised
XLSXMX_nomina_0926.xlsxLatAm EOR307SPEINormalised
CSVUS_register_0926.csvUS processor609NACHAReading
Five file shapes, one column set

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

CheckScopeFoundResult
Duplicate bank accountsAll countries0Pass
Leavers flagged in the inputAll countries0Pass
Net pay outside toleranceGermany, Spain3Review
Ghost employeesAll countries0Pass
Bank details changed this monthGermany2Review
Gross to net recalculation1,947 payslips0Pass

5 exceptions to review

Nothing is blocked. You decide what goes back to the vendor.

Same checks, every country, every run

Reconciliation & Discrepancies

Review and resolve discrepancies from vendor reconciliations.

Instructed against paid 5

CountryRailPayslipsInstructedPaidVarianceResult
United StatesNACHA6093,775,8003,775,8000Matched
Germanypain.0013511,632,1501,632,1500Matched
Spainpain.001268948,720948,580140Variance
MexicoSPEI307279,370279,3700Matched
PhilippinesPESONet412255,440255,4400Matched
Total, EUR eq1,9476,891,4806,891,340140

Vendor query Drafted for the Iberia bureau, evidenced and logged.

September instructed EUR 948,720 for 268 payslips, your confirmation shows EUR 948,580. The EUR 140 sits on E‑2118, a mid month leaver. Please confirm and advise on recovery.

Send with evidence Assign an owner

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!

No spam, no sales calls. Product updates and a note the day we go live.

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.