Transaction set guide
EDI 810 Invoice
The 810 is how suppliers bill retailers electronically. Get it wrong and you don't get paid until you fix it — that's typically a 7-to-30-day delay on top of standard net terms.
Required segment overview
| Segment | Purpose | Required? |
|---|---|---|
| BIG | Beginning of invoice — invoice number, date, PO number | Yes |
| REF | References (vendor #, BOL, ASN ID) | Often |
| N1 / N3 / N4 | Remit-to address (where to mail the check) | Often required (N1*RI) |
| ITD | Terms of sale (net 30, 2/10 net 30) | Often |
| DTM | Invoice date, due date | Often |
| IT1 | Line item | Yes (one per line) |
| PID | Item description | Often |
| TDS | Total monetary value due | Yes |
| SAC | Service / allowances / charges (freight, fuel surcharge) | Optional |
| CTT | Total line item count | Yes |
BIG segment — invoice header
BIG*20250506*INV789*20250504*PO12345~
- BIG01 — invoice date, YYYYMMDD.
- BIG02 — your invoice number. Must be unique per supplier; some retailers reject duplicates indefinitely.
- BIG03 — date of the original PO (BEG05 from the 850).
- BIG04 — PO number — must match the 850's BEG03 character-for-character.
IT1 segment — line items
IT1*1*5*EA*12.50**VC*ABC123~
Mirrors the PO1 from the 850 — line number, quantity, UOM, unit price, qualifier, vendor part. The retailer cross-references each IT1 to the matching PO1 and rejects if quantities or prices don't match what was on the PO (within tolerance).
TDS segment — total amount due
TDS*6250~
Amount in cents (no decimal). $62.50 = TDS*6250. This must equal the sum of (IT1 quantity × IT1 unit price) plus any SAC charges minus allowances.
The five most common 810 rejections
- PO number mismatch. BIG04 doesn't match the 850's BEG03 exactly (case, leading zeros, dashes).
- Duplicate invoice number. The retailer's AP system rejects the second submission of the same BIG02 — even if the first was wrong.
- Quantity mismatch with 856. Retailer compares IT1 quantity to what was actually received per the 856 / dock receipt. If the 810 invoices for more than was received, it rejects.
- Price mismatch with 850. IT1 unit price doesn't equal PO1 unit price (within retailer tolerance, often 0%).
- TDS calculation wrong. Doesn't equal sum of line totals + SAC. Retailer's AP system flags it.
Pre-flight checklist before sending an 810
- BIG04 PO number matches the 850 exactly.
- Each IT1 line corresponds to a PO1 from the 850.
- IT1 quantity ≤ 856 SN1 quantity for that line.
- IT1 unit price = PO1 unit price.
- TDS = sum(IT1 qty × IT1 price) + SAC charges − SAC allowances.
- Invoice number BIG02 is unique across your invoice history with this retailer.
- REF*VR vendor number matches the partner profile.
Validating an 810 in EDI-X12
- Paste the 810 into the validator.
- Click Validate for structural checks.
- If a rejection email exists, paste the 810 + rejection text into the AI explainer with task "Explain rejection."
Related
- 850 PO — the document you're invoicing against
- 856 ASN — what was actually shipped
- 997 — confirms structural acceptance, not payment
Invoice rejected? Don't wait 30 days to find out why.
Paste the 810 and the rejection email. Get a fix in plain English in seconds.
Open the validator