Friday afternoon with the bank feed
The bank feed is connected, so the transactions arrive in Xero or QuickBooks on their own. That was supposed to be the end of it. Instead someone still sits down each week and works through a column of unmatched lines, searching for the invoice that a payment relates to, checking a customer's name against three slightly different spellings, and parking anything odd in a suspense account to look at later.
Later tends to become month end. By then there are dozens of parked items, the person who knew what they were has been on holiday, and the reconciliation becomes a small investigation.
Why bank rules only go so far
Bank rules are exact-match tools. They are good for the rent, the phone bill, the monthly software subscription. They do nothing for the transactions that actually take time, because those are the ones that vary.
| Transaction type | Why it resists simple rules |
|---|---|
| Customer pays three invoices in one transfer | One bank line, several ledger items, total matches none of them individually |
| Part payment or short payment | Amount matches no open invoice |
| Card processor settlement | Net of fees, batched across many sales |
| Reference is a PO number or blank | Nothing links it to your invoice number |
| Payer name differs from the account name | Parent company, director's personal account, trading name |
The root cause is that the matching decision needs more than the bank line. It needs your open invoices, your remittance emails, your customers' known payer names and a sense of what is plausible. A bank rule sees none of that.
What the manual version costs you
Staff time is the visible part. The less visible part is that your receivables are wrong until reconciliation catches up. Customers who have paid get chased. Customers who have not paid look fine because an unallocated receipt is sitting against the wrong account. Cash position reports carry a suspense balance that everyone learns to ignore.
Errors also compound. A payment allocated to the wrong invoice is harder to unpick three weeks later than on the day it arrived.
And there is a people risk. In many businesses one person holds the knowledge of which director's account pays for which company, or that a particular customer always pays net of a retention. When that person is off sick or leaves, reconciliation stalls completely, and the new starter learns it all again from scratch by trial and error.
The matching layer we build
- Read transactions from the bank feed already in Xero or QuickBooks, or directly from your bank's open banking or statement export where that is cleaner.
- Pull the open invoices, bills and credit notes from the ledger through its API.
- Match in passes: exact amount and reference first, then combinations of open invoices that add up to a payment, then known payer names and aliases, then near amounts that suggest a short payment or a fee.
- Use remittance emails where they exist, reading the invoice list from them so a combined payment can be split correctly.
- Score each proposed match and record the reason in plain words, such as 'three invoices for this customer sum to this amount'.
- Post confident matches, and send everything else to an exception list where a person accepts, edits or rejects with one action.
When someone resolves an exception, for example by confirming that a payer name belongs to a customer, we store that so the same situation matches on its own next time.
After it is running
Reconciliation becomes a daily glance instead of a weekly session. The exception list is short and each line explains itself, so it can be cleared by whoever is in, rather than waiting for the one person who remembers how that customer pays.
Your aged debtors report reflects who has actually paid, and credit control stops chasing money that is already in the bank.
Month end also gets lighter, because there is no pile of parked items to investigate. The suspense account either stays empty or holds a few lines that each have a note explaining what they are waiting for.
Does this sound familiar?
- The bank feed is connected but unmatched lines build up every week.
- Your suspense account always has a balance.
- Customers regularly pay several invoices in one transfer.
- You take card or online payments that settle net of fees.
- Only one person really knows how to reconcile certain customers.