EDI 997 Functional Acknowledgment: What It Confirms
A receipt for an EDI document: it confirms the document arrived and could be read, or reports why it couldn’t.
- Document
- X12 997: Functional Acknowledgment
- Sent by
- Whoever received a document
- Sent to
- Whoever sent it
- In NetSuite
- None; tracked in the EDI provider or integration log
(01)What it is
The 997 is sent back automatically for most EDI documents. It says that a group of documents arrived and passed basic checks, or that some were rejected for errors in their structure.
It does not mean the other side agrees with the content. A 997 for an invoice says the invoice was readable, not that it will be paid. Its absence is the warning sign: if no 997 comes back, the partner may never have received the document.
(02)What it carries
- 01Which document group it acknowledges
- 02Accepted, accepted with errors, or rejected
- 03Error details for documents that failed checks
In plain language. Each trading partner’s implementation guide sets the exact fields it requires.
(03)Where it fits
Documents usually exchanged before and after the 997.
(04)In NetSuite
The 997 usually never reaches NetSuite. The EDI provider or integration tracks it, and the useful part is an alert: a document with no 997 after a set time, or a rejected 997, should notify someone before a deadline is missed.
(05)Common mistakes
- 01Not monitoring for missing 997s, so a failed ASN is discovered only when the chargeback arrives.
- 02Treating a 997 as business acceptance of an order or invoice.
(06)Questions
What is an EDI 997?
The EDI 997 is the X12 functional acknowledgment: an automatic receipt confirming that EDI documents were received and could be read, or listing errors.
What is the difference between a 997 and a 999?
Both acknowledge receipt. The 999 implementation acknowledgment also checks the document against an implementation guide and is used mostly in healthcare; retail and logistics mostly use the 997.