Skip to main content

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

SegmentRole
STOpens transaction set 810.
BIGInvoice number, date, and PO reference for three-way match.
N1Remit-to and ship-to parties.
IT1Invoiced line quantity, UOM, and price.
TDSTotal invoice amount.
SETransaction set trailer.

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" }
}

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

EDI 810 FAQ

Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.

SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.

HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees

Operations teams

A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.

Healthcare billing

837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling and a documented BAA review path for diligence.

Developer teams

JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.

Preview case studies

© 2026 CCCM Consulting LLC. All rights reserved.