816 Organizational Relationships (005020)

This is the standard X12 005020 spec, with 3 loops and 22 segment positions, as OpenEDI JSON, an ediFabric C# template and an ediFabric Native model. To change it for a trading partner, customize it in the EDI Spec Builder.

Loading the spec…

The spec as an OpenAPI 3 schema with x-openedi-* extensions, for ediFabric Native, ediFabric Cloud and the EDI Spec Builder. Download OpenEDI (68 KB) Generate classes

The ediFabric .NET template, class TS816. It needs the common segments, composites and codes of X12 005020, one download for every transaction in the version. Download C# (1 KB) Common files (267 KB)

The intermediary model ediFabric Native loads with set_map. Download Native (48 KB)

Use the 816 spec in your code

ediFabric .NET

Add the C# template and its common files to your project, or reference the template NuGet package, and read 816 files into TS816 objects. See ediFabric .NET.

ediFabric Native

Map version 005020 to the Native model with set_map, then parse 816 files to JSON from Python, Java, C or C#. See Convert between EDI and JSON.

OpenEDI

Select Customize in Spec Builder to copy the spec under your own name, change it for your partner, and parse files against it in EdiNation, ediFabric Native or ediFabric Cloud. Read about OpenEDI.

Generate 816 classes in Python, Java, Node.js, Go, Rust or C

ediFabric Native returns each 816 as JSON, with the property names of the OpenEDI schema. To work with that JSON as typed objects, generate classes from the OpenEDI file in your language and deserialize the JSON into TS816. Serialize the objects back to JSON to build EDI with ediFabric Native. The classes keep the loops, segments, lengths and code lists, but not the EDI data formats, so validate files with ediFabric Native. Read more in Generate a class from OpenEDI.

Python: datamodel-code-generator. Node.js: openapi-typescript. Java, Go, Rust and C: OpenAPI Generator.

816 structure

Loops and segments of the standard 816, with their usage and maximum repeats.

ID	Name	Usage	Max use
ST	Transaction Set Header	Optional	1
BHT	Beginning of Hierarchical Transaction	Mandatory	1
DTM	Date/Time Reference	Optional	10
REF	Reference Information	Optional	12
Loop N1	Party Identification	Mandatory	>1
N1	Party Identification	Mandatory	1
N2	Additional Name Information	Optional	2
N3	Party Location	Optional	2
N4	Geographic Location	Optional	1
PER	Administrative Communications Contact	Optional	3
REF	Reference Information	Optional	12
Loop HL	Hierarchical Level	Mandatory	>1
HL	Hierarchical Level	Mandatory	1
Loop N1	Party Identification	Mandatory	>1
N1	Party Identification	Mandatory	1
N2	Additional Name Information	Optional	2
N3	Party Location	Optional	2
N4	Geographic Location	Optional	1
PER	Administrative Communications Contact	Optional	>1
REF	Reference Information	Optional	12
QTY	Quantity Information	Optional	5
DTM	Date/Time Reference	Optional	10
LQ	Industry Code Identification	Optional	>1
ASI	Action or Status Indicator	Optional	1
SE	Transaction Set Trailer	Optional	1