EDI 810 is an invoice, also known as EDIFACT INVOIC, that is typically sent in response to a purchase order (EDI 850) as a request to receive payments for good or services rendered. An electronic invoice, similar to a paper-based invoice, is one of the most commonly used EDI transaction sets by trading partners.
The 810 is a core document that trading partners utilize with important details to bill for goods/services rendered. Key data elements the 810 include:
Trading partners’ EDI 810 requirements, specifications and formatting may vary. On the left is a sample of raw EDI 810 transaction code format. On the right is a preview of the users’ view of the 810 within WebEDI, similar to a paper-based invoice.
The purpose of an EDI 810 invoice is to allow for a seamless exchange of billable information such as goods and/or services rendered between two separate companies. The supplier will send the trading partner an 810 in response to an EDI 850 purchase order. With DataTrans WebEDI, the supplier will generate the EDI 810 invoice from the EDI 850 purchase order. DataTrans intuitive forms will pull the relevant information onto the EDI 810 invoice to be sent back to the trading partner. The 997 functional acknowledgment (also known as CONTRL) will notify the supplier the EDI 810 invoice has been received.
For more information about how EDI works, view our EDI guide.
The 810 transaction set is an important document in the procurement cycle. Discrepancies in the EDI 810 could result in payment delays. Common issues suppliers may encounter include:
With DataTrans as your partner, easily maintain 100% EDI compliance. DataTrans adheres to trading partners’ EDI 810 requirements as well as all document specifications, mapping, connectivity and setup. As DataTrans acts as an extension of your company, you can focus on what you do best, your business.