X12 transaction guide · Acknowledgments

EDI 824 Application Advice

The X12 document a receiver sends to report business-level errors or rejections in a document it received.

Sent by: Receiver of a document (often a retailer or OEM)
Received by: Original sender (often a supplier)
Standard: ANSI ASC X12
EDIFACT equivalent: APERAK

What is an EDI 824?

The EDI 824 Application Advice is the ANSI X12 transaction set a receiver uses to report the results of processing a document in its business application. Unlike the 997, which checks syntax, the 824 reports business problems, such as a ship notice that references an unknown purchase order or an invoice with invalid data, and can indicate whether a document was accepted, accepted with errors or rejected.

Retailers, automotive manufacturers and other large buyers use the 824 to give suppliers specific feedback. Suppliers that monitor 824s and act on them quickly can fix problems before they affect receiving, compliance scores or payment.

How to read this diagram: the top row shows who sends the 824, to whom, and which documents usually come before and after it. The lower part shows what X12 release 004010 itself requires: the envelopes around the 824 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

Reporting errors in advance ship notices
Rejecting invoices that fail business validation
Notifying suppliers of data problems in other inbound documents

Where it fits in the document flow

Usually follows 856 Advance Ship Notice 810 Invoice

This document 824 Application Advice

Structure

Key segments in the 824

The segments most implementations use, described in plain language. The last column shows what X12 release 004010 itself requires: "Required" marks a segment the standard requires in every 824; "Optional, common" marks a segment the standard leaves optional, or that sits in an optional loop, but that implementations often use. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, makes some optional segments mandatory and restricts the values, and requirements can differ between releases. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

Segment	Name	What it carries	In X12 004010
BGN	Beginning Segment	Purpose code, reference number and date of the application advice.	Required
N1 loop	Party Identification	Parties involved, such as the supplier being notified.	Optional, common
OTI	Original Transaction Identification	Identifies the original document, its status (accepted or rejected) and its reference numbers.	Required
TED	Technical Error Description	Error code and free-form description of the problem.	Optional, common

Example

Sample EDI 824

The receiver reports that the transaction referenced by bill of lading BOL123456 was rejected (TR). TED reports the reason as missing data (007) with a free-form description.

Illustrative data only, not tied to one X12 release or trading partner. The interchange (ISA/IEA) and functional group (GS/GE) envelopes are omitted for readability.

ST*824*0001~
BGN*00*AA1001*20261022~
N1*SU*Example Supplier~
OTI*TR*BM*BOL123456~
TED*007*Carton label data missing~
SE*6*0001~

The sample is the same one shown above, with a note beside each segment the first time it appears. Segment IDs are highlighted at the start of each line; the fields after them are separated by asterisks, and each segment ends with a tilde.

Expand diagram Download SVG

Avoid problems