The EDI 810 is your invoice to the retailer, sent electronically. It is where everything earlier in the order gets checked: if the 810 does not reconcile with the purchase order and the ship notice, payment slows down or arrives short.
The EDI 810 is the X12 invoice transaction set. A supplier sends it to bill a retailer for goods that shipped, listing the items, quantities, prices, payment terms, and any allowances or charges.
The retailer matches it against its purchase order and what it actually received. When all three agree, the invoice pays on terms. When they do not, the retailer short-pays and the difference shows up on your remittance as a deduction.
Retailers check the 810 against the 850 they sent and against what they received, which they know from your 856 and their own receiving scans. Where the three disagree, they generally pay the lowest number and deduct the rest.
A header with the invoice and order references, one IT1 line per item, then summary segments for totals, allowances and charges.
| Segment | Name | What it carries in an apparel invoice |
|---|---|---|
| BIG | Beginning segment for invoice | Invoice date and number, PO date and PO number |
| CUR | Currency | Currency of the invoice |
| REF | Reference identification | Vendor number, department, bill of lading |
| N1 | Name | Remit-to, bill-to and ship-to parties |
| ITD | Terms of sale | Payment terms, discount and due dates |
| DTM | Date and time | Ship date |
| IT1 | Baseline item data | Quantity invoiced, unit of measure, unit price and item identifiers |
| PID | Product description | Item description text |
| TDS | Total monetary value summary | Total invoice amount, with two decimal places implied |
| CAD | Carrier detail | Carrier and routing used |
| SAC | Allowance or charge | Allowances, discounts, freight or other charges |
| ISS | Invoice shipment summary | Units shipped and weight |
| CTT | Transaction totals | Number of line items |
Required segments and formats are set by each retailer's 810 implementation guide. Map to the guide, not to the X12 standard alone.
The total in the TDS segment carries two implied decimal places, so 125000 means 1,250.00. A formatting error here bills the retailer for a hundred times the real amount, or a hundredth of it, and the invoice is rejected or held.
Some styles carry different costs by size, for example extended sizes priced higher. The invoice has to price each size the way the purchase order did, or the retailer adjusts every line.
If you shipped prepacks, invoice them the way the order and ship notice described them. Invoicing component units against a prepack order, or the reverse, breaks the match.
Invoice what actually shipped, per shipment, not what was ordered. One invoice per shipment, tied to its 856, is the cleanest pattern for most retailers.
Where a retailer expects agreed allowances on the invoice, they belong in SAC segments. Leave them off and the retailer deducts them anyway, and a deduction is far harder to reconcile than an allowance would have been.
If you factor, the invoice your factor buys has to match the 810 the retailer receives. A mismatch creates a dispute in two places at once.
The pattern is the same as with the 856: invoices built from what actually shipped, rather than from what was ordered, avoid most of these.
810 is the X12 transaction set number for an invoice. It sits alongside the 850 purchase order and the 856 advance ship notice as one of the core documents retailers require.
The 856 tells the retailer what shipped and in which cartons. The 810 bills for it. Retailers usually expect the 856 to arrive first.
The retailer pays on terms, often with an 820 remittance advice listing what was paid and what was deducted. Some retailers also use the 812 credit and debit adjustment to communicate adjustments, so check for 812s as well as remittance detail.
Usually because it did not match the purchase order or what was received: a price difference, units the retailer did not receive, a missing allowance, or a compliance chargeback taken against the payment. The remittance detail tells you which.
The order every invoice is matched against, including size runs, prepacks and store splits.
Read the guideThe ship notice your invoice has to follow, and the mistakes that trigger receiving chargebacks.
Read the guideHow to code every deduction to a cause, dispute the ones you can win, and stop repeats.
Read the guidePlain definitions for every EDI, compliance, inventory and sourcing term.
Open the glossaryEvery X12 document an apparel brand is likely to see, including the 820 and 812 that follow an invoice.
See the listHow to tell whether your 810 actually arrived, and what to do when it comes back rejected.
Read the guideWe reconcile your 850s, 856s and 810s against remittances, find where the three stop matching, and fix it at the source. If your invoices already match cleanly, we will tell you that.
Book a call