To start and identify an interchange of zero or more functional groups and interchange-related control segments
KeHE Distributors X12 812 Credit/Debit Adjustment
Plan X12 812 Credit/Debit Adjustment for KeHE Distributors (via SPS Commerce). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 16
- Loops
- 3
- X12 812
- Partner references ↗
Implementation guide
KeHE Distributors (via SPS Commerce): 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.
This document is listed for KeHE Distributors (via SPS Commerce). Confirm the version, required fields and responses that apply to your account.
| 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 |
|
The document reference includes 16 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
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.
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 KeHE Distributors 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.
Transaction context
Where 812 Credit/Debit Adjustment fits on KeHE Distributors (via SPS Commerce)
- KeHE Distributors channels
- 1 of 5
1 of KeHE Distributors's 5 channels list 812
- Trading partners
- 17
partner references list 812
- Channels
- 26
channel entries list 812
Frequently listed alongside 812
The directory associates SPS Commerce and 812 with 8 channels.
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 |
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
Segment reference — 16 segments 3 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 identify a person or office to whom administrative communications should be directed
To specify pertinent dates and times
To indicate shipment details in terms of quantity, weight, and routing instructions related to credit or debit of returned product
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 specify the location of the named party
To specify the geographic place of the named party
CDD Loop Repeat: 25
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)
SAC Loop Repeat: 25
Related references
Other transactions in KeHE Distributors (via SPS Commerce)
Other EDI documents listed on this channel.
Invoice X12 810 Purchase Order Change Request Buyer Initiated X12 860 Ship Notice Manifest X12 856 Purchase Order Acknowledgment X12 855 Purchase Order X12 850
No references match your search.
Showing 5 of 5 references
Browse the full directoryKeHE Distributors (via SPS Commerce) EDI 812 questions
Common questions about 812 Credit/Debit Adjustment on the KeHE Distributors (via SPS Commerce) channel.
What is X12 812 Credit/Debit Adjustment used for?
812 is used when a financial difference needs a documented adjustment. It carries information for the credit or debit adjustment. Match it to your business system using adjustment reference, original invoice and reason.
Is 812 required for KeHE Distributors (via SPS Commerce)?
812 is listed for KeHE Distributors (via SPS Commerce). Confirm the required version and direction for your business unit and account with the partner.
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.
How does 812 relate to other EDI messages?
X12 810 Invoice is a related document also listed on KeHE Distributors (via SPS Commerce). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 812 and 810?
812 is used when a financial difference needs a documented adjustment. 810 is used when a bill is ready for the buyer to process. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect KeHE Distributors 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.
