Redwood Logistics
/
Motor Carrier Freight Details and Invoice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Redwood Logistics. Contact Redwood Logistics for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Redwood Logistics logo

X12 210 Motor Carrier Freight Details and Invoice

X12 Release 4010

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.

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
    B3
    020
    Beginning Segment for Carrier's Invoice
    Max use 1
    Required
    C3
    040
    Currency
    Max use 1
    Optional
    N9
    060
    Reference Identification
    Max use 300
    Optional
    G62
    070
    Date/Time
    Max use 6
    Optional
    R3
    080
    Route Information - Motor
    Max use 12
    Optional
    Bill-to-Party
    Customer
    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

    IM
    Motor Carrier Freight Details and Invoice (210, 980)
    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).
    210
    Motor Carrier Freight Details and Invoice
    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

    B3
    020

    Beginning Segment for Carrier's Invoice

    RequiredMax use 1

    To transmit basic data relating to the carrier's invoice

    Usage notes

    Example: B3123456SHIPMENT_IDTP20190925261465**20190925035SCAC20190925~

    Example
    If either Delivery Date (B3-09) or Date/Time Qualifier (B3-10) is present, then the other is required
    B3-02
    76
    Invoice Number
    Required
    Min 1Max 22

    Identifying number assigned by issuer

    B3-03
    145
    Shipment Identification Number
    Optional
    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)

    Usage notes

    Redwood customer’s unique identifier for the shipment.

    B3-04
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    CC
    Collect
    PP
    Prepaid (by Seller)
    TP
    Third Party Pay
    B3-05
    188
    Weight Unit Code
    Optional

    Code specifying the weight unit

    K
    Kilograms
    L
    Pounds
    B3-06
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • B306 is the billing date.
    B3-07
    193
    Net Amount Due
    Required
    Min 1Max 12

    Total charges to be paid by the receiver of this transaction set expressed in the standard monetary denomination for the currency specified

    Usage notes

    Total invoice amount (with implied decimal, e.g., 261465 means $2,614.65).

    B3-08
    202
    Correction Indicator
    Optional

    Code used to indicate that the transaction set contains information which corrects previous information

    Usage notes

    If an EDI 210 is being issued as a correction to a previous EDI 210, this will be set to CO.

    CO
    Correction
    B3-09
    32
    Delivery Date
    Optional
    CCYYMMDD format

    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.
    B3-10
    374
    Date/Time Qualifier
    Optional

    Code specifying type of date or time, or both date and time

    035
    Delivered
    B3-11
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    Usage notes

    Carrier’s designated SCAC identifier code.

    B3-12
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    C3
    040

    Currency

    OptionalMax use 1

    To specify the currency being used in the transaction set

    Usage notes

    Example: C3*USD~

    Example
    C3-01
    100
    Currency Code
    Required
    Min 3Max 3

    Code (Standard ISO) for country in whose currency the charges are specified

    • C301 is the billing currency.
    N9
    060

    Reference Identification

    OptionalMax use 300

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    Used to specify additional reference numbers beyond those provided on the B3 segment.

    Examples:
    N9P8PICKUP_NO~
    N9POPO_NUMBER~

    Example
    At least one of Reference Identification (N9-02) or Free-form Description (N9-03) is required
    N9-01
    128
    Reference Identification Qualifier
    Required
    Min 2Max 3

    Code qualifying the Reference Identification

    N9-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    N9-03
    369
    Free-form Description
    Optional
    Min 1Max 45

    Free-form descriptive text

    G62
    070

    Date/Time

    OptionalMax use 6

    To specify pertinent dates and times

    Usage notes

    Used to specify additional reference numbers beyond those provided on the B3 segment.

    Example
    If either Date Qualifier (G62-01) or Date (G62-02) is present, then the other is required
    G62-01
    432
    Date Qualifier
    Optional

    Code specifying type of date

    03
    Invoice Date
    11
    Shipped on This Date
    35
    Delivered on This Date
    86
    Actual Pickup Date
    G62-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    R3
    080

    Route Information - Motor

    OptionalMax use 12

    To specify carrier and routing sequences and details

    Usage notes

    Used to define the shipment mode type to the carrier’s invoice.

    This segment fits between the G62 and N1.

    Example: R3SCACB**M.~

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

    Standard Carrier Alpha Code

    R3-02
    133
    Routing Sequence Code
    Required

    Code describing the relationship of a carrier to a specific shipment movement

    B
    Origin/Delivery Carrier (Any Mode)
    R3-04
    91
    Transportation Method/Type Code
    Required

    Code specifying the method or type of transportation for the shipment

    A
    Air
    LT
    Less Than Trailer Load (LTL)
    M
    Motor (Common Carrier)
    MP
    Motor (Package Carrier)
    O
    Containerized Ocean
    R
    Rail
    X
    Intermodal (Piggyback)
    0100 Bill-to-Party
    OptionalMax >1
    Variants (all may be used)
    0100Consignee or Ship From or Shipper or Ship To0100Customer
    N1
    110

    Name

    RequiredMax use 1

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

    Usage notes

    Examples: N1BTPAYING PARTY93ABCD1234~

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) 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
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    Usage notes

    Name of the location/involved party.

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    Usage notes

    If using a location identifier codes, use 93.

    93
    Code assigned by the organization originating the transaction set
    N1-04
    67
    Identification Code
    Required
    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.
    Usage notes

    If using location identifier codes, please send code as received on tender. Location code required when BT entity identifier code is used. Required to match 204 N104.

    N3
    130

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Usage notes

    Example: N31765 N Elston AveSuite 300~

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

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    140

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    Example: N4CHICAGOIL60622USA~

    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

    0100 Consignee or Ship From or Shipper or Ship To
    OptionalMax >1
    Variants (all may be used)
    0100Bill-to-Party0100Customer
    N1
    110

    Name

    RequiredMax use 1

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

    Usage notes

    Examples:
    N1SHSHIPPING PARTY ~
    N1CNRECEIVING PARTY~

    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

    CN
    Consignee
    SF
    Ship From
    SH
    Shipper
    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    Usage notes

    Name of the location/involved party.

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    Usage notes

    If using a location identifier codes, use 93.

    93
    Code assigned by the organization originating the transaction set
    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.
    Usage notes

    If using location identifier codes, please send code as received on tender. Location code required when BT entity identifier code is used. Required to match 204 N104.

    N3
    130

    Address Information

    RequiredMax use 2

    To specify the location of the named party

    Usage notes

    Example: N31765 N Elston AveSuite 300~

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

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    140

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Usage notes

    Example: N4CHICAGOIL60622USA~

    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

    0100 Customer
    RequiredMax >1
    N1
    110

    Name

    RequiredMax use 1

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

    Usage notes

    If the Entity Identifier Code of “LW” is included in the tender, the data in the N1 segment must be included on corresponding 210 messages.

    Example: N1LWCustomer Name93CUSTOMERCODE~

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    LW
    Customer
    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)

    93
    Code assigned by the organization originating the transaction set
    N1-04
    67
    Identification Code
    Required
    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.
    Usage notes

    Redwood Customer Code

    Detail

    0400 Loop
    RequiredMax >1
    LX
    120

    Assigned Number

    RequiredMax use 1

    To reference a line number in a transaction set

    Usage notes

    Example: LX*1~

    Example
    LX-01
    554
    Assigned Number
    Required
    Min 1Max 6

    Number assigned for differentiation within a transaction set

    Usage notes

    Invoice charge line sequence number.

    L5
    140

    Description, Marks and Numbers

    RequiredMax use 30

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

    Usage notes

    Example: L51LINE HAUL~

    Example
    L5-01
    213
    Lading Line Item Number
    Required
    Min 1Max 3

    Sequential line number for a lading item

    Usage notes

    Invoice charge line item sequence number (matches LX).

    L5-02
    79
    Lading Description
    Optional
    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.
    Usage notes

    Description of invoice charge line.

    L0
    170

    Line Item - Quantity and Weight

    OptionalMax use 10

    To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data

    Usage notes

    L013 is used to convey the total number of boxes, cartons, or pieces contained on a pallet, skid, or slip sheet for the line item.

    Example: L0143000FR43000G3*PCSL~

    Example
    If either Billed/Rated-as Quantity (L0-02) or Billed/Rated-as Qualifier (L0-03) is present, then the other is required
    If either Weight (L0-04) or Weight Qualifier (L0-05) is present, then the other is required
    If either Lading Quantity (L0-08) or Packaging Form Code (L0-09) is present, then the other is required
    If Weight Unit Code (L0-11) is present, then Weight (L0-04) is required
    L0-01
    213
    Lading Line Item Number
    Required
    Min 1Max 3

    Sequential line number for a lading item

    Usage notes

    Invoice charge line sequence number (matches LX).

    L0-02
    220
    Billed/Rated-as Quantity
    Optional
    Min 1Max 11

    Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81

    L0-03
    221
    Billed/Rated-as Qualifier
    Optional

    Code identifying the type of quantity or value on which the rate or item pricing is based

    FR
    Flat Rate
    L0-04
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    L0-05
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    G
    Gross Weight
    L0-08
    80
    Lading Quantity
    Optional
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    • L008 is the number of handling units of the line item tendered to the carrier.
    Usage notes

    Total Quantity Shipped

    L0-09
    211
    Packaging Form Code
    Optional

    Code for packaging form of the lading quantity

    PCS
    Pieces
    PLT
    Pallet
    L0-11
    188
    Weight Unit Code
    Optional

    Code specifying the weight unit

    K
    Kilograms
    L
    Pounds
    L1
    180

    Rate and Charges

    RequiredMax use 10

    To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements

    Usage notes

    If either L102 or L103 is present, then the other is required.

    Example: L112100.00FR210000****400~

    Example
    If either Freight Rate (L1-02) or Rate/Value Qualifier (L1-03) is present, then the other is required
    L1-01
    213
    Lading Line Item Number
    Required
    Min 1Max 3

    Sequential line number for a lading item

    Usage notes

    Invoice charge line sequence number (matches LX).

    L1-02
    60
    Freight Rate
    Optional
    Min 1Max 9

    Rate that applies to the specific commodity

    Usage notes

    Rate Per Unit

    L1-03
    122
    Rate/Value Qualifier
    Optional
    Min 2Max 2

    Code qualifying how to extend charges or interpret value

    Usage notes

    Type of per unit rate qualifier.

    L1-04
    58
    Charge
    Optional
    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

    Usage notes

    Amount of charge (decimal implied).

    L1-08
    150
    Special Charge or Allowance Code
    Optional
    Min 3Max 3

    Code identifying type of special charge or allowance

    Usage notes

    ANSI standard EDI code for type of charge.

    L1-12
    276
    Special Charge Description
    Optional
    Min 2Max 25

    Identification of special charge; this data element is used whenever an applicable code cannot be found in data element 150

    L7
    200

    Tariff Reference

    OptionalMax use 10

    To reference details of the tariff used to arrive at applicable rates or charge

    Usage notes

    Mandatory for base (non-accessorial) charges.

    L7 segment is only needed for LTL loads.

    Example: L71*****85~

    Example
    L7-01
    213
    Lading Line Item Number
    Required
    Min 1Max 3

    Sequential line number for a lading item

    Usage notes

    Invoice charge line sequence number (matches LX).

    L7-07
    59
    Freight Class Code
    Required
    Min 2Max 5

    Code indicating generalized classification that applies to one or more items in the shipment, i.e., class 70, 77.5, etc.

    Usage notes

    Code indicating generalized classification that applies to one or more items in the shipment, i.e., class 70, 77.5, etc.

    Summary

    L3
    010

    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

    Usage notes

    Example: L343000G261465***3~

    Example
    If either Weight (L3-01) or Weight Qualifier (L3-02) is present, then the other is required
    If either Freight Rate (L3-03) or Rate/Value Qualifier (L3-04) is present, then the other is required
    L3-01
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    Usage notes

    Total Shipment Weight

    L3-02
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    G
    Gross Weight
    L3-03
    60
    Freight Rate
    Optional
    Min 1Max 9

    Rate that applies to the specific commodity

    L3-04
    122
    Rate/Value Qualifier
    Optional
    Min 2Max 2

    Code qualifying how to extend charges or interpret value

    L3-05
    58
    Charge
    Optional
    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.
    Usage notes

    Total invoice amount (with implied decimal, e.g., 261465 means $2,614.65).

    L3-11
    80
    Lading Quantity
    Optional
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    Usage notes

    Total sum of quantities.

    SE
    020

    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

    B3**123456*SHIPMENT_ID*TP**20190925*261465**20190925*035*SCAC*20190925~
    C3*USD~
    N9*P8*PICKUP_NO~
    N9*PO*PO_NUMBER~
    G62*86*20190923~
    N1*LW*Customer Name*93*CUSTOMERCODE~
    N1*BT*PAYING PARTY*93*ABCD1234~
    N3*1765 N ELSTON*SUITE 300~
    N4*CHICAGO*IL*60642*USA~
    N1*SH*SHIPPING PARTY~
    N3*1234 SHIPPERS STREET~
    N4*SUMNER*WA*98390*USA~
    N1*CN*RECEIVING PARTY~
    N3*9876 RECEIVERS ROAD~
    N4*CHICAGO*IL*60606*USA~
    LX*1~
    L5*1*LINE HAUL~
    L0*1*43000*FR*43000*G***3*PCS**L~
    L1*1*2100.00*FR*210000****400~
    L7*1******85~
    LX*2~
    L5*2*FUEL SURCHARGE~
    L1*2*0.235*PM*51465****FUE****FUEL SURCHARGE~
    L3*43000*G***261465******3~

    Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.