EDI 997: the functional acknowledgment

What it confirms, precisely

Syntax. The envelope was addressed correctly, the segments parsed, the file is structurally valid X12. A 997 can accept a document your business process will later reject, because readable and agreeable are different questions.

Business acceptance is the 855's job. The 997 only promises that the document reached the other side in one piece, and that narrow promise is what makes it useful: it isolates transport problems from business problems.

How it runs around Odoo

Outbound 997s are generated automatically when documents land; nobody authors one. The work is on the watching side: every document Odoo sends should have a matching 997 back within a window, and reconciling sent against acknowledged is a report, running quietly.

That report is part of the go-live definition of done. A connector that sends documents without watching acknowledgments is a connector that fails silently.

Where it goes wrong

Silence. A certificate expired, a mailbox moved, a network changed something, and documents stopped arriving, in either direction. Nothing errors, because nothing is running. The missing 997 is the first observable symptom.

The failure that follows is human: an alert someone assumed somebody else was watching. Deciding who sees the unacknowledged-documents report, and when, is part of standing the connection up.

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.

For the checkpoint after syntax acceptance, see how an EDI 824 application advice reports application-level errors.

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.