We Make EDI Integration Easy

Below you will essential information in regards to this EDI. If you have any specific questions about integrating your EDI with your ERP and eCommerce please reach out. Take advantage of our "start planning" feature to map out your integration needs. 

>>  Request a Demo
>>  Map Your Ideal Integration


 

What is a 816 - Organizational Relationships document?

The 816 EDI document type is an electronic version of a paper Organizational Relationships. Standard EDI formats include X12, ANSI, EDIFACT and its subsets. The 816 EDI document type is used to provide location address information for a company and its related operating entities, maintain location address information through periodic updates, or convey location or logical relationships.

What makes up the 816 - Organizational Relationships document?

An EDI 816 - Organizational Relationships document is organized into segment and data elements. A segment can contain at least one data element. Each data element contains a data field. Data elements can include trading partner number, store number, address, just like a paper organizational relationship list. There are an infinite number of possibilities available for a company to include data on an 816 Organizational Relationships. There are an infinite number of possibilities available for a company to include data on an 816 - Organizational Relationships.

How is a 816 - Organizational Relationships used?

The 816 Organizational Relationships is transmitted by the trading partner to the supplier to eliminate the need to send separate address information for purchase orders or other documents. After the 816 Organizational Relationships is received, a 997 Functional Acknowledgment is sent back from the transportation provider indicating that the Organizational Relationships was successfully received.

How is a 816 - Organizational Relationships processed?

An EDI solution is required to process the EDI documents received into an ERP or accounting system or into a readable format for manual entry. Each trading partner will have an EDI Implementation guide outlining the specific segments, data elements, values accepted, and the applicable business rules to be followed.

eBridge Connections has pre-built maps for all EDI transaction documents including 850 purchase orders, 810 invoices, and 856 advance shipping notices.