EDI 816: Organizational Relationship

Read the guide below to learn about the EDI 816.

If you need to send or receive EDI 816s, contact our team of EDI experts today.

Speak with an EDI Expert
EDI Transaction Header

EDI 816: Organizational Relationship

What is an EDI 816?
The EDI 816 Organizational Relationship transmits location information in two formats. One format of the 816 is for providing location addresses. The second format is to communicate information about the organizational relationships between locations, such as stores services by specific Distribution Centers, warehouses, etc.


How to use an EDI 816?
An EDI 816 Organizational Relationship 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.

Many of the most commonly used EDI transactions, such as EDI 850 Purchase Orders and EDI 810 Invoices, typically do not include detailed location information.The EDI 816 transaction provides trading partners with the sender’s location addresses and their corresponding codes.


A parent organization with various locations may include any of the following within the EDI 816:

  • Manufacturers with multiple locations for production, assembly, distribution, etc.
  • Multi-hospital and medical facility healthcare systems
  • A chain of retail stores and regional distribution centers
  • Associations with regional membership locations


EDI 816 Specification 
This X12 Transaction Set contains the format and establishes the data contents of the Organizational Relationships Transaction Set (816) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to transmit pertinent information about a parent organization, its members and the relationship of a member to another member, and/or to the parent organization. A parent organization could be an association, a multi-hospital system, a chain of retail stores, a holding company, etc. This transaction set can be used to convey the identity and relationship of members to a parent organization; identify eligibility to purchase under the terms and conditions negotiated by a parent organization on behalf of its members; and to update application databases.


Accredited Standards Committee X12. ASC X12 Standard [Table Data]. Data Interchange Standards Association, Inc., Falls Church, VA. https://x12.org/index.php/products/transaction-sets

EDI transaction automation

Automate EDI / API Transactions

Eliminate manual integration flows by automating and orchestrating EDI and API-based transactions in an intuitive self-service, low-code development environment. 

Not ready for self-service? Leverage Cleo’s Managed Services team to get you up and running.

Keep a list of all X12 EDI transaction sets at hand.

Access a free EDI Transaction Set Guide

More EDI Resources

Explore additional EDI resources to deepen your understanding and enhance your proficiency in Electronic Data Interchange.

  • EDI compliance
    3 Ways to Become EDI Compliant & Eliminate EDI Chargebacks

    Many major companies have requirements for EDI trading partner setup and maintenance, both of which are important in keeping compliant...

    Read the Blog
  • EDI visibility
    EDI Visibility & Business Insights

    23% of companies say visibility is one of their biggest integration challenges. Let's analyze this issue and unleash a powerful solution...

    Read More
  • Cleo Integration Cloud EDI integration video resource
    EDI Integration in Action

    Explore a curated list of videos to help you understand the unprecedented value of EDI integration...

    Start Watching