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
- None included
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
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)
"The Bill of lading number (BOL) could be referenced as Shipping Bill of lading number, a Order #, or Shipper's number. If there is a RMA number, please use the RMA number in the B3 03.
If there is no BOL number type ""NONE"", Field is to be captured.
Note: A ""Shipper"" number is not the same as a ""Shipment"" number. “MANUAL BOL” or ""NS"" is not a valid bill of lading number. "
Code identifying payment terms for transportation charges
Allowable terms of sale are: Prepaid, Collect and Third Party. Please make sure to look at the terms of sale on the back up documentation and capture them correctly.
Date expressed as CCYYMMDD
- B306 is the billing date.
Invoice date is Required
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
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
Code qualifying the Reference Identification
- CR
- Customer Reference Number
- GL
- Geographic Destination Zone Number
- IN
- Consignee's Invoice Number
- LD
- Loan Number
- OR
- Order/Paragraph Number
- PO
- Purchase Order Number
- QT
- Warranty Registration Number
- SN
- Seal Number
- VN
- Vendor Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
N9-01 = CR:
This is the EDI Ref. # which can be found on the location listing (Tab two). If the terms of sale are Prepaid, submit the shippers reference number. If the terms of sale are collect, submit the consignee's ref. #. And if the terms are third party, submit the bill to's ref. #
N9-01 = PO:
"Collect shipments for Laticrete require a purchase order number/Signed POD. PO number is required to be captured and is all numeric.
Range is all numeric and normally 6 digits and can vary in range. If there is a PO number available out of the 6 digit range, please go ahead and capture. Do not key the alphas on the end of the PO numbers.
Please submit for both inbound/collect shipments when available.
When there are multiple PO numbers, please submit and type ""multiple"" in the 1st N9 PO segment, then submit each PO number individually in separate multiple N9 PO Segments.
If there is no PO number available type ""NONE""."
N9-01 = SN:
"Submit the Shipment number from the Laticrete Bill of Lading. Shipment number must be be captured on prepaid shipments.
Starts with number 14 and is 8 digits in range.
Note: Appointment numbers begin with 700, 701,Etc on collect or third party shipments. Do not submit appointment number (begins with 700 or 701) as a shipment number.
(Shipment # is mostly on prepaid Laticrete BOLs, only capture when presented, if there isn't one leave blank).
Prepaid shipments require the shipment number. *If prepaid terms and shipment number (N9 SN) is not available, the invoice may be subject to suspend/hold or reject.
Note: A ""Shipper"" number is not the same as a ""Shipment"" number. “NS” is not a valid Shipment number"
N9-01 = IN:
Dedicated Invoice number field, if a different number, other than invoice number, is populated in pro number field B3 02.
N9-01 = QT:
Local Custom Quote # needs to be captured when presented. When applicable, Custom Quote Number when presented on invoice, this signifies the invoice is approved. CST Quote # is ONLY captured when there is a special type of move (not on EDI)
N9-01 = OR:
Capture the order numbers when they are supplied on the invoice or back up. The order numbers should be 6 to 7 digits.*Capture the alphas on the end past the 6-7 range. This is required on prepaid shipments. The Order # is mostly on prepaid Laticrete BOLs, and can be on some collect terms, capture when presented, if there isn't one leave blank.
N9-01 = VN:
Vendor number
N9-01 = GL:
The full GL code can range up to 13 characters. Can be both alpha and numeric
N9-01 = LD:
Submit the Load number if applicable.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
- CN
- Consignee
- SN
- Store
Code designating the system/method of code structure used for Identification Code (67)
- ZZ
- Mutually Defined
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.
Shipper or Consignee Code
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)
Prefix or alphabetic part of an equipment unit's identifying number
- N701 is mandatory for rail transactions.
Element 01 and 02 will be combined during the translation at the VAN
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Element 01 and 02 will be combined during the translation at the VAN
Detail
"S5 / STOP OFF DETAIL -
Please create a N1 Loop (N1 (*USE ""CN"" as the N1 Qualifier) Name, N3 Address N4 City State and Zip) to each S5 Loop as needed for the stop off detail/Multiple stops:"
Stop Off Details
To specify stop-off detail reference numbers and stop reason
- Loops 0300, 0305, 0310 and 0320 shall only be used to identify all stop-off locations and associated data for loading and unloading of freight with the exception of the original stop-off location (shipper) for truckload carriers.
The original stop-off location (shipper) shall be transmitted in loop 0100.
Identifying number for the specific stop and the sequence in which the stop is to be performed
Sequential Number
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- PO
- Purchase Order Number
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
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
- CN
- Consignee
- SH
- Shipper
Code designating the system/method of code structure used for Identification Code (67)
- ZZ
- Mutually Defined
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
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)
Assigned Number
To reference a line number in a transaction set
Number assigned for differentiation within a transaction set
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.
Submit the commodity being shipped in the first LX loop, which should contain the freight charge. Lading description on freight is required. Example: Sand, Chemicals, Pails, and Labels, Color Kits, Powder, Foam, Kits, Shower Systems,Torginol, Etc.
Code describing a commodity or group of commodities
Submit the NMFC code in this element
Code identifying the commodity coding system used for Commodity Code
- N
- National Motor Freight Classification (NMFC)
Line Item - Quantity and Weight
To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data
Sequential line number for a lading item
Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81
This is the total miles when the rate is based per mile. Or As Weight/ Dimensional Weight. L0 02 is basis for miles when rated, or As weight/Dim weight.
Code identifying the type of quantity or value on which the rate or item pricing is based
- DM
- Miles
Numeric value of weight
This is the Total Net Weight of the charge amount.
Number of units (pieces) of the lading commodity
- L008 is the number of handling units of the line item tendered to the carrier.
"This is the Total Number of pieces. This is a mandatory field.
5 digits maximum."
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
Sequential line number for a lading item
Code qualifying how to extend charges or interpret value
FR=Flat Rate, CW= Counter/Per Hundred weight, ML or PM = Mileage or Per Mile, MN or MC or MI = Minimum charge, AC = Accessorial charge. Code qualifying how to extend charges or interpret value.
- AC
- Percent Of Amount Of Collection
- CW
- Per Hundred Weight
- FR
- Flat Rate
- MC
- Minimum Per Car
- MI
- Negative Charge
- ML
- Mileage
- MN
- Minimum
- 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
You will only submit this element in LX loops for charges other then Freight
Identification of special charge; this data element is used whenever an applicable code cannot be found in data element 150
Freight description is required/Special Charge Description is needed for GL coding.
Tariff Reference
To reference details of the tariff used to arrive at applicable rates or charge
Sequential line number for a lading item
Code indicating generalized classification that applies to one or more items in the shipment, i.e., class 70, 77.5, etc.
Class code is mandatory. Submit on all LTL shipments. Class 70 should read as 70 not 070. Required field on all LTL shipments, if the class is not presented the invoices will go on hold.
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
This is the Sum of all L0 04 weights
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.
This is the Sum of all L1 04 charges
Number of units (pieces) of the lading commodity
This is the Sum of all L0 08 / Number of Containers
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
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.