Skip to content
X12 EDI

Kroger X12 812 Credit/Debit Adjustment

X12 812 (Credit/Debit Adjustment) is the EDI transaction exchanged between Kroger (Peyton's Group (a Kroger Division)) 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 Peyton's Group (a Kroger Division)

Kroger channels
1 of 2

1 of Kroger's 2 channels carries 812

Trading partners
17

partners across the Stacksync network trade 812

Channels
26

channels network-wide carry 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
Segments with mandatory elements
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
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

BCD Beginning Credit/Debit Adjustment 14 elements

To transmit identifying dates and numbers for the transaction set and indicate the monetary value to the receiver of the transaction

N9 Extended Reference Information 3 elements

To transmit identifying information as specified by the Reference Identification Qualifier

PER Administrative Communications Contact 4 elements

To identify a person or office to whom administrative communications should be directed

DTM Date/Time Reference 2 elements

To specify pertinent dates and times

N1 Loop Repeat: 200
N1 Party Identification 4 elements

To identify a party by type of organization, name, and code

N3 Party Location 2 elements

To specify the location of the named party

N4 Geographic Location 3 elements

To specify the geographic place of the named party

CDD Loop
CDD Credit/Debit Adjustment Detail 10 elements

To provide information relative to a line item adjustment

LIN Item Identification 5 elements

To specify basic item identification data

SE Transaction Set Trailer 2 elements

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

8+ 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.

Kroger Peyton's Group (a Kroger Division) EDI 812 FAQ

Common questions about 812 Credit/Debit Adjustment on the Peyton's Group (a Kroger Division) 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. Kroger's Peyton's Group (a Kroger Division) channel requires it from trading partners.
Does Kroger Peyton's Group (a Kroger Division) require 812 for trading partners?
Yes, Kroger (Peyton's Group (a Kroger Division)) supports X12 812 Credit/Debit Adjustment. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Kroger 812 with Stacksync?
Most companies go live with Kroger 812 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 812 on Peyton's Group (a Kroger Division)?
On Peyton's Group (a Kroger Division), X12 812 is typically exchanged alongside 850 Purchase Order, 810 Invoice, 856 Ship Notice Manifest, 855 Purchase Order Acknowledgment. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.

Ready to automate your Kroger EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.