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
Beginning Segment for Carrier's Invoice
To transmit basic data relating to the carrier's invoice
Example: B3013581007054PP2001033194120**2001033035*CUOT
Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)
Code identifying payment terms for transportation charges
- CC
- Collect
- PP
- Prepaid (by Seller)
Total charges to be paid by the receiver of this transaction set expressed in the standard monetary denomination for the currency specified
Date for delivery of cargo to final consignee or to next mode expressed in format CCYYMMDD
- On collect freight bills the data in B309 will be the actual delivery date. For the shipments invoiced prior to delivery, the B309 will be the estimated date of delivery.
Code specifying type of date or time, or both date and time
- 035
- Delivered
Currency
To specify the currency being used in the transaction set
Example: C3*USD
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Example: N9CN8624793
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- CR
- Customer Reference Number / Trip Instance ID
- EQ
- Equipment Number
- MTI
- Master Tracking Number
Date/Time
To specify pertinent dates and times
Example: G621120010330
Route Information - Motor
To specify carrier and routing sequences and details
Example: R3CUOTO
Name
To identify a party by type of organization, name, and code
This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Example: N1BTCEVA LOGISTICS
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Address Information
To specify the location of the named party
Example: N3*10751 DEERWOOD PARK BLVD
Geographic Location
To specify the geographic place of the named party
Example: N4JACKSONVILLEFL*32256
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)
Name
To identify a party by type of organization, name, and code
This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Code identifying an organizational entity, a physical location, property or an individual
- CN
- Consignee
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Address Information
To specify the location of the named party
Example: N3*10751 DEERWOOD PARK BLVD
Geographic Location
To specify the geographic place of the named party
Example: N4JACKSONVILLEFL*32256
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)
Name
To identify a party by type of organization, name, and code
This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Code identifying an organizational entity, a physical location, property or an individual
- SH
- Shipper
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Address Information
To specify the location of the named party
Example: N3*10751 DEERWOOD PARK BLVD
Geographic Location
To specify the geographic place of the named party
Example: N4JACKSONVILLEFL*32256
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)
Detail
Assigned Number
To reference a line number in a transaction set
Example: LX*1
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
L502 may be used to send quantity information as part of the product description.
Example: L5**50
Line Item - Quantity and Weight
To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data
Example: L025DM862G25*PCS**L
Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81
Code identifying the type of quantity or value on which the rate or item pricing is based
- DM
- Miles
Number of units (pieces) of the lading commodity
- L008 is the number of handling units of the line item tendered to the carrier.
Code for packaging form of the lading quantity
- PCS
- Pieces
Rate and Charges
To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements
Example: L1*1.15PM*118220
Code qualifying how to extend charges or interpret value
- FR
- Flat Rate
- PM
- Per Mile
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
Code identifying type of special charge or allowance
Tariff Reference
To reference details of the tariff used to arrive at applicable rates or charge
Example: L7*******100
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
Example: L328290G118220**34L
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.
Number of units (pieces) of the lading commodity
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 1
GS*IM*SENDERGS*RECEIVERGS*20240524*152113*000000001*X*004010~
ST*210*0001~
B3**0135810*07054*PP**20010331*94120**20010330*035*CUOT~
C3*USD~
N9*CN*8624793~
G62*11*20010330~
R3*CUOT*O~
N1*BT*CEVA LOGISTICS~
N3*10751 DEERWOOD PARK BLVD~
N4*JACKSONVILLE*FL*32256~
LX*1~
L5**50~
L0**25*DM*862*G***25*PCS**L~
L1**1.15*PM*118220~
L7*******100~
L3*28290*G***118220******34*L~
SE*16*0001~
GE*1*000000001~
IEA*1*000000001~
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.