223 Consolidators Freight Bill and Invoice (005040)

This is the standard X12 005040 spec, with 8 loops and 28 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 (66 KB) Generate classes

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

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

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

ediFabric Native

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

ediFabric Native returns each 223 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 TS223. 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.

223 structure

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

ID	Name	Usage	Max use
ST	Transaction Set Header	Optional	1
B10	Beginning Segment for Transportation Carrier Shipment Status Message	Optional	1
B3A	Invoice Type	Mandatory	1
B2A	Set Purpose	Mandatory	1
Loop N1	Party Identification	Optional	10
N1	Party Identification	Mandatory	1
N2	Additional Name Information	Optional	1
N3	Party Location	Optional	2
N4	Geographic Location	Optional	1
L11	Business Instructions and Reference Number	Optional	5
Loop N7	Equipment Details	Optional	10
N7	Equipment Details	Mandatory	1
M7	Seal Numbers	Optional	5
Loop CSD	Consolidated Shipment Invoice Data	Optional	9999
CSD	Consolidated Shipment Invoice Data	Mandatory	1
Loop OID	Order Information Detail	Optional	9999
OID	Order Information Detail	Mandatory	1
SDQ	Destination Quantity	Optional	10
Loop LX	Transaction Set Line Number	Mandatory	9999
LX	Transaction Set Line Number	Mandatory	1
N1	Party Identification	Optional	1
N2	Additional Name Information	Optional	1
N3	Party Location	Optional	2
N4	Geographic Location	Optional	1
L11	Business Instructions and Reference Number	Optional	10
Loop LS	Loop Header	Optional	1
LS	Loop Header	Mandatory	1
Loop CSD	Consolidated Shipment Invoice Data	Optional	9999
CSD	Consolidated Shipment Invoice Data	Mandatory	1
AT8	Shipment Weight, Packaging and Quantity Data	Optional	1
L1	Rate and Charges	Optional	10
LE	Loop Trailer	Mandatory	1
Loop OID	Order Information Detail	Optional	9999
OID	Order Information Detail	Mandatory	1
SDQ	Destination Quantity	Optional	10
SE	Transaction Set Trailer	Optional	1