Invoice
The X12 810 is the electronic invoice a supplier sends after (or with) a shipment, billing the buyer for goods or services delivered.
In this guide
810 Invoice moves from Supplier / Manufacturer to Buyer / Accounts Payable (Seller → Buyer) via AS2, SFTP, VAN. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How 810 Invoice Works
Sender
Supplier / Manufacturer
Receiver
Buyer / Accounts Payable
Direction
Seller → Buyer
Standard
ANSI ASC X12
Version
005010
Transport
AS2 / SFTP / VAN
Business Purpose
Finance
Sender — Supplier / Manufacturer
EDI Transmission
810
Invoice
ANSI ASC X12 004010 / 005010
Receiver — Buyer / Accounts Payable
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →810 Invoice workflow. Steps: Shipment Completed, Generate Invoice, Create X12 810, AS2 / SFTP / VAN, EDI Gateway, ERP / AP, Invoice Validation, Payment Process. Transmitted from Supplier / Manufacturer to Buyer / Accounts Payable via AS2, SFTP, VAN, following ANSI ASC X12 004010 / 005010.
Overview
Drives automated three-way matching (PO, ASN/receipt, invoice) in accounts payable, reducing manual invoice entry and payment delays.
Sender
Supplier / Manufacturer
Receiver
Buyer / Accounts Payable
Direction
Seller → Buyer
Standard / Version
ANSI ASC X12 004010 / 005010
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| BIG | Beginning Segment for Invoice | Invoice number, date, and referenced PO number. |
| IT1 | Baseline Item Data (Invoice) | Line-level quantity, price, and product ID being billed. |
| TDS | Total Monetary Value Summary | Total invoice amount. |
| SAC | Service, Promotion, Allowance, or Charge | Discounts, freight charges, or allowances. |
Interactive example
Click any segment below to see its business meaning.
ST
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
ST*810*0001~
BIG*20230925*INV-90210*20230914*PO-2024-88213~
N1*ST*BuyerCorp Distribution Center 4~
ITD*01*3*2**10**30~
IT1*1*100*EA*25.00*PE*VP*SKU-10293*IN*44921~
IT1*2*100*EA*4.50*PE*VP*SKU-38810*IN*44987~
TDS*295000~
SAC*C*D240***-5000~
CTT*2~
SE*10*0001~Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| ERP Billing Document | invoice.total_amount | TDS01 (Amount) |
| ERP Billing Document | line.billed_qty | IT102 (Quantity Invoiced) |
| ERP Billing Document | invoice.po_number | BIG04 (Purchase Order Number) |
Validation rules
- BIG04 must reference a PO number that exists in the buyer's system.
- The sum of IT102 × IT104 across all IT1 loops plus SAC adjustments must equal TDS01.
- Quantities invoiced should not exceed quantities shipped per the associated 856, within tolerance rules.
- Payment terms in ITD must match the agreed vendor terms on file.
Common errors & troubleshooting
Invoice held in AP matching exception queue
Cause: Unit price on IT104 doesn't match the price on the original 850/contract.
Fix: Reconcile pricing in the item master before invoicing, or require a price change notice ahead of the order.
Total mismatch (999/reconciliation failure)
Cause: SAC allowance/charge amounts were omitted from the TDS01 total calculation.
Fix: Ensure the mapping logic sums IT1 extended amounts and all SAC adjustments before writing TDS01.
Related articles
Frequently asked questions
Automated comparison of the 850 (what was ordered), the 856 (what was shipped/received), and the 810 (what is being billed) to approve payment without manual review when all three agree.
Still have questions about 810?
Ask EDI AI →