The EDI 820 remittance advice is how a retailer tells you what it actually paid and what it deducted. It is the document where chargebacks become visible, and the one most brands never reconcile.
You invoiced 100. They paid 94. The 820 remittance advice is the document that explains the six, and for most brands it is the only place a chargeback is ever itemized. It is also the document most often ignored, which is why deductions go unchallenged and get written off as a cost of doing business.
The EDI 820 is the transaction set a retailer sends to tell a supplier what it is paying, which invoices the payment covers, and what has been deducted. It can also instruct a bank to move the money, which is why the standard calls it a payment order as well as a remittance advice. From a supplier's side it is the document that turns a bank deposit into a set of line items you can reconcile.
Every other document in the order cycle describes what should happen. The 820 describes what did. It is the end of the loop that starts with the 850, and if you never read it you have no closed loop at all: you have invoices and you have deposits, and no reliable way to connect them.
This matters commercially more than it sounds. Retail deductions are not usually announced. They arrive as a smaller payment. A brand that does not process the 820 discovers its chargeback exposure at the end of a quarter, in aggregate, long past the dispute window on most of them.
A simplified remittance covering two invoices, one of them short paid.
ST*820*0001 / BPR*C*18420.00*C*ACH*CTX*01*021000021*DA*1234567*1234567890**01*071000013*DA*7654321*20260812 / TRN*1*20260812001 / REF*CK*889231 / N1*PR*BIG RETAILER / N1*PE*YOUR BRAND**91*VENDOR123 / ENT*1 / RMR*IV*INV10021**9200.00*9200.00 / RMR*IV*INV10022**9220.00*9800.00 / ADX*-580.00*CS**INV10022 / SE*11*0001| BPR | Beginning segment for payment order and remittance advice. Total amount, credit or debit, payment method such as ACH, and the banking detail for both sides. |
| TRN | Trace number. The reference that ties this remittance to the actual money movement, which is what your bank statement will show. |
| REF | Additional references such as a check number or the retailer's internal payment identifier. |
| N1 PR / N1 PE | Payer and payee. The payee segment usually carries your vendor number, which is how you know which of your accounts this belongs to. |
| ENT | Entity grouping, used when one payment covers several divisions or entities. |
| RMR | Remittance detail, one per invoice. Invoice number, the amount paid, and the amount originally invoiced. When those two differ, you have a deduction. |
| ADX | Adjustment. The amount, a reason code and the invoice it applies to. This is where a chargeback is itemized when the retailer provides one. |
| SE | Closes the transaction set with a segment count. |
In the example, invoice INV10021 is paid in full. INV10022 was invoiced at 9,800 and paid at 9,220, with an ADX of minus 580 against it. That single line is the difference between knowing you have a chargeback and noticing a shortfall three weeks later.
Retailers rarely invoice a supplier for non-compliance. They deduct it from what they owe you. Macy's calls the mechanism an expense offset and states in its vendor standards that non-compliance constitutes consent to offsetting charges from amounts otherwise payable. The language differs by retailer, the mechanism does not.
Some retailers populate ADX with a reason code and an invoice reference. Others short pay the RMR and leave you to work out why from a portal. Either way, the 820 is what tells you the money is missing, and the sooner you know the more of the dispute window you have left.
Retailers commonly allow a limited period to dispute a deduction, and it runs from the deduction, not from when you notice it. Batch reconciling remittances monthly can put a meaningful share of your deductions out of scope before anyone looks at them.
Most deductions are disputed on facts you already have: the ASN timestamp, the carton manifest, the routing confirmation, the delivery receipt. If those live in four systems, assembling them per claim costs more than the claim. If they live on one order record, the dispute goes out with the evidence attached.
Ten identical deductions across three months usually means one broken process, not ten mistakes. You can only see that if remittances are captured in a structured way. Reading them as PDFs finds individual claims. Processing the 820 finds the cause.
AIMS360 imports the 820 and matches each RMR line to the 810 invoice it refers to, which is already tied to the shipment, the ASN and the original purchase order. A short payment is flagged against the specific order rather than appearing as an unexplained variance in accounting.
Where the amount paid differs from the amount invoiced, the difference is raised as a deduction against that order rather than absorbed into a cash application total.
Chargeback management holds each claim against the order, shipment and invoice, so a dispute carries the ASN timestamp and carton detail without anyone rebuilding it.
The remittance posts against open receivables in AIMS360 accounting, so the bank deposit, the invoices and the deductions reconcile in one place.
Because claims are structured rather than free text, you can see which reason codes and which retailers are actually costing you, which is the input to fixing the underlying process.
It is the payment order and remittance advice. A retailer sends it to tell a supplier what it is paying, which invoices the payment covers, and what has been deducted. It can also carry instructions to move the money through the banking system, which is why the standard name covers both functions. For a supplier, it is what converts a lump sum deposit into invoice level detail you can reconcile.
Two places. The RMR remittance line shows the amount paid against the amount invoiced, so any difference is a deduction. The ADX adjustment segment itemizes it with an amount, a reason code and the invoice it applies to. Not every retailer populates ADX. Some simply short pay the RMR and expect you to look the reason up in their portal, which is why the 820 tells you money is missing even when it does not tell you why.
Not necessarily, and this trips people up. The 820 can be an instruction that accompanies a payment, or it can travel separately from the funds, sometimes arriving before or after the money. The TRN trace number is what ties the advice to the actual movement on your bank statement. Treat the 820 as the explanation of a payment rather than the payment itself.
You can work from a portal, and plenty of brands do. The cost is time and coverage. A portal shows you claims one at a time and only for retailers that have one. Processing the 820 gives you every deduction across every account in a structured form, matched automatically to the invoice and order it relates to, which is what lets you see that ten separate claims are actually one broken process.
The 810 is your invoice, what you asked for. The 820 is the remittance, what they paid and what they held back. The 812 credit and debit adjustment is a separate document some retailers use to raise or settle an adjustment explicitly rather than burying it in a payment. Not every retailer uses an 812. Almost all of them send an 820.
It varies by retailer and it is set in their vendor agreement or standards, not by the EDI standard. What is consistent is that the clock runs from the deduction rather than from the day you notice it, so a monthly reconciliation cycle can quietly put part of your exposure out of scope. We are not going to publish specific windows here because they change and differ by account. Check yours, and then make sure your process fits inside it.
Last reviewed 7 August 2026 by the AIMS360 EDI team. Segment detail reflects the ANSI ASC X12 820 transaction set. Deduction practices, reason codes and dispute windows are set by each retailer in its own vendor standards and can change. Specific deduction amounts are not published here because they are not reliably public and vary by account.
See AIMS360 reconcile remittances against the orders they came from in a 30 minute demo.
