Matching bank payments to invoices: a weekly routine for unidentified and part payments

The bank statement shows 1,210 received from a name nobody recognises, with no reference. Another payment covers only half of an invoice. A third covers two invoices at once, minus a small fee. Each one is easy to solve alone. Left to pile up, they delay the closing of invoices, trigger reminders to customers who have already paid and make the cash picture unreliable.

This article describes a short weekly routine for matching payments, with clear rules for the awkward cases.

Pick one day and one owner

Matching works best as a short, repeated task. Choose a fixed weekday and a named person, with a deputy for holidays. Thirty minutes a week is usually enough for a small company. If payments are matched only at month end, the list is long and nobody remembers the context.

Before sending any payment reminder, check the list first. Sending a reminder to a customer who paid last Tuesday costs goodwill.

The routine in five steps

1. Export the bank movements since the last matching day.
2. Match the clear ones first. The variable symbol or invoice number in the reference, plus the right amount, settles most payments within minutes.
3. Match by amount and payer where the reference is missing. Only do this when the answer is obvious.
4. Move the rest to the unmatched list. Write the date, amount, payer name and account number.
5. Mark invoices as paid and note the bank date, not the date you processed it.

Unidentified payments

Do not guess. Assigning a payment to the wrong invoice creates two problems instead of one: the wrong invoice looks paid and the right one gets a reminder.

Instead:

• Search for the payer name and the amount in open invoices.
• If nothing fits, write to the payer within two working days: "We received 1,210 from your account on 21 October without a reference. Which invoice should it be applied to?"
• If there is no answer in a week, ask once more, then keep the amount as a customer credit and say so in writing.

Keep the unmatched list in one place with an age column. Anything older than two weeks gets looked at in the next weekly session.

Part payments

A customer pays half. There are three common reasons: a disagreement about part of the invoice, a cash flow problem or a simple mistake.

• Record the part payment against the invoice. The invoice stays open with the remaining balance visible.
• Ask which reason applies. A disagreement belongs with whoever handles the order, not with accounting alone.
• Do not send a standard reminder for the full amount. Mention the amount received and the amount still due.

For the wider routine on overdue amounts, see the late customer payments collection routine.

One payment for several invoices

When a customer pays several invoices in one transfer, match each invoice separately and keep a note of the total. If the sum is a little lower, check for a bank fee, a rounding difference or an agreed discount. Decide in advance a small tolerance, for example a few units of currency, within which you close the invoice and write the difference off with a note. Anything above it goes back to the customer.

Overpayments and duplicates

A customer sometimes pays twice. Do not wait for them to notice. Tell them, and agree whether the amount is refunded or applied to the next invoice. Record the decision, because otherwise the credit will still sit on the list months later.

Prevent the next unidentified payment

Many unmatched payments start with the invoice, not the customer. Look at the cause:

• the payment reference is hidden in a corner or too long to copy;
• the bank account differs from the one customers used before;
• there are several invoice numbers per order;
• the invoice does not make clear how to pay.

Print the reference and the amount in a visible box and keep it identical across invoices. The article on payment terms and payment methods lists what belongs on the invoice.

Connect it to the month-end

Open items on the unmatched list at month end distort both receivables and revenue timing. Make the list a line in your month-end close checklist: empty it, or explain every remaining item.

When a tool helps

If invoices live in one system and bank statements in another, someone has to compare them by eye every week. Importing the statement and proposing matches by reference and amount, with a human confirming the uncertain ones, removes most of the manual work. This is a focused custom software task, worth building once the manual rules above are stable. If your customer records also differ between systems, see two systems, two truths.

What to avoid

• Matching payments only once a month.
• Guessing the invoice for a payment without a reference.
• Sending reminders before checking the latest bank movements.
• Leaving part payments as "unpaid" with no balance shown.
• Keeping the unmatched list in one person's inbox.
• Ignoring overpayments until the customer complains.

A simple start

1. Choose the weekday and the owner.
2. Create one unmatched-payments list with date, amount, payer and age.
3. Write the standard question to send to a payer without a reference.
4. Set the tolerance for small differences.
5. Check the list before every reminder and at month end.

Sources

• This article describes a working routine and makes no statistical claims. The related WVI articles linked above cover payment terms, late payments, the month-end close and reconciling customer records.