X12 transaction code
EDI 812 Credit/Debit Adjustment (X12 812)
EDI 812 is the X12 Credit/Debit Adjustment transaction set, used when a financial difference needs a documented adjustment. 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.
- Standard
- X12
- Code
- 812
- Partner references
- 17
At a glance
EDI 812 at a glance
What the 812 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 812 Credit/Debit Adjustment |
|---|---|
| Business record | Credit or debit adjustment |
| Who sends it to whom | 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 is sent | 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. |
| Match on | Adjustment reference, original invoice and reason |
| Partner references | 17 trading partners in this directory |
| Related documents | X12 810 Invoice, X12 820 Payment Order/Remittance Advice |
Key segments in an EDI 812
The business segments that appear in at least half of the 26 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 |
|---|---|---|---|
| BCD | Beginning Credit/Debit Adjustment | To transmit identifying dates and numbers for the transaction set and indicate the monetary value to the receiver of the transaction. | 26 of 26 |
| N1 | Name | To identify a party by type of organization, name, and code. | 26 of 26 |
| CDD | Credit/Debit Adjustment Detail | To provide information relative to a line item adjustment. | 26 of 26 |
| LIN | Item Identification | To specify basic item identification data. | 26 of 26 |
| N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 22 of 26 |
| SAC | Service, Promotion, Allowance, or Charge Information | To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge. | 20 of 26 |
| DTM | Date/Time Reference | To specify pertinent dates and times. | 17 of 26 |
| N3 | Address Information | To specify the location of the named party. | 16 of 26 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 16 of 26 |
Stacksync connects EDI documents such as the X12 812 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 812 mapping and validation
X12 812 Credit/Debit Adjustment is used when a financial difference needs a documented adjustment. Preserve adjustment reference, original invoice and reason so the credit or debit adjustment 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 | credit or debit adjustment adjustment reference, original invoice and reason |
|
| Update the receiving system | Processing the credit or debit adjustment ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the credit or debit adjustment 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 810 Invoice
accounts-receivable or accounts-payable invoice: a bill is ready for the buyer to process.
- X12 820 Payment Order/Remittance Advice
payment or remittance record: payment instructions or allocation details are ready.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a financial difference needs a documented adjustment. Name the operational owner of the credit or debit adjustment and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map adjustment reference, original invoice and reason. 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 credit or debit adjustment 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 credit or debit adjustment processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 812 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic credit or debit adjustment 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 credit or debit adjustment without processing it twice.
Document structure
X12 812 Credit/Debit Adjustment at the element level
The X12 812 reference contains 22 segment entries and 99 data elements; 44 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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 |
- Date
- Credit/Debit Adjustment Number
- Transaction Handling Code
- Amount
- Credit/Debit Flag Code
- Reference Identification Qualifier
- Contact Function Code
- Date/Time Qualifier
Find your trading partner for X12 812
17 partners, 26 channels. Choose a channel to inspect its listed document reference and implementation context.
- Ace Hardware
- Ashley Furniture Industries, LLC
- Buc-ee's, Ltd.
- Core-Mark (via SPS Commerce)
- CVS
- Dillard's Department Stores, Inc.
- Family Dollar
- Family Farm & Home, Inc.
- JCPenney
- KeHE Distributors
- Kroger
- Loblaw Companies Limited
- PFG Customized Distribution
- PFG PerformanceFoodservice North
- Sprouts Farmers Market
- The Home Depot
- Worldwide Golf Shops
Catalog breakdown
Where X12 812 Credit/Debit Adjustment appears in this catalog
The largest groups of classified 812 catalog entries are in grocery & food, retail and building & hardware.
By industry
- grocery & food 9 channels
- retail 5 channels
- building & hardware 4 channels
- healthcare & pharma 4 channels
- apparel & footwear 3 channels
- furniture & home 1 channel
By network
- SPS Commerce 8 channels
- InterTrade 1 channel
FAQ
EDI 812 questions
What is an EDI 812?
EDI 812 is the X12 Credit/Debit Adjustment transaction set. Trading partners use it when a financial difference needs a documented adjustment. It carries the data for the credit or debit adjustment, and your system matches it on adjustment reference, original invoice and reason.
Who sends an EDI 812 and who receives it?
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. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 812 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 812?
Across 26 partner document references listed here, the business segments that appear most often include BCD (Beginning Credit/Debit Adjustment), N1 (Name), CDD (Credit/Debit Adjustment Detail), LIN (Item Identification), N9 (Reference Identification), SAC (Service, Promotion, Allowance, or Charge Information). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 812 and EDI 810?
The 812 carries the credit or debit adjustment and is used when a financial difference needs a documented adjustment. The 810 carries the accounts-receivable or accounts-payable invoice and is used when a bill is ready for the buyer to process.
What should I map for X12 812?
Start with adjustment reference, original invoice and reason and the target credit or debit adjustment. 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 812 error handling?
Test opposite credit/debit signs and verify their ledger effect. Apply a partial adjustment to the correct invoice line while preserving the original invoice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 812?
The directory on this page links 17 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.
