410 Rail Carrier Freight Details and Invoice (004030)

This is the standard X12 004030 spec, with 6 loops and 45 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 (122 KB) Generate classes
The ediFabric .NET template, class TS410. It needs the common segments, composites and codes of X12 004030, one download for every transaction in the version. Download C# (1 KB) Common files (259 KB)
The intermediary model ediFabric Native loads with set_map. Download Native (101 KB)

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

ediFabric Native

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

ediFabric Native returns each 410 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 TS410. 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.

410 structure

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

IDNameUsageMax use
STTransaction Set HeaderOptional1
B3BBeginning Segment for Carrier's InvoiceMandatory1
C4Alternate Amount DueOptional1
N9Reference IdentificationOptional30
CMCargo ManifestOptional2
NTENote/Special InstructionOptional2
Loop N7Equipment DetailsMandatory500
N7Equipment DetailsMandatory1
VCMotor Vehicle ControlOptional30
G4Scale IdentificationOptional1
M7Seal NumbersOptional5
N5Equipment OrderedOptional1
ICIntermodal Chassis EquipmentOptional1
IMIntermodal Movement InformationOptional1
M12In-bond Identifying InformationOptional1
GACanadian Grain InformationOptional15
N8Waybill ReferenceMandatory499
F9Origin StationMandatory1
D9Destination StationMandatory1
Loop N1NameOptional15
N1NameMandatory1
N2Additional Name InformationOptional2
N3Address InformationOptional2
N4Geographic LocationOptional1
PERAdministrative Communications ContactOptional2
BLBilling InformationOptional12
Loop S1Stop-off NameOptional12
S1Stop-off NameMandatory1
S2Stop-off AddressOptional1
S9Stop-off StationOptional1
R2Route InformationOptional13
R9Route CodeOptional1
PSProtective Service InstructionsOptional5
Loop LXAssigned NumberMandatory25
LXAssigned NumberMandatory1
L5Description, Marks and NumbersMandatory15
Loop L0Line Item - Quantity and WeightMandatory25
L0Line Item - Quantity and WeightMandatory1
MEAMeasurementsOptional3
L1Rate and ChargesMandatory10
DTMDate/Time ReferenceOptional2
PIPrice Authority IdentificationOptional30
Loop T1Transit Inbound OriginOptional64
T1Transit Inbound OriginMandatory1
T2Transit Inbound LadingOptional30
T3Transit Inbound RouteOptional12
T6Transit Inbound RatesOptional1
T8Free-form Transit DataOptional99
L3Total Weight and ChargesMandatory1
X7Customs InformationOptional2
SETransaction Set TrailerOptional1