X12 transaction code
X12 816 Organizational Relationships
X12 816 Organizational Relationships: explore its business purpose, mapping identifiers, validation tests and 4 partner references across 6 listed channels.
- Standard
- X12
- Code
- 816
- Partner references
- 4
Implementation guide
X12 816 mapping and validation
X12 816 Organizational Relationships is used when trading-party or location relationships change. Preserve organization, location and parent references so the organization and location hierarchy in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | organization and location hierarchy organization, location and parent references |
|
| Update the receiving system | Processing the organization and location hierarchy ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the organization and location hierarchy Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 856 Ship Notice Manifest
shipment notice (ASN): shipment contents are known before the agreed notification deadline.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when trading-party or location relationships change. Name the operational owner of the organization and location hierarchy and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map organization, location and parent references. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic organization and location hierarchy data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful organization and location hierarchy processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 816 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic organization and location hierarchy data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out organization and location hierarchy without processing it twice.
Document structure
X12 816 Organizational Relationships at the element level
The X12 816 reference contains 17 segment entries and 79 data elements; 38 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 17
- Data elements
- 79
- Mandatory elements
- 38
| Segment | Elements | Mandatory |
|---|---|---|
| BHT | 6 | 2 |
| N1 | 6 | 1 |
| HL | 4 | 2 |
| N3 | 2 | 1 |
| PER | 9 | 1 |
| REF | 3 | 1 |
| DTM | 6 | 1 |
| ASI | 3 | 2 |
- Hierarchical Structure Code
- Transaction Set Purpose Code
- Entity Identifier Code
- Hierarchical ID Number
- Hierarchical Level Code
- Address Information
- Contact Function Code
- Reference Identification Qualifier
Find your trading partner for X12 816
4 partners, 6 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 816 Organizational Relationships appears in this catalog
The largest groups of classified 816 catalog entries are in apparel & footwear and retail.
By industry
- apparel & footwear 5 channels
- retail 1 channel
By network
- InterTrade 1 channel
FAQ
X12 816 questions
What is X12 816 Organizational Relationships used for?
816 is used when trading-party or location relationships change. It carries information for the organization and location hierarchy. Match it to your business system using organization, location and parent references.
Which partners list X12 816?
The directory on this page links 4 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
What should I map for X12 816?
Start with organization, location and parent references and the target organization and location hierarchy. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 816 error handling?
Move a store between parent organizations without changing its stable location identity. Test an inactive ship-to location referenced by an open order. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 816 relate to other EDI messages?
X12 850 Purchase Order; X12 856 Ship Notice Manifest are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 816 and 850?
816 is used when trading-party or location relationships change. 850 is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
