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 real files 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.
Statements and ledgers pulled from live Sage 50, Xero, QuickBooks, NetSuite, SAP and other ERP accounts — not synthetic test fixtures built to make the parser look good.
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.
Split columns, merged columns, multi-currency statements, discounts and rounding — the formats most likely to fail quietly are the ones deliberately tested first.
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.
That work is never finished — every ERP adds new export quirks over time, and each one gets tested the same way before it’s trusted. If a pilot ever finds something the engine missed, that gap gets fixed and re-tested before anyone else’s statement runs through it.