To start and identify an interchange of zero or more functional groups and interchange-related control segments
CVS X12 812 Credit/Debit Adjustment
X12 812 (Credit/Debit Adjustment) 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
- 13
- Loops
- 2
- X12 812
- All partners ↗
Transaction context
Where 812 Credit/Debit Adjustment fits on CVS (Legacy ISA ID: CVSD)
- CVS channels
- 4 of 5
- Trading partners
- 17
- Channels
- 26
4 of CVS's 5 channels carry 812
partners across the Stacksync network trade 812
channels network-wide carry 812
Most common alongside 812
The X12 812 is the electronic equivalent of a credit or debit memo. It communicates adjustments to amounts already invoiced, covering events such as over- or under-shipments, returns, price discrepancies, billing errors, and billbacks under trading-partner agreements, so both parties' payables and receivables stay reconciled. It typically flows after the EDI 810 invoice and before the EDI 820 remittance, and it notifies or requests an adjustment rather than moving funds. The 812 flows in both directions: sellers send credit or debit memos to buyers, and buyers such as retailers and distributors send it to suppliers to document deductions and billbacks.
When it fires: A discrepancy is found after invoicing, such as a shortage, return, pricing error, or agreed billback, and one party issues an adjustment against the original invoice.
Common 812 rejection causes
- Adjustments that do not reference the original document, such as the EDI 810 invoice or purchase order number, cannot be matched during deduction reconciliation.
- Free-form text used in place of coded adjustment details prevents automated posting and forces manual review.
- Adjustment reason codes that are invalid or not supported by the receiving trading partner cause rejections and disputed deductions.
Specification summary
X12 812 Credit/Debit Adjustment at the element level
The X12 812 specification defines 22 segments carrying 99 data elements, 44 of which are mandatory.
- Segments
- 22
- Data elements
- 99
- Mandatory elements
- 44
| Segment | Elements | Mandatory |
|---|---|---|
| BCD | 9 | 5 |
| N9 | 3 | 1 |
| PER | 6 | 1 |
| DTM | 2 | 1 |
| SAC | 8 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| CDD | 8 | 2 |
| LIN | 9 | 2 |
Key identifiers in 812
- Date
- Credit/Debit Adjustment Number
- Transaction Handling Code
- Amount
- Credit/Debit Flag Code
- Reference Identification Qualifier
- Contact Function Code
- Date/Time Qualifier
Full segment guideline — 13 segments 2 loops · X12 812 Credit/Debit Adjustment
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 transmit identifying dates and numbers for the transaction set and indicate the monetary value to the receiver of the transaction
To transmit identifying information as specified by the Reference Identification Qualifier
To specify pertinent dates and times
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
N1 Loop Repeat: 200
To identify a party by type of organization, name, and code
To indicate the total monetary amount
CDD Loop
To provide information relative to a line item adjustment
To specify basic item identification data
To specify the physical qualities, packaging, weights, and dimensions relating to the item
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
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 AP Application Advice 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 812 FAQ
Common questions about 812 Credit/Debit Adjustment on the CVS (Legacy ISA ID: CVSD) channel.
What is X12 812 Credit/Debit Adjustment?
X12 812 (Credit/Debit Adjustment) is the EDI transaction set used to exchange credit/debit adjustment data. CVS's CVS (Legacy ISA ID: CVSD) channel requires it from trading partners.
Does CVS CVS (Legacy ISA ID: CVSD) require 812 for trading partners?
Yes, CVS (CVS (Legacy ISA ID: CVSD)) supports X12 812 Credit/Debit Adjustment. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate CVS 812 with Stacksync?
Most companies go live with CVS 812 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other CVS channels accept 812?
X12 812 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.
