About

We test the parser before we test the market.

RecoupLedger is built by one person, on the belief that reconciliation software earns trust the same way an auditor does — by being checked, line by line, against the messiest export formats before it’s ever handed to a customer. Every ERP export format has its own quirks. The only way to know the engine handles yours is to have already broken it on one just like it.

How we validate

Before it reaches a supplier statement, it has already failed a few.

01

Formats matched to each ERP

Test packs are built to mirror how Sage, Xero, QuickBooks, NetSuite, SAP, Dynamics and others actually export — and practising bookkeepers, shown one cold, read it as an ordinary supplier statement rather than test data.

02

A sealed answer, worked out by hand

Every file is reconciled by hand first, so there's a known-correct result to check the software against, before it ever runs on something a customer will see.

03

Built to break it

Split columns, merged columns, multi-currency statements, discounts and rounding — the formats most likely to fail quietly are the ones deliberately tested first.

A real example from testing

One of our sealed validation packs hid a real credit note worth £2,001.05 — issued by a supplier, sitting on their statement, never entered into the ledger. Early on, a naive column-mapping approach found £0.00 — it silently dropped the credit rather than flagging it. That failure got fixed, and the fix was re-run against every pack that had already passed, not just the one that failed, before it counted as done.

What hasn’t happened yet is a run against your own live export. No test pack, however faithful, can anticipate every quirk of a real account — which is exactly what a pilot is for. If it finds something the engine missed, that gap gets fixed and re-tested against every pack that already passed, before anyone else’s statement runs through it.

Send us one statement. We’ll show you exactly how it was checked.