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 810 — Invoice

The 810 is the standard EDI invoice on the North American side. Issued by the supplier after shipment, it closes the commercial loop opened by the 850 and precedes payment.

Purpose

The 810 documents a request for payment: for one or more shipments, the supplier issues an invoice that lists the items delivered, unit price, applicable discounts, taxes, and the net amount due. It references the original 850 (and ideally the 856) so that accounts payable can match invoice to order to receipt — the so-called three-way match.

Depending on sector practice, an 810 may be an evaluated receipt (auto-billed, triggered on the buyer side after the 861), consolidated (multiple shipments on one invoice), or batch-emitted. Mass retail expects "clean" 810s to avoid short-pays caused by price discrepancies or miscalculated taxes.

Envelope structure

The 810 travels in an IN functional group (Invoice). A didactic 810 for order PO78901:

x12 example-810.x12 
ISA*00*          *00*          *ZZ*ACMEVENDOR    *ZZ*ACMERETAIL    *260525*1015*U*00401*000000301*0*P*>~
GS*IN*ACMEVENDOR*ACMERETAIL*20260525*1015*1*X*004010~
ST*810*0001~
BIG*20260525*INV-2026-552*20260513*PO78901~
REF*VR*VENDOR-552~
N1*BT*ACME RETAIL CO*92*0001~
N1*RE*ACME VENDOR INC*92*VEND001~
ITD*01*3*2**10***30~
IT1*1*2*EA*9.99**UP*012345678905~
IT1*2*5*EA*19.50**UP*012345678912~
TDS*11748~
TXI*ST*734.55*6.25~
CTT*2~
SE*12*0001~
GE*1*1~
IEA*1*000000301~

The BIG segment opens the invoice: issue date, invoice number, referenced PO date, PO number. ITD states payment terms (here: 3% if paid within 10 days, otherwise net 30). Each IT1 is an invoiced line. TDS carries the total amount in hundredths (11748 = $117.48). TXI breaks down taxes per jurisdiction.

Common segments

  • Header — ST, BIG (Beginning Segment for Invoice), NTE (notes), REF (references), PER (contacts), ITD (Terms of Sale).
  • Parties — N1 loop for Bill To (BT), Remit To (RE), Ship From, Ship To.
  • Lines — IT1 loop (Baseline Item Data — Invoice) with PID (description), SAC (allowance/charge), TXI (line taxes), REF, DTM, IT3 (Additional Item Data).
  • Summary — TDS (Total Monetary Value Summary), SAC (header-level allowances/charges), TXI (global taxes), CAD (Carrier Detail), CTT, SE.

When you'll see it

  • Retail / distribution — daily billing flow between CPG suppliers and mass retailers.
  • Manufacturing — used for spot and consolidated invoicing (monthly invoices).
  • Transport — carriers invoice their services via 810, sometimes 859 (Freight Invoice) depending on customer conventions.
  • B2B marketplaces — Amazon Business, Coupa, SAP Ariba consume 810 for integrated sellers.

Documentation

The code 810 and the name Invoice are public and listed on x12.org/products/transaction-sets. Segment-by-segment detail (the qualifiers accepted in BIG, ITD, IT1, the full structure of the N1 and SAC loops) is covered by the paid Implementation Guides (TR3) owned by ASC X12 and DISA. ediverse.io does not redistribute them.