Page 1 of 15
The 810 invoice document is used to bill the dealer for products purchased from the vendor. The
objective of this document is to reduce errors and charge backs and provide efficient data entry to
invoice processing and accounts payable systems
The invoice document contains the same basic information found on a printed invoice. It contains
invoice date and number, selling company, group account, carrier description, bill of lading
number and shipment date. Also, it contains SKU, quantity and unit price per invoice line item.
Ship-to information and remit-to information are also included.
A 997 Functional Acknowledgement is expected within 24 hours of origin of this document. If an
error(s) causes the EDI invoice to become "unworkable", the dealer must send the vendor a 997
Functional Acknowledgment document indicating this. The 997 document is generated as ANSI
compliance errors are detected by EDI translation software (e.g., missing mandatory fields). If a
997 is received with a status flag of "R", the EDI department of the appropriate vendor will contact
the dealer. The corrected invoice will be sent via EDI using the original invoice number.
Each vendor creates 810 invoice documents on a different schedule.
One Purchase Order number per invoice.
Release 1.09 06/1/05
8/22/05 - Correction made to add repeat value of >1 for the ITD segment according to the ANSI
X12 4010 standard and to eliminate any confusion for the installed B2B user base which is already
allowing for more than one ITD segment or planning to allow for more than one ITD segment in
the near future using version 1.09. The 810 example was also updated to contain two ITD
segments, i.e., showing the ability to send more than one ITD segment.