Money shows up in the bank account; the mystery is what it paid. A large buyer's payment might cover forty invoices, minus a dozen deductions, plus a rebilled allowance — and the bank statement shows one number. The EDI 820 Payment Order / Remittance Advice is the document that decodes it, and it is the reason cash application at EDI-heavy suppliers can run without a spreadsheet full of guesswork.
Reading the document
Four segments carry nearly everything that matters:
- BPR — the payment itself: amount, payment method, and effective date. This is the header that says how much money moved and how.
- TRN — the trace number that reassociates this advice with the ACH transaction that carried the funds. When remittance data and money travel separately, TRN is the thread that ties them back together.
- RMR — one per invoice: the invoice number being paid and the amount applied to it. This is the segment your AR team actually wants.
- ADX — adjustments: each deduction or credit, with a reason code. Shortage claims, compliance chargebacks, promotional allowances — itemized, not lumped.
An 820 covering many invoices is still one document, which matters both for parsing and — later in this post — for what it costs to receive.
Where it sits in the financial chain
The 820 closes the loop that the 810 invoice opened. You billed; the buyer's payables system matched your invoice against the PO and the receiving record; whatever survived that match gets paid and reported here. Deductions that need more explanation than an ADX reason code often arrive separately as an 812 credit/debit adjustment, and like every inbound document the 820 gets receipted with a 997 automatically.
Grocery and mass-retail programs lean on this chain hard: high invoice volume, frequent allowances, and deduction-heavy payment practices mean the remittance advice is often the first place a supplier learns a chargeback happened at all. That early-warning property is underrated — a supplier who parses 820s systematically usually knows about a compliance problem days before the formal deduction paperwork catches up.
Cash application without the spreadsheet
Manually, applying a big remittance means downloading a PDF from a portal, matching line by line against open AR, and coding deductions by hand — hours per payment cycle. Automated, the 820 posts itself: RMR lines match and clear open invoices in your ERP, ADX adjustments land in deduction accounts by reason code, and the only human work left is deciding which deductions to dispute.
That last part is worth automating a step further. Deduction reason codes are the raw material of recovery: when every ADX lands in a structured queue instead of a PDF, patterns emerge — a DC that always claims shortages, an allowance deducted twice — and disputes get filed while the trail is fresh. Over a few payment cycles that queue becomes a dataset: deduction rates by partner, by reason, by location. Finance teams that report on it tend to find their most profitable fix is upstream — labeling, ASN accuracy, price maintenance — rather than in faster dispute letters.
EDISQ maps inbound 820s into whichever system runs your AR, from QuickBooks Online to 30+ ERPs and accounting platforms, with reassociation, invoice matching, and deduction coding handled in the map rather than in your inbox.
What receiving 820s costs
Some providers meter remittance advices the same way they meter everything else — on top of a subscription that buys nothing. EDISQ's model turns its one fixed piece into usage — the $100/month Production minimum applies in full to documents: you get 25 documents free every month, then pay from $0.50 per document with the rate stepping down to $0.10 at the highest volume tier, applied marginally. A single 820 that clears forty invoices costs the same as any other document, and AS2, SFTP, and VAN connectivity are part of the price rather than an add-on.
If deductions are the reason you care about this document, the transaction glossary shows how the 820 and 812 divide the adjustment story between them.
FAQ
Is the EDI 820 a payment?
It can be either the payment instruction itself or the advice describing a payment made through the bank. In supplier flows it usually travels alongside an ACH payment and explains which invoices and deductions the money covers.
What is the difference between an 820 and an 812?
The 820 reports what was paid and lists adjustments in summary; the 812 is a standalone credit/debit adjustment document with fuller detail about a specific deduction or allowance.
Why does my 820 not match my invoice total?
Deductions. Buyers subtract chargebacks, allowances, and shortages before paying, and itemize them in ADX segments with reason codes. Reading those codes is how you find out what was taken and why.
How does EDISQ price inbound 820s?
Like every document: 25 free each month, then from $0.50 per document, decreasing with volume. There are no document-type surcharges, so receiving remittance data costs nothing extra.