X12 transaction set reference
X12 810 — Invoice
The X12 810 is an electronic invoice from supplier to buyer, carrying invoice number, dates, PO references, line items, and totals for payment processing.
EDI 810 facts
- GS01 for 810 groups is IN — invoice functional groups are acknowledged separately from PO and ASN groups.
- BIG04 purchase order reference is the primary three-way match key linking 810 back to 850 and 856.
- SignalEDI flags duplicate invoice numbers and PO/total mismatches in validation before partner send.
Where EDI 810 fits
- Direction
- Supplier → buyer / retailer
- GS functional ID
- IN
- Workflow position
- 810 closes order-to-cash after 850 and 856: invoice BIG04 must reference the original PO; totals must reconcile with shipped quantities.
Related sets: 850, 856, 997 · Document guide
Key segments in EDI 810
Sample EDI 810
ST*810*0003~ BIG*20260504*INV7781**PO1001~ N1*ST*DC RECEIVING~ IT1*1*12*EA*19.99**VN*SKU-100~ TDS*23988~ CTT*1~ SE*6*0003~
Validate samples with the free EDI validator.
Send EDI 810 with SignalEDI
POST /api/v1/documents/outbound
{
"partnerId": "retailer-demo",
"documentTypeCode": "810",
"payload": {
"invoiceNumber": "INV7781",
"purchaseOrderNumber": "PO1001",
"lines": [{ "sku": "SKU-100", "quantity": 12, "unitPrice": 19.99 }]
}
}Your side can reach partner-ready setup in days, not weeks — partner certification calendars may still take longer. See the API quickstart.
Common EDI 810 errors
- BIG04 PO number missing or not on original 850
- IT1 invoiced quantity exceeds 856 shipped quantity
- TDS total does not sum IT1 lines
- Duplicate BIG02 invoice number for same partner
Related reference
FAQ
EDI 810 FAQ
SignalEDI provides QuickBooks-oriented mapping previews and structured invoice outputs for review before accounting writes.
Retailers compare 850 ordered qty, 856 shipped qty, and 810 invoiced qty — mismatches trigger deductions or rejections.