ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 812 — Credit/Debit Adjustment

The 812 documents a request or notification of adjustment: credit, debit, or billback between a buyer and a supplier after the original invoice has been issued.

Purpose

The 812 reports — or requests — an adjustment after the original invoice (810) or remittance (820) has been transmitted. It carries the detail of detected discrepancies: incorrect price, quantity received lower than quantity invoiced, late promotion, partial return, or supplier-borne billback (compliance, retail chargebacks). Each 812 line typically references the original invoice and line so the supplier ERP can reconcile automatically.

The 812 does not replace a corrected 810: it is an adjustment document, not a re-invoice. Its scope is limited to correcting amounts already posted, or declaring operational events (allowance, return, penalty) that change the outstanding balance.

Envelope structure

Like every transaction set, the 812 travels inside the standard X12 envelope. The functional group is CD (Credit/Debit). Didactic example in release 004010:

x12 example-812.x12 
ISA*00*          *00*          *ZZ*ACMERETAIL    *ZZ*ACMEVENDOR    *260514*1100*U*00401*000000812*0*P*>~
GS*CD*ACMERETAIL*ACMEVENDOR*20260514*1100*1*X*004010~
ST*812*0001~
BCD*20260514*CD-2026-0042*CR*CR-7781**INV-50012*20260420~
N1*BY*ACME RETAIL CO*92*0001~
N1*VN*ACME VENDOR INC*92*V-9087~
IT1*1*5*EA*9.99**UP*012345678905~
CAD*M****ACMECARRIER**PRO*PRO-7781~
SAC*A*A310***5000~
TDS*4995~
CTT*1~
SE*11*0001~
GE*1*1~
IEA*1*000000812~

The BCD opens the adjustment: date, document identifier, type (CR for credit, DR for debit) and reference to the original invoice. The IT1 loops carry the adjusted lines, with CAD (Carrier Detail), SAC (Service, Promotion, Allowance, or Charge) and TXI (Tax Information). The TDS carries the adjusted total amount, CTT a consistency check.

Common segments

  • Header — ST, BCD (Beginning Segment for Credit/Debit), CUR (currency), REF (references — contract no., original invoice no.).
  • Parties — N1 loop (BY = Buyer, VN = Vendor, RI = Remit-To) with N3/N4/PER.
  • Lines — IT1 loop (Baseline Item Data) with CAD, SAC, TXI, REF to point at the original invoice line.
  • Summary — TDS (Total Monetary Value Summary), document-level SAC, CTT and SE.

Common pitfalls

  • Amount sign: confusion between BCD02 credit/debit indicator and the sign of the TDS amount. Follow the TR3 convention strictly, or provide an ERP mapping that flips the sign on BCD02.
  • Reference to the source invoice: omitting REF*IV (Invoice Number) blocks automatic reconciliation on the supplier-AR side.
  • Retail compliance chargebacks: large retailers send 812s for penalties (missing label, out-of-window delivery); without allowance/charge codes consistent with their Vendor Compliance Manual, the document is rejected.

Documentation

The code 812 and the name Credit/Debit Adjustment are public and listed on x12.org/products/transaction-sets. The detailed segment-level content, qualifier lists, and full loop structure are the property of ASC X12 and DISA, distributed through paid Implementation Guides (TR3) per release. ediverse.io only covers concepts, the public envelope, and didactic examples.