X12 transaction code
X12 824 Application Advice
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 824
- Trading partners
- 28
Specification summary
X12 824 Application Advice at the element level
The X12 824 specification defines 30 segments carrying 145 data elements, 50 of which are mandatory.
- Segments
- 30
- Data elements
- 145
- Mandatory elements
- 50
| Segment | Elements | Mandatory |
|---|---|---|
| BGN | 9 | 3 |
| N1 | 6 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| REF | 3 | 1 |
| PER | 9 | 1 |
| OTI | 17 | 3 |
| DTM | 6 | 1 |
| AMT | 3 | 2 |
| QTY | 3 | 1 |
- Transaction Set Purpose Code
- Reference Identification
- Date
- Entity Identifier Code
- Name
- Address Information
- Reference Identification Qualifier
- Contact Function Code
Trading partners that support X12 824
28 partners, 53 channels. Click a channel for the full segment guideline.
- AAFES (Army and Air Force Exchange Service)
- Affiliated Foods Inc.
- Albertsons (Safeway)
- Amazon
- ASUSTeK Computer Inc. (dba ASUS)
- AT&T Inc.
- Burlington Coat Factory
- Canadian National Railway
- Canadian Pacific Railway
- COFC
- Costco
- CPKC (formerly Kansas City Southern)
- CVS
- Ford Motor Company
- Fred Meyer Group
- Hudson's Bay
- JCPenney
- Joann Stores
- John Deere John Deere (Thibodaux -T8) (ISA ID: 008473506)John Deere (AG) (ISA ID: 149825353)John Deere (SP) (ISA ID: 557074379SP)John Deere (Engines) (ISA ID: 021688858)John Deere (ISA ID: 249619198)John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773)John Deere (Kernersville) (ISA ID: 557074379)John Deere (M3) (ISA ID: 812912349)John Deere (Dubuque and Davenport) (ISA ID: 833123370)John Deere (Reman- SE) (ISA ID: 010678766)
- John Deere Mexico
- Kroger
- Kroger Manufacturing
- Kroger Modernized Systems
- Norfolk Southern
- Saks Fifth Avenue & Saks OFF 5th
- Starbucks Coffee Company
- United Natural Foods, Inc. (UNFI)
- Walmart
Usage breakdown
Who trades X12 824 Application Advice
824 is used most heavily in retail, grocery & food and agriculture.
The 824 reports the application-level result of a previously received EDI document: accepted, accepted with errors, or rejected, with detail on what failed. Trading partners require it because a 997 functional acknowledgment confirms syntax only; the 824 is how a receiver tells the sender that an invoice, order, or shipment document failed business validation and must be corrected before it can be processed or paid. Sent by the receiver of the original document, commonly a buyer or retailer that has validated a supplier's invoice or shipment document, back to the original sender. A receiver's application validates an inbound EDI document, most often an invoice, after clean syntax acknowledgment and finds business-level data errors that prevent processing.
By industry
- retail 15 channels
- grocery & food 10 channels
- agriculture 10 channels
- logistics & transport 5 channels
- healthcare & pharma 4 channels
- electronics & technology 3 channels
By network
- Ibmsterling 1 channel
- SPS Commerce 1 channel
- Saicits 1 channel
- Ibm Van Old 1 channel
- IBM 1 channel
FAQ
X12 824 questions
What is X12 824 Application Advice?
X12 824 (Application Advice) is an EDI transaction set defined by ANSI ASC X12 for exchanging application advice between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 28 Stacksync trading partners support this code across 53 channels.
Which trading partners use X12 824?
28 Stacksync partners accept X12 824: AAFES (Army and Air Force Exchange Service), Affiliated Foods Inc., Albertsons (Safeway), Amazon, ASUSTeK Computer Inc. (dba ASUS), AT&T Inc., Burlington Coat Factory, Canadian National Railway, and more. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 824 with my ERP?
Stacksync handles the full X12 824 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
