SCI Group
/
Motor Carrier Load Tender
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from SCI Group. Contact SCI Group for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
SCI Group logo

X12 204 Motor Carrier Load Tender

X12 Release 4010

This Draft Standard for Trial Use 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, pick-up notification, or manifest.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/sci-group/motor-carrier-load-tender/01HRQ06RDJVPPG9D2B87YJV379
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
B2
020
Beginning Segment for Shipment Information Transaction
Max use 1
Required
B2A
030
Set Purpose
Max use 1
Required
L11
080
Business Instructions and Reference Number
Max use 50
Required
G62
090
Date/Time
Max use 1
Required
AT5
110
Bill of Lading Handling Requirements
Max use 6
Required
NTE
130
Note/Special Instruction
Max use 10
Required
0200 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

SM
Motor Carrier Load Tender (204)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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).
204
Motor Carrier Load Tender
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

B2
020
Heading > B2

Beginning Segment for Shipment Information Transaction

RequiredMax use 1

To transmit basic data relating to shipment information

Example
B2-04
145
Shipment Identification Number
Required
String (AN)
Min 1Max 30

Freight Bill #

B2-05
188
Weight Unit Code
Required
Identifier (ID)
Min 1Max 1

Code specifying the weight unit

B2-06
146
Shipment Method of Payment
Required
Identifier (ID)

Code identifying payment terms for transportation charges

PP
Prepaid (by Seller)
B2-07
147
Shipment Qualifier
Required
Identifier (ID)
Min 1Max 1

Code defining relationship of this shipment with respect to other shipments given to the carrier at the same time

B2A
030
Heading > B2A

Set Purpose

RequiredMax use 1

To allow for positive identification of transaction set purpose

Example
B2A-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
B2A-02
346
Application Type
Required
Identifier (ID)

Code identifying an application

LT
Load Tender
L11
080
Heading > L11

Business Instructions and Reference Number

RequiredMax use 50

To specify instructions in this business relationship or a reference number

Example
L11-01
127
Reference Identification
Required
String (AN)
Min 1Max 30

Start Zone (ship from postal code) OR End Zone (ship to postal code)

Example values
  • H7T 2Z2
  • H7T 2P6
L11-02
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

9S
Delivery Region
SF
Ship From
L11-03
352
Description
Required
String (AN)
Min 1Max 80

City, Province

G62
090
Heading > G62

Date/Time

RequiredMax use 1

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.
Example
G62-01
432
Date Qualifier
Required
Identifier (ID)

Code specifying type of date

64
Must Respond By
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

G62-03
176
Time Qualifier
Required
Identifier (ID)

Code specifying the reported time

1
Must Respond By
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

Usage notes

Disregard timezone; all times are local.

G62-05
623
Time Code
Required
Identifier (ID)
Min 2Max 2

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

AT5
110
Heading > AT5

Bill of Lading Handling Requirements

RequiredMax use 6

To identify Bill of Lading handling and service requirements

Example
AT5-01
152
Service Level
Required
Identifier (ID)
Min 2Max 3

Code specifying special transportation handling instructions

Example values
  • 2H
  • 30M
  • 4H
  • 60M
  • 90M
  • DIR
  • NFO
  • SCH
NTE
130
Heading > NTE

Note/Special Instruction

RequiredMax use 10

To transmit information in a free-form format, if necessary, for comment or special instruction

Example
NTE-01
363
Note Reference Code
Required
Identifier (ID)

Code identifying the functional area or purpose for which the note applies

Usage notes

SHP (type D for pickup notes) or DEL (type O for Delivery notes)

DEL
Delivery
SHP
NTE-02
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

0200 Loop
RequiredMax >1
N7
200
Heading > 0200 Loop > N7

Equipment Details

RequiredMax use 1

To identify the equipment

Example
N7-02
207
Equipment Number
Required
String (AN)
Min 1Max 10

Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

N7-11
40
Equipment Type
Required
Identifier (ID)

Code identifying type of equipment used for shipment

5T
5 Tonne
BK
Bike/Car
CA
Cargo Van
CU
Cube Van
LG
Lift Gate
ST
Straight Truck
TR
Trailer
VN
Van
0200 Loop end
Heading end

Detail

0300 Loop Load
RequiredMax 1
Variants (all may be used)
0300 Loop Unload
S5
010
Detail > 0300 Loop Load > S5

Stop Off Details

RequiredMax use 1

To specify stop-off detail reference numbers and stop reason

Example
S5-01
165
Stop Sequence Number
Required
Numeric (N0)
Min 1Max 3

Identifying number for the specific stop and the sequence in which the stop is to be performed

S5-02
163
Stop Reason Code
Required
Identifier (ID)

Code specifying the reason for the stop

LD
Load
G62
030
Detail > 0300 Loop Load > G62

Date/Time

RequiredMax use 2

To specify pertinent dates and times

  • Use G62 segment either in loop 0300 or loop 0350, but not both.
Example
G62-01
432
Date Qualifier
Required
Identifier (ID)

Code specifying type of date

37
Ship Not Before Date
38
Ship Not Later Than Date
G62-02
373
Pickup Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Early Pickup Date OR Late Pickup Date

G62-03
176
Time Qualifier
Required
Identifier (ID)
Min 1Max 2

Code specifying the reported time

Example values
  • Y
  • 1
G62-04
337
Pickup Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

Usage notes

Early Pickup Time OR Late Pickup Time

G62-05
623
Time Code
Required
Identifier (ID)
Min 2Max 2

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

0310 Loop
RequiredMax >1
N1
070
Detail > 0300 Loop Load > 0310 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SH
Shipper
N1-02
93
Shipper Name
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

93
Code assigned by the organization originating the transaction set
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
N3
090
Detail > 0300 Loop Load > 0310 Loop > N3

Address Information

RequiredMax use 2

To specify the location of the named party

Example
N3-01
166
Shipper Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N4
100
Detail > 0300 Loop Load > 0310 Loop > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Example
N4-01
19
Shipper City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
Shipper State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Shipper Postal Code/Zip Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

G61
120
Detail > 0300 Loop Load > 0310 Loop > G61

Contact

RequiredMax use 3

To identify a person or office to whom communications should be directed

Example
G61-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

SH
Shipper Contact
G61-02
93
Shipper Name
Required
String (AN)
Min 1Max 60

Free-form name

G61-03
365
Communication Number Qualifier
Required
Identifier (ID)

Code identifying the type of communication number

  • G6103 qualifies G6104.
TE
Telephone
G61-04
364
Shipper Communication Number
Required
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

0310 Loop end
0300 Loop Load end
0300 Loop Unload
RequiredMax 1
Variants (all may be used)
0300 Loop Load
S5
010
Detail > 0300 Loop Unload > S5

Stop Off Details

RequiredMax use 1

To specify stop-off detail reference numbers and stop reason

Example
S5-01
165
Stop Sequence Number
Required
Numeric (N0)
Min 1Max 3

Identifying number for the specific stop and the sequence in which the stop is to be performed

S5-02
163
Stop Reason Code
Required
Identifier (ID)

Code specifying the reason for the stop

UL
Unload
L11
020
Detail > 0300 Loop Unload > L11

Business Instructions and Reference Number

RequiredMax use 50

To specify instructions in this business relationship or a reference number

Example
L11-01
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

L11-02
128
Reference Identification Qualifier
Required
Identifier (ID)
Min 2Max 3

Code qualifying the Reference Identification

G62
030
Detail > 0300 Loop Unload > G62

Date/Time

RequiredMax use 2

To specify pertinent dates and times

  • Use G62 segment either in loop 0300 or loop 0350, but not both.
Example
G62-01
432
Date Qualifier
Required
Identifier (ID)

Code specifying type of date

53
Deliver Not Before Date
54
Deliver No Later Than Date
G62-02
373
Delivery Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Early Delivery Date OR Late Delivery Date

G62-03
176
Time Qualifier
Required
Identifier (ID)
Min 1Max 2

Code specifying the reported time

Example values
  • Y
  • 1
G62-04
337
Delivery Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

Usage notes

Early Delivery Time OR Late Delivery Time

G62-05
623
Time Code
Required
Identifier (ID)
Min 2Max 2

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

0310 Loop
RequiredMax >1
N1
070
Detail > 0300 Loop Unload > 0310 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

CN
Consignee
N1-02
93
Con. Name
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

93
Code assigned by the organization originating the transaction set
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

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.
N3
090
Detail > 0300 Loop Unload > 0310 Loop > N3

Address Information

RequiredMax use 2

To specify the location of the named party

Example
N3-01
166
Con. Address Information
Required
String (AN)
Min 1Max 55

Address information

N4
100
Detail > 0300 Loop Unload > 0310 Loop > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Example
N4-01
19
Con. City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
Con. State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Con. Postal Code/Zip Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

G61
120
Detail > 0300 Loop Unload > 0310 Loop > G61

Contact

RequiredMax use 3

To identify a person or office to whom communications should be directed

Example
G61-01
366
Con. Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

RE
Receiving Contact
Required
String (AN)
Min 1Max 60

Free-form name

G61-03
365
Communication Number Qualifier
Required
Identifier (ID)

Code identifying the type of communication number

  • G6103 qualifies G6104.
TE
Telephone
G61-04
364
Con. Communication Number
Required
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

0310 Loop end
0320 Loop
RequiredMax >1
L5
130
Detail > 0300 Loop Unload > 0320 Loop > L5

Description, Marks and Numbers

RequiredMax use 1

To specify the line item in terms of description, quantity, packaging, and marks and numbers

Example
If either Commodity Code (L5-03) or Commodity Code Qualifier (L5-04) is present, then the other is required
L5-01
213
Lading Line Item Number
Required
Numeric (N0)
Min 1Max 3

Sequential line number for a lading item

L5-02
79
Lading Description
Required
String (AN)
Min 1Max 50

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.
L5-03
22
Commodity Code
Optional
String (AN)
Min 1Max 30

Code describing a commodity or group of commodities

L5-04
23
Commodity Code Qualifier
Required
Identifier (ID)
Min 1Max 1

Code identifying the commodity coding system used for Commodity Code

AT8
135
Detail > 0300 Loop Unload > 0320 Loop > AT8

Shipment Weight, Packaging and Quantity Data

RequiredMax use 1

To specify shipment details in terms of weight, and quantity of handling units

Example
AT8-01
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

G
Gross Weight
AT8-02
188
Weight Unit Code
Required
Identifier (ID)

Code specifying the weight unit

L
Pounds
AT8-03
81
Weight
Required
Decimal number (R)
Min 1Max 10

Numeric value of weight

AT8-04
80
Pieces
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

  • AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
AT8-05
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

  • AT805 is the quantity of handling units that are unitized (for example on a pallet or slip sheet). When added to the quantity in AT804 it is the total quantity of handling units for the shipment.
AT8-06
184
Volume Unit Qualifier
Required
Identifier (ID)
Min 1Max 1

Code identifying the volume unit

AT8-07
183
Volume
Required
Decimal number (R)
Min 1Max 8

Value of volumetric measure

0320 Loop end
0300 Loop Unload end
Detail end

Summary

L3
010
Summary > L3

Total Weight and Charges

RequiredMax use 1

To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

Example
If either Volume (L3-09) or Volume Unit Qualifier (L3-10) is present, then the other is required
If either Interliner Amount (L3-03) or Interliner Accessorial Amount (L3-04) is present, then the other is required
L3-01
81
Weight
Required
Decimal number (R)
Min 1Max 10

Numeric value of weight

L3-02
187
Total Gross Weight of Shipment and Equipment
Required
Identifier (ID)

Code defining the type of weight

G
Gross Weight
L3-03
60
Interliner Amount
Optional
Decimal number (R)
Min 1Max 9

Rate that applies to the specific commodity

L3-04
122
Interliner Accessorial Amount
Optional
Identifier (ID)
Min 2Max 2

Code qualifying how to extend charges or interpret value

L3-05
58
Charge
Required
Numeric (N2)
Min 1Max 12

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.
L3-09
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

L3-10
184
Volume Unit Qualifier
Required
Identifier (ID)
Min 1Max 1

Code identifying the volume unit

L3-11
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

L3-12
188
Weight Unit Code
Required
Identifier (ID)
Min 1Max 1

Code specifying the weight unit

SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample 1

ST*204*618950001~
B2****F0051400*L*PP*L~
B2A*00*LT~
L11*H4T 2B4*SF*SAINT-LAURENT,QC~
L11*H9S 5X5*9S*DORVAL,QC~
G62*64*20240304*1*1650*PT~
AT5*DIR~
NTE*SHP*FLASH 2154321 CISCO SYSTEM~
NTE*DEL*DELIVER BETWEEN 0930-0945 AM MAR 05~
N7**TRAILER*********BK~
S5*1*LD~
G62*37*20240304*Y*1238*LT~
G62*38*20240304*Y*1238*LT~
N1*SH*CP02 -P306/P336 - MONTREAL CPN*93*YUL-003~
N3*625 RUE GOUGEON*LOW DOCK-NEED TAILGATE~
N4*SAINT-LAURENT*QC*H4T 2B4~
G61*SH*ROBERT*TE*514-989-1906~
S5*2*UL~
L11*2154321*Z1~
L11*12.2154321*BM~
L11*12.2154321*PO~
G62*53*20240305*Y*0930*LT~
G62*54*20240305*Y*0930*LT~
N1*CN*BELL CANADA~
N3*200 BOUL BOUCHARD SS 1 DORVAL~
N4*DORVAL*QC*H9S 5X5~
G61*RE*OCCBellSupport Support*TE*18663549295Ext801243~
L5*1*UCS-MR-X32G2RS-H=*XXXX*Z~
AT8*G*L*0*1*0*E*0~
L3*0*G***0****0*E*1*L~
SE*31*618950001~

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.