EDI 810 Invoice
An EDI 810 is the X12 invoice. The supplier sends it to the buyer to bill for goods that shipped. It follows the 850 purchase order and the 856 ship notice, and it should bill for what actually shipped, line for line. We generate every 810 inside your ERP from your own invoice records.
+ RULES
- Top Rated PlusUpwork talent badge
- 100%Upwork Job Success score
- 17,800+Hours billed on Upwork
- 2012AppsXone established
“They integrated with multiple third-party systems and they did a great job with it. It’s stable, scalable, which was our goal, and we saved a lot of time and effort.”
What the 810 does, and where it fits
-
850Purchase order. The buyer orders. See EDI 850 purchase order. -
856Advance ship notice. The supplier says what shipped. See EDI 856 advance ship notice. -
810Invoice. The supplier bills for what shipped: items, quantities, prices, charges and terms. -
824Application advice. Some buyers reject an invoice with an 824 that gives the reason. -
812Credit or debit adjustment. Corrects a billing discrepancy after the fact, often tied to a chargeback or a pricing dispute. -
820Payment and remittance advice. Some buyers send remittance detail saying which invoices a payment covers.
Key data in an 810 invoice
An 810 says who is billing whom, for which order, for which items and for how much. The segments below usually carry that. Which are required, and how each field is filled, is set by the buyer's implementation guide.
-
BIGBeginning segment. The invoice number and date, and the purchase order number it bills against. -
N1Parties. Remit-to, bill-to and ship-to. -
ITDTerms of sale. Payment terms, such as the due date and any discount. -
IT1Line items. One per line: quantity invoiced, unit, price and item identifiers. -
SACAllowances and charges. Freight, allowances and other amounts added to or taken off the invoice. -
TDSTotal. The invoice total, which has to agree with the lines and charges.
The invoice bills for what shipped, not what was ordered
Most invoice disputes come from a gap between the order and the shipment. A line is shorted, an item is substituted, or a price changed after the order was placed. If the invoice is built from the original order, it bills for something that did not happen.
Buyers compare the invoice with the purchase order and with what they received. A line that does not agree is rejected or short paid, and a person then has to work out which document was wrong.
How we build the 810 inside your ERP
Generated from your own invoice record
The 810 is built inside your ERP with the EdiFabric .NET library from the invoice for the shipment, so EDI and accounting carry the same numbers.
Lines follow the shipment
Invoiced quantities and items reflect what the warehouse recorded as shipped, including shortages and substitutions.
Buyer item numbers kept in the mapping
Each line carries the item identifiers the buyer expects, mapped from your own SKUs.
Raw file kept with the invoice
Each 810 is stored with its raw file next to the parsed result, so a dispute about what was billed is a lookup.
The 810 in a live multi-partner ERP
- 810 invoices generated inside one ERP for retail trading partners, including Amazon Vendor Central and Costco Wholesale, using the EdiFabric .NET library. The Amazon Vendor Central connection also handles 824 application advice and 812 adjustments.
- On one retailer connection, the item billed on an invoice did not match what physically shipped. It was a recurring pattern where a warehouse substitution never reached the order record.
- Every outbound file stored beside the parsed result, so a dispute about what was billed is a lookup.
Why an 810 gets rejected or short paid
- The item billed is not the item that shipped On one retailer connection we run, the SKU on the invoice did not match what physically shipped. A substitution at the warehouse had never made it back into the order record, so the pattern repeated. The lasting fix is for the invoice to follow the shipment.
- Quantity invoiced is greater than quantity received A common pattern after a short shipment. The invoice carries the ordered quantity and the buyer pays only for what arrived. Invoicing shipped quantities avoids the deduction.
- Price on the invoice differs from the purchase order A common pattern after a price change. Comparing the invoice price with the 850 before sending shows the difference while it can still be agreed with the buyer.
- Duplicate invoice numbers A common pattern when a rejected invoice is corrected and resent under the same number, or an invoice is sent twice. Check your partner's guide for how it expects a corrected invoice to be numbered.
- Totals that do not add up A common pattern where freight or an allowance is included in the total but not sent as its own charge. The total has to agree with the lines and the charges in the file.
EDI 810 questions
What is an EDI 810?
The X12 invoice. A supplier sends it to a buyer to bill for goods that shipped. It carries the invoice number, the purchase order it bills against, the lines, any charges and the total.
When is the 810 sent?
After the goods ship. Each partner sets its own timing rules, so check the implementation guide for yours.
What happens when an 810 is rejected?
The buyer does not pay it until it is corrected. Some buyers send an 824 with the reason. Find the line that disagreed, correct it at the source and resend.
What is the difference between an 810 and an 812?
The 810 is the invoice. The 812 is a credit or debit adjustment that corrects a billing discrepancy afterwards.
Can the 810 post to QuickBooks as well?
The 810 is generated from the invoice in your ERP. Where that ERP syncs invoices to QuickBooks, both come from the same record. See our QuickBooks integration services.
Can the 810 be generated from an ERP we did not build?
Often yes. What matters is whether your invoice and shipment data is reachable. We confirm that during scoping.
Are invoices being rejected or short paid?
Tell us the trading partner and what the rejection or deduction said. We will tell you which line to compare first and where the value should come from.