Stop double-paying suppliers: matching bills to bank payments
On this page
- 1.How to know who you owe and when it's due
- 2.How to track business expenses (the no-shoebox method)
- 3.Snap a receipt, done: how receipt scanning should work
- 4.Stop double-paying suppliers: matching bills to bank payments
Paying the same invoice twice is embarrassing and avoidable. Here's how matching bills to bank payments works — automatically — so every bill is marked paid the moment the money leaves, and nothing's ever paid twice.
The pain: paying the same invoice twice
A supplier sends a polite reminder: "Just following up on invoice 2041." You don't remember paying it, you can't quickly tell, and you don't want to annoy a good supplier — so you pay it. A week later you discover you'd already paid it the first time. Now you're £600 out, chasing a refund, feeling daft.
Or the reverse: you did pay it, the supplier's reminder was a crossed wire, and you spend twenty minutes proving you already paid — digging through bank statements to find the transaction that matches the invoice.
Both are the same problem wearing two faces. Your list of bills and your bank account don't talk to each other. The bill says "unpaid" because nobody marked it paid. The payment sits in your bank with no label saying which bill it settled. So you can never be sure, at a glance, whether a given invoice has actually been paid.
That uncertainty is where double-payments live. The fix is matching bills to payments — joining each invoice to the exact bank payment that settled it — so "is this paid?" always has a one-second answer. Here's why it's so fiddly by hand, and how it should just happen.
The hard way today: cross-checking two lists by eye
Matching bills to payments manually means holding two separate lists side by side and pairing them up — and it's exactly as error-prone as it sounds.
The bank-statement squint. You've got a folder of invoices and a bank statement. You scroll the statement looking for a £600 payment around the right date, to roughly the right name, and decide "that's probably invoice 2041." Supplier names on bank statements are rarely the names on the invoice, amounts get rounded or combined, and one supplier might have three payments out. You're guessing, and you mark it paid on a hunch.
The spreadsheet tick-off. You keep a bills tab and tick each one as paid when you remember to. But if you pay something and forget to tick it, the sheet still says "unpaid" — and that's the exact gap a double-payment falls through. The sheet's only as truthful as your last update.
The Xero "find & match". Properly built for this — you match each bank line to its bill. Much better than a squint. But it's still you doing the matching, one transaction at a time, and anything you don't get round to matching leaves a bill looking unpaid and a payment looking unexplained. The tool helps; the work and the judgement are still yours, and a missed match still risks a second payment.
The root issue across all three: the matching depends on you doing it, promptly and correctly, every time. Miss one, and the bill and the payment drift apart — and that's when you pay twice or chase something that's settled.
How it's automatic in Ledgers: every payment finds its bill
Ledgers does the matching itself, continuously, so your bills and your bank are always in agreement without you pairing anything by eye.
Here's what happens.
Bills live as structured records. Every bill — captured from a forwarded or snapped invoice via receipt OCR (software reading the document) — sits in your payables list with its supplier, amount and due date. That's the thing a payment can be matched to. (See how to know who you owe and when it's due for the bills view itself.)
The bank feed brings payments in automatically. Via your connected bank feed, every payment that leaves your account flows into Ledgers as it happens — no statement exports, no manual entry.
It auto-matches each payment to its bill. As a payment arrives, Ledgers matches it to the open bill it settles — reading the amount, the supplier, the timing and the pattern, not just a name that has to be identical. When it finds the match, it marks the bill paid by itself. The bill leaves the "owed" list and joins the payment, joined up and done.
It flags — it doesn't guess wildly. When a payment doesn't clearly belong to a bill (a part-payment, an unexpected amount, a supplier with several open bills), Ledgers doesn't force a bad match. It puts that one item in a short review queue (the Exception Inbox) and asks you to confirm which bill it goes with. You decide the genuinely ambiguous handful; the software handles the clear majority.
Nothing gets buried. The ledger is event-sourced — every match recorded, nothing overwritten — so you can always see which payment settled which bill, and when. If a supplier ever queries it, the answer is right there.
What you'd see and do
The double-payment scenario simply stops happening. When that "following up on invoice 2041" email lands, you open Ledgers and the bill clearly shows as paid, with the exact bank payment that settled it attached. One look, honest answer, no second payment, no twenty-minute statement hunt.
Day to day, you're not matching anything by eye. Bills you owe sit in the payables list; the moment you pay one, the bank feed matches the payment and the bill flips to paid on its own. Your "what's still owed" list is therefore always true — what's showing as unpaid genuinely is unpaid, so you can pay it without second-guessing.
The only thing left for you is the short queue of payments the software couldn't confidently match — a part-payment here, an odd amount there. You confirm those in a moment, and they're done too.
That's the end of double-paying. Not "be more careful." Just: every payment finds its bill automatically, every bill tells you the truth about whether it's settled, and the few uncertain cases come to you instead of slipping through.
Ready to never pay an invoice twice? In Ledgers, every bank payment is matched to its bill automatically and the bill is marked paid the moment the money leaves — so you always know what's settled, without cross-checking by eye. See your numbers without learning accounting → start free.
Want the full payables picture first? How to know who you owe and when it's due →
New to the idea of matching records against the bank? What is reconciliation in accounting? →
Frequently asked questions
How do I match bills to payments?
You link each supplier bill to the exact bank payment that settled it, so the bill is marked paid and the payment is explained. Doing this by hand means cross-checking your bills against your bank statement; software can match them automatically by reading the amount, supplier and timing, and flag only the unclear ones.
How do I stop double-paying suppliers?
The reliable fix is having every bill marked paid the moment the matching payment leaves your bank, so you can always see at a glance whether an invoice is settled. In Ledgers, payments auto-match to bills, so a "have I paid this?" question has an instant, accurate answer — and there's no gap for a second payment to fall through.
Why doesn't my supplier's name match my bank statement?
Bank statements often show a payment processor, a trading name, or an abbreviation rather than the name on the invoice — which is exactly why manual matching is error-prone. Good matching software reads the amount, timing and pattern too, so it pairs the payment with the right bill even when the names don't line up.
What happens if a payment doesn't clearly match a bill?
It shouldn't be force-matched. In Ledgers, an unclear payment — a part-payment or an odd amount — goes to a short review queue for you to confirm which bill it belongs to, so the software handles the obvious matches and you only judge the genuinely ambiguous few.
See your numbers without learning accounting
Ledgers does the bookkeeping — bank feeds, VAT, year-end — and keeps your accountant in the loop. Free for pre-revenue founders.
Start free →Get the next guide by email
Plain-English accounting for founders — a couple of new guides a week. No spam, unsubscribe anytime.
Keep reading · Spending / bills / receipts
How to know who you owe and when it's due
Not knowing what bills are coming is how cash flow surprises you. Here's how accounts payable should work — every bill captured, every due date visible, matched to your bank — so you always know who you owe and when.
4 min readSpending / bills / receiptsHow to track business expenses (the no-shoebox method)
The shoebox of crumpled receipts is where tax savings go to die. Here's how to track business expenses the easy way — snap a receipt, get a draft, done — so nothing's lost and your numbers stay current.
4 min readSpending / bills / receiptsSnap a receipt, done: how receipt scanning should work
Most receipt scanner apps just store a photo — you still type everything in. Here's how scanning should work: snap the receipt, get a finished draft expense, matched to your bank. Done.
4 min read