What Is Remittance Advice? Formats, Uses and Why It Matters

Remittance advice is a notification a customer sends to tell you which invoices a payment covers. It travels with or ahead of the payment, as an email, a check stub, an EDI 820 file, or a note in a payment portal, and it lists the invoice numbers, amounts and any deductions the customer applied. Its whole job is to answer one question for your AR team: what is this money for? When remittance advice is complete, cash application is fast and accurate. When it is missing or vague, payments sit unapplied and someone has to chase the customer to find out how to post them.

It is one of those back-office documents nobody notices until it is missing. A clean remittance turns a $40,000 wire into fourteen invoices marked paid in seconds. A wire with no remittance turns the same $40,000 into a morning of detective work.

What is remittance advice used for?

Remittance advice exists to connect a payment to the specific invoices it settles. A payment on its own is just an amount and a payer name. Most B2B customers pay many invoices at once, net out credits, and take deductions for shortages or disputes, so the raw payment rarely matches any single invoice you have open. The remittance is the key that unlocks it: it says this $40,000 pays invoices 1002 through 1015 in full, less a $600 credit on 1009 and a $200 short-pay on 1011.

Without that breakdown, your team is left matching by hand, and the harder the payment, the longer it takes. This is the single biggest driver of unapplied cash, and unapplied cash is a problem because an invoice does not count as collected until the payment is posted against it, no matter that the money is already in your bank.

What does remittance advice include?

A complete remittance advice contains enough detail to post the payment with no follow-up. At minimum that means:

• Payer name and payment date. Who paid and when.
• Payment amount and method. The total and whether it came by ACH, wire, check or card.
• Invoice numbers. Every invoice the payment applies to, which is the field that actually drives the matching.
• Amount applied per invoice. How much of the payment goes against each invoice, which matters whenever an invoice is only partly paid.
• Deductions and reasons. Any credits, short-pays or disputed amounts the customer subtracted, with a reason code where possible.

The last line is the one that most often gets left off, and it is the one that causes the most work. A short-pay with no reason forces your team to open a deduction investigation just to find out whether it was a legitimate allowance or a mistake.

The main types of remittance advice

Remittance advice and cash application

Remittance advice is the raw material that cash application runs on. Cash application is the process of matching each incoming payment to the open invoices it pays and posting it to the ledger. When the remittance is clean and structured, that match is close to automatic. When it is messy, incomplete or missing, someone has to interpret it, and match rates fall.

This is exactly where the format matters. An EDI 820 is machine-readable by design. An email remittance is not: it might be a tidy spreadsheet from one customer and three lines of text from the next. Teams that receive most of their remittances by email increasingly pull the structured data out of those emails automatically rather than rekeying each one, because the manual version does not scale past a few dozen payments a day. Once the data is structured, matching it to open invoices is the easy part.

What to do when remittance advice is missing

Unapplied cash from missing remittance is normal, but it should be worked down quickly, not left to pile up. A workable process looks like this:

1. Park it clearly. Post the payment to an unapplied or suspense account so the cash is recorded but visibly not yet matched.
2. Try the obvious matches first. Check whether the amount equals a single open invoice or an exact sum of a few. Many bare payments resolve this way in under a minute.
3. Contact the payer. If it does not resolve, email the customer's AP contact and ask for the remittance detail. Keep the request specific: the payment date, amount and reference.
4. Set a rule for the future. When a customer repeatedly pays without remittance, add a standing request to their onboarding or ask them to include invoice numbers in the payment reference field.

The goal is a low, stable unapplied balance, not zero on any given day. What you want to avoid is an unapplied account that grows month over month, because every dollar in it is cash you have collected but cannot yet report as collected.

How to get better remittance advice from customers

Most missing-remittance problems are fixable on the front end. Ask customers to send remittance to a dedicated inbox rather than to a salesperson. Give large or EDI-capable customers the option to send an 820. For everyone else, request invoice numbers in the ACH or wire reference field, which alone resolves a surprising share of otherwise-blind payments. And make your own invoices easy to reference, with clear invoice numbers and terms, so a customer's AP team can build accurate remittance without guessing. Our overview of the cash application process covers where this fits in the wider flow from payment to posted.

The bottom line

Remittance advice is the note that tells you which invoices a payment covers, and it is the difference between cash application that runs itself and cash application that eats your team's mornings. Complete remittance lists every invoice, the amount applied to each, and the reason for any deduction. It arrives in several formats, from clean EDI files to bare wires with nothing attached, and the messier the format the more unapplied cash it creates. Push customers toward structured remittance sent to a dedicated destination, automate the reading of what arrives, and work your unapplied balance down on a schedule so collected cash actually shows up as collected.