Remittance Advice

Remittance advice is the payment detail a customer provides telling the seller what a payment is for: the invoices being paid, credit memos being taken, discounts claimed, and deductions applied. It may arrive as a check stub, an emailed PDF or spreadsheet, an EDI 820 transaction, a line in an ACH addendum record, or a download from the customer's AP portal. Without it, a $312,447.19 ACH deposit is a puzzle; with it, cash application is mechanical.

The core operational problem is that remittance data is decoupled from the money. ACH and wire formats carry limited structured detail, many customers email remittances to whatever address they have on file, and large retailers publish them only inside their supplier portals. Mature AR teams run remittance aggregation deliberately: a dedicated remittance inbox with automated parsing, scheduled retrieval from major customer portals, EDI where volume justifies it, and bank lockbox data feeds, all funneling into the cash application match engine.

Remittance advice is also where customer behavior becomes data. Deductions and short pays are announced on the remittance, often with the customer's own reason codes; discount-taking behavior, payment batching patterns, and habitual rounding all show up there first. Parsing and storing remittance lines, rather than discarding them after matching, gives the AR team a queryable history of exactly how each customer pays.