EDI 810 invoice
An EDI 810 is the ANSI X12 transaction set for an invoice: a structured electronic bill a supplier sends a customer for goods or services, referencing the purchase order it fulfils.
What an 810 contains
- BIG opens the invoice with the invoice number and date, and the purchase order number it bills against.
- N1 loops name the parties, such as the remit-to and the ship-to.
- ITD states the payment terms, including any early-payment discount.
- IT1 is one invoice line: quantity, unit of measure, unit price and product identifiers.
- SAC carries allowances and charges, such as freight or a surcharge.
- TDS gives the invoice total.
Where it sits in the order cycle
The 810 is usually the last document in the exchange that starts with an EDI 850 purchase order, followed by the EDI 855 acknowledgment and the EDI 856 ship notice. A buyer’s system can then compare the invoice with the order and the receipt, which is three-way matching.
Why 810s get rejected
An invoice that arrives electronically is checked electronically, so small differences stop it:
- The purchase order number or line number does not match the order.
- The price or unit of measure differs from the purchase order.
- The quantity billed is more than the quantity received.
- A charge appears that the buyer does not accept on an invoice.
- The same invoice number is sent twice.
A rejected 810 delays payment until someone finds the difference and resends it.
How Runtara handles it
Runtara works on both sides of the invoice. Outgoing invoices to customers are sent from ERP data, with each trading partner set up by our team from the partner’s specs and test files. Incoming supplier invoices, whether they arrive by EDI, email or PDF, are matched line by line against the purchase order and goods receipt in your ERP, and variances are held for a person before anything is posted.