Skip to content
Independent EDI conversion and validation software. Retailer names identify interoperability targets; no retailer endorsement is implied.
Shipment Sentry
Start routing

Operational EDI reference

EDI 824 vs 997: Application Advice and Syntax Acknowledgement

Use 997 for X12 syntax handling and 824 for application-level advice without collapsing both into one accepted flag.

Use the free validator See batch and API plans

Direct answer

Direct answer

A 997 Functional Acknowledgement normally reports whether an X12 functional group or transaction set passed syntax checks. An 824 Application Advice reports how an application handled a referenced transaction and can carry business-level errors through OTI and TED. One does not automatically replace the other. Store each response type separately, match its controls or reference, and expose both states in the document timeline.

Why a parser is not enough

The useful unit is not a file that parses; it is a business document with a known decision, an owner, a source trail and a matched downstream response. This page connects the technical structure to that operating workflow.

What the control should check

  1. 01997: parse AK1, AK2, AK5 and AK9.
  2. 02824: parse OTI acceptance code and references.
  3. 03Keep syntax and application status separate.
  4. 04Match both inside the same tenant.
  5. 05Escalate rejection, accepted-with-errors and missing responses.

Working example

997 A = syntax accepted / 824 TE = application accepted with errors

The excerpt is intentionally compact. Use the working validator or authenticated gateway with the complete interchange to obtain a decision.

Failure modes worth catching

  • A transport receipt is mistaken for business acceptance.
  • Control identifiers are regenerated between validation and submission.
  • A warning has no owner and becomes a recurring manual investigation.
  • The document is checked alone even though the truth exists in a purchase order, label or acknowledgement.

Put it into the dispatch workflow

  1. 1Validate the source document before transport.
  2. 2Block deterministic failures and assign every review item.
  3. 3Release with a recorded owner and timestamp.
  4. 4Match functional and application acknowledgements.
  5. 5Reconcile confirmed outcomes back into fixtures and rules.
Use batch validation and acknowledgement tracking

Questions

Implementation answers

Does Shipment Sentry replace my EDI provider?

No. It sits before the existing transport as a validation and evidence sidecar.

What does cleared mean?

The document has no blocking finding in the current rule pack. It is not a guarantee of trading-partner or receiving acceptance.

How are repeat requests kept safe?

The API requires an idempotency key, stores only a token hash, scopes every record to one workspace and rejects reuse with different content.

Sources and limits

Reviewed 2026-07-18. Public references cannot establish every partner-specific rule. Current implementation guides and agreements remain controlling.

Keep investigating

Related EDI controls

View the library
Add an EDI API gate without rebuilding partner operations Connect Business Central records to controlled EDI delivery Send EDI over AS2 without mistaking HTTP success for delivery proof Connect validated invoices to a certified Peppol access point Turn EDI partner testing into a versioned release gate Give EDI users reports that lead back to transaction evidence