X12 transaction code
EDI 824 Application Advice (X12 824)
EDI 824 is the X12 Application Advice transaction set, used when a receiving application reports processing results. The receiver of the original document, commonly a buyer or retailer that has validated a supplier's invoice or shipment document, sends the 824 back to the original sender.
- Standard
- X12
- Code
- 824
- Partner references
- 28
At a glance
EDI 824 at a glance
What the 824 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 824 Application Advice |
|---|---|
| Business record | Application validation result |
| Who sends it to whom | The receiver of the original document, commonly a buyer or retailer that has validated a supplier's invoice or shipment document, sends the 824 back to the original sender. |
| When it is sent | 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. |
| Match on | Original document reference, error location and response status |
| Partner references | 28 trading partners in this directory |
| Related documents | X12 850 Purchase Order, X12 856 Ship Notice/Manifest, X12 810 Invoice |
Key segments in an EDI 824
The business segments that appear in at least half of the 53 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BGN | Beginning Segment | To indicate the beginning of a transaction set. | 53 of 53 |
| OTI | Original Transaction Identification | To identify the edited transaction set and the level at which the results of the edit are reported, and to indicate the accepted, rejected, or accepted-with-change edit result. | 53 of 53 |
| TED | Technical Error Description | To identify the error and, if feasible, the erroneous segment, or data element, or both. | 53 of 53 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 44 of 53 |
Stacksync connects EDI documents such as the X12 824 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 824 mapping and validation
X12 824 Application Advice is used when a receiving application reports processing results. Preserve original document reference, error location and response status so the application validation result in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | application validation result original document reference, error location and response status |
|
| Update the receiving system | Processing the application validation result ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the application validation result Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 856 Ship Notice/Manifest
shipment notice (ASN): an order ships, before the goods arrive.
- X12 810 Invoice
accounts-receivable or accounts-payable invoice: a bill is ready for the buyer to process.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a receiving application reports processing results. Name the operational owner of the application validation result and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map original document reference, error location and response status. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic application validation result data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful application validation result processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 824 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic application validation result data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out application validation result without processing it twice.
Document structure
X12 824 Application Advice at the element level
The X12 824 reference contains 30 segment entries and 145 data elements; 50 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Find your trading partner for X12 824
28 partners, 53 channels. Choose a channel to inspect its listed document reference and implementation context.
- 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
Catalog breakdown
Where X12 824 Application Advice appears in this catalog
The largest groups of classified 824 catalog entries are in retail, grocery & food and agriculture.
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
EDI 824 questions
What is an EDI 824?
EDI 824 is the X12 Application Advice transaction set. Trading partners use it when a receiving application reports processing results. It carries the data for the application validation result, and your system matches it on original document reference, error location and response status.
Who sends an EDI 824 and who receives it?
The receiver of the original document, commonly a buyer or retailer that has validated a supplier's invoice or shipment document, sends the 824 back to the original sender. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 824 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 824?
Across 53 partner document references listed here, the business segments that appear most often include BGN (Beginning Segment), OTI (Original Transaction Identification), TED (Technical Error Description), N1 (Party Identification). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 824 and EDI 850?
The 824 carries the application validation result and is used when a receiving application reports processing results. The 850 carries the purchase order or sales order and is used when a buyer places an order.
What should I map for X12 824?
Start with original document reference, error location and response status and the target application validation result. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 824 error handling?
Return an error for one line and associate it with that line rather than rejecting unrelated records. Keep application acceptance distinct from transport receipt and syntax acknowledgment. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 824?
The directory on this page links 28 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
