BCD
Beginning segment for credit/debit adjustment: the adjustment date and number, the credit/debit flag, the amount, and the invoice or PO it references.
EDI 812: Credit / Debit Adjustment
A notice that an amount owed is being adjusted up or down, with the invoice it applies to and the reason. Either party to the other, most often buyer to supplier. This page covers what the 812 is for, the segments you meet when you open one, the documents it travels with, where it tends to go wrong, and how it moves over AS2 into your systems on Files.com, which receives, parses, validates, and routes it as configuration.
No credit card required · 7-day free trial · Live in minutes
#1 MFT vendor in Gartner Peer Insights
Trusted by 4,000+ companies
Every protocol included
What The 812 Is For
The 812 adjusts money already invoiced. A buyer sends it to claim a credit for a shortage, damage, pricing error, or return, or to notify a debit; a supplier sends it to issue a credit memo. It names the invoice or PO the adjustment applies to, the amount, the direction (credit or debit), and the reason code.
It travels with the 810 and 820 in the settlement cycle: an 812 credit explains why an 820 pays less than the 810 asked, or arrives on its own as a standalone credit or debit memo.
The Segments You Meet First
In document order, the segments that carry the 812's meaning. A partner's implementation guide says which are required and which fields each must hold.
N1
Parties.
CDD
Credit/debit adjustment detail: the adjustment reason code, the amount at the line level, and quantities.
LIN
Item identification for a line-level adjustment.
SAC
Allowance or charge detail when the adjustment is one.
Where It Goes Wrong
Adjustments that reference an invoice the supplier cannot find, and reason codes used inconsistently, so a deduction cannot be classified or disputed. Deduction management is a discipline of its own for suppliers to large retailers largely because of unclear 812s.
The Documents It Travels With
The 812 rarely moves alone. These are the documents that precede, answer, or settle it.
810 · Invoice
The supplier’s bill for goods or services delivered against a purchase order.
See The 810820 · Payment Order / Remittance Advice
A payer’s notice of payment: which invoices are being paid, for how much, and how.
See The 820997 · Functional Acknowledgment
The receipt that says an EDI transmission arrived and was parsed, with any syntax errors found.
See The 997How The 812 Moves On Files.com
A partner sends the 812 over AS2, SFTP, or FTPS, and it lands in that partner’s inbox folder on Files.com with the transport receipt recorded. From there it is a workflow, not a project: TransformScript parses the X12 natively into the JSON, CSV, or XML your ERP or WMS reads, content validation flags a document whose contents are wrong before anything ingests it, and an automation routes the result to the system and the people who act on it.
Outbound is the mirror image. Your system exports its record, TransformScript builds the 812 the partner’s guide specifies, and the file dropped in the partner’s outbox goes out over AS2 with automatic retries until the MDN confirms delivery. Every transmission in both directions is in the audit log, and delivery monitoring alerts when a 812 that was due never arrives. The full picture is on the EDI software page.
EDI 812 Questions
What teams ask about the 812 and how it moves on Files.com.
An EDI 812 is the X12 Credit/Debit Adjustment. It notifies a trading partner that an invoiced amount is being adjusted, credit or debit, with the invoice referenced, the amount, and the reason code.
The 820 can carry adjustments inline when a payment is made. The 812 stands alone: a credit or debit memo issued outside a payment, or a claim raised before payment.
Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 812 sent by a trading partner lands in that partner’s inbox folder with a signed MDN receipt returned to the sender. Partners who exchange over SFTP or FTPS connect to the same platform and the document lands in the same place.
Yes. TransformScript parses the X12 812 natively and writes the JSON, CSV, or XML your systems ingest, as a step in the workflow that fires when the document arrives. Outbound, the same engine builds a 812 from your system’s export and drops it in the partner’s outbox for delivery.
Exchange The 812 Without The Legacy Stack
Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 812 lands in their folder, parses into the record your system reads, and every transmission carries a signed receipt.
No credit card required • Free for 7 days • Live in minutes