850 Purchase Order
A buyer communicates an order number, lines, quantities, prices, and instructions. See What Is an EDI 850 Purchase Order?
Invoice fundamentals
What Is an EDI 810 Invoice?
A practical guide to the X12 transaction set businesses use to communicate invoice details.
EDI 810 is the X12 Invoice transaction set. A supplier commonly sends it to a buyer after an order or delivery to report an invoice number and date, purchase-order references, parties, product or service lines, prices, terms, allowances or charges, tax, freight, and source-reported monetary information. The parties' implementation guide determines what is required.
What business problem does an 810 solve?
An 810 replaces a paper, emailed, or proprietary invoice with a structured business message. Accounts-payable, procurement, finance, and supplier teams can route the same source facts into review and payment workflows without rekeying every line. A simple invoice may contain one line; a detailed invoice can include sublines, product identifiers, terms, taxes, freight, packaging, shipment facts, qualified measurements, notes, and repeated references.
The transaction communicates what the sender reported. It does not prove that goods were received, that every amount is correct, that the buyer accepted the invoice, or that payment is due under a particular partner agreement.
How does EDI 810 relate to EDI 850?
Fulfillment events
A partner workflow may include acknowledgments, changes, shipping notices, receipts, or other messages.
810 Invoice
A supplier reports invoice identity, lines, terms, and monetary facts for payment processing.
This is a conceptual relationship, not an automatic match. Partner workflows vary. Purchase-order and invoice values can differ for legitimate reasons, and this product does not reconcile an 810 against an 850.
Important EDI 810 segments
ISA, GS, and ST
Define interchange, functional-group, and 810 transaction boundaries and control identifiers.
BIG
Establishes invoice date and number and may carry purchase-order or related invoice references.
CUR, REF, DTM, and N1
Carry qualified currency, references, dates, and parties at their applicable scopes.
ITD
Reports payment terms such as discount timing and due-date context when supplied.
IT1, PID, PO4, and CTP
Describe invoice lines, quantities, units, prices, products, descriptions, packaging, and alternate pricing.
SLN
Creates a child subline owned by the active IT1 line; it is not another independent parent line.
SAC, TXI, FOB, CAD, and ISS
Carry qualified allowances or charges, tax, shipment terms, carrier data, and shipment summary facts.
TDS, AMT, CTT, and SE
Report source monetary or count facts and close the transaction. Their meanings stay qualifier- and source-bound.
These descriptions are orientation to the implemented mapping, not a reproduction of an X12 standard or partner code list.
Short synthetic EDI 810 example
This illustrative transaction set uses invented identifiers and values; it is not copied from the test corpus or a real invoice.
ST*810*0001~
BIG*20260830*INV-DEMO-001*20260829*PO-DEMO-001~
N1*ST*DEMO SHIP TO*92*LOC01~
IT1*1*2*EA*12.50**BP*DEMO-ITEM~
TDS*2500~
CTT*1~
SE*7*0001~BIG identifies the invoice, IT1 reports one line, TDS01 supplies a source-reported scaled amount, and SE closes the set. Real partner files can be much richer.
How Smart Mapping represents invoice lines
The canonical schema has exactly 195 fields. It emits one IT1 row per physical invoice line and then one row per owned SLN child in source order. If a transaction has no IT1, it emits exactly one SUMMARY row so header and summary facts remain available. Repeating structures are preserved in 20 collection fields as deterministic JSON strings instead of multiplying rows.
Header context may repeat on usable rows, while row applicability, scope, ownership, and provenance fields distinguish repeated context from row-native content. Inspect the complete EDI 810 data map before building downstream column assumptions.
Which EDI 810 releases are tested?
The product is tested against the generic releases 004010, 004030, and 005010. Other releases and partner-specific implementation references exist, but they are not advertised as supported and tested by this implementation. Generic support also does not establish compliance with a particular trading partner's rules.
How can I open or convert an EDI 810?
Use the browser-local EDI Viewer for readable source segments and mapped fields. Use the EDI Converter for CSV, Excel, JSON, or XML exports, the EDI Parser to inspect canonical field mapping, or the EDI Validator for implemented structural and data-quality checks. The browser performs EDI-content parsing; application servers do not receive those contents. Account, quota, billing, and bounded analytics metadata can still communicate with application services.
Continue with the conversion guide, validation guide, or conservative analytics guide. Partner workflows vary, so use the applicable licensed standard and partner guide for production obligations.