Inbound or outbound
EDI 824: the application advice
The 824 reports what an application made of another document. A file may have arrived and parsed, then failed a business rule when the receiving system tried to use it. The 824 is one way a trading partner reports that result.
It matters because a successful transmission is only the first checkpoint. The order, invoice or catalog still has to pass the rules on the other side.
What the document carries
An 824 identifies the document being reported on and carries application-level status or error information. The partner's implementation guide decides when it is sent, which codes it uses and how much detail comes back.
It sits beside the 997, but the two answer different questions. A 997 reports whether the X12 envelope and transaction set were syntactically accepted. An 824 can report what happened after an application examined the content.
Where it belongs around Odoo
An inbound 824 should resolve to the original outbound document and the Odoo record behind it. An error against an invoice should point back to that invoice. An error against a catalog should identify the affected product or price line when the partner sends enough detail.
The useful result is an exception with an owner, a reason and the original payload close at hand. Some errors can be corrected and resent automatically. Others need a person because the partner's rule conflicts with the source data in Odoo.
Where it goes wrong
The dangerous case is treating transport success as business success. The outbound file shows delivered, the 997 shows accepted, and the 824 carrying the real application error sits in a separate mailbox or portal.
The control is a joined view of sent documents and every response that followed. If an 824 rejects something, the original Odoo record stays open until the correction is accepted or a person closes the exception with a reason.
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