---
title: "EDI 824 Application Advice: X12 824 Guide | Stacksync"
description: "EDI 824 is the X12 Application Advice, used when a receiving application reports processing results. See key segments (BGN, OTI, TED) and mapping checks."
canonical: https://www.stacksync.com/edi/x12/824-application-advice
last_modified: 2026-09-29
---

X12 transaction code

# EDI 824 Application Advice (X12 824)

> For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md

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

[Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi)

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.

**X12 824 Application Advice summary**

|  |  |
| --- | --- |
| 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](https://www.stacksync.com/edi/x12/850-purchase-order), [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest), [X12 810 Invoice](https://www.stacksync.com/edi/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](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/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.

**Map records and test the business result**

| 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 | Define which combination of original document reference, error location and response status identifies one business record, its lines and any later revision. |
| Update the receiving system | **Processing the application validation result** ID assigned by the receiving system and processing result | 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. |
| Check the processing result | **Processing status for the application validation result** Original document reference and matching response | Reconcile the application validation result with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. |

### 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](https://www.stacksync.com/edi/x12/850-purchase-order)

  **purchase order or sales order:** a buyer places an order.
- [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest)

  **shipment notice (ASN):** an order ships, before the goods arrive.
- [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice)

  **accounts-receivable or accounts-payable invoice:** a bill is ready for the buyer to process.

### Implementation steps

1. #### 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.
2. #### 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.
3. #### 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.
4. #### 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.

### Related documents and resources

- [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order)
- [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest)
- [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice)
- [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook)
- [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist)

**Sources.** Sources reviewed 2026-09-15.

- [X12 transaction-set directory](https://x12.org/products/transaction-sets)
- [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/)

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

**Segments with elements marked mandatory in this reference**

| 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 |

Key identifiers in 824

- 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)](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service)

  [AAFES](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service/aafes/x12-824-application-advice)
- [Affiliated Foods Inc.](https://www.stacksync.com/edi/affiliated-foods)

  [Affiliated Foods Inc. (Amarillo Texas)](https://www.stacksync.com/edi/affiliated-foods/affiliated-foods-inc-amarillo-texas/x12-824-application-advice)
- [Albertsons (Safeway)](https://www.stacksync.com/edi/albertsons-safeway)

  [Safeway](https://www.stacksync.com/edi/albertsons-safeway/safeway/x12-824-application-advice)
- [Amazon](https://www.stacksync.com/edi/amazon)

  [Amazon Retail - US](https://www.stacksync.com/edi/amazon/amazon-retail-us/x12-824-application-advice)
- [ASUSTeK Computer Inc. (dba ASUS)](https://www.stacksync.com/edi/asus)

  [ASUS](https://www.stacksync.com/edi/asus/asus/x12-824-application-advice)
- [AT&T Inc.](https://www.stacksync.com/edi/att)

  [AT&T (Legacy ISA ID: 108024050NHP)](https://www.stacksync.com/edi/att/at-t-legacy-isa-id-108024050nhp/x12-824-application-advice) [AT&T (New ISA ID: 108024050B2B)](https://www.stacksync.com/edi/att/at-t-new-isa-id-108024050b2b/x12-824-application-advice)
- [Burlington Coat Factory](https://www.stacksync.com/edi/burlington-coat-factory)

  [Burlington Coat Factory](https://www.stacksync.com/edi/burlington-coat-factory/burlington-coat-factory/x12-824-application-advice)
- [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway)

  [Canadian National Railway](https://www.stacksync.com/edi/canadian-national-railway/canadian-national-railway/x12-824-application-advice)
- [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway)

  [Canadian Pacific Railway](https://www.stacksync.com/edi/canadian-pacific-railway/canadian-pacific-railway/x12-824-application-advice)
- [COFC](https://www.stacksync.com/edi/cofc)

  [COFC](https://www.stacksync.com/edi/cofc/cofc/x12-824-application-advice)
- [Costco](https://www.stacksync.com/edi/costco)

  [Costco Wholesale (Canada)](https://www.stacksync.com/edi/costco/costco-wholesale-canada/x12-824-application-advice) [Costco Merchandise US - Direct (IBM) - NEW](https://www.stacksync.com/edi/costco/costco-merchandise-us-direct-ibm-new/x12-824-application-advice) [Costco Merchandise Canada - Direct (IBM)(OLD)](https://www.stacksync.com/edi/costco/costco-merchandise-canada-direct-ibm-old/x12-824-application-advice) [Costco Merchandise US - Direct via IBM VAN (OLD)](https://www.stacksync.com/edi/costco/costco-merchandise-us-direct-via-ibm-van-old/x12-824-application-advice) [Costco (ISA: 12/2068288100)](https://www.stacksync.com/edi/costco/costco-isa-12-2068288100/x12-824-application-advice) [Costco Wholesale Canada](https://www.stacksync.com/edi/costco/costco-wholesale-canada-2/x12-824-application-advice) [Costco Merchandise Canada - Direct (via IBM)(NEW)](https://www.stacksync.com/edi/costco/costco-merchandise-canada-direct-via-ibm-new/x12-824-application-advice)
- [CPKC (formerly Kansas City Southern)](https://www.stacksync.com/edi/kansas-city-southern)

  [Kansas City Southern](https://www.stacksync.com/edi/kansas-city-southern/kansas-city-southern/x12-824-application-advice)
- [CVS](https://www.stacksync.com/edi/cvs)

  [CVS](https://www.stacksync.com/edi/cvs/cvs/x12-824-application-advice) [CVS (Legacy ISA ID: CVS)](https://www.stacksync.com/edi/cvs/cvs-legacy-isa-id-cvs/x12-824-application-advice) [CVS (Legacy ISA ID: 001786664)](https://www.stacksync.com/edi/cvs/cvs-legacy-isa-id-001786664/x12-824-application-advice) [CVS (Legacy ISA ID: CVSD)](https://www.stacksync.com/edi/cvs/cvs-legacy-isa-id-cvsd/x12-824-application-advice)
- [Ford Motor Company](https://www.stacksync.com/edi/ford-motor-company-sds)

  [Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)](https://www.stacksync.com/edi/ford-motor-company-sds/ford-motor-company-customer-service-division-north-america-supplier-direct-ship-sds/x12-824-application-advice)
- [Fred Meyer Group](https://www.stacksync.com/edi/krogerfred-meyer-group)

  [Fred Meyer Group](https://www.stacksync.com/edi/krogerfred-meyer-group/fred-meyer-group/x12-824-application-advice)
- [Hudson's Bay](https://www.stacksync.com/edi/hudsons-bay)

  [Hudson's Bay](https://www.stacksync.com/edi/hudsons-bay/hudson-s-bay/x12-824-application-advice)
- [JCPenney](https://www.stacksync.com/edi/jcpenney)

  [JCPenney (Accounting (All Business Types)) (824)](https://www.stacksync.com/edi/jcpenney/jcpenney-accounting-all-business-types-824/x12-824-application-advice)
- [Joann Stores](https://www.stacksync.com/edi/joann-stores)

  [Joann Stores](https://www.stacksync.com/edi/joann-stores/joann-stores/x12-824-application-advice)
- [John Deere](https://www.stacksync.com/edi/john-deere)

  [John Deere (Thibodaux -T8) (ISA ID: 008473506)](https://www.stacksync.com/edi/john-deere/john-deere-thibodaux-t8-isa-id-008473506/x12-824-application-advice) [John Deere (AG) (ISA ID: 149825353)](https://www.stacksync.com/edi/john-deere/john-deere-ag-isa-id-149825353/x12-824-application-advice) [John Deere (SP) (ISA ID: 557074379SP)](https://www.stacksync.com/edi/john-deere/john-deere-sp-isa-id-557074379sp/x12-824-application-advice) [John Deere (Engines) (ISA ID: 021688858)](https://www.stacksync.com/edi/john-deere/john-deere-engines-isa-id-021688858/x12-824-application-advice) [John Deere (ISA ID: 249619198)](https://www.stacksync.com/edi/john-deere/john-deere-isa-id-249619198/x12-824-application-advice) [John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773)](https://www.stacksync.com/edi/john-deere/john-deere-via-saicits-1b-worldwide-logistics-isa-id-156471773/x12-824-application-advice) [John Deere (Kernersville) (ISA ID: 557074379)](https://www.stacksync.com/edi/john-deere/john-deere-kernersville-isa-id-557074379/x12-824-application-advice) [John Deere (M3) (ISA ID: 812912349)](https://www.stacksync.com/edi/john-deere/john-deere-m3-isa-id-812912349/x12-824-application-advice) [John Deere (Dubuque and Davenport) (ISA ID: 833123370)](https://www.stacksync.com/edi/john-deere/john-deere-dubuque-and-davenport-isa-id-833123370/x12-824-application-advice) [John Deere (Reman- SE) (ISA ID: 010678766)](https://www.stacksync.com/edi/john-deere/john-deere-reman-se-isa-id-010678766/x12-824-application-advice)
- [John Deere Mexico](https://www.stacksync.com/edi/john-deere-mexico)

  [John Deere (Mexico)](https://www.stacksync.com/edi/john-deere-mexico/john-deere-mexico/x12-824-application-advice)
- [Kroger](https://www.stacksync.com/edi/kroger)

  [Peyton's Group (a Kroger Division)](https://www.stacksync.com/edi/kroger/peyton-s-group-a-kroger-division/x12-824-application-advice)
- [Kroger Manufacturing](https://www.stacksync.com/edi/kroger-manufacturing)

  [Kroger Manufacturing](https://www.stacksync.com/edi/kroger-manufacturing/kroger-manufacturing/x12-824-application-advice)
- [Kroger Modernized Systems](https://www.stacksync.com/edi/kroger-modernized-systems)

  [Kroger Modernized Systems](https://www.stacksync.com/edi/kroger-modernized-systems/kroger-modernized-systems/x12-824-application-advice)
- [Norfolk Southern](https://www.stacksync.com/edi/norfolk-southern)

  [Norfolk Southern](https://www.stacksync.com/edi/norfolk-southern/norfolk-southern/x12-824-application-advice)
- [Saks Fifth Avenue & Saks OFF 5th](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th)

  [Saks Fifth Avenue & Saks OFF 5th - Canada (850 and 824 only)](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th/saks-fifth-avenue-saks-off-5th-canada-850-and-824-only/x12-824-application-advice) [Saks Fifth Avenue & Saks OFF 5th - US (850 and 824)](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th/saks-fifth-avenue-saks-off-5th-us-850-and-824/x12-824-application-advice)
- [Starbucks Coffee Company](https://www.stacksync.com/edi/starbucks)

  [Starbucks Coffee Company (ISA ID: SBUXCP)](https://www.stacksync.com/edi/starbucks/starbucks-coffee-company-isa-id-sbuxcp/x12-824-application-advice)
- [United Natural Foods, Inc. (UNFI)](https://www.stacksync.com/edi/united-natural-foods-inc-unfi)

  [United Natural Foods (UNFI) US](https://www.stacksync.com/edi/united-natural-foods-inc-unfi/united-natural-foods-unfi-us/x12-824-application-advice) [United Natural Foods via IBMSterling](https://www.stacksync.com/edi/united-natural-foods-inc-unfi/united-natural-foods-via-ibmsterling/x12-824-application-advice) [UNFI Conventional (Legacy Supervalu)](https://www.stacksync.com/edi/united-natural-foods-inc-unfi/unfi-conventional-legacy-supervalu/x12-824-application-advice)
- [Walmart](https://www.stacksync.com/edi/walmart)

  [Walmart US (Goods for Resale)](https://www.stacksync.com/edi/walmart/walmart-us-goods-for-resale/x12-824-application-advice) [Walmart Canada](https://www.stacksync.com/edi/walmart/walmart-canada/x12-824-application-advice) [Sam's Club](https://www.stacksync.com/edi/walmart/sam-s-club/x12-824-application-advice) [Walmart Drop Ship Vendor via SPS](https://www.stacksync.com/edi/walmart/walmart-drop-ship-vendor-via-sps/x12-824-application-advice)

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

Partner entries with the most listed channels

- [John Deere](https://www.stacksync.com/edi/john-deere)
- [Costco](https://www.stacksync.com/edi/costco)
- [CVS](https://www.stacksync.com/edi/cvs)
- [Walmart](https://www.stacksync.com/edi/walmart)
- [United Natural Foods, Inc. (UNFI)](https://www.stacksync.com/edi/united-natural-foods-inc-unfi)
- [AT&T Inc.](https://www.stacksync.com/edi/att)
- [Saks Fifth Avenue & Saks OFF 5th](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th)
- [AAFES (Army and Air Force Exchange Service)](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service)

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.

[Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)
