ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 824 — Application Advice

The 824 is the application-level acknowledgment: a business response that says "I received and interpreted, here is what I accept, what I reject, and why" — beyond the simple syntactic check of the 997.

Purpose

The 824 is used to respond to a received transaction when the sender / receiver pair does not have a dedicated business acknowledgment — for instance, an 855 for an 850 or a 277 for an 837. It carries three pieces of information: the identity of the original document (ST control number, type, date), the verdict (accepted, accepted with change, rejected, partially accepted) and the list of anomalies detected at transaction, segment or element level.

The 824 differs from the 997: the 997 is a syntactic acknowledgment confirming the document was parsed correctly; the 824 goes further and conveys a business verdict (the PO was received but the referenced item is not in catalogue, for example).

Envelope structure

The 824 travels in a functional group AG (Advice). Didactic example rejecting a PO line, in release 004010:

x12 example-824.x12 
ISA*00*          *00*          *ZZ*ACMEVENDOR    *ZZ*ACMERETAIL    *260514*1500*U*00401*000000824*0*P*>~
GS*AG*ACMEVENDOR*ACMERETAIL*20260514*1500*1*X*004010~
ST*824*0001~
BGN*11*ADV-2026-555*20260514*1500~
N1*BY*ACME RETAIL CO*92*0001~
N1*VN*ACME VENDOR INC*92*V-9087~
OTI*TR*PO*PO78901**20260513*004010*850*1~
TED*15*Invalid item identifier*PO1*5*012345678999~
SE*7*0001~
GE*1*1~
IEA*1*000000824~

The BGN opens the document with an advice identifier and issue date. The N1 segments identify buyer and supplier. The OTI (Original Transaction Identification) points at the relevant transaction — here an 850 received on 20260513 with control number 1. The TED (Technical Error Description) segments list the errors with code and human-readable message, and identify the segment and element at fault.

Common segments

  • Header — ST, BGN (Beginning Segment).
  • Parties — N1 loop (BY, VN, FR, TO depending on context).
  • Reference to original — OTI loop (Original Transaction Identification), one per acknowledged document.
  • Error detail — TED (Technical Error Description) nested in the OTI loop, with error code, segment, element and description.
  • Summary — SE.

Common pitfalls

  • Confusion with 997 / 999: some integrators emit an 824 for syntactic errors; the X12 spec asks for the 824 to be reserved for application-content errors.
  • Incomplete OTI: without the exact ST control number of the original document, automatic reconciliation on the sender side fails.
  • Proprietary error codes: TED01 accepts a standard X12 list; some retail partners define proprietary codes that must be documented in the Trading Partner Implementation.

Documentation

The code 824 and the name Application Advice are public and listed on x12.org/products/transaction-sets. Full TED01 error-code lists and the detailed loop structure are in the licensed X12 Implementation Guide (TR3).