Glossary

EDI 997 (Functional Acknowledgment)

EDI 997 is the ANSI X12 transaction set a receiving system sends back automatically to confirm that it received and could parse a group of EDI documents — a purchase order, an invoice, an ASN — reporting only whether the transmission was syntactically valid, not whether its contents were correct or agreed to. It answers a narrower question than it looks like: "did this arrive and parse," not "do I accept what's in it." A purchase order that is syntactically perfect but priced wrong still earns a 997 accepting it; a price dispute surfaces later, if at all, through an EDI 855 or a chargeback.

What the 997 reports

A 997 is generated automatically by a trading partner's EDI translation software, not reviewed or sent by a person, and it responds at the level of a functional group — the envelope (GS/GE segments) wrapping one or more transaction sets of the same type.

Its structure mirrors what it's acknowledging: an AK1 segment identifies which functional group it's responding to, an AK2 loop repeats once for each transaction set inside that group, and an AK5 segment inside each loop carries a status — accepted, accepted with errors, or rejected — based on whether the transaction set's syntax matched the X12 standard. Field and segment details shift slightly between X12 versions (4010, 5010, and others), so the exact structure depends on which version a given trading-partner agreement specifies. Standard practice is one 997 per functional group received, unless the trading partners have agreed to something else.

What it is not

A 997 is not a business acknowledgment of order terms, pricing, or quantity — it's a receipt-and-syntax check, nothing more. "Accepted" means the receiver's system could read the transaction set against the X12 spec; it says nothing about whether the receiver agrees the purchase order is priced right, the invoice matches the contract, or the ASN's ship date is workable.

For purchase orders specifically, that business-level confirmation is a separate transaction set, the EDI 855 (Purchase Order Acknowledgment). For most other document types there's no equivalent at all — the 997 is the only acknowledgment a sender gets. Treating a 997 as order confirmation is a common mistake for a team new to a trading-partner relationship: the green checkmark on the transmission doesn't mean the other side has reviewed, agreed to, or even looked at what's inside it.

Where it fits in a trading-partner setup

A typical sequence runs: 850 (purchase order) sent, answered by a 997; optionally an 855 (business acknowledgment) follows; later an 856 (ASN) is sent and 997'd; then an 810 (invoice) is sent and 997'd. Nearly every outbound EDI document in a trading relationship earns an inbound 997, and many partner agreements set a required turnaround — often 24 to 48 hours — making a missing 997 itself a monitored error condition.

That makes a missing 997 a useful diagnostic. It usually points to a transmission or connectivity failure — a VAN outage, an AS2 certificate issue, a translator misconfiguration — rather than a trading partner silently ignoring the document. The troubleshooting step is checking the connection, not calling the supplier to ask why they haven't responded to a PO they most likely never received.

Frequently asked questions

What does an EDI 997 confirm?

It confirms that a functional group of EDI documents was received and that its syntax matched the X12 standard — the AK5 segment reports accepted, accepted with errors, or rejected for each transaction set inside the group. It says nothing about whether the receiver agrees with the business content.

Does a 997 mean my purchase order was accepted?

No. A 997 only confirms the 850 purchase order arrived and parsed correctly as an EDI document. Whether the supplier actually accepts the order as written — the price, quantity, and ship date — is confirmed separately, through an EDI 855, if the trading partner sends one at all.

How many 997s are generated per EDI transmission?

Standard practice is one 997 per functional group received, covering every transaction set in that group, unless a trading-partner agreement specifies otherwise. It's generated automatically by the receiving system's EDI translator, with no manual review.

What does it mean if an expected EDI 997 never arrives?

It usually signals a transmission or connectivity problem — a VAN issue, an AS2 certificate expiring, a translator error — rather than a trading partner ignoring the document. Many partner agreements set a required 997 turnaround time, so a missing acknowledgment is itself flagged as an error condition to investigate at the connection level first.

Related terms

See it on your own SKUs.

A 30-minute walkthrough on your categories and your supplier data.

Book a demo