540 Notice of Employment Status (003070)

This is the standard X12 003070 spec, with 3 loops and 25 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 (71 KB) Generate classes
The ediFabric .NET template, class TS540. It needs the common segments, composites and codes of X12 003070, one download for every transaction in the version. Download C# (1 KB) Common files (238 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (52 KB)

Use the 540 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 540 files into TS540 objects. See ediFabric .NET.

ediFabric Native

Map version 003070 to the Native model with set_map, then parse 540 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 540 classes in Python, Java, Node.js, Go, Rust or C

ediFabric Native returns each 540 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 TS540. 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.

540 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
BGNBeginning SegmentMandatory1
Loop N1NameOptional>1
N1NameMandatory1
N2Additional Name InformationOptional2
N3Address InformationOptional2
N4Geographic LocationOptional1
PERAdministrative Communications ContactOptional>1
REFReference IdentificationOptional>1
Loop NM1Individual or Organizational NameMandatory>1
NM1Individual or Organizational NameMandatory1
N2Additional Name InformationOptional2
N3Address InformationOptional2
N4Geographic LocationOptional1
PERAdministrative Communications ContactOptional>1
REFReference IdentificationOptional>1
Loop ENTEntityMandatory>1
ENTEntityMandatory1
IN2Individual Name Structure ComponentsOptional>1
N3Address InformationOptional2
N4Geographic LocationOptional>1
REFReference IdentificationOptional>1
YNQYes/No QuestionOptional10
DTMDate/Time ReferenceOptional>1
HDHealth CoverageOptional1
EMSEmployment PositionOptional1
PAMPeriod AmountOptional>1
SETransaction Set TrailerOptional1