Use cases / Payment reconciliation
Use case
Payment reconciliation software — and the money that won't match.
Your accounting package already matches the easy lines. The rest — the lump-sum payout, the payment that covers fourteen invoices, the remittance email nobody opens — is where the month-end goes. Here's a fair look at the tools, and what a matcher that acts on what it finds looks like.
The real options.
Payment reconciliation software matches money arriving in your accounts to the invoices and records it belongs to, so the books show what's actually been paid. For matching a bank feed line to an invoice, you almost certainly already own the answer.
Built into what you already pay for
| Tool | Known for | Typically best for |
|---|---|---|
| Xero | Suggested matches of bank-feed lines to invoices and bills; automatic reconciliation rolling out | Anyone on Xero — included |
| QuickBooks | Bank-feed review with suggested matches; marks the invoice paid | Anyone on QuickBooks — included |
| Sage Accounting | Match suggestions plus bank rules that auto-create transactions | Sage users |
| FreeAgent | Bank feeds with smart categorisation; free with some business bank accounts | Freelancers & micro-businesses |
For the money the bank feed can't explain
| Tool | Known for | Typically best for |
|---|---|---|
| A2X | Turns marketplace payouts into clean summaries that match the bank deposit | Amazon/Shopify/eBay sellers |
| Link My Books | UK-founded payout breakdowns with the VAT handled properly | UK marketplace sellers |
| Synder | Multi-channel payment sync with payout-based reconciliation | Sellers mixing Stripe, PayPal and marketplaces |
| RemitClear | Reads remittance-advice PDFs and applies one payment across many invoices | UK B2B firms drowning in remittances |
A snapshot, not a ranking — features and pricing change, so check current specs. Two notes: free connectors exist that match Stripe and GoCardless payments into Xero or QuickBooks, so wire those in before buying anything. And if one of these covers your gap — payouts, or remittances — buy it; we'd tell you which. (Month-end-close platforms for standalone finance teams — BlackLine, Trintech's Adra, FloQast, HighRadius — are a different aisle, priced and built for much bigger firms.) This page is for the firm whose money arrives through five doors and whose matching has to do something once it's made.
Where the matching tools stop.
Each tool matches well inside its own patch. The wall is the shape of your money, not the quality of any one matcher:
- One line, one document. Built-ins match a bank line to an invoice. One customer payment covering fourteen invoices means someone ticking boxes by hand — and no built-in reads the remittance email that explains which fourteen.
- Money through five doors. Bank transfer, Stripe, GoCardless, the card terminal, the marketplace — each payout lands as a lump sum net of fees that equals no invoice, and each needs its own connector, priced per channel per month. The subscription stack grows with every door.
- The exceptions pile up unowned. Whatever doesn't auto-match falls into a queue someone works through at month-end — the payment with the mistyped reference, the overpayment, the part-payment — weeks after the customer thought they'd paid.
- The match doesn't act. Marking an invoice paid in the ledger doesn't stop the reminder that's about to go out, release the held order, or update the job — the systems that need to know find out later, from a person.
The cost of standing still
Unmatched money is your cash position.
Reconciliation reads as housekeeping until you ask what it actually protects — knowing what you're owed, what you've been paid, and what HMRC sees when it looks:
When the ONS asked UK businesses in late December 2025 how long their cash reserves would last, roughly one in seven trading businesses said they had none — and one in five couldn't say. A firm whose money-in isn't reconciled is in that last group whether it admits it or not: the true cash position is a guess. (ONS BICS, Dec 2025) (dataset)
HMRC's June 2026 figures put the 2024–25 tax gap at £59.2 billion — and HMRC's own illustrative estimate attributes over half of it to failure to take reasonable care (35%) and error (16%), with small businesses accounting for 62% of the gap overall. HMRC doesn't name reconciliation — but books that don't match the money are exactly where carelessness and error live. (HMRC, 2026) (behaviour estimates)
Payments going to the wrong details is a real enough problem that the industry now name-checks payees before money moves: more than 300 firms run Confirmation of Payee, with over 2.5 billion checks completed since 2020 — coverage now spanning more than 99% of Faster Payments and CHAPS transactions. The money arriving at your account has no such safeguard — it lands with whatever reference the customer mistyped, and matching it is your problem. (PSR, 2024)
What we'd build instead.
One matching engine for every door your money comes through, built into the system that runs the work. Shaped to your firm, live in weeks, yours to own:
Every door, one matcher
Bank feed, Stripe, GoCardless, terminal, marketplace payouts — money-in from everywhere lands in one engine that knows your invoices, your fees and your references, instead of five connectors that each know a fifth of the story.
The remittance email, read and proven
The "we've paid these fourteen invoices" PDF would be read by AI and verified with deterministic checks — each line traced to its invoice, the total re-added, the lump sum applied across all fourteen — with a person seeing only the line that fails.
Overnight, not month-end
Matching runs nightly, so the morning list is short and every item on it is a real question — the mistyped reference, the overpayment — each with an owner, not a shoebox to empty in week four.
The match that acts
A matched payment stops the chasing the same minute, releases the held order, updates the job — because the matcher lives inside your operating system, not beside it in another tab.
Every one is a capability we can build now with AI-assisted development — not a promise your firm needs all of it. We start with the door that loses you the most time.
Where we've done it
We reconcile with arithmetic, not optimism.
This discipline runs in production: the operating platform we built for a UK firm reads bank statements with AI, verifies every line with deterministic checks, and reconciles the stuck payments overnight — people see only what doesn't balance, with the evidence attached.
Fair questions
What firms ask us about reconciliation.
What is payment reconciliation software?
Software that matches money arriving in your accounts — bank transfers, card payouts, direct debits — to the invoices and records it belongs to, so your books show what has actually been paid. The simple version ships inside your accounting package; the hard cases are lump-sum payouts, one payment covering many invoices, and payments that arrive with a mistyped reference.
Doesn't Xero already reconcile my bank?
The bank feed, yes — and its suggested matching is genuinely good, so use it. The gaps sit around it: a Stripe or marketplace payout lands as one lump sum net of fees that equals no invoice; one customer payment covering fourteen invoices means matching by hand; and no built-in reads the remittance email that explains it. That's the part worth building properly.
Can ChatGPT do bank reconciliation?
Not on its own — and it shouldn't. A language model reads documents well, but its output is probabilistic, and money needs proof. The right pattern is the one we build with: AI reads the document, then deterministic checks verify every figure against your records — the sums re-added, each payment traced to its invoice. A person sees only what fails a check. Reading by AI; verification by arithmetic.
What's the best reconciliation software for a small UK firm?
Start with what you own: Xero, QuickBooks, Sage and FreeAgent all include bank-feed matching. Selling through marketplaces or Stripe, add a payout tool like A2X or Link My Books. Drowning in remittance advices, a point tool like RemitClear reads them. If one of those covers your gap, buy it. Custom earns its keep when the matching has to live inside the system that runs the work — and act on what it finds.
How much does custom payment reconciliation cost?
It's a monthly retainer, not a big up-front project — tiers from £2,500 to £6,500 a month, with a free process audit first and an optional fixed-price discovery sprint credited against month one. You own the code and the data from day one.
Where this goes next
- For wholesale & distribution → — reconciliation that doesn't wait for month-end, on a distributor's order flow.
- Invoice chasing that runs itself → — the chasing your matcher should be switching off.
- Document & invoice intake → — the same read-then-verify discipline, pointed at paperwork.
- The 20-question self-audit → — ranks which of your processes could run themselves. Free, two minutes, no email.
Start here
Bring us your unmatched list.
A free process audit is thirty minutes. Show us the payments that didn't match this month — where they came from and who untangles them — and you'll leave with a written map of how the matching could run without you, whether or not we ever work together.
No pitch deck, no obligation. The map is yours either way.