--- title: "What Is an EDI 824 (Application Advice)?" url: https://www.uncap.com/glossary/edi-824 author: "Denis Dyli" published: 2026-10-28 updated: 2026-10-29 summary: "An EDI 824 is the X12 Application Advice transaction set: the document that reports the results of an application system's data content edits on a transaction set it received. It can report acceptance, rejection, acceptance with change, or partial acceptance or rejection, for a whole functional group, a whole transaction set or any portion of one." --- # What Is an EDI 824 (Application Advice)? > An EDI 824 is the X12 Application Advice transaction set: the document that reports the results of an application system's data content edits on a transaction set it received. It can report acceptance, rejection, acceptance with change, or partial acceptance or rejection, for a whole functional group, a whole transaction set or any portion of one. **EDI 824 (Application Advice)**: An EDI 824 is the X12 Application Advice transaction set: the document that reports the results of an application system's data content edits on a transaction set it received. It can report acceptance, rejection, acceptance with change, or partial acceptance or rejection, for a whole functional group, a whole transaction set or any portion of one. ## How it works X12 defines the 824 by what it reports and where it stops: - Scope. The results of editing can be reported at the functional group, an entire transaction set, or any portion of a transaction set. - Format. Results can be sent in coded or free-form format. - Outcomes. The 824 is designed for reporting the acceptance, rejection, acceptance with change, or partial acceptance or rejection of any transaction set. - Limit. It should not be used in place of a transaction set designed as a specific response to another. X12's own example: a purchase order acknowledgment sent in response to a purchase order. That is why an 855, not an 824, answers an 850. Alongside the EDI 824, X12 has a separate transaction set for one-time communications such as messages, contracts and explanations: the [864 Text Message](/glossary/edi-864), which is meant for people, not for computer processing. ## 824 vs 997 Both come back to the sender, but they check different things. The 997 Functional Acknowledgment indicates the results of the syntactical analysis of the electronically encoded documents, and X12 says that standard does not cover the semantic meaning of the information in the transaction sets. The 824 reports the results of an application system's data content edits. In short, a 997 reports on syntax, and an 824 reports on the data content. ## What it contains X12's published example from its aerospace implementation guide (004010X350) shows an 824 rejecting an 810 Invoice because the unit of measure on invoice line 3 does not match the originating purchase order: - BGN: marks the transaction set as a response, with a reference identification, date and time. - OTI: identifies the transaction being reported on and the result. In the example it is a transaction rejection, pointing to the control number of the 810 Invoice. - REF: a reference number, in the example the invoice number. - TED: the error, as a code plus a message. The example uses the code for "other" and says the item unit of measure in the invoice does not match the purchase order. - RED: where the problem is, in the example invoice line 3. ## Example A supplier sends a 5-line 810 Invoice for $1,250. Line 3, worth $150, bills in eaches while the purchase order ordered in cases. The buyer's application rejects the invoice and returns an 824 that points to line 3. Because the whole transaction is rejected, the full $1,250 waits for the corrected invoice, not just the $150 line. The other four lines, $1,250 minus $150 = $1,100, were correct all along. ## On Shopify EDI purchase orders can reach Shopify through pre-built integrations: Shopify's Winter '26 Edition announced pre-built integrations that sync EDI purchase orders from two EDI providers directly into the admin as draft orders. For other external systems, Shopify's B2B documentation lists three methods: - Direct integrations from the Shopify App Store, for select ERP, accounting and PIM systems. - iPaaS providers that work as intermediaries between Shopify and your external system and handle the data transformation and synchronization. - Custom, API-based integrations, which offer the most flexibility but are more resource intensive. The order record keeps a reference an invoice needs. Shopify's poNumber field holds the purchase order number associated with an order, typically provided by business customers who require a PO number for their procurement, and X12 says an invoice must include a purchase order reference. ## How Uncap helps Uncap's [Shopify EDI integration guide](/post/shopify-edi-integration) tells suppliers to verify that an integration handles all the document types their trading partners require: 850, 855, 856, and 810 at minimum, and some partners also require 846, 860 (Purchase Order Change Request), or 824 (Application Advice). A connector that only handles inbound 850s and outbound 810s leaves acknowledgment and ASN generation as manual steps, which is where chargeback exposure accumulates. ## Related terms - EDI 997 - EDI 810 - EDI 855 - EDI 850 - EDI 860 - EDI (electronic data interchange) ## Sources - X12: 824 Application Advice - X12 EDI Examples: 824 rejecting an 810 Invoice for a line-item error - X12 Transaction Sets ## Frequently asked questions ### What is EDI code 824? 824 is the X12 transaction set number for the Application Advice. It reports whether a received transaction set, or part of one, passed the receiving application's data content edits: accepted, rejected, accepted with change, or partly accepted or rejected. ### What is an EDI 864? The X12 864 Text Message moves messages, contracts, explanations and other one-time communications electronically. X12 says it is meant for people, not for computer processing. ### What is EDI 860 used for? A buyer uses the X12 860 Purchase Order Change Request to request a change to a previously submitted purchase order, or to confirm acceptance of a change the seller initiated or both parties agreed.