X12 204 Motor Carrier Load Tender
This X12 Transaction Set contains the format and establishes the data contents of the Motor Carrier Load Tender Transaction Set (204) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers or other interested parties to offer (tender) a shipment to a full load (truckload) motor carrier including detailed scheduling, equipment requirements, commodities, and shipping instructions pertinent to a load tender. It is not to be used to provide a motor carrier with data relative to a Less-than-Truckload bill of lading, pickup notification, or manifest.
- ~ Segment
- * Element
- > Component
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating 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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating 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
- SM
- Motor Carrier Load Tender (204)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 204
- Motor Carrier Load Tender
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Shipment Information Transaction
To transmit basic data relating to shipment information
Standard Carrier Alpha Code
- B202 contains the Standard Carrier Alpha Code (SCAC) of the carrier that will receive the bill of lading.
- B202 is mandatory for transaction set 204.
Carrier's SCAC Code
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 B2-04 element will contain the KINEXO load number that must be returned in the EDI 990 Response To a Load Tender B1-02 element and in the EDI 214 Order
Status Update B10-10 element.
• The KINEXO load number will begin with an “L”. (i.e.: L100850).
Code identifying payment terms for transportation charges
- DF
- Defined by Buyer and Seller
- PP
- Prepaid (by Seller)
Set Purpose
To allow for positive identification of transaction set purpose
Code identifying purpose of transaction set
KINEXO will send '03' for the delete and/or cancellation of an EDI 204 load tender in the B2A-01. If the carrier prefers the '01' code be sent instead of the '03' for cancellations then the carrier must inform KINEXO of this during testing.
KINEXO will send '05' for revisions/changes to an EDI 204 load tender.
All EDI 204 Revision/Changes must be responded to with an EDI 990 acceptance within 2 hours of the date/time on the EDI 204 load tender revision or the load my expire in the KINEXO TMS.
All EDI 204 Revision/Changes must be responded to with an EDI 990 acceptance within 2 hours of the date/time on the EDI 204 load tender revision or the load my expire in the KINEXO TMS.
AN EDI 990 ACCEPTANCE MUST BE RECIEVED FOR EACH EDI 204 LOAD TENDER REVISION/CHANGE EVEN IF THE ORIGINAL EDI 204 LOAD TENDER HAD PREVIOUSLY BEEN ACCEPTED VIA AN EDI 990.
For an EDI 204 Cancellation we request that the carrier NOT send an EDI 990, ONLY send an EDI 997 Functional Acknowledgement.
- 00
- Original
- 03
- Delete
'03'-Delete/Cancellation
- 05
- Replace
Revisions/Changes to the original EDI 204 load tender.
Code identifying an application
- BL
- Bill of Lading
- LT
- Load Tender - Truckload (TL) Carrier Only
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
The load number from our TMS system will begin with an “L”. (i.e.:L100850).
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- LO
- Load Planning Number
Date/Time
To specify pertinent dates and times
- Segment G62 in header is used to convey the must-respond-by date and time when responding to a 204 transaction.
The EDI 204 must be responded to with an EDI 990 or via the KINEXO carrier portal within 2 hours of the date/time on the EDI 204.
Cancellation 204's will be sent and the load tendered to another carrier if the response has not been received within the cancellation date/time.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
- ET
- Eastern Time
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Party Identification
To identify a party by type of organization, name, and code
- Loop 0100 is used to convey name and address detail relative to bill-to, party controlling freight, or other shipment level name and address information. It is not used to convey ship from or ship to detail which should be handled within loop 0300 in table 2.
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)
- 91
- Assigned by Seller or Seller's Agent
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.
Additional Name Information
To specify additional names
Party Location
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)
Contact
To identify a person or office to whom communications should be directed
Code identifying the major duty or responsibility of the person or group named
- BI
- Bill Inquiry Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- TE
- Telephone
Complete communications number including country or area code when applicable
Detail
Stop-off Details
To specify stop-off detail reference numbers and stop reason
Note:
The EDI 204 will contain at least one S5-LD and one S5-UL.
LD = Load Stop
UL = Unload Stop
Below are all the possible 204 stop sequence combinations that you should expect:
- SS1 - Single probill/Single pickup/Single delivery (LD - UL)
- SS2 - Multiple probills/Single pickup/Single delivery (LD - UL)
- SM - Multiple probills/Single pickup/Multiple deliveries (LD - UL+)
- MS - Multiple probills/Multiple pickups/Single delivery (LD+ - UL)
- MM - Multiple probills/Multiple pickups/Multiple deliveries (LD+ - UL+)
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
Please return the L11 CR - Customer Reference Numbers and the L11 PO KINEXO Customer PO Number
in the EDI 214s for the correct and corresponding stops.
Carrier should expect one or more reference numbers to be sent.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- AO
- Appointment Number
- AP
- Accounts Receivable Number
- BG
- Beginning Serial Number
- BM
- Bill of Lading Number
- BN
- Booking Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- CR
- Customer Reference Number
KINEXO Customer Reference Number - multiple may be sent.
- DO
- Delivery Order Number
- LO
- Load Planning Number
- P8
- Pickup Reference Number
- PO
- Purchase Order Number
KINEXO Customer PO Number
- SCA
- Standard Carrier Alpha Code (SCAC)
- SI
- Shipper's Identifying Number for Shipment (SID)
Date/Time
To specify pertinent dates and times
- Use G62 segment either in loop 0300 or loop 0350, but not both.
Carrier's EDI program should allow for all possible G62 Date Time formats to be sent from KINEXO.
Code specifying type of date
- 02
- Delivery Requested on This Date
- 10
- Requested Ship Date/Pickup Date
- 37
- Ship Not Before Date
- 38
- Ship Not Later Than Date
- 53
- Deliver Not Before Date
- 54
- Deliver No Later Than Date
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Code specifying the reported time
- 4
- Pickup Requested Scheduled Time
- 5
- Delivery Requested Scheduled Time
- G
- Earliest Requested Deliver Time
- I
- Earliest Requested Pickup Time
- K
- Latest Requested Pickup Time
- L
- Latest Requested Delivery Time
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)
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Party Identification
To identify a party by type of organization, name, and code
KINEXO requests that the address data sent on the EDI 204 is sent back on the EDI 214 from the carrier.
The N103 and N104 will not be sent on some EDI 204's from KINEXO.
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
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.
Additional Name Information
To specify additional names
Party Location
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)
Contact
To identify a person or office to whom communications should be directed
Code identifying the major duty or responsibility of the person or group named
- RE
- Receiving Contact
- SH
- Shipper Contact
Code identifying the type of communication number
- G6103 qualifies G6104.
- TE
- Telephone
Complete communications number including country or area code when applicable
Order Information Detail
To specify order information detail
- Use loop 0350 for conveying seller's order/invoice level detail or buyer's purchase order level detail. If not using order level detail, this loop should not be used.
Note that the OID-05 "Quantity" element, the OID-07 "Weight" element, and OID-09 "Volume" element are
NOT mandatory elements in the KINEXO EDI 204. Be prepared to receive and process some KINEXO EDI
204's without the OID-05, OID-07 and/or the OID-09 elements populated.
KINEXO does not populate the OID-01 or OID-03 elements.
Identifying number for Purchase Order assigned by the orderer/purchaser
Code for packaging form of the lading quantity
- PCS
- Pieces
Lading Detail
To transmit detailed lading data pertinent to a pickup or delivery
The LAD segment is NOT a mandatory segment from KINEXO. If the KINEXO TMS has the pallet count
field populated then it will be transmitted in this LAD segment. The carrier should anticipate some
KINEXO 204's will be sent with the LAD-02 element populated with a quanitity of "0".
One or more LAD segments will be sent per S5 stop depending upon how many PO's are on the stop.
Code for packaging form of the lading quantity
- SKD
- Skid
Number of units (pieces) of the lading commodity
KINEXO Note: The LAD-02 will contain the number of pallets if available in the KINEXO TMS
Description, Marks and Numbers
To specify the line item in terms of description, quantity, packaging, and marks and numbers
- If sending order level detail within the 0350 loop, then use L5 and AT8 segments in loop 0360 to relay commodity detail. Otherwise, use L5 and AT8 segments within the 0320 loop to relay commodity detail. Use either loop 0320 or loop 0360, but not both.
KINEXO uses the L5 segment to transmitt commodity information.
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.
Code describing a commodity or group of commodities
"DRY"
"FRESH"
"FROZEN"
"MIXED"
"REFRIGERATED"
"PRO" - Produce
"MEAT"
"FAK" - Freight of All Kinds
Code identifying the commodity coding system used for Commodity Code
- Z
- Mutually defined
Equipment Details
To identify the equipment
The N7 segment is optional. It will only be sent if it is available at the time the EDI 204 generates from the Kinexo TMS system.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
If no equipment number available and this N7 segment is sent, Kinexo will
populate N702 with zero '0'.
Standard Carrier Alpha Code
- N712 is the owner of the equipment.
Free-form abbreviation of temperature range or flash-point temperature
If the temperature range is available in the Kinexo TMS at the time the EDI 204 load tender is generated, it will be populated here.
Example: A temperature range of minus ten to minus twenty degrees fahrenheit would be shown as "-10-20".
All temperature will be in fahrenheit.
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
L3-03 will contain the freight rate amount (R2 format).
L3-05 contains the total charges including accessorials (N2 format).
L3-06 contains only the accessorial charges (N2 format).
(Subtract L3-06 from L3-05 for freight only amount)
Code qualifying how to extend charges or interpret value
- CW
- Per Hundred Weight
- FR
- Flat Rate
- PM
- Per Mile
- VS
- Various
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.
Incidental charges occurring during transportation which are not generally considered to be freight charges (examples - stop charges, diversion and reconsignment, icing) expressed in the standard monetary denomination for the currency specified
Number of units (pieces) of the lading commodity
Code specifying the weight unit
KINEXO Not Used
Standard tariff number for the tariff which governs the rates applied to the commodity item(s)
KINEXO Not Used
Monetary assigned value expressed in the standard monetary denomination for the currency specified
KINEXO Uses to send Total Declared Value if present in the KINEXO TMS. Note: KINEXO Uses to send Total Declared Value if present in the KINEXO TMS.Carrier should expect "0" to be sent at times.
If L3.14 = "0" or anything then L3.15 will = "ZZ".
Code qualifying how to extend charges or interpret value
- ZZ
- Mutually Defined
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.