How do I handle supplier refunds on bank statements?

Supplier refunds appear as incoming credits on your bank statement but don't correspond to any sales invoice. They're usually easy to spot — the payee name matches a known supplier, but the transaction is a credit rather than a debit. In your accounting software, create a credit note against the original supplier and match the bank entry to that credit note, not to an invoice. If the refund relates to a specific purchase invoice that was already paid, you may need to reverse the original payment and re-allocate. For partial refunds (e.g., you returned one item from a multi-item order), match the refund to a credit note for the returned portion while leaving the original invoice intact for the items you kept. Always keep the supplier's refund confirmation email as supporting documentation.

Can I automate matching bank transactions to invoices entirely?

Not entirely — but you can get very close. Bank rules handle recurring transactions automatically. Open Banking feeds eliminate the data-entry step by pulling transactions directly. Many accounting platforms now use AI to suggest matches based on amount, date, and payee patterns. The remaining manual work is the 'judgement layer': transactions where amounts don't quite match (bank fees added, currency rounding), payments from unfamiliar payees, and batch payments covering multiple invoices. The goal isn't zero-touch reconciliation — it's reducing the manual work to the 10-20% of transactions that genuinely need human judgement. For the rest, the combination of clean bank statement data (via a converter like BankScan AI), well-configured bank rules, and software auto-matching will handle most of the heavy lifting.

How to Match Bank Statement Transactions to Invoices

Q: How do I match bank statement transactions to invoices manually?

Start by downloading your bank statement as a clean spreadsheet (CSV or Excel) and your invoice list from your accounting software. Sort both by date. Match transactions using: (1) exact amounts — the same figure on both sides is your first clue; (2) reference numbers — many businesses include the invoice number in the payment reference field; (3) date proximity — payments typically clear 2-5 working days after the invoice date; (4) payee name — the customer or supplier name on the bank statement should match your accounting records. For anything that still doesn't match, check for partial payments (multiple small payments against one invoice), batch payments (one payment covering several invoices), and bank fees that look like supplier payments. Mark each match as you go to track what's left unreconciled.

Q: What do I do when a payment doesn't match any invoice?

Unmatched payments fall into four common categories: (1) Direct debits and standing orders — these rarely have invoice numbers in the reference field; check the payee name against your supplier list for recurring payments like rent, utilities, and subscriptions. (2) Bank fees and charges — many bank statements list these in the same format as regular transactions, especially for business accounts. (3) Supplier refunds and chargebacks — these credit your account but won't match an outgoing invoice; look for the original supplier name. (4) Genuinely unmatched — if a payment has no identifiable payee and doesn't match any known amount, flag it for follow-up. It could be an error, a forgotten payment, or in rare cases, fraud. Create a suspense account entry and investigate.

Q: How do I handle partial payments against invoices?

Partial payments — where a customer pays part of an invoice, often because they're disputing a line item or spreading the cost — are one of the most common reconciliation headaches. In Xero, you can apply a partial payment to an invoice by selecting 'Add Payment' and entering the amount received rather than the full invoice total; the invoice remains open for the balance. In QuickBooks, use 'Receive Payment' and enter the partial amount. Always record the payment reference from the bank statement in the payment notes so you can trace it later. For the remaining balance, set a reminder or note on the invoice so it doesn't get forgotten. If partial payments are a pattern with a particular customer, consider breaking future invoices into milestone-based billing.

Q: Why do my bank feed transactions not match in Xero?

Bank feeds in Xero fail to auto-match for three main reasons: (1) Amount mismatch — the bank transaction amount differs from the invoice or bill total, even by a few pence, usually due to bank charges, currency conversion differences, or disputed line items. (2) Date gap — Xero's matching rules look within a specific date window; if the payment cleared outside that window (common with international transfers), it won't auto-suggest. (3) Reference mismatch — if the payment reference on the bank statement doesn't contain the invoice number or supplier name exactly as it appears in Xero, the matching algorithm skips it. The fix: manually search by amount, expand the date range in Reconcile view, or create a bank rule that maps common reference patterns to the right contacts.

Q: How can I speed up matching bank transactions to invoices?

The single biggest time-saver is starting with clean data. If your bank statement is in a structured spreadsheet (not a PDF you're squinting at), you can sort, filter, and pivot by amount, date, and payee. Beyond that: (1) Create bank rules in your accounting software for recurring transactions (rent, utilities, software subscriptions, payroll) so they auto-match every month. (2) Ask clients and suppliers to always include the invoice number in the payment reference — it's a small ask that transforms your reconciliation speed. (3) Use a bank statement converter like BankScan AI to turn PDF statements into clean, sortable spreadsheets in seconds, eliminating the data-entry bottleneck. (4) Batch similar transactions — process all direct debits first, then all card payments, then all transfers; different payment types have different matching patterns.

Q: What are bank rules and how do they help with reconciliation?

Bank rules are automated matching rules you set up in accounting software (Xero, QuickBooks, FreeAgent, Sage) that tell the system: 'Whenever you see a transaction with these characteristics, automatically match it to this contact or account.' For example, a rule might say: 'If the payee contains Gocardless, the amount is under £500, and the transaction type is Direct Debit, match it to the Client Payments clearing account.' Rules work best for recurring transactions with consistent descriptions — standing orders, direct debits, subscription payments, and regular supplier payments. Spend 20 minutes setting up rules for your 10-15 most frequent transaction types and you'll cut your reconciliation time by 30-50% every month.

You've just finished month-end. The bank statements are in. The invoices are in. And nothing — absolutely nothing — lines up.

There's a payment from "SMITH REF 88472" for £2,450. You have three open invoices for John Smith: one for £2,450, one for £2,200, and one for £980. Which one is it? The reference doesn't match any of your invoice numbers. The date is six days after the last invoice. And you've got another 140 transactions to go before you can close the month.

If this is your Tuesday night — or your Wednesday night, or the night before the VAT deadline — you're in the right place. Matching bank statement transactions to invoices is, pound for pound, the most tedious, time-consuming, and error-prone step in the entire bookkeeping cycle. It's also the one where mistakes cost real money: missed payments, double-counted income, and unreconciled differences that snowball into painful HMRC conversations.

This guide covers every technique — from the manual detective work to the automated approach that experienced UK bookkeepers use to cut reconciliation time by 80%. Whether you're in Xero, QuickBooks, Sage, FreeAgent, or working from spreadsheets, the principles are the same.

Why Transaction Matching Goes Wrong (Before You Even Start)

Most matching problems aren't about skill — they're about the data coming in broken. Here are the four ways your bank statement data is already fighting you before you open your first invoice:

1. The Reference Number Black Hole

Your client sends a payment with the reference "INV-2026-0147." Beautiful. Clear. Matches perfectly. But your other client types "payment" as the reference. And your supplier? Their standing order reference is "DD/REF/88271/XQ9" — which means absolutely nothing to anyone except their own internal system. Payment references are the single most unreliable matching field, and yet they're the first thing most bookkeepers reach for. When references fail, you need a system that works without them.

2. The Amount That's Close But Not Right

Invoice says £1,200. Bank statement says £1,192.50. That £7.50 difference — it's a bank transfer fee, a currency conversion rounding, or a PayPal processing charge. Close enough that your brain wants to match it, but different enough that your accounting software refuses. These near-misses accumulate, and by month-end you've got 15 transactions sitting in the "unmatched" column, each one requiring manual investigation.

3. The Batch Payment Puzzle

A single bank credit for £7,840 arrives from a client. It's not a single invoice — it's three invoices (£3,200 + £2,400 + £2,240) paid in one lump. There's no note, no breakdown, no indication of how it should be split. If you reconcile it against one invoice, the other two stay open forever. If you don't spot the pattern, you chase the client for money they've already paid.

4. The PDF Prison

Your client sends their bank statements as PDFs — and they're not even digital PDFs, they're photos of paper statements taken on a phone. Before you can match anything, you have to read the data. That means either squinting at 90 pages of PDF and manually typing transaction amounts into your reconciliation spreadsheet, or pasting it into Excel and spending 40 minutes cleaning up the inevitable formatting disaster. Neither is billable work.

🔴 Red Flags

Unknown payee names. Amounts that don't match any invoice total. Batch payments with no breakdown. Transactions from 3 months ago that nobody investigated.

🟠 Amber Warnings

Amount is close but not exact. Reference hints at an invoice number but doesn't match. Date is outside expected range. Payee is a trading name, not the legal entity.

🟢 Clean Match

Amount, date, payee, and reference all align. One bank transaction = one invoice. Auto-suggested by your software. Reconciled in 5 seconds.

Here's the thing most guides won't tell you: the quality of your bank statement data determines 80% of your matching speed. If your bank data is clean, structured, and in a sortable format, matching is systematic. If it's a mangled PDF paste, every transaction is a puzzle. Start with the data, and the matching follows.

The Step-by-Step Matching Process (That Actually Works)

Here's the workflow that experienced UK bookkeepers use — not the textbook version, but the one that gets you home before 11pm:

Step 1: Get Clean Data First

Before you match a single transaction, make sure both sides of the equation are in a usable format. Your bank statement should be in a spreadsheet — clean columns for date, description/payee, money in, money out, and balance. Your invoice list should be exported from your accounting software with columns for invoice number, customer/supplier name, date, amount, and status. If either side is still in PDF format, convert it first. BankScan AI converts UK bank statement PDFs to clean Excel or CSV in seconds, covering 16+ UK bank formats including the tricky ones that paste as gibberish (HSBC, Barclays, Lloyds).

Step 2: Sort Everything by Amount

Most bookkeepers sort by date first. Don't. Sort by amount. Unique amounts — unusual figures like £847.32 — will match instantly because there's only one possible invoice they could be. Common amounts like £100 or £250 will need secondary checks, but you've cleared the easy wins in minutes. Sort your bank transactions descending by amount and your invoices descending by amount. Walk down both lists simultaneously. You'll clear 30-40% of your matches in under 10 minutes.

Step 3: Use Reference Numbers (But Don't Trust Them Blindly)

For the remaining transactions, check the payment reference field. Some clients and suppliers are meticulous about including invoice numbers; others type whatever their banking app auto-fills. When references match your invoice numbers, you can reconcile with confidence. When they don't — or there's no reference at all — move on. Don't spend 15 minutes trying to decode a cryptic reference. Come back to it after you've cleared everything that does match.

Step 4: Match by Payee and Date Proximity

Now filter your unmatched transactions by payee name. Group all payments from "ACME Ltd" together and compare them against all open invoices for ACME Ltd. Payments typically clear 2-5 working days after the invoice date for UK bank transfers, or 7-10 days for international payments. If you have three ACME invoices for £500, £750, and £1,200 and three ACME payments for the same amounts within the date window, you've found your matches — even if the references are gibberish.

Step 5: Investigate the Remainder

At this point, you should have matched 70-85% of your transactions. What's left falls into predictable categories:

Direct debits and standing orders — match by payee name and fixed amount pattern. These rarely have invoice numbers.
Bank fees and charges — account maintenance fees, overdraft charges, returned payment fees. Match to a bank charges nominal code, not an invoice.
Partial payments — a single invoice paid in instalments. Check if two or more smaller payments add up to an invoice total.
Batch payments — one large payment covering multiple invoices. Check if one large credit equals the sum of several open invoices for the same customer.
Supplier refunds and chargebacks — credits from suppliers that don't match any outgoing invoice. Match to credit notes, not invoices.
Genuinely unidentified — flag these for client follow-up. Create a suspense entry rather than guessing.

💡 Pro tip: Keep a running "unmatched log" spreadsheet. Every time you can't match a transaction, add it to the log with the date, amount, payee, and reference. Review the log weekly with your client. Most unmatched items resolve within a week — they're payments that hadn't cleared yet, or invoices the client hadn't sent you. The log stops problems from accumulating month after month.

How to Handle the Tricky Cases

Partial Payments

A customer owes £3,000. They pay £1,500 now and promise the rest next month. This is incredibly common — especially with contractors, freelancers, and small businesses managing cash flow — and it breaks the one-to-one matching assumption that most reconciliation processes are built on.

In practice: record the £1,500 payment against the invoice in your accounting software. Most platforms (Xero, QuickBooks, Sage, FreeAgent) let you apply a partial payment — the invoice remains open with a balance of £1,500. Always note the payment reference in the payment record. Most importantly: set a follow-up task. The remaining £1,500 will be forgotten by next month unless you have a system to track it. If partial payments are routine for a particular client, consider restructuring their billing into milestone payments or smaller, more frequent invoices so each one can be paid in full.

Batch Payments (One Payment, Multiple Invoices)

This is the one that makes bookkeepers groan at their screen. A single bank credit for £12,500 arrives from "BuildCo Ltd" with the reference "Q2 INVOICES." You open BuildCo's account and find five open invoices: £3,800, £4,200, £2,100, £1,600, and £800. That's £12,500 total. Bingo — but your software doesn't know that.

The fix: in Xero, you can split a bank transaction line into multiple allocations during reconciliation. In QuickBooks, use "Find Match" and select multiple invoices before confirming. In Sage and FreeAgent, you'll need to record the payment as a lump sum on account and then allocate it to individual invoices. The key is doing the maths before you start allocating — check which combination of open invoices adds up to the payment amount. If no combination works, the payment may include an invoice you haven't received yet, or it may include VAT that wasn't on the original invoices. Ask the client for a remittance advice.

Supplier Refunds and Chargebacks

You paid a supplier £850 last month for goods. This month, £200 appears in your bank account from the same supplier. It's a refund for returned items — but your accounting software sees a credit with no matching invoice (because you don't issue invoices to your suppliers).

Match the refund to a credit note, not a bill. Create a credit note for £200 against the supplier's account, then match the bank credit to that credit note. If the original £850 bill has already been paid, you may need to reverse the payment for the refunded portion. For partial refunds where you kept some items and returned others, leave the original bill intact and create a separate credit note for the returned value. Keep the supplier's refund confirmation on file — HMRC may want to see it during an audit.

Bank Fees Masquerading as Supplier Payments

Many UK business bank statements list fees in the same transaction feed as regular debits. An "Account Fee" for £6.50 looks just like a supplier payment when you're scanning down the list. Code bank fees to a dedicated nominal account — "Bank Charges" or "Bank Fees" — not to a supplier. If you use bank rules, create a rule that catches common fee descriptions ("Account Fee," "Service Charge," "Transaction Fee") and auto-codes them. This alone saves 5-10 minutes per month-end.

Software-Specific Matching Tips

Software	Best Matching Feature	Common Pitfall	Quick Fix
Xero	Auto-suggest matches by amount + date + contact	Ignores transactions outside a 14-day date window	Expand the date range in Reconcile view manually
QuickBooks	Rules engine for recurring transactions	Struggles with partial payments from bank feed	Use "Find Match" to select multiple invoices
Sage	Bank reconciliation with direct matching	Limited auto-suggest compared to Xero/QB	Import CSV with clean columns to reduce manual mapping
FreeAgent	Smart bank explanation engine	New payees default to "unexplained"	Set up explanation rules for repeat suppliers

Read our detailed import guides for Xero, QuickBooks, Sage, and FreeAgent.

What to Do When Your Bank Feed Stops Syncing

Open Banking bank feeds are brilliant — when they work. But every UK bookkeeper has experienced the sinking feeling of opening Xero or QuickBooks and seeing "Last updated: 4 days ago" next to a client's bank feed. Here's what to do:

Check the bank's Open Banking status — most UK banks publish service status pages. The issue is often on their end (scheduled maintenance, API changes).
Reauthorise the feed — Open Banking consent expires every 90 days. If the client hasn't reauthorised, the feed goes dead. Send them the reauthorisation link from your accounting software.
Check for account changes — if the client opened a new account, closed an old one, or changed their banking package, the existing feed connection may break.
Don't wait — work from the statement — while the feed is down, download the missing transactions as a bank statement PDF or CSV, convert it to a clean spreadsheet using BankScan AI, and import it manually. Don't let a broken feed hold up month-end close.
Reconcile the gap — when the feed comes back, double-check that the manually imported transactions don't duplicate with the feed data. Most software flags duplicates automatically, but verify.

This is where having a backup workflow matters. Sole reliance on bank feeds means a single broken connection stops your entire month-end. A hybrid approach — feeds for daily use, plus the ability to convert PDF statements quickly when feeds fail — keeps you moving regardless.

Bank Rules: Your Silent Reconciliation Assistant

Bank rules are the single highest-leverage time-saver in transaction matching, and most bookkeepers underuse them. A well-configured set of rules can auto-match 40-60% of your recurring transactions before you even open the reconciliation screen.

Here's what to set up rules for:

Software subscriptions — Xero, QuickBooks, Adobe, Microsoft 365, antivirus, hosting. These hit every month for the same amount from the same payee. One rule each = 12 matches/year automated.
Standing orders and direct debits — rent, utilities, insurance, loan repayments, HMRC payments. Fixed amounts, predictable frequency.
Payroll — salary payments, pension contributions, HMRC PAYE payments. Usually the same payee reference pattern each month.
Bank fees — account maintenance charges, overdraft fees. Match to bank charges nominal code.
Recurring client payments — retainer clients who pay the same amount monthly. Match by amount range and payee name pattern.

With Good Bank Rules

40-60% of transactions auto-matched
Month-end reconciliation starts at 70% complete
New staff pick up the process in days, not weeks
Recurring transactions never sit "unexplained"
Audit trail is clean and consistent

Without Bank Rules

Every transaction needs manual review
Same 20 recurring transactions matched from scratch each month
New staff take weeks to learn which codes to use
"Unexplained" list grows by 30+ items every month-end
Inconsistent coding makes year-end adjustments painful

💡 Pro tip: Schedule a 30-minute "rule review" every quarter. New subscriptions start. Old ones end. Payees change their reference formats. A quarterly refresh keeps your rules accurate. Set a recurring calendar reminder — this is the kind of task that's never urgent but always pays off.

Year-End and VAT Period: The Stress-Test for Your Matching Process

If your transaction matching process limps along during normal months, it collapses entirely during year-end or VAT quarter-end. The volume doubles (you're catching up on months you deferred). The stakes are higher (HMRC deadlines are real). And the data is messier (clients dump a year's worth of PDFs on your desk).

Here's how to survive:

Convert everything to spreadsheets first — do not try to match from PDFs. The eye strain alone will cost you accuracy. Use BankScan AI's bulk conversion to turn a year's worth of bank statements into clean Excel files in one batch. Now you're matching from data, not documents.
Match by quarter, not by month — during year-end, group transactions by VAT quarter rather than calendar month. It aligns with your VAT return periods and reduces the number of reconciliation blocks you're working with.
Focus on the big numbers first — sort by amount descending. Reconcile the top 20% of transactions by value. They'll cover 80% of your total movement. The remaining small transactions can be batch-coded if necessary to meet the deadline.
Have a suspense system — anything you genuinely cannot match goes into a suspense account with a detailed note. It's auditable, it keeps your reconciliation balanced, and it means you're not holding up the entire close for one mystery transaction.

Read our dedicated guides: Tax Season Bank Statement Conversion and Year-End Bank Statement Processing.

The One Change That Transforms Your Matching Speed

If you take one thing away from this guide, let it be this: the quality of your bank statement data is the bottleneck. Not your matching technique. Not your accounting software. Not your knowledge of the client's business.

When your bank data arrives already clean — every transaction on one row, dates formatted consistently, debits and credits in separate columns, payee names complete and uncut — matching is systematic. It's a sorting exercise, not a detective investigation.

When your bank data arrives as a PDF you have to manually re-type, or a CSV with split rows and missing dates, every single transaction becomes a puzzle. Multiply that by 200 transactions per client, and multiply that by 10 clients, and you're losing entire days every month to data entry that adds zero value to your clients or your practice.

BankScan AI was built to eliminate that bottleneck. Upload any UK bank statement — digital PDF, scanned paper, CSV export — and get a clean, structured spreadsheet back in under 30 seconds. It handles the formatting quirks of 16+ UK banks automatically, so you spend your time matching and reconciling, not squinting at misaligned columns. Free first conversion at bankscanai.com/landing.

Your Monthly Matching Checklist

Print this. Stick it next to your monitor. Run through it every month-end:

Convert all bank statement PDFs to clean spreadsheets (don't work from PDFs)
Export open invoices list from accounting software
Sort bank transactions and invoices by amount (descending)
Match exact-amount transactions first (unique amounts will pop immediately)
Match by reference number where available and reliable
Match by payee + date proximity for remaining transactions
Check for partial payments (multiple credits = one invoice total?)
Check for batch payments (one credit = multiple invoice totals?)
Identify direct debits, standing orders, and bank fees — code appropriately
Flag unmatched items in your running log for client follow-up
Verify closing balances match between bank statement and reconciliation
Review bank rules — any new recurring transactions to add?

Stop Losing Evenings to Transaction Matching

Convert any UK bank statement to a clean, sortable spreadsheet in seconds. Match transactions to invoices in minutes, not hours. Free first conversion — no credit card, no commitment.

Try BankScan AI Free →

Frequently Asked Questions

How do I match bank statement transactions to invoices manually?

Start by converting both sides to spreadsheet format — clean bank data and exported invoice list. Sort both by amount (descending) rather than date. Match by amount first: unique amounts will pair instantly (an £847.32 payment can only match one invoice). For common amounts, use the payment reference field — but don't trust it blindly; many clients put generic references that don't match invoice numbers. Next, group by payee and check against the date window (UK payments typically clear 2-5 working days after invoice date). What's left will be direct debits (match by fixed amount + payee pattern), bank fees (code to bank charges), partial payments, and batch payments. Keep a running log of unmatched items to review with the client weekly. For the cleanest data, convert bank statement PDFs to spreadsheets with BankScan AI before you start matching.

What do I do when a payment doesn't match any invoice?

Don't guess — and don't leave it sitting unreconciled. Categorise the unmatched payment into one of four buckets: (1) Direct debits and standing orders — match by fixed amount and payee pattern; these rarely have invoice references. (2) Bank fees — code to a dedicated bank charges nominal account. (3) Supplier refunds or chargebacks — match to a credit note, not an invoice. (4) Genuinely unidentified — create a suspense account entry with full details (date, amount, payee, reference) and flag for client follow-up within the week. Never force-match a transaction you're unsure about; unreconciled differences compound and become much harder to unpick later. Most mystery transactions resolve within days when you ask the client directly.

How do I handle partial payments against invoices?

In Xero: select "Add Payment" on the invoice and enter the partial amount received. The invoice remains open for the balance. In QuickBooks: use "Receive Payment" with the partial amount. Always record the bank statement payment reference in the payment notes. Crucially, set a follow-up task for the remaining balance — partial payments are the most commonly forgotten items in bookkeeping. If partial payments are a pattern with a particular customer (more than twice in a quarter), consider restructuring their billing: break large invoices into milestone payments, or switch to smaller, more frequent invoices that can each be paid in full. This eliminates the reconciliation complexity at source.

Why do my bank feed transactions not match in Xero?

Xero's auto-matching fails for three predictable reasons: (1) The bank transaction amount differs from the invoice total — even by a few pence, usually from bank fees or currency conversion rounding. (2) The payment cleared outside Xero's default date-matching window (typically 14 days) — common with international transfers and late payments. Manually expand the date range in the Reconcile screen. (3) The payment reference on the bank statement doesn't contain the invoice number or contact name exactly as it appears in Xero. The fix: manually search transactions by amount, broaden the date range, or create bank rules that map common reference patterns to the correct contacts. For transactions that still won't match, check the bank statement for split rows or formatting issues — clean data from a converter like BankScan AI eliminates this variable entirely.

How can I speed up matching bank transactions to invoices?

Four changes that compound: (1) Start with clean bank data — convert PDF statements to structured spreadsheets with BankScan AI so you're matching from sortable columns, not squinting at a PDF. (2) Set up bank rules for every recurring transaction (subscriptions, standing orders, payroll, rent, bank fees) — 30 minutes of rule setup auto-matches 40-60% of transactions every month. (3) Sort by amount, not date — unique amounts match instantly. (4) Batch by transaction type — process all direct debits first (they share matching patterns), then card payments, then transfers. Switching between different matching strategies for every transaction is cognitive overhead that slows you down. Read our full guide on reconciling bank statements faster for the complete workflow.

What are bank rules and how do they help with reconciliation?

Bank rules are automated matching instructions you configure in your accounting software (Xero, QuickBooks, FreeAgent, Sage). A rule says: "When a transaction has these characteristics — e.g., payee contains 'GoCardless', amount is under £500, type is Direct Debit — automatically match it to this contact/account/code." Rules excel at recurring transactions: software subscriptions (same amount, same payee, every month), rent payments, utility direct debits, payroll, loan repayments. Spend 20 minutes setting up rules for your 10-15 most frequent transaction patterns and you'll cut reconciliation time by 30-50% every month. Review rules quarterly — subscriptions change, payees update their reference formats, and stale rules create as many problems as no rules.

How do I handle batch payments covering multiple invoices?

Start with arithmetic: list all open invoices for that customer and check which combination sums to the payment amount. If £12,500 arrived and open invoices are £3,800 + £4,200 + £2,100 + £1,600 + £800 — that's £12,500 total. In Xero: split the bank transaction line during reconciliation and allocate portions to each invoice. In QuickBooks: use "Find Match" and select multiple invoices. Always record which invoices the payment covers in the payment notes — your future self (or the next bookkeeper) will thank you. If no combination of open invoices adds up, ask the client for a remittance advice. Never split a batch payment arbitrarily; misallocations create a trail of reconciliation errors that are painful to unwind.

Can bank statement matching be fully automated?

Not completely — but you can automate 80-90% of it. Bank rules handle recurring transactions. Open Banking feeds eliminate manual data entry. Modern accounting platforms auto-suggest matches based on amount, date, and payee patterns. What remains is the judgement layer: near-miss amounts (bank fees, currency rounding), batch payments that need manual splitting, payments from unfamiliar payees, and transactions where the reference is ambiguous. The realistic goal isn't zero-touch matching — it's reducing manual work to the 10-20% of transactions that genuinely need human judgement. Start with clean bank statement data (a converter like BankScan AI eliminates the data-entry bottleneck), add well-configured bank rules, and let your software handle the rest. For the remaining edge cases, your running unmatched log and weekly client review keep everything under control.

Last updated: 24 July 2026. BankScan AI supports 16+ UK bank formats — read our UK bank statement formats guide or browse all blog posts for UK accountants and bookkeepers.

How to Match Bank Statement Transactions to Invoices — Complete UK Guide (2026)