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
Example: B3123456SHIPMENT_IDTP20190925261465**20190925035SCAC20190925~
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)
Redwood customer’s unique identifier for the shipment.
Code identifying payment terms for transportation charges
- CC
- Collect
- PP
- Prepaid (by Seller)
- TP
- Third Party Pay
Total charges to be paid by the receiver of this transaction set expressed in the standard monetary denomination for the currency specified
Total invoice amount (with implied decimal, e.g., 261465 means $2,614.65).
Code used to indicate that the transaction set contains information which corrects previous information
If an EDI 210 is being issued as a correction to a previous EDI 210, this will be set to CO.
- CO
- Correction
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
Standard Carrier Alpha Code
Carrier’s designated SCAC identifier code.
Currency
To specify the currency being used in the transaction set
Example: C3*USD~
Code (Standard ISO) for country in whose currency the charges are specified
- C301 is the billing currency.
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Used to specify additional reference numbers beyond those provided on the B3 segment.
Examples:
N9P8PICKUP_NO~
N9POPO_NUMBER~
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Time
To specify pertinent dates and times
Used to specify additional reference numbers beyond those provided on the B3 segment.
Route Information - Motor
To specify carrier and routing sequences and details
Used to define the shipment mode type to the carrier’s invoice.
This segment fits between the G62 and N1.
Example: R3SCACB**M.~
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
Code specifying the method or type of transportation for the shipment
- A
- Air
- LT
- Less Than Trailer Load (LTL)
- M
- Motor (Common Carrier)
- MP
- Motor (Package Carrier)
- O
- Containerized Ocean
- R
- Rail
- X
- Intermodal (Piggyback)
Name
To identify a party by type of organization, name, and code
Examples: N1BTPAYING PARTY93ABCD1234~
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)
If using a location identifier codes, use 93.
- 93
- Code assigned by the organization originating the transaction set
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.
If using location identifier codes, please send code as received on tender. Location code required when BT entity identifier code is used. Required to match 204 N104.
Address Information
To specify the location of the named party
Example: N31765 N Elston AveSuite 300~
Geographic Location
To specify the geographic place of the named party
Example: N4CHICAGOIL60622USA~
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
Examples:
N1SHSHIPPING PARTY ~
N1CNRECEIVING PARTY~
Code identifying an organizational entity, a physical location, property or an individual
- CN
- Consignee
- SF
- Ship From
- SH
- Shipper
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
If using a location identifier codes, use 93.
- 93
- Code assigned by the organization originating the transaction set
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.
If using location identifier codes, please send code as received on tender. Location code required when BT entity identifier code is used. Required to match 204 N104.
Address Information
To specify the location of the named party
Example: N31765 N Elston AveSuite 300~
Geographic Location
To specify the geographic place of the named party
Example: N4CHICAGOIL60622USA~
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
If the Entity Identifier Code of “LW” is included in the tender, the data in the N1 segment must be included on corresponding 210 messages.
Example: N1LWCustomer Name93CUSTOMERCODE~
Code identifying an organizational entity, a physical location, property or an individual
- LW
- Customer
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
Redwood Customer Code
Detail
Assigned Number
To reference a line number in a transaction set
Example: LX*1~
Number assigned for differentiation within a transaction set
Invoice charge line sequence number.
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
Example: L51LINE HAUL~
Sequential line number for a lading item
Invoice charge line item sequence number (matches LX).
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.
Description of invoice charge line.
Line Item - Quantity and Weight
To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data
L013 is used to convey the total number of boxes, cartons, or pieces contained on a pallet, skid, or slip sheet for the line item.
Example: L0143000FR43000G3*PCSL~
Sequential line number for a lading item
Invoice charge line sequence number (matches LX).
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
- FR
- Flat Rate
Number of units (pieces) of the lading commodity
- L008 is the number of handling units of the line item tendered to the carrier.
Total Quantity Shipped
Code for packaging form of the lading quantity
- PCS
- Pieces
- PLT
- Pallet
Rate and Charges
To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements
If either L102 or L103 is present, then the other is required.
Example: L112100.00FR210000****400~
Sequential line number for a lading item
Invoice charge line sequence number (matches LX).
Rate that applies to the specific commodity
Rate Per Unit
Code qualifying how to extend charges or interpret value
Type of per unit rate qualifier.
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
Amount of charge (decimal implied).
Code identifying type of special charge or allowance
ANSI standard EDI code for type of charge.
Identification of special charge; this data element is used whenever an applicable code cannot be found in data element 150
Tariff Reference
To reference details of the tariff used to arrive at applicable rates or charge
Mandatory for base (non-accessorial) charges.
L7 segment is only needed for LTL loads.
Example: L71*****85~
Sequential line number for a lading item
Invoice charge line sequence number (matches LX).
Code indicating generalized classification that applies to one or more items in the shipment, i.e., class 70, 77.5, etc.
Code indicating generalized classification that applies to one or more items in the shipment, i.e., class 70, 77.5, etc.
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: L343000G261465***3~
Code qualifying how to extend charges or interpret value
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 invoice amount (with implied decimal, e.g., 261465 means $2,614.65).
Number of units (pieces) of the lading commodity
Total sum of quantities.
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
Sample
C3*USD~
N9*P8*PICKUP_NO~
N9*PO*PO_NUMBER~
G62*86*20190923~
N1*LW*Customer Name*93*CUSTOMERCODE~
N1*BT*PAYING PARTY*93*ABCD1234~
N3*1765 N ELSTON*SUITE 300~
N4*CHICAGO*IL*60642*USA~
N1*SH*SHIPPING PARTY~
N3*1234 SHIPPERS STREET~
N4*SUMNER*WA*98390*USA~
N1*CN*RECEIVING PARTY~
N3*9876 RECEIVERS ROAD~
N4*CHICAGO*IL*60606*USA~
LX*1~
L5*1*LINE HAUL~
L0*1*43000*FR*43000*G***3*PCS**L~
L1*1*2100.00*FR*210000****400~
L7*1******85~
LX*2~
L5*2*FUEL SURCHARGE~
L1*2*0.235*PM*51465****FUE****FUEL SURCHARGE~
L3*43000*G***261465******3~
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.