X12 210 Motor Carrier Freight Details and Invoice
This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Freight Details and Invoice Transaction Set (210) for use within the context of an Electronic Data Interchange (EDI) environment.
The transaction set can be used to provide detail information for charges for services rendered by a motor carrier. It is used both as a motor carrier invoice to request payment or as details pertaining to motor freight shipment(s) charges.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- IM
- Motor Carrier Freight Details and Invoice (210, 980)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 210
- Motor Carrier Freight Details and Invoice
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Carrier's Invoice
To transmit basic data relating to the carrier's invoice
Identifying number assigned by issuer
Radiant Invoice Number
Code identifying payment terms for transportation charges
- TP
- Third Party
Date expressed as CCYYMMDD
- B306 is the billing date.
Invoice Date: YYYYMMDD
Total charges to be paid by the receiver of this transaction set expressed in the standard monetary denomination for the currency specified
Total Charges Due
Code used to indicate that the transaction set contains information which corrects previous information
- AD
- Addition
- CO
- Correction
Currency
To specify the currency being used in the transaction set
Code (Standard ISO) for country in whose currency the charges are specified
- C301 is the billing currency.
Currently, only USD invoices (and payment) are supported.
- USD
- US Dollar
Date/Time
To specify pertinent dates and times
Remarks
To transmit information in a free-form format for comment or special instruction
Free-form information
Optional Remarks
The N1 in the header is for the Bill-To party and the Bill-From party (the Radiant remittance location). The Shipper and Consignee are listed below in the LX loop.
Name
To identify a party by type of organization, name, and code
The N1 in the header is for the Bill-To party and the Bill-From party (the Radiant remittance location). The Shipper and Consignee are listed below in the LX loop.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Bill-To/From City
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Bill-To/From State-Province
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Bill-To/From Zip-Postal Code
Code identifying the country
Bill-To/From County
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Detail
Assigned Number
To reference a line number in a transaction set
Note: The LX loop will repeat in the event of a consolidated invoice. If this is not a consolidated invoice, there will be only one iteration of the LX loop – representing one shipment. For each item in a consolidated invoice there will be a LX loop with the individual charges and each shipper and
consignee, representing each shipment on the consolidated invoice.
Number assigned for differentiation within a transaction set
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
This will occur 1 to 3 times. One, with the ‘WY’ qualifier will be the Radiant housebill number,which will always be present. If a customer purchase order number and/or customer bill of lading number were provided at the time of booking, then these values will be listed each in a separate N9 iteration with ‘PO’ and ‘BM’ qualifiers respectively.
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- PO
- Purchase Order Number
- WY
- Our house bill
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Proof of Delivery
To provide proof of delivery
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
Sequential line number for a lading item
Description of an item as required for rating and billing purposes
- L502 may be used to send quantity information as part of the product description.
Contents of the shipment
Line Item - Quantity and Weight
To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data
The contents of the shipment are itemized here for customer audit approval. The 210 EDI only allows up to ten L0 lines, so any items after the tenth will be omitted from the EDI invoice.
Sequential line number for a lading item
Number of units (pieces) of the lading commodity
- L008 is the number of handling units of the line item tendered to the carrier.
Number of pieces
Rate and Charges
To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements
Sequential line number for a lading item
Rate that applies to the specific commodity
Rate
Code qualifying how to extend charges or interpret value
- FR
- Flat Rate
For a line item: freight or special charge; for the total invoice: the total charges -- expressed in the standard monetary denomination for the currency specified
Charge
Code identifying type of special charge or allowance
Code for the Charge
Identification of special charge; this data element is used whenever an applicable code cannot be found in data element 150
Charge Description
Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81
Quantity
Code identifying the type of quantity or value on which the rate or item pricing is based
- EA
- Each
Code (Standard ISO) for country in whose currency the charges are specified
- L120, if used, indicates the currency for all monetary amounts in this L1 segment.
Code for Currency
Measurement
To describe physical dimensions and quantities
Volumetric data about the shipment contents itemized in the L0 segment. The L4 segment has no line item number, but these are listed in the same order as the contents listed in the L0 segment
Largest horizontal dimension of an object measured when the object is in the upright position
Length
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Width
Vertical dimension of an object measured when the object is in the upright position
Height
Code specifying the linear dimensional unit
- C
- Centimeters
- E
- Feet
- N
- Inches
- X
- Meters
Name
To identify a party by type of organization, name, and code
- Loops 0460 and 0463 shall be used to identify all small package carrier details related to the consignee (delivery location) and the related shipment. The shipper shall be identified in loop 0100.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Summary
Total Weight and Charges
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
Numeric value of weight
Total billable weight
For a line item: freight or special charge; for the total invoice: the total charges -- expressed in the standard monetary denomination for the currency specified
- L305 is the total charges.
Total charge for this invoice
Number of units (pieces) of the lading commodity
Total package quantity
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
210 Sample
GS*IM*ABCD*AGRP*20130329*0644*88*X*004010~
ST*210*000001167~
B3**987654321**TP**20130326*11883****ABCD*20130326~
G62*03*20130328~
G62*13*20130326~
K1*NOTES~
N1*BF*ABC COMPANY~
N3*123 MANUFACTURERS DR~
N4*PAWNEE*IN*60001~
N1*BT*RADIANT LOGISTICS~
N3*405 114TH AVE SE FL 3~
N4*BELLEVUE*WA*980046475~
LX*1~
N9*BM*123456789~
N9*PO*987654321~
L5*1*PLASTIC STUFF~
L0*1***120*G***1*PCS**L~
L1*1*386.52*FR*38652~
L1*2***-29602****DSC~
L1*3*28.33*FR*2833****FUE~
N1*SF*NOW FORWARDING~
N3*123 YABETCHA LN~
N4*LAREDO*TX*78000~
N1*ST*ABC COMPANY~
N3*123 MANUFACTURERS DR~
N4*PAWNEE*IN*60001~
L3*120*B***11883******1~
SE*27*000001167~
GE*1*88~
IEA*1*000000308~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.