Supply chain collaborationInvoice (EDI 810) Meet embedded SpicY™ AI

SPICE™ Glossary / Invoice (EDI 810)

Invoice (EDI 810)

An invoice (EDI 810) is the X12 transaction a supplier sends to bill a buyer for goods or services, referencing the purchase order and listing quantities, prices, charges and terms.

The 810 replaces a paper or PDF invoice with structured data. The header (the BIG segment) carries the invoice number, invoice date and related PO number. Lines (IT1 segments) list each item billed with quantity, unit of measure and unit price. Allowances and charges, such as freight or promotional discounts, follow, along with payment terms and the total amount due (the TDS segment).

The invoice normally comes last in the order flow: purchase order, PO acknowledgment, advance ship notice, then the 810. The buyer matches it against the order and the receipt in a three-way match before approving payment. The payment, and the explanation of what was paid, may then arrive as a remittance advice (EDI 820).

Invoice errors delay cash. Prices that differ from the PO, quantities billed but not received, missing references and wrong charge codes cause an invoice to fail matching or be rejected. Unresolved differences become short payments, claims and deductions or a credit/debit adjustment (EDI 812), all of which take much longer to settle than an invoice that was right the first time.

How SPICE™ handles it

For your suppliers, SPICE Web OMS™ creates invoices from the order and shipment already on record, so non-EDI suppliers bill against the right lines and your rules flag differences before submission, as part of procure-to-pay. For your customers, SPICE™ delivers your invoices as 810s or in the format each customer accepts, linked to the order and shipment, as part of order-to-cash.

FAQ

Frequently asked questions

Is an EDI 810 the same as a paper invoice?

In most trading relationships, yes: the trading partner agreement makes the 810 the official invoice. Tax and e-invoicing rules vary by country, so requirements should be confirmed for each jurisdiction.

Why was my EDI 810 rejected?

Common reasons are a PO number the buyer doesn't recognize, prices or quantities that don't match the order or receipt, missing required fields, or an invoice sent before the ASN. A rejected 997 points to a formatting problem; business rejections usually come from the buyer's accounts payable team.