Money Without a Message: A Remittance Protocol for Unadvised Cash
Photo: Минфин РФ, Public domain, via Wikimedia Commons
There is a particular kind of relief that comes from seeing a credit on the bank statement after a long chase, followed quickly by a particular kind of irritation when no remittance advice arrives to explain it. The money is real; the allocation is not. Until someone decides which invoices that payment settles, the ledger is telling a story that is at best incomplete and at worst wrong.
For UK suppliers this is a recurring operational problem rather than an occasional one. Faster Payments arrive in seconds with a reference field that has been truncated, abbreviated or ignored. BACS credits land three days after the input date, by which time the buyer's accounts team has moved on. The result is unallocated cash sitting on account while invoices that have in fact been paid continue to age.
Why unallocated cash is not good news
A payment on account is a liability as much as an asset. It inflates your cash position while leaving your aged debtors report overstated, which means your credit control team spends the following week chasing invoices the customer has already settled. That is not merely wasted effort. It damages the relationship, because a supplier chasing a paid invoice looks either disorganised or accusatory.
There are further consequences. Your own credit limits and stop flags, applied to the customer's account, may be triggered by invoices that are no longer due. Any financing arrangement — invoice discounting, a revolving facility, an asset-based loan — that relies on the aged ledger will be drawing against numbers that do not reflect reality. And in the worst cases, the customer's own payables ledger records the balance differently from yours, which converts a routine allocation question into a formal reconciliation dispute six months later.
The reference is the contract
Allocation begins long before the money arrives. The reference field on a payment is the only instruction most buyers will ever give, and suppliers who treat it as optional should not be surprised when it is omitted.
Practical rules to adopt:
- Issue invoices with a single, short, structured reference that fits comfortably within the payment field, and print it nowhere else on the document.
- Quote the same reference in every chase email, statement and credit note so the buyer's team sees one consistent string.
- Require a remittance advice for every payment, sent to a dedicated and monitored inbox rather than an individual's address.
- Ask for the remittance on the day of payment, and specify a cut-off — for example, by 16:00 on the value date.
- Where a buyer pays several invoices in one transfer, ask for a single line-level advice rather than a lump-sum reference.
Those points should appear in your standard terms and in the onboarding documents you send to new trade customers, not in a paragraph added after the first problem arises.
The allocation log
Every supplier should keep a simple unallocated cash log, maintained by whoever performs the bank reconciliation. It needs only a handful of columns: date received, amount, payer name, bank reference as received, the invoices suspected, the invoices confirmed, the person who confirmed it, the date confirmed, and the age of the item.
Two disciplines make the log useful. The first is that nothing is allocated on guesswork. Where a payment plausibly matches an invoice by amount, it may be allocated provisionally, but the allocation must be flagged until the customer confirms it in writing. The second is that the log is reviewed weekly, with any item older than five working days escalated. Unallocated cash that nobody is looking at has a habit of becoming a write-off.
A standard request that gets answers
Most remittance requests fail because they are vague. A short, specific, polite request with the bank details quoted back to the customer tends to work better than a general appeal. Something along these lines:
Dear [Name], thank you for your payment of £[amount] received on [date] to our account ending [digits], quoting reference [reference as received]. We are unable to allocate this payment against your account and would be grateful if you could confirm which invoices it settles. For reference, the invoices currently showing as outstanding are [list with dates and amounts]. A reply by [date, five working days ahead] would allow us to update our records before the next statement run.
Note the three features: the payment is acknowledged rather than challenged, the ambiguity is stated plainly, and a deadline is given. Requests framed this way are difficult to ignore, and the reply becomes the audit evidence you need if the allocation is later disputed.
Escalation: from query to recorded dispute
Silence should have a timetable of its own. A workable sequence for a UK supplier is: same-day written request on receipt of unadvised cash; a telephone call to the buyer's accounts payable team at day two; a second written request copying your usual commercial contact at day five; a formal notice at day ten that the payment remains unallocated and that the affected invoices are treated as outstanding pending confirmation; and a referral to the buyer's finance manager at day fifteen.
If a buyer repeatedly pays without advice, treat it as a control failure on their side rather than an accident. It is worth raising at a commercial review, and it is worth recording. Persistent silence over allocations is one of the quieter ways in which a payment culture degrades, because it allows a buyer to pay late while keeping the ledger permanently ambiguous.
Measuring the gap
Finally, count it. An unallocated cash balance is a metric in its own right, alongside debtor days and the ageing profile. A supplier that reports unallocated cash weekly, with an ageing of the items, will find that the problem shrinks simply because it is visible. Cash that arrives without explanation is still cash, but until it is allocated it is not yet a settled invoice — and the difference matters every time you pick up the phone to chase.