To start and identify an interchange of zero or more functional groups and interchange-related control segments
CVS X12 824 Application Advice
X12 824 (Application Advice) is the EDI transaction exchanged between CVS (CVS (Legacy ISA ID: CVSD)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 12
- Loops
- 3
- X12 824
- All partners ↗
Transaction context
Where 824 Application Advice fits on CVS (Legacy ISA ID: CVSD)
- CVS channels
- 4 of 5
- Trading partners
- 28
- Channels
- 53
4 of CVS's 5 channels carry 824
partners across the Stacksync network trade 824
channels network-wide carry 824
Most common alongside 824
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.
When it fires: 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.
Common 824 rejection causes
- Original documents rejected for non-numeric or invalid PO numbers, invalid vendor numbers, or blank invoice numbers and dates.
- Invoice totals that do not match the sum of the detail lines, or invalid currency and warehouse codes.
- Suppliers monitoring only 997s and missing inbound 824 rejections, so business-level failures go uncorrected until a payment or fulfillment dispute surfaces them.
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 |
Key identifiers in 824
- Transaction Set Purpose Code
- Reference Identification
- Date
- Entity Identifier Code
- Name
- Address Information
- Reference Identification Qualifier
- Contact Function Code
Full segment guideline — 12 segments 3 loops · X12 824 Application Advice
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of a transaction set
N1 Loop
To identify a party by type of organization, name, and code
To identify a person or office to whom administrative communications should be directed
OTI Loop
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
To specify identifying information
To specify pertinent dates and times
To indicate the total monetary amount
TED Loop
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To identify the error and, if feasible, the erroneous segment, or data element, or both
Trading partners
3+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
No trading partner matches your search.
Browse the full directory
Trading partners
5+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
PU Purchase Order Change Request Buyer Initiated CR Credit Debit Adjustment PU Purchase Order PL Planning Schedule With Release Capability IN Invoice
No trading partner matches your search.
Browse the full directory
CVS CVS (Legacy ISA ID: CVSD) EDI 824 FAQ
Common questions about 824 Application Advice on the CVS (Legacy ISA ID: CVSD) channel.
What is X12 824 Application Advice?
X12 824 (Application Advice) is the EDI transaction set used to exchange application advice data. CVS's CVS (Legacy ISA ID: CVSD) channel requires it from trading partners.
Does CVS CVS (Legacy ISA ID: CVSD) require 824 for trading partners?
Yes, CVS (CVS (Legacy ISA ID: CVSD)) supports X12 824 Application Advice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate CVS 824 with Stacksync?
Most companies go live with CVS 824 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other CVS channels accept 824?
X12 824 runs on 4 of CVS's 5 channels. Besides CVS (Legacy ISA ID: CVSD), it is accepted on CVS, CVS (Legacy ISA ID: CVS), CVS (Legacy ISA ID: 001786664). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.
Ready to automate your CVS EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
