Inbound or outbound
EDI 812: the credit and debit adjustment
The 812 communicates an adjustment to money already billed or expected between trading partners. It can carry a credit, a debit or supporting detail for an adjustment, according to the programme that requires it.
Inside Odoo, the accounting entry is only half the result. The adjustment also needs a trace back to the invoice, shipment or agreement that explains it.
What the document carries
An 812 identifies the parties, the adjustment amount and the references needed to explain the change. Line-level detail and reason codes depend on the trading partner's guide. The standard supplies the structure; the bilateral programme supplies the operating rules.
Direction depends on the relationship. A customer may send an adjustment to a supplier, or a supplier may use the document to communicate one back. The mandate settles who sends it and what response follows.
What it becomes in Odoo
A valid 812 can lead to a credit note, debit entry or review task, depending on the reason and the company's accounting policy. The integration should first identify the original invoice or commercial document, then apply the approved accounting treatment.
Automatic posting belongs only to reasons the finance team has approved in advance. Unknown references, duplicate adjustments and disputed amounts need a controlled review path with the original payload attached.
Where it goes wrong
A lump-sum entry clears the immediate reconciliation problem and loses the explanation. Finance can see that receivables changed, but operations cannot see which document or process caused the adjustment.
Duplicate handling is the other risk. The partner's control numbers and adjustment references need an idempotency check before Odoo creates anything. A resent 812 should reopen or confirm the same case, never create a second credit.
Official definition
X12 publishes the formal transaction-set definition linked below. Your trading partner's implementation guide still governs the fields, codes and timing used in your relationship.
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.
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