EDI 812 vs EDI 810: When To Use A Credit/Debit Adjustment

EDI 812 Credit/Debit Adjustment The EDI transaction used to communicate credit or debit adjustments between trading partners. It is related to the invoice transaction but serves a different purpose: the 810 issues an invoice for goods or services, while the 812 corrects or adjusts amounts previously invoiced.

Understanding the distinction between an EDI 812 Credit/Debit Adjustment and an EDI 810 Invoice avoids duplicate billing, incorrect postings, and reconciliation headaches. The 810 initiates the payable/receivable; the 812 updates that record when new information emerges. For example, you send an 810 to bill a retailer for a shipment; later, if returns or pricing errors are discovered, you send an 812 to adjust the original invoice rather than issuing a brand-new 810 that would complicate matching.

Main Functional Differences

• Purpose: 810: bill for goods or services; 812: amend or correct billed amounts after the invoice is issued.
• Reference: 812 must reference the original invoice (810) so systems can post adjustments correctly.
• Accounting Treatment: 810 creates an accounts receivable/payable entry; 812 modifies that entry (reduces or increases outstanding balance).
• Timing: 810 generally follows shipment; 812 can occur days to months later when discrepancies surface.

When To Send An 812 Instead Of A New 810

Use an 812 when the intent is to alter a specific previously issued invoice. Typical triggers include post-invoice agreements to accept returns, retroactive pricing corrections, promotional allowances applied after settlement, and discovered billing mistakes. Sending an 812 keeps financial records coherent: the original invoice remains the basis for the transaction history, and the adjustment clearly documents the correction.

When A New 810 Is Appropriate

Create a new 810 when there is a new sale or when the adjustment cannot be cleanly linked to an earlier invoice. For instance, if a retailer places a new order, or if the parties decide to reissue consolidated billing for multiple POs, a fresh 810 is the correct choice. Do not use an 812 to create standalone charges unrelated to prior invoices.

Matching And Systems Impact

ERP and accounts systems typically match incoming 812s to existing 810 records using invoice numbers, PO references, and invoice dates. A well-configured matching engine will accept line-level or summary 812s and post the credit/debit so the net payable reflects the adjustment. If an 812 lacks sufficient references or uses non-standard reason codes, it will trigger exceptions that require manual review — which is why trading partner agreements should specify required fields.

Practical Example

A retailer receives an 810 for $8,500. During reconciliation, the supplier and retailer agree that $500 of the invoiced amount represented promotional overcharges. Rather than voiding the invoice, the supplier issues an EDI 812 Credit/Debit Adjustment referencing the 810 number, indicating a $500 credit, and citing the promotional allowance reason code. The retailer’s system applies the 812, reducing the payable balance and preserving an auditable chain from original invoice to final settlement.

Best Practices When Using 812s

• Standardize Reason Codes: Agree on a finite set of adjustment reason codes to allow automated categorization and reporting.
• Require Invoice References: Enforce reference fields in the implementation guide so 812s always map to an 810.
• Define Cutoff Windows: Set a time limit for issuing 812s to prevent long-tail adjustments that complicate financial close.
• Automate Exception Handling: Route unmatched or conflicting 812s into a workflow for rapid dispute resolution.

In short, the EDI 812 Credit/Debit Adjustment complements the 810 invoice: use 810 to bill and 812 to correct that billing. Clear trading partner rules, robust matching logic, and standardized reason codes make the pair reliable for retail billing and settlement.