EDI 997 Functional Acknowledgment: The Complete Guide (2026)

The EDI 997 is the receipt. Every document you send or receive gets one back: a small, automatic acknowledgment saying "your transmission arrived, and it parsed." It's the least glamorous document in X12 and the one that keeps the entire system honest.

What the 997 confirms — and what it doesn't

The 997 operates at the syntax level. When your 856 ship notice reaches a retailer, their system checks: did the interchange open and close correctly, do the segments parse, do the control numbers match? The 997 reports the verdict — accepted, accepted with errors, or rejected — per functional group (AK1), per transaction set (AK2/AK5), with a summary count (AK9).

Here's what it does not confirm: that your content was right. An ASN with a valid structure and completely wrong carton data sails through with a clean 997 — and earns a deduction at the receiving dock three days later. Business-level acceptance is a different layer, carried by the 824 application advice where partners support it, or by the blunter instruments of short-pays and buyer phone calls where they don't.

Understanding that split — syntax versus substance — is most of understanding EDI operations. The 997 tells you the pipe works. It says nothing about what flowed through it.

Why a boring document deserves monitoring

The 997's real value is negative space: the acknowledgment that doesn't arrive.

You transmit an invoice batch Friday evening. One interchange never lands — a certificate expired, a VAN queue hiccupped, a mailbox filled. Nothing errors on your side. Without acknowledgment tracking, you learn about it when the retailer calls about missing invoices, or worse, when an 850 purchase order you never received becomes an order you never shipped.

Disciplined 997 handling means:

1. Every outbound document opens a timer. Expected 997 within the agreed window — minutes in practice, hours by contract.
2. A missing 997 is an alert, not a log line. Retransmit, investigate, or escalate before the partner notices.
3. A 997 rejection stops the line. Rejected functional groups get corrected and retransmitted immediately — the partner's system has already discarded the original.
4. Inbound documents are acknowledged automatically. Your acknowledgment rate is itself measured by partner compliance programs. Walmart and its peers notice silent suppliers.

None of this should involve a human until something breaks. In EDISQ, the ack trail rides alongside every document — sent, acknowledged, timing — and the needs-attention queue surfaces only the exceptions: the 997 that didn't come back, the rejection that needs a fix.

The 997 in the document chain

The core retail chain runs 850 → 855 → 856 → 810, and the 997 travels alongside every hop, in both directions. Four business documents, up to eight acknowledgments, all invisible when things work. That invisibility is the point: the 997 layer is infrastructure, like dial tone. You notice it only by its absence — which is exactly why your EDI platform, not your team, should be the one listening for it.

One operational note for new EDI teams: keep 997 handling out of your ERP entirely. Acknowledgments are transport plumbing, not business events; your ERP cares that the order arrived, not that interchange 000000412's control numbers reconciled. EDISQ keeps that layer in the platform — automatic, both directions, within minutes — so what reaches your business system is business.

The transaction glossary covers the rest of the X12 catalog the same way: what each document is, when it moves, and what actually matters inside it.

FAQ