CSA Software
/
Motor Carrier Bill of Lading
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from CSA Software. Contact CSA Software for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
CSA Software

X12 211 Motor Carrier Bill of Lading

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Bill of Lading Transaction Set (211) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers or other parties, responsible for contracting with a motor carrier, to provide a legal bill of lading for a shipment. It is not to be used to provide a motor carrier with data relative to a load tender, pick-up manifest, or appointment scheduling.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    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
    BOL
    020
    Beginning Segment for the Motor Carrier Bill of Lading
    Max use 1
    Required
    B2A
    030
    Set Purpose
    Max use 1
    Required
    L11
    060
    Bill of Lading Number
    Max use 100
    Optional
    L11
    060
    Customer Reference Number
    Max use 100
    Optional
    G62
    070
    Delivery Date
    Max use 6
    Optional
    G62
    070
    Ship Date/Pick-up Date
    Max use 6
    Optional
    AT5
    080
    Bill of Lading Handling Requirements
    Max use 50
    Optional
    0100 Loop
    detail
    0200 Loop
    SE
    220
    Transaction Set Trailer
    Max use 1
    Required
    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

    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
    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

    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
    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
    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
    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
    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
    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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    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

    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
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    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
    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
    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

    Code identifying a group of application related transaction sets

    BL
    Motor Carrier Bill of Lading (211)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

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

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

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

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    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

    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

    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

    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).
    211
    Motor Carrier Bill of Lading
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

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

    BOL
    020

    Beginning Segment for the Motor Carrier Bill of Lading

    RequiredMax use 1

    To transmit identifying numbers, dates, and other basic data related to the transaction set

    Example
    BOL-01
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    • BOL01 is the Standard Carrier Alpha Code (SCAC) of the carrier that is to provide transportation services.
    Usage notes

    SCAC CODE – Please insert your SCAC code

    BOL-02
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • BOL02 is the method of payment for the freight charges.
    CC
    Collect
    PP
    Prepaid (by Seller)
    TP
    Third Party Pay
    BOL-03
    145
    Shipment Identification Number
    Required
    Min 1Max 30

    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)

    • BOL03 is the identification number assigned by the shipper, usually the Bill of Lading number.
    BOL-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BOL04 is the date the carrier picked up the freight.
    BOL-05
    337
    Time
    Optional
    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)

    • BOL05 is the actual time the carrier picked up the freight.
    BOL-06
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    • BOL06 is the number assigned by the carrier to the shipment, usually the PRO number.
    B2A
    030

    Set Purpose

    RequiredMax use 1

    To allow for positive identification of transaction set purpose

    Example
    B2A-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    01
    Cancellation
    04
    Change
    L11
    060

    Bill of Lading Number

    OptionalMax use 100

    To specify instructions in this business relationship or a reference number

    Example
    Variants (all may be used)
    L11Customer Reference Number
    L11-01
    127
    Reference Identification
    Optional
    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

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    L11
    060

    Customer Reference Number

    OptionalMax use 100

    To specify instructions in this business relationship or a reference number

    Example
    Variants (all may be used)
    L11Bill of Lading Number
    L11-01
    127
    Reference Identification
    Optional
    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

    Code qualifying the Reference Identification

    CR
    Customer Reference Number
    G62
    070

    Delivery Date

    OptionalMax use 6

    To specify pertinent dates and times

    Example
    Variants (all may be used)
    G62Ship Date/Pick-up Date
    If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
    G62-01
    432
    Date Qualifier
    Required

    Code specifying type of date

    68
    Delivery Date
    G62-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    G62-03
    176
    Time Qualifier
    Optional

    Code specifying the reported time

    E
    Earliest time
    L
    Latest time
    G62-04
    337
    Time
    Optional
    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)

    G62
    070

    Ship Date/Pick-up Date

    OptionalMax use 6

    To specify pertinent dates and times

    Example
    Variants (all may be used)
    G62Delivery Date
    If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
    G62-01
    432
    Date Qualifier
    Required

    Code specifying type of date

    10
    Ship Date/Pick-up Date
    G62-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    G62-03
    176
    Time Qualifier
    Optional

    Code specifying the reported time

    E
    Earliest time
    L
    Latest time
    G62-04
    337
    Time
    Optional
    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)

    AT5
    080

    Bill of Lading Handling Requirements

    OptionalMax use 50

    To identify Bill of Lading handling and service requirements

    Example
    AT5-01
    152
    Special Handling Code
    Optional

    Code specifying special transportation handling instructions

    DEL
    Delivery
    PUC
    Pickup
    0100 Loop
    OptionalMax >1
    N1
    100

    Name

    RequiredMax use 1

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

    • Loop 0100 is used to specify the parties to the Bill of Lading, including but not limited to, the ship-from, ship-to, or bill-to parties.
    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    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

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

    BT
    Bill-to-Party
    CN
    Consignee
    DL
    Delivery
    DT
    Destination
    FR
    From
    OT
    Origin
    PU
    Pick-up
    SF
    Ship From
    SH
    Shipper
    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    25
    Bill-To or Ship-to Customer Number
    N1-04
    67
    Identification Code
    Optional
    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
    120

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    130

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    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
    State or Province Code
    Optional
    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
    Postal Code
    Optional
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    G61
    140

    Contact

    OptionalMax use 3

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

    Example
    If either Communication Number Qualifier (G61-03) or Communication Number (G61-04) is present, then the other is required
    G61-01
    366
    Contact Function Code
    Required

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

    IC
    Information Contact
    G61-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    G61-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    • G6103 qualifies G6104.
    EM
    Electronic Mail
    FX
    Facsimile
    TE
    Telephone
    G61-04
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    Detail

    0200 Loop
    RequiredMax >1
    AT1
    010

    Bill of Lading Line Item Number

    RequiredMax use 1

    To reference a Bill of Lading line number

    • The AT1 segment provides the line number for all of the related items included.
      It may include reference numbers, rates and charges, descriptions, and or line item details. Any data included within a single loop is related to the other data included in that loop. Any reference numbers included in a loop with line item details are related to that line item only. Any reference numbers included in its own line item are related to the entire shipment and can not be broken out by line item detail.
    Example
    AT1-01
    213
    Lading Line Item Number
    Required
    Min 1Max 3

    Sequential line number for a lading item

    L11
    020

    Bill of Lading Number

    OptionalMax use 100

    To specify instructions in this business relationship or a reference number

    Example
    Variants (all may be used)
    L11Customer Reference Number
    If either Reference Identification (L11-01) or Reference Identification Qualifier (L11-02) is present, then the other is required
    L11-01
    127
    Reference Identification
    Optional
    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

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    L11
    020

    Customer Reference Number

    OptionalMax use 100

    To specify instructions in this business relationship or a reference number

    Example
    Variants (all may be used)
    L11Bill of Lading Number
    If either Reference Identification (L11-01) or Reference Identification Qualifier (L11-02) is present, then the other is required
    L11-01
    127
    Reference Identification
    Optional
    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

    Code qualifying the Reference Identification

    CR
    Customer Reference Number
    AT4
    040

    Bill of Lading Description

    OptionalMax use 99

    To specify the lading description

    • Segment AT4 provides a means for the shipper to provide a text description of the line item. The National Motor Freight Classification and the freight class shall be included in the AT2 segment if applicable.
    Example
    AT4-01
    79
    Lading Description
    Required
    Min 1Max 50

    Description of an item as required for rating and billing purposes

    0210 Loop
    OptionalMax >1
    AT2
    050

    Bill of Lading Line Item Detail

    RequiredMax use 1

    To specify Bill of Lading quantity, weight, and commodity classification

    • The AT2 segment is used to provide the carrier with the appropriate data to rate the shipment. It is included per line item when the line item includes an item of freight.
    Example
    AT2-01
    80
    Lading Quantity
    Required
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    • AT201 is the number of carrier handling units for the line item.
    AT2-02
    211
    Packaging Form Code
    Required
    Min 3Max 3

    Code for packaging form of the lading quantity

    • AT202 is the packaging form of the lading quantity in AT201.
    AT2-03
    187
    Weight Qualifier
    Required

    Code defining the type of weight

    • AT203 and AT204 qualify AT205.
    G
    Gross Weight
    AT2-04
    188
    Weight Unit Code
    Required

    Code specifying the weight unit

    K
    Kilograms
    L
    Pounds
    AT2-05
    81
    Weight
    Required
    Min 1Max 10

    Numeric value of weight

    • AT205 is the weight of the lading quantity identified in AT201.
    SE
    220

    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
    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
    Min 4Max 9

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

    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
    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
    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
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    ISA*00* *00* *02*CSA *12*VEND *161207*1422*U*00401*000000001*0*P*:
    GS*SM*CSA*VEND*20161207*145500*000000001*X*004010
    ST*211*000000144
    BOL*TEST*TP*022423*20230329*0713*EWR
    B2A*00
    L11*04070100000417178*BM
    AT5*DEL
    N1*SH*EXPEDITORS INTL. OF WASHINGTON*25*2136663
    N3*123 MAIN
    N4*HANAHAN*SC*29406*USA
    G61*IC*Monica Young*TE*(888)555-1234
    N1*CN*EXPEDITORS INTERNATIONAL
    N3*4260 FRONTAGE ROAD
    N4*ATLANTA*GA*30354*USA
    AT1*1
    L11*4310019971*CR
    AT4*SOLID FRENCH DOUBLE DOORS / MELA 7
    AT2*1*CNT*G*L*80
    SE*15*000000144
    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.