The EDI 997 Functional Acknowledgment confirms only that a transmission parsed as valid syntax, not that the retailer accepted the content. The EDI 824 Application Advice reports that separately, later, and only where a retailer chooses to send one. A clean 997 with no follow-up 824 is not proof of acceptance.
Based on the public X12 997 and 824 transaction-set structure (Stedi's EDI reference), Kroger's public EDI portal documentation, and LearnEDI.org's acknowledgment references, August 2026. Segment names and the two-document structure are the public standard; which retailers run an 824 program at all is implementation-specific and not universal.
You checked the acknowledgment log an hour after the invoice went out. Clean 997, accepted. As the supply chain or finance lead running EDI at a $10M–$500M CPG supplier, that’s the signal you were trained to trust. So you closed the ticket and moved to the next shipment. Three weeks later a deduction shows up on the remittance for that same invoice, and nothing in your system explains why.
You pull the transmission log again. Still accepted. You check the PO, the ship date, the pack count. Everything visible from your side looks fine, but the check is short by a line item anyway. It isn’t a one-time thing either. It’s the same deduction pattern eating into margin month after month, one invoice at a time. It’s rarely clear to your team when it actually went wrong.
It went wrong because a 997 only answers one question: did the file parse. It says nothing about whether the retailer’s system accepted what the file described, the invoice total, the PO reference, the shipment quantity. A second document, the 824, is built to answer that second question, but a meaningful number of retailers never send one. Where there’s no 824, the deduction on the remittance is the only notice you get. It arrives weeks after the fact, with nothing on it pointing back to the warning that never arrived. That’s the 997 false-positive problem this piece walks through, and it’s exactly the kind of gap a data-bridge assessment is built to find.
What is a 997, and what does it actually check?
In practice, a 997 isn’t a document anyone reads. It shows up as a status flag, “Accepted” or a green checkmark, in your EDI translator log or your VAN portal. Nearly every retailer running standard EDI generates one automatically, so if you trade EDI at all, you’re already getting these back on every transmission.
What it’s actually checking is syntax, and only syntax: right segments, right order, right delimiters, envelope counts that reconcile, per the X12 997 transaction-set structure. It’s a mechanical response, generated automatically, usually within minutes of the original transmission going out.
It has no opinion on whether an invoice total is correct, whether a PO number is still open, or whether you’re billing for a quantity the retailer’s system will actually recognize. Those are business-content questions, and the 997 doesn’t ask them.
An AK9 segment at the end of the 997 rolls up the result: accepted, accepted with errors, or rejected, but purely at the syntax level. A transmission can sail through AK9 as fully accepted and still describe an invoice total that’s wrong, a shipment quantity that doesn’t match the PO, or a reference the retailer has never heard of.
What is an 824, and what does it actually check?
Unlike the 997, an 824 is worth actually opening when one arrives. It’s the one document in this pair that says something specific about what went wrong. The EDI 824 Application Advice is where a retailer, if it sends one, reports on the content. It arrives after the 997, once the retailer’s system has actually tried to process what the document said: minutes later or overnight, depending on the retailer’s batch cycle. Not every retailer runs this program. Some, like Kroger below, publish a detailed one. Others skip it and let a mismatch surface only as a deduction, covered further down.
Every 824 carries an OTI segment linking it back to the original document, the 850, 810, or 856 it’s responding to. OTI01 carries the outcome, and it only has three values: TA (accepted, no content errors), TE (accepted with error, it’ll process but something’s flagged), or TR (rejected outright).
Where something’s wrong, the detail lives in the TED segment, Technical Error Description: a numeric error code, free text explaining the specific problem, and a pointer to which part of the original document triggered it. Kroger’s public EDI portal is a useful visible example of how far a retailer’s own error catalog extends past that base structure, covered in more depth in the EDI 824 rejection codes entry. The point here is narrower: the 824 is the only one of the two documents that says anything about content at all.
How do the 997 and 824 compare side by side?
| EDI 997 | EDI 824 | |
|---|---|---|
| What it validates | Syntax: segments, structure, delimiters, envelope counts | Content: invoice totals, PO references, quantities the retailer’s system actually recognizes |
| When it arrives | Automatically, usually within minutes | After content processing, minutes to overnight |
| Is it universal | Effectively yes, most trading partners generate one | No. Many retailers run no 824 program at all |
| What to do on rejection | Fix the envelope: malformed segment, wrong delimiter, bad control number, and retransmit | Fix the underlying document (invoice, ASN, PO response) and resend it, not just the acknowledgment |
| What a clean result actually proves | The transmission was structurally valid. Nothing about acceptance | The content was accepted, flagged, or rejected, on record, in writing |
What does a 997 false positive look like in practice?
A supplier transmits an 810 invoice. The 997 comes back accepted within the hour. The EDI team marks it done and moves on, because that’s what a clean acknowledgment is supposed to mean.
The invoice’s line-item totals don’t actually sum to the header total, a four-hundred-dollar gap left by a discount applied at the header level that never got distributed down to the lines. The retailer’s system catches it during content processing and sends back an 824 with OTI01 = TR, TED01 = 010 (Total Out of Balance).
It rarely gets read. It gets filed in the same EDI mailbox as routine 997s, with no special handling, and stays there.
Thirty-plus days later, a deduction code appears on the remittance. By then the shipment is old news, and rarely does anyone connect the line item to the invoice, the invoice to the 824, or the 824 to the original discount error. The 997 was clean. The 824 said exactly what was wrong, in writing, over a month before the deduction landed. But the second document rarely gets watched once the first one feels like the answer.
Monitoring rules: which acknowledgment gaps to alert on
Treating a 997 or an 824 as something to read by hand, instead of routed automatically, is how a written warning turns into an unexplained deduction weeks later. The fix is routing, not diligence.
- Alert on missing 997s first. A transmission with no functional acknowledgment at all, not even rejected, usually means it never arrived. That’s a connectivity or VAN problem worth catching same-day.
- Where an 824 program exists, branch on OTI01 automatically. TR obviously needs attention, but TE needs a queue too, not a shrug. It’s an acceptance carrying a live error that most teams read as a pass.
- Key every 824 exception to the OTI segment’s reference back to the source document. That way, a flagged invoice or ASN shows up next to the transaction it came from, instead of as an orphaned message in a shared inbox.
- Set an age-based alert on unresolved 824 exceptions. One left untouched for more than a few business days is exactly the kind of gap that becomes an unexplained remittance line a month out.
What retailers with no 824 program do instead
Some retailers skip the application-advice step entirely, per LearnEDI’s overview of the 824’s role. Content validation still happens somewhere in their system. It just never gets reported back as a document. If something doesn’t match, the system deducts against the remittance directly, with no intermediate warning at all.
For a supplier trading with one of those retailers, the 997 really is the only acknowledgment that will ever arrive, clean or not. It was never built to answer the question, “did this get accepted?” The deduction itself becomes the first and only notice, arriving on the timeline described in how to read a Walmart remittance advice. It shows up weeks after the shipment, with a code that has to be looked up separately to mean anything.
Where that’s the trading relationship you’re in, the Walmart deduction code 22 entry is a worked example of exactly this pattern: a documented quantity mismatch that generated no application advice at all and surfaced only as a shortage claim on the check. The dispute deadline table covers how long you have to act once the deduction lands, by retailer and claim type.
The underlying gap is the same one a data-bridge assessment is built to find: a system that received or generated a clear signal something didn’t match, and never routed it to a person who could act on it. That signal might be an 824 that went unread, or a receiving variance with no acknowledgment trail at all.
The data-bridge calculator gives a rough sense of what that gap is worth before committing to finding it, and the full cost of the manual reconciliation work behind it usually runs past the labor line alone.
If your ERP says shipped and the retailer still deducted, the 997 and 824 are two of the nine checks in the Monday morning deduction triage. The full chain of four quantities from four systems is in the root-cause trace.
Sources
- “EDI 997 Functional Acknowledgment,” Stedi, for AK9 structure and what the 997 does and does not validate.
- “EDI 824 Application Advice,” Stedi, for OTI/TED segment structure and OTI01 code values.
- “824 Application Advice Error Codes,” Kroger EDI Portal, for a real-world example of a retailer-specific error catalog layered on the 824 standard.
- “What’s an EDI 824 Transaction? The Application Advice Document,” LearnEDI.org, for the 997-versus-824 relationship.
Segment names and structure are the public X12 standard. Which retailers run an 824 program, and how they name their own error catalogs, is implementation-specific. If a detail here doesn’t match your own trading partner’s guide, tell us and we’ll correct it.
Frequently Asked Questions
- What's the difference between a 997 and an 824?
- The 997 Functional Acknowledgment confirms a transmission arrived and parsed as valid EDI syntax, nothing about the business content. The 824 Application Advice reports whether that content was actually accepted, once the retailer's system tries to process it. That content might be an invoice total, a PO reference, or a shipment quantity. They answer different questions and neither substitutes for the other.
- If I get a clean 997, does that mean my EDI document was accepted?
- No. It means the envelope was structurally valid, right segments, right order, right delimiters. Whether the retailer's system did anything useful with the content inside is a separate question. Where an 824 exists, it answers that question later. Where it doesn't, the question goes unanswered.
- Do all retailers send an 824?
- No. Some retailers validate content and simply deduct against the remittance if something doesn't match, with no application-advice program at all. Where that's the case, a clean 997 is the only acknowledgment you'll ever get, and it was never designed to tell you what you're using it for.
- Is a rejected 824 the same as a chargeback?
- Not directly. It's a data-validation response, not a deduction. But an 824 rejection that goes uncorrected routinely becomes one. The gap between the two is usually 30 or more days, with nothing on the remittance connecting the eventual deduction back to the written warning that preceded it.
- What should I actually monitor if I only get 997s?
- Watch the receiving and payment signals downstream of the document itself, since there's no earlier warning coming. That means tracking invoice-to-payment variance, unexpected remittance deduction codes, and receiving discrepancies as the de facto acknowledgment, weeks later than an 824 would have told you.
Find out what your deductions are actually costing you.
A 30-minute call with the founder, who will tell you which of the three scans fits your problem, or that none of them do.