ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 816 — Organizational Relationships

The 816 transmits organizational structure between two partners: hierarchy, divisions, sub-entities, role assignments for business processes.

Purpose

The 816 documents the internal structure of an enterprise for its EDI partners: divisions, departments, profit centers, physical locations with their codes, parent-child hierarchy. It helps partners correctly route transactions, attribute invoices to right profit centers, avoid crossing independent entities.

It is typical at partner onboarding setup and during reorganizations (mergers, divestitures). Acknowledged by 997.

Envelope structure

The 816 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group OR, and ST/SE). Didactic example in release 004010:

x12 example-816.x12 
ISA*00*          *00*          *ZZ*PARENTCO      *ZZ*PARTNERCO      *260514*1300*U*00401*000000816*0*P*>~
GS*OR*PARENTCO*PARTNERCO*20260514*1300*1*X*004010~
ST*816*0001~
BGN*00*OR-2026-0042*20260514~
N1*PT*PARENT CORP*24*EIN-PARENT~
LX*1~
N1*CH*DIVISION NORTH*24*EIN-DIVN~
N4*CHICAGO*IL*60601*US~
LX*2~
N1*CH*DIVISION SOUTH*24*EIN-DIVS~
N4*DALLAS*TX*75201*US~
SE*10*0001~
GE*1*1~
IEA*1*000000816~

Common segments

  • Header — ST, BGN.
  • Parent — N1*PT (Parent entity), REF*ZZ (DUNS, EIN).
  • Children — repeated LX loop: N1*CH (Child entity), N3/N4, REF*ZZ (cost center, profit center code).
  • Hierarchy — for multi-level structures, an HL can document relationships.
  • Summary — SE.

Common pitfalls

  • EIN vs operating identifier: federal EIN and internal operating identifier may diverge; the 816 must include both for correct routing and tax compliance.
  • Stale data: an 816 outdated after merger or divestiture can route invoices to a non-existent entity; mandatory regular refresh.
  • Privacy in mergers: during pre-merger due diligence, premature disclosure of structure may violate the confidentiality agreement.

Documentation

The code 816 and the name Organizational Relationships are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.