What Is an EDI 810 Invoice?
The EDI 810 is the X12 transaction set that carries an invoice from a supplier to a buyer. It is the electronic version of a paper invoice and the document that triggers payment under the retailer's terms. The 810 references the original 850 purchase order and the 856 advance ship notice, and it must agree with both for the retailer's accounts payable system to release funds automatically.
EDI 810 Segments and Structure
A standard 810 follows a header / line-item / summary pattern. The segments you will see in almost every retailer spec:
- BIG - Invoice number, invoice date, and the original PO number.
- REF - Vendor number, department number, and BOL or pro number references.
- N1 / N3 / N4 - Remit-to, bill-to, and ship-to parties.
- ITD - Payment terms, discount percent, and net due date.
- IT1 - Each invoiced line with quantity, UOM, unit price, UPC/GTIN, and vendor part.
- SAC - Allowances, charges, and promotional deductions.
- TDS - Total invoice amount including taxes and adjustments.
- CTT / SE - Line count, hash totals, and transaction set trailer.
Three-Way Matching: 850, 856, 810
Retailers run three-way matching across the 850 (what was ordered), the 856 (what was shipped), and the 810 (what is being invoiced). If quantities, prices, UPCs, or PO references do not agree across all three, the invoice goes on hold or is short-paid. Validating the 810 against the originating 850 and 856 before transmission is the single biggest lever for getting paid on time and avoiding deduction disputes.
Common EDI 810 Errors That Trigger Chargebacks
These are the issues that drive the majority of payment holds Yoke sees in production:
- Invoice price does not match the PO line price (price discrepancy).
- Invoiced quantity exceeds shipped quantity on the 856.
- PO number on the 810 does not exist in the retailer's system.
- UPC or vendor part number does not match the buyer's item master.
- Invoice transmitted before the 856 (out-of-sequence ASN/invoice).
- Terms or remit-to address differ from the vendor master.
How Yoke Handles the EDI 810 for You
Yoke generates compliant 810s from your ERP, validates each invoice against the originating 850 and 856 before it leaves your environment, applies retailer-specific allowance and SAC rules, and monitors AP responses (820 remittance, 824 application advice) so you see exactly which invoices paid, short-paid, or got deducted - and why.
Frequently Asked Questions
Quick answers to the questions buyers and suppliers ask most about this transaction.
- What is an EDI 810? The EDI 810 is the X12 transaction set that carries an invoice from a supplier to a buyer. It contains the invoice number, PO reference, line items, quantities, prices, taxes, and totals needed to request payment electronically.
- What is the difference between an EDI 810 and a regular invoice? There is no business difference - both are invoices. The 810 is simply the standardized electronic format that lets suppliers and buyers exchange invoices system-to-system, which enables automated three-way matching and auto-pay.
- What is three-way matching for an EDI 810? Three-way matching compares the 850 purchase order, the 856 advance ship notice, and the 810 invoice. Quantities, prices, UPCs, and PO references must agree across all three for the retailer's AP system to release payment without manual review.
- When should I send the EDI 810? The 810 must be sent after the 856 ASN, never before. Sending an invoice before the matching shipment notice typically causes the invoice to be rejected or held until the ASN is reconciled.
- What happens after the 810 is sent? The buyer's system returns a 997 functional acknowledgment, optionally an 824 application advice (with any validation errors), and eventually an 820 remittance advice when the invoice is paid - including any deductions or chargebacks.