EDI basics · November 1, 2026

997 vs 999: Which Acknowledgment, When

The difference between the 997 Functional Acknowledgment and the 999 Implementation Acknowledgment — where each is used, what each proves, and reconciliation.

Every X12 transmission deserves a receipt. The question is which receipt — and the answer splits cleanly along industry lines. Retail and supply chain run on the 997 Functional Acknowledgment; healthcare mandates the 999 Implementation Acknowledgment. They look similar on the wire, but they answer different questions, and knowing which question your partner is answering keeps you from over-reading an "accepted."

What the 997 says

The 997 reports whether a received functional group parsed correctly against the X12 standard itself: segments in valid order, elements of valid types and lengths, control numbers consistent, counts matching. It answers at the group and transaction-set level — accepted, accepted with errors, or rejected — with AK segments pinpointing the offending segment and element when something fails.

What the 997 cannot say is whether the document made business sense. An 850 with a valid structure but an item number you've never heard of gets a clean 997. The 997 is the postal receipt, not the customer's signature. Business-level rejection arrives separately — most formally as an 824 Application Advice, less formally as a portal flag or a buyer's email. The full anatomy is in our 997 guide.

What the 999 adds

The 999 Implementation Acknowledgment reports conformance against a specific implementation guide, not just the base standard. X12 defines what a transaction may contain; an implementation guide defines what a particular program requires — mandatory segments the standard calls optional, restricted code lists, situational rules ("if this element is present, that one is required").

The 999's IK segments can therefore reject a transmission that is perfectly valid X12 but violates the guide: a situational segment omitted, a code outside the allowed subset. That extra layer is exactly what a regulated exchange needs, which is why the 999 lives where implementation guides carry legal weight.

Retail uses 997, healthcare mandates 999

The split in practice:

  • Retail and supply chain: the 997, overwhelmingly. Purchase orders, ASNs, invoices, warehouse documents — partners exchange 997s automatically in both directions, and companion-guide conformance is enforced by the partner's business validation rather than by the acknowledgment. A few programs have adopted the 999, but if you trade with retailers and distributors, plan on the 997.
  • Healthcare: the 999, as a rule. HIPAA transactions — 837 claims, 835 remittances, 270/271 eligibility — are governed by federal implementation guides, and clearinghouses and payers acknowledge with the 999 because guide conformance is the whole point. (These HIPAA sets run in the 5010 world; supply-chain EDI commonly trades 4010 or 5010.)

If a partner's spec says "997," send and expect 997s. If it says "999," your acknowledgment logic needs to parse IK-level detail. Do not send both, and do not acknowledge acknowledgments — neither document is itself acknowledged.

Reconciliation: the part that actually protects you

Whichever flavor you trade, the acknowledgment is only useful if something checks it. Solid reconciliation looks the same in both worlds:

  1. Every outbound document creates an expectation — an ack due within the partner's window (minutes to hours, commonly same-day).
  2. Inbound acks match against expectations by control number, closing them out.
  3. Unacknowledged documents escalate automatically — retransmit, then alert. A missing ack means your document may as well not exist; discovering that at invoice time is how "we never received your ASN" chargebacks are born.
  4. Rejections route to a human with the AK/IK detail attached, so the fix targets the actual segment rather than starting an investigation.

And in both worlds, remember the ceiling: an accepted 997 or 999 proves receipt and (for the 999) guide conformance — never business acceptance. Watch for the 824 or its informal equivalents.

EDISQ handles the retail side of this automatically: 997s generated and transmitted in both directions within minutes, expectations tracked, and unacknowledged documents surfaced before they age into disputes — all inside the per-document price on the pricing page, with the first 25 documents each month free.

FAQ

What is the difference between a 997 and a 999?

Both acknowledge a received EDI transmission. The 997 reports syntax-level results against the X12 standard. The 999 goes further, reporting conformance against a specific implementation guide — which segments and codes the guide requires, not just what X12 allows.

Who uses the 999?

Healthcare, primarily. HIPAA transactions (837 claims, 835 remittances, 270/271 eligibility) are acknowledged with the 999 because conformance to the HIPAA implementation guides is what matters. Retail and supply-chain EDI overwhelmingly uses the 997.

Does a 997 acceptance mean my document was OK?

Only syntactically. The partner's business application can still reject it — wrong item numbers, missing required references — typically surfaced later as an 824 Application Advice, a portal notice, or a phone call.

What should I do about unacknowledged documents?

Treat them as undelivered. Reconcile expected acknowledgments continuously and retransmit anything unacknowledged within your partner's window — a missing ack discovered at invoice time is a chargeback with a long fuse.