Amazon
/
Direct Fulfillment Invoice
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Amazon. Contact Amazon for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Amazon logo

X12 810 Direct Fulfillment Invoice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free 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
    BIG
    020
    Beginning Segment for Invoice
    Max use 1
    Required
    CUR
    040
    Currency
    Max use 1
    Required
    N1 Loop Ship From
    ITD
    130
    Terms of Sale/Deferred Terms of Sale
    Max use 1
    Required
    detail
    IT1 Loop
    IT1
    010
    Baseline Item Data (Invoice)
    Max use 1
    Required
    TXI
    040
    Tax Information
    Max use 10
    Optional
    SAC 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

    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

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

    01
    Duns (Dun & Bradstreet)
    02
    SCAC (Standard Carrier Alpha Code)
    03
    FMC (Federal Maritime Commission)
    04
    IATA (International Air Transport Association)
    08
    UCC EDI Communications ID (Comm ID)
    09
    X.121 (CCITT)
    12
    Phone (Telephone Companies)
    14
    Duns Plus Suffix
    16
    Duns Number With 4-Character Suffix
    ZZ
    Mutually Defined
    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

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

    ZZ
    Mutually Defined
    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

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

    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

    IN
    Invoice Information (810,819)
    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

    Code used in conjunction with Data Element 480 to identify the issuer of the standard

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

    BIG
    020

    Beginning Segment for Invoice

    RequiredMax use 1

    To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

    Example
    BIG-01
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BIG01 is the invoice issue date.
    BIG-02
    76
    Invoice Number
    Required
    Min 1Max 22

    Identifying number assigned by issuer

    BIG-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BIG03 is the date assigned by the purchaser to purchase order.
    BIG-07
    640
    Transaction Type Code
    Required

    Code specifying the type of transaction

    • BIG07 is used only to further define the type of invoice when needed.
    CI
    Consolidated Invoice
    CUR
    040

    Currency

    RequiredMax use 1

    To specify the currency (dollars, pounds, francs, etc.) used in a transaction

    Example
    CUR-01
    98
    Entity Identifier Code
    Required

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

    BT
    Bill-to-Party
    CUR-02
    100
    Currency Code
    Required

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

    CAD
    Canadian Dollar
    USD
    US Dollar
    N1 N1 Loop Ship From
    RequiredMax 200
    Variants (all may be used)
    N1N1 Loop Remit To
    N1
    070

    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

    SF
    Ship From
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    Usage notes

    This will be the Amazon code representing the vendor warehouse that the order shipped from. This is usually a four-character alpha code(e.g. ABCD)

    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    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

    This will be the Amazon code representing the vendor warehouse that the order shipped from. This is usually a four-character alpha code(e.g. ABCD)

    N1 N1 Loop Remit To
    RequiredMax 200
    Variants (all may be used)
    N1N1 Loop Ship From
    N1
    070

    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

    RI
    Remit To
    N1-02
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    92
    Assigned by Buyer or Buyer's Agent
    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

    Vendor Payee Code. This is a five-character Payee code that Amazon will provide during the integration process.
    Format: AAAAN (ABCD1)

    N2
    080

    Additional Name Information

    OptionalMax use 2

    To specify additional names or those longer than 35 characters in length

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N3
    090

    Address Information

    RequiredMax use 2

    To specify the location of the named party

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

    Address information

    Usage notes

    Vendor Remit To Address. Amazon's AP department will verify that the remit-to address provided via the N3 and N4 segments matches the address on file.

    N4
    100

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    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
    Required
    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
    Required
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Required
    Min 2Max 3

    Code identifying the country

    ITD
    130

    Terms of Sale/Deferred Terms of Sale

    RequiredMax use >1

    To specify terms of sale

    Example
    If Terms Deferred Due Date (ITD-09) is present, then at least one of Deferred Amount Due (ITD-10) or Percent of Invoice Payable (ITD-11) is required
    ITD-01
    336
    Terms Type Code
    Required

    Code identifying type of payment terms

    • If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
    01
    Basic
    ITD-02
    333
    Terms Basis Date Code
    Required

    Code identifying the beginning of the terms period

    3
    Invoice Date
    ITD-03
    338
    Terms Discount Percent
    Optional
    Min 1Max 6

    Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date

    ITD-04
    370
    Terms Discount Due Date
    Optional
    CCYYMMDD format

    Date payment is due if discount is to be earned expressed in format CCYYMMDD

    ITD-05
    351
    Terms Discount Days Due
    Optional
    Min 1Max 3

    Number of days in the terms discount period by which payment is due if terms discount is earned

    ITD-06
    446
    Terms Net Due Date
    Optional
    CCYYMMDD format

    Date when total invoice amount becomes due expressed in format CCYYMMDD

    ITD-07
    386
    Terms Net Days
    Required
    Min 1Max 3

    Number of days until total invoice amount is due (discount not applicable)

    ITD-08
    362
    Terms Discount Amount
    Optional
    Min 1Max 10

    Total amount of terms discount

    ITD-09
    388
    Terms Deferred Due Date
    Optional
    CCYYMMDD format

    Date deferred payment or percent of invoice payable is due expressed in format CCYYMMDD

    ITD-10
    389
    Deferred Amount Due
    Optional
    Min 1Max 10

    Deferred amount due for payment

    ITD-11
    342
    Percent of Invoice Payable
    Optional
    Min 1Max 5

    Amount of invoice payable expressed in percent

    ITD-12
    352
    Description
    Required
    Min 1Max 80

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

    Detail

    IT1 Loop
    RequiredMax 200000
    IT1
    010

    Baseline Item Data (Invoice)

    RequiredMax use 1

    To specify the basic and most frequently used line item data for the invoice and related transactions

    Example
    If either Product/Service ID Qualifier (IT1-10) or Product/Service ID (IT1-11) is present, then the other is required
    IT1-01
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • IT101 is the purchase order line item identification.
    IT1-02
    358
    Quantity Invoiced
    Required
    Min 1Max 10

    Number of units invoiced (supplier units)

    IT1-03
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    EA
    Each
    IT1-04
    212
    Unit Price
    Required
    Min 1Max 17

    Price per unit of product, service, commodity, etc.

    IT1-05
    639
    Basis of Unit Price Code
    Required

    Code identifying the type of unit price for an item

    NT
    Net
    IT1-06
    235
    Product/Service ID Qualifier
    Required

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    • IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    SK
    Stock Keeping Unit (SKU)
    IT1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    IT1-08
    235
    Product/Service ID Qualifier
    Required

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    PO
    Purchase Order Number
    IT1-09
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    This will be the Amazon encrypted Ship ID/ PO Number provided in the BEG03 of the corresponding 850. The PO Number is 9-12 characters long and is case-sensitive.

    IT1-10
    235
    Product/Service ID Qualifier
    Optional

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    Usage notes

    Vendor Order Reference Number
    The Vendor Order Reference Number(VO) would be used to tie back to the individual PO shipped and billed against the Amazon Ship ID/ PO Number.

    VO
    Vendor's Order Number
    IT1-11
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    IT1-12
    235
    Product/Service ID Qualifier
    Optional

    Code identifying the type/source of the descriptive number used in Product/Service ID (234)

    ON
    Customer Order Number
    IT1-13
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Amazon.com 19-digit customer order number. This number will be all numeric 3-7-7 (e.g. 123-1234567-1234567) and needs to include the dashes. The customer order number is provided via the REF*OQ segment on the corresponding 850.
    This number is not unique and may be used on more than one shipment.

    TXI
    040

    Tax Information

    OptionalMax use 10

    To specify tax information

    Usage notes

    ** Mandatory for all vendors in Australia and Canada**
    Do not use for US marketplace. Any US invoice received with the TXI segment will fail to be processed.
    The line item level TXI segment has to be provided for every item that is being invoiced.

    Example
    TXI-01
    963
    Tax Type Code
    Required

    Code specifying the type of tax

    GS
    Goods and Services Tax
    ST
    State Sales Tax

    "ST" is only used to specify Québec sales tax.

    VA
    Value Added Tax
    ZZ
    Mutually Defined
    TXI-02
    782
    Monetary Amount
    Optional
    Min 1Max 18

    Monetary amount

    • TXI02 is the monetary amount of the tax.
    TXI-03
    954
    Percent
    Optional
    Min 1Max 10

    Percentage expressed as a decimal

    • TXI03 is the tax percent expressed as a decimal.
    SAC Loop
    OptionalMax 25
    SAC
    180

    Service, Promotion, Allowance, or Charge Information

    RequiredMax use 1

    To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

    Example
    SAC-01
    248
    Allowance or Charge Indicator
    Required

    Code which indicates an allowance or charge for the service specified

    • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
    C
    Charge
    SAC-02
    1300
    Service, Promotion, Allowance, or Charge Code
    Optional

    Code identifying the service, promotion, allowance, or charge

    B790
    Crafting

    Use 'B790' for Gift Wrap fees

    D240
    Freight

    Freight Fees are inbound transportation charges, this code should not be used for shipping charges on a customer order.

    D500
    Handling

    Use 'D500' for Fulfillment Fees

    E170
    Labeling

    Use 'E170' for Marketing Insert Fees

    F155
    Packaging

    Use 'F155' for Packaging Fees

    G821
    Shipping

    Note: This should be used for billing carrier shipping charges when Amazon accounts are not used: For example, USPS Shipments

    SAC-05
    610
    Amount
    Optional
    Min 1Max 15

    Monetary amount

    • SAC05 is the total amount for the service, promotion, allowance, or charge.
    • If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

    Summary

    TDS
    010

    Total Monetary Value Summary

    RequiredMax use 1

    To specify the total invoice discounts and amounts

    Example
    TDS-01
    610
    Amount
    Required
    Min 1Max 15

    Monetary amount

    • TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
    TXI
    020

    Tax Information

    OptionalMax use 10

    To specify tax information

    Usage notes

    ** Mandatory for all vendors in Australia and Canada**
    Do not use for US marketplace. Any US invoice received with the TXI segment will fail to be processed. The TXI segment sums the tax amount for the invoiced line items belonging to the same purchase order.

    Example
    At least one of Monetary Amount (TXI-02), Percent (TXI-03) or Tax Exempt Code (TXI-06) is required
    If Dollar Basis For Percent (TXI-08) is present, then Percent (TXI-03) is required
    TXI-01
    963
    Tax Type Code
    Required

    Code specifying the type of tax

    GS
    Goods and Services Tax
    ST
    State Sales Tax

    Usage Notes: "ST" is only used to specify Québec sales tax.

    VA
    Value Added Tax
    ZZ
    Mutually Defined
    TXI-02
    782
    Monetary Amount
    Optional
    Min 1Max 18

    Monetary amount

    • TXI02 is the monetary amount of the tax.
    TXI-03
    954
    Percent
    Optional
    Min 1Max 10

    Percentage expressed as a decimal

    • TXI03 is the tax percent expressed as a decimal.
    TXI-05
    956
    Tax Jurisdiction Code
    Optional
    Min 1Max 10

    Code identifying the taxing jurisdiction

    TXI-06
    441
    Tax Exempt Code
    Optional
    Min 1Max 1

    Code identifying exemption status from sales and use tax

    TXI-08
    828
    Dollar Basis For Percent
    Optional
    Min 1Max 9

    Dollar basis to be used in the percent calculation of the allowance, charge or tax

    TXI-09
    325
    Tax Identification Number
    Optional
    Min 1Max 20

    Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state, county, etc.); often called a tax exemption number or certificate number

    Usage notes

    This is the vendor's registered business TAX ID. This field is required for Canada vendors (GST ID/HST ID/QST ID) and for vendors in Australia to comply with tax requirements.

    CTT
    070

    Transaction Totals

    OptionalMax use 1

    To transmit a hash total for a specific element in the transaction set

    • Number of line items (CTT01) is the accumulation of the number of IT1 segments.
      If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.
    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    CTT-02
    347
    Hash Total
    Required
    Min 1Max 10

    Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

    ## Example:
    -.0018 First occurrence of value being hashed.
    .18 Second occurrence of value being hashed.
    1.8 Third occurrence of value being hashed.
    18.01 Fourth occurrence of value being hashed.

    1855 Hash total prior to truncation.
    855 Hash total after truncation to three-digit field.

    SE
    080

    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

    No Tax

    ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *220824*2001*U*00401*000000088*0*P*>~
    GS*IN*SENDERID*AMAZONDS*20220824*2001*88*X*004010~
    ST*810*0001~
    BIG*20220822*SINV00070492*20220822****CI~
    CUR*BT*USD~
    N1*RI*VendorRemitToName*92*PAYE1~
    N3*705 5TH AVE S~
    N4*SEATTLE*WA*981044425*US~
    N1*SF*WHSE*92*WHSE~
    ITD*01*3*****30*****NET 30~
    IT1*1*2*EA*18.04*NT*SK*1617*PO*TkFd5Zn32*VO*SO00095341*ON*123-1234567-1234567~
    IT1*2*3*EA*54.42*NT*SK*4927*PO*TkFd5Zn32*VO*SO00095341*ON*123-1234567-1234567~
    TDS*19934~
    CTT*2*5~
    SE*12*0001~
    GE*1*88~
    IEA*1*000000088~

    With Tax

    ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *220824*2001*U*00401*000000076*0*P*>~
    GS*IN*SENDERID*AMAZONDS*20220824*2001*76*X*004010~
    ST*810*000000001~
    BIG*20220822*SINV00070511*20220822****CI~
    CUR*BT*CAD~
    N1*RI*VendorRemitToName*92*PAYE1~
    N3*5225 Boundary Road~
    N4*Navan*ON*K4B 0L3*CA~
    N1*SF*WHSE*92*WHSE~
    ITD*01*3*****30*****NET 30~
    IT1*1*2*EA*18.04*NT*SK*1617*PO*TkFd5Zn32*VO*SO00095341*ON*123-1234567-1234567~
    TXI*GS*4.69*13~
    IT1*2*3*EA*54.42*NT*SK*4927*PO*TkFd5Zn32*VO*SO00095341*ON*123-1234567-1234567~
    TXI*GS*21.22*13~
    TDS*22525~
    TXI*GS*25.91*13*****199.34*VendorTaxID~
    CTT*1*3~
    SE*12*000000001~
    GE*1*76~
    IEA*1*000000076~

    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.