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

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
    N1
    110
    Name
    Max use 1
    Required
    N3
    130
    Address Information
    Max use 2
    Optional
    N4
    140
    Geographic Location
    Max use 1
    Optional
    Consignee
    N1
    110
    Name
    Max use 1
    Required
    N3
    130
    Address Information
    Max use 2
    Optional
    N4
    140
    Geographic Location
    Max use 1
    Optional
    Shipper
    N1
    110
    Name
    Max use 1
    Required
    N3
    130
    Address Information
    Max use 2
    Optional
    N4
    140
    Geographic Location
    Max use 1
    Optional
    detail
    0400 Loop
    LX
    120
    Assigned Number
    Max use 1
    Required
    L0
    170
    Line Item - Quantity and Weight
    Max use 10
    Optional
    L1
    180
    Rate and Charges
    Max use 10
    Optional
    summary
    L3
    010
    Total Weight and Charges
    Max use 1
    Optional
    SE
    020
    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
    GS

    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

    Example
    B3-02
    76
    Invoice Number
    Required
    Min 1Max 22

    Identifying number assigned by issuer

    B3-04
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    PP
    Prepaid (by Seller)
    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 14

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

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

    Standard Carrier Alpha Code

    C3
    040

    Currency

    OptionalMax use 1

    To specify the currency being used in the transaction set

    Example
    C3-01
    100
    Currency Code
    Required

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

    • C301 is the billing currency.
    USD
    US Dollar
    N9
    060

    Reference Identification

    OptionalMax use 300

    To transmit identifying information as specified by the Reference Identification Qualifier

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    2I
    Tracking Number
    BM
    Bill of Lading Number
    CO
    Customer Order Number
    PL
    Price List Number
    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

    G62
    070

    Date/Time

    OptionalMax use 6

    To specify pertinent dates and times

    Example
    G62-01
    432
    Date Qualifier
    Optional

    Code specifying type of date

    86
    Actual Pickup Date
    G62-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    G62-03
    176
    Time Qualifier
    Optional

    Code specifying the reported time

    8
    Actual Pickup 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)

    R3
    080

    Route Information - Motor

    OptionalMax use 12

    To specify carrier and routing sequences and details

    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
    Optional

    Code specifying the method or type of transportation for the shipment

    C
    Consolidation
    0100 Bill To Party
    OptionalMax 10
    Variants (all may be used)
    0100Consignee0100Shipper
    N1
    110

    Name

    RequiredMax use 1

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

    Example
    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

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    25
    Carrier's Customer Code
    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
    130

    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

    N4
    140

    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

    Code identifying the country

    USA
    United States of America (the)
    0100 Consignee
    OptionalMax 10
    Variants (all may be used)
    0100Bill To Party0100Shipper
    N1
    110

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    CN
    Consignee
    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
    Carrier's Customer Code
    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
    130

    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

    N4
    140

    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

    Code identifying the country

    USA
    United States of America (the)
    0100 Shipper
    OptionalMax 10
    Variants (all may be used)
    0100Bill To Party0100Consignee
    N1
    110

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    SH
    Shipper
    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
    Carrier's Customer Code
    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
    130

    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

    N4
    140

    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

    Code identifying the country

    USA
    United States of America (the)

    Detail

    0400 Loop
    OptionalMax 9999
    LX
    120

    Assigned Number

    RequiredMax use 1

    To reference a line number in a transaction set

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

    Number assigned for differentiation within a transaction set

    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

    Example
    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

    MR
    Mileage
    L0-04
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    L0-05
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    LB
    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.
    L0-09
    211
    Packaging Form Code
    Optional

    Code for packaging form of the lading quantity

    PCS
    Pieces
    L1
    180

    Rate and Charges

    OptionalMax use 10

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

    Example
    L1-04
    58
    Charge
    Optional
    Min 1Max 14

    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

    L1-08
    150
    Special Charge or Allowance Code
    Optional

    Code identifying type of special charge or allowance

    FAILEDMAPLOOKUP
    FSC
    NXD
    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

    Summary

    L3
    010

    Total Weight and Charges

    OptionalMax 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
    L3-01
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    L3-02
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    G
    Gross Weight
    L3-05
    58
    Charge
    Optional
    Min 1Max 14

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

    GE

    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

    IEA

    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

    AXCC210_202308231047.1.txt

    ISA*00* *00* *02*AXCC *ZZ*MGDOHMEN *230823*1047*U*00400*000000212*0*P*>~
    GS*IM*AXCC*MGDOHMEN*20230823*1047*212*X*004010~
    ST*210*002120001~
    B3**14754478**PP**20230725*82250****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14754478*~
    N9*PL*FR*~
    G62*86*20230719*8*1722~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****76869****NXD****NextDay~
    LX*2~
    L1****5381****FSC**~
    L3*1*G***82250***~
    SE*25*002120001~
    ST*210*002120002~
    B3**14754479**PP**20230725*90415****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14754479*~
    N9*PL*FR*~
    G62*86*20230719*8*1733~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****75000****NXD****NextDay~
    LX*2~
    L1****9500****FAILEDMAPLOOKUP**~
    LX*3~
    L1****5915****FSC**~
    L3*1*G***90415***~
    SE*27*002120002~
    ST*210*002120003~
    B3**14747794**PP**20230725*82250****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14747794*~
    N9*PL*FR*~
    G62*86*20230717*8*1759~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****76869****NXD****NextDay~
    LX*2~
    L1****5381****FSC**~
    L3*1*G***82250***~
    SE*25*002120003~
    ST*210*002120004~
    B3**14758662**PP**20230725*82250****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14758662*~
    N9*PL*FR*~
    G62*86*20230721*8*1558~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****76869****NXD****NextDay~
    LX*2~
    L1****5381****FSC**~
    L3*1*G***82250***~
    SE*25*002120004~
    ST*210*002120005~
    B3**14751777**PP**20230725*82250****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14751777*~
    N9*PL*FR*~
    G62*86*20230718*8*2052~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****76869****NXD****NextDay~
    LX*2~
    L1****5381****FSC**~
    L3*1*G***82250***~
    SE*25*002120005~
    ST*210*002120006~
    B3**14751778**PP**20230725*90415****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14751778*~
    N9*PL*FR*~
    G62*86*20230718*8*2053~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****75000****NXD****NextDay~
    LX*2~
    L1****9500****FAILEDMAPLOOKUP**~
    LX*3~
    L1****5915****FSC**~
    L3*1*G***90415***~
    SE*27*002120006~
    ST*210*002120007~
    B3**14747795**PP**20230725*90415****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14747795*~
    N9*PL*FR*~
    G62*86*20230717*8*1800~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****75000****NXD****NextDay~
    LX*2~
    L1****9500****FAILEDMAPLOOKUP**~
    LX*3~
    L1****5915****FSC**~
    L3*1*G***90415***~
    SE*27*002120007~
    ST*210*002120008~
    B3**14758663**PP**20230725*90415****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14758663*~
    N9*PL*FR*~
    G62*86*20230721*8*1559~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****75000****NXD****NextDay~
    LX*2~
    L1****9500****FAILEDMAPLOOKUP**~
    LX*3~
    L1****5915****FSC**~
    L3*1*G***90415***~
    SE*27*002120008~
    ST*210*002120009~
    B3**14756548**PP**20230725*82250****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14756548*~
    N9*PL*FR*~
    G62*86*20230720*8*1800~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****76869****NXD****NextDay~
    LX*2~
    L1****5381****FSC**~
    L3*1*G***82250***~
    SE*25*002120009~
    ST*210*002120010~
    B3**14756549**PP**20230725*90415****AXCC**~
    C3*USD~
    N9*CO*1205665*~
    N9*BM**~
    N9*2I*14756549*~
    N9*PL*FR*~
    G62*86*20230720*8*1800~
    R3*1HTX*B**C**~
    N1*BT*EVERSANA Source Alliance Network*25*2163~
    N3*2023 W Carroll Ave. Suite C205*~
    N4*Chicago*IL*60612*USA~
    N1*CN*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    N1*SH*EVERSANA~
    N3*4580 S Mendenhall Rd*~
    N4*Memphis*TN*38141*USA~
    LX*1~
    L0**0*MR*1*LB***1*PCS*~
    L1****75000****NXD****NextDay~
    LX*2~
    L1****9500****FAILEDMAPLOOKUP**~
    LX*3~
    L1****5915****FSC**~
    L3*1*G***90415***~
    SE*27*002120010~
    GE*10*212~
    IEA*1*000000212~

    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.