What is a remittance advice?

The matching problem it solves

A supplier's bank feed shows an amount and a payer name, sometimes truncated to twelve characters. Their ledger shows nine open invoices for that customer. Working out which are now settled is guesswork unless the amounts happen to be unique, and it gets worse when the payment is short by the value of a credit note the supplier has not applied yet. The advice removes the guesswork by doing the arithmetic on the payer's side, where the decision was actually made. That is why large customers send them automatically and why suppliers ask for them constantly. An unmatched payment sits in a suspense account, the invoices stay open, and the supplier's collections process keeps chasing money that has already arrived.

What belongs on it

The payer's name as it will appear on the bank statement, which is often not the trading name and is the single most useful line on the page. The payment date and method, and the bank reference where one exists. Then a table: each invoice with its number, its date and the amount being paid against it. Deductions on their own lines, naming the credit note or the reason, so a short payment is explained rather than discovered. A total that exactly equals the amount transferred. And a contact, by name and email, for queries. That last one turns a two week email chain into a phone call, which is worth more than any of the formatting.

Why suppliers chase it so hard

Cash application is one of the slowest tasks in a finance team and it is entirely reactive. Every unexplained deposit becomes an investigation, and every investigation delays the supplier's own view of who owes what. Beyond the effort, there is a relationship cost: a supplier chasing an invoice that was paid a fortnight ago looks disorganised and the customer feels harassed, when the real fault was a missing note. Small suppliers feel it most, because they have no dedicated cash application function and the person reconciling the bank account is usually the person who did the work. Sending the advice takes a payer thirty seconds and saves the supplier an afternoon.

How it differs from a receipt

Direction, and who benefits. A receipt travels from the party who received money to the party who paid it, confirming the amount arrived. A remittance advice travels the other way, in advance of or alongside the money, explaining what it is for. They are frequently confused because both are short documents about a payment, and the confusion causes real problems in accounts payable systems where a receipt gets filed as a remittance and neither party has an explanation of the allocation. A statement of account is a third thing again: it lists everything outstanding rather than describing one payment, and it comes from the supplier.

Automating it without making it useless

Most accounting systems generate one when a payment run is processed, and the generated version is usually adequate. Two things are worth checking before turning it on. First, whether it emails to the right address, since accounts payable systems tend to hold the sales contact rather than the supplier's accounts inbox, and an advice sent to a salesperson helps nobody. Second, whether it includes the deductions with their reasons, because many templates show a net figure per invoice with no explanation of the difference. Where a payment run covers dozens of invoices, attach the detail as a separate schedule rather than compressing it, since a supplier reconciling forty lines needs them all legible. It is also worth sending one for a payment made outside the normal run, such as an urgent transfer approved by phone. Those are exactly the payments a supplier cannot place, because nothing about them fits the pattern their ledger expects, and they are the ones most likely to be chased twice.

Questions people ask