Inbound to you

EDI 820: the remittance advice

The 820 explains a payment. It names the invoices the money covers, and it itemises what was held back: each deduction with an amount and a reason code.

It is the document a controller is reading when a payment does not match what was billed, and it is where a chargeback first becomes visible to your side of the relationship.

What the document carries

One payment, broken down. The invoice numbers being settled, the amount applied to each, and then the adjustment lines: a code from the retailer's reason-code list and the dollars taken against it. Late ship notice, price difference, shortage, each wearing its own code.

Read one 820 and you learn what last month cost. Read three months of them, sorted by reason code, and you learn what your document quality costs as a run rate, which is the counting exercise the chargebacks guide walks through.

How it reconciles in Odoo

Landed automatically, the 820 becomes a customer payment matched against the invoices it names. Each deduction line stays attached to the invoice it was taken from, so the question changes from where did the money go to what do we do about this line.

Each line then needs a decision: write it off, dispute it, or fix the operational cause so next month's 820 is shorter. That routing is a configuration conversation, and the controller who reconciles payments today is the person who has it.

Where it goes wrong

Unreconciled, the 820 is a statement nobody reads. The payment gets applied as a lump, the deductions dissolve into a receivables write-off line, and the reason codes that explain them never reach anyone who could act.

The expensive version of that is quiet: a recurring deduction with the same code, month after month, that nobody has ever sorted by cause. The 820 carries the answer the whole time.

The rest of the set

One document never travels alone. The mandate that asks for this one names its siblings, and the questions repeat: direction, mapping, and what happens when it is late or wrong.

When the partner sends a separate accounting adjustment, follow the EDI 812 credit or debit adjustment into Odoo with its original reference intact.

Every code in plain language: the X12 catalog. What a late or wrong document costs: chargebacks and deductions. Who mandates and how it is enforced: the US programmes and the Canadian ones. How the documents fit into purchasing, fulfilment and accounting: EDI across the supply chain.

Start with the letter

The Requirement Check takes two answers: who mandated you and where you stand today. You get back a plain readout of which documents that customer asks for and what has to change inside your Odoo. It is free and it commits you to nothing.

Book a 30-minute call