Hudson's Bay
/
Invoice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Hudson's Bay. Contact Hudson's Bay for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Hudson's Bay logo

X12 810 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 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
    Buying Party (Purchaser)
    ITD
    130
    Terms of Sale/Deferred Terms of Sale
    Max use 1
    Optional
    DTM
    140
    Date/Time Reference
    Max use 10
    Optional
    detail
    IT1 Loop
    IT1
    010
    Baseline Item Data (Invoice)
    Max use 1
    Required
    PID Loop
    SDQ
    140
    Destination Quantity
    Max use 500
    Optional
    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

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

    Usage notes

    The Purchase Order date (BIG03) and Purchase Order Number (BIG04) should match the BEG segment (BEG03 and BEG05) on corresponding EDI 850. Also note BIG10 Shipment ID number must match EDI 856 BSN02. See examples below.

    EDI 850 - BEG00SA47030890596**20200501
    EDI 856 - BSN
    00292707318720200116185636000001

    Example: BIG202005011261353272020050147030890596******2927073187

    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-04
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BIG-10
    76
    Invoice Number
    Required
    Min 1Max 22

    Identifying number assigned by issuer

    • BIG10 indicates the consolidated invoice number. When BIG07 contains code CI, BIG10 is not used.
    CUR
    040

    Currency

    RequiredMax use 1

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

    Usage notes

    The currency code must match currency indicated on EDI 850.

    Example: CURBYCAD

    Example
    CUR-01
    98
    Entity Identifier Code
    Required

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

    BY
    Buying Party (Purchaser)
    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 Buying Party (Purchaser)
    RequiredMax >1
    Variants (all may be used)
    N1Supplier/Manufacturer
    N1
    070

    Name

    RequiredMax use 1

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

    Usage notes

    Store and DC values must be numeric. Do not use alphanumeric store or DC code included in EDI 850 SDQ segment. Please replace region code with ‘00’. For example, ecommerce store ‘TR1963’ should be transmitted as ‘001963’ on the electronic invoice.

    Examples:
    Direct to Store shipment: N1BY**92001101
    DC shipment: N1BY**92000596

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    BY
    Buying Party (Purchaser)
    N1-03
    66
    Identification Code Qualifier
    Required
    Min 1Max 2

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

    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

    Store / DC Location Code

    N1 Supplier/Manufacturer
    RequiredMax >1
    Variants (all may be used)
    N1Buying Party (Purchaser)
    N1
    070

    Name

    RequiredMax use 1

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

    Usage notes

    The vendor number on invoice must match the vendor number on EDI 850.

    Example: N1SUCOMPANY NAME92012345

    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

    SU
    Supplier/Manufacturer
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    Usage notes

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

    ITD
    130

    Terms of Sale/Deferred Terms of Sale

    OptionalMax use >1

    To specify terms of sale

    Usage notes

    Example: ITD012*****30

    Example
    If Terms Discount Percent (ITD-03) is present, then at least one of Terms Discount Due Date (ITD-04), Terms Discount Days Due (ITD-05) or Day of Month (ITD-13) 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
    02
    End of Month (EOM)
    05
    Discount Not Applicable
    08
    Basic Discount Offered
    12
    10 Days After End of Month (10 EOM)
    ITD-02
    333
    Terms Basis Date Code
    Required

    Code identifying the beginning of the terms period

    1
    Ship Date
    2
    Delivery Date
    3
    Invoice Date
    15
    Receipt of Goods
    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
    Required
    Min 1Max 3

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

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

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

    ITD-13
    765
    Day of Month
    Optional
    Min 1Max 2

    The numeric value of the day of the month between 1 and the maximum day of the month being referenced

    DTM
    140

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Example: DTM01120190620

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    011
    Shipped
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Detail

    IT1 Loop
    RequiredMax >1
    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

    Usage notes

    Example: IT112EA281QTUP000123456789VN*VENDORSTYLE

    Example
    If either Product/Service ID Qualifier (IT1-08) or Product/Service ID (IT1-09) 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 15

    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

    QT
    Quoted
    RE
    Retail Price per Each
    WE
    Wholesale Price per Each
    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.
    EN
    European Article Number (EAN) (2-5-5-1)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    IT1-07
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    IT1-08
    235
    Product/Service ID Qualifier
    Optional

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

    VN
    Vendor's (Seller's) Item Number
    IT1-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PID Loop
    OptionalMax >1
    PID
    060

    Product/Item Description

    RequiredMax use 1

    To describe a product or process in coded or free-form format

    Example
    PID-01
    349
    Item Description Type
    Required

    Code indicating the format of a description

    • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
    F
    Free-form
    PID-05
    352
    Description
    Required
    Min 1Max 80

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

    SDQ
    140

    Destination Quantity

    OptionalMax use 500

    To specify destination and quantity detail

    Usage notes

    The store number and quantity pairs may be repeated 10 times within the SDQ segment. Multiple SDQ segments may be sent. For store addresses, please refer to store and DC list available at hbcediextranet.hbc.com/.

    Example: SDQEA92CX11142CX11382CX11442CX11502CX11642EY11252EY11472EY11832LS16172TQ15142

    Example
    If either Identification Code (SDQ-05) or Quantity (SDQ-06) is present, then the other is required
    If either Identification Code (SDQ-07) or Quantity (SDQ-08) is present, then the other is required
    If either Identification Code (SDQ-09) or Quantity (SDQ-10) is present, then the other is required
    If either Identification Code (SDQ-11) or Quantity (SDQ-12) is present, then the other is required
    If either Identification Code (SDQ-13) or Quantity (SDQ-14) is present, then the other is required
    If either Identification Code (SDQ-15) or Quantity (SDQ-16) is present, then the other is required
    If either Identification Code (SDQ-17) or Quantity (SDQ-18) is present, then the other is required
    If either Identification Code (SDQ-19) or Quantity (SDQ-20) is present, then the other is required
    If either Identification Code (SDQ-21) or Quantity (SDQ-22) is present, then the other is required
    SDQ-01
    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
    SDQ-02
    66
    Identification Code Qualifier
    Required

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

    • SDQ02 is used only if different than previously defined in the transaction set.
    92
    Assigned by Buyer or Buyer's Agent
    SDQ-03
    67
    Identification Code
    Required
    Min 2Max 80

    Code identifying a party or other code

    • SDQ03 is the store number.
    Usage notes

    Region code and Store Number.

    SDQ-04
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    SDQ-05
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-06
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-07
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-08
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-09
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-10
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-11
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-12
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-13
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-14
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-15
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-16
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-17
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-18
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-19
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-20
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SDQ-21
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    Region code and Store Number.

    SDQ-22
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    Summary

    TDS
    010

    Total Monetary Value Summary

    RequiredMax use 1

    To specify the total invoice discounts and amounts

    Usage notes

    Amounts should not include decimal places. For example, $2472.65 should be transmitted as ‘247265’.

    Example: TDS247265247265

    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).
    TDS-02
    610
    Amount
    Optional
    Min 1Max 15

    Monetary amount

    • TDS02 indicates the amount upon which the terms discount amount is calculated.
    • TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01.
    TDS-03
    610
    Amount
    Optional
    Min 1Max 15

    Monetary amount

    • TDS03 is the amount of invoice due if paid by terms discount due date (total invoice or installment amount less cash discount).
    TDS-04
    610
    Amount
    Optional
    Min 1Max 15

    Monetary amount

    • TDS04 indicates the total amount of terms discount.
    CAD
    030

    Carrier Detail

    RequiredMax use 1

    To specify transportation details for the transaction

    Usage notes

    Examples:
    CADMABFS*ABF FREIGHT SYSTEM INCBM*00684740032552578

    Example
    CAD-01
    91
    Transportation Method/Type Code
    Required
    Min 1Max 2

    Code specifying the method or type of transportation for the shipment

    CAD-04
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    CAD-05
    387
    Routing
    Required
    Min 1Max 35

    Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

    Usage notes

    Carrier Name

    CAD-07
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    BM
    Bill of Lading Number
    CAD-08
    127
    Reference Identification
    Required
    Min 1Max 30

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

    SAC Loop
    OptionalMax >1
    SAC
    040

    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

    Usage notes

    Do not include decimal in charge amount. SAC15 Element must include 2 byte Provincial Code and Tax Charge Code. For example, if a shipment from Ontario is shipped to various stores with variant provincial tax requirements, SAC15 should include ‘ONHST.’

    Acceptable SAC02 / SAC15 Combinations:

    Element / Code / Element / Code
    SAC02 H770 SAC15 PQQST
    SAC02 H770 SAC15 QCQST
    SAC02 D360 SAC15 ONHST
    SAC02 D360 SAC15 NSHST
    SAC02 D360 SAC15 NBHST
    SAC02 D360 SAC15 NFHST
    SAC02 D360 SAC15 PEHST
    SAC02 D361 SAC15 ABGST
    SAC02 D361 SAC15 BCGST
    SAC02 D361 SAC15 MBGST
    SAC02 D361 SAC15 SKGST
    SAC02 D361 SAC15 YTGST
    SAC02 D361 SAC15 NTGST
    SAC02 D361 SAC15 NUGST
    SAC02 D361 SAC15 PQGST
    SAC02 D361 SAC15 QCGST

    Provincial Codes:

    Province / Abbreviation
    Alberta AB
    British Columbia BC
    Manitoba MB
    New Brunswick NB
    Newfoundland & Labrador NF
    Northwest Territories NT
    Nova Scotia NS
    Nunavut NU
    Ontario ON
    Prince Edward Island PE
    Quebec PQ
    Saskatchewan SK
    Yukon YT

    Example: SACCD36013720*******ONHST

    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.
    A
    Allowance
    C
    Charge
    SAC-02
    1300
    Service, Promotion, Allowance, or Charge Code
    Required

    Code identifying the service, promotion, allowance, or charge

    D360
    Goods and Services Tax Charge
    D361
    Goods and Services Tax Charge
    H770
    Tax - State Tax
    SAC-05
    610
    Amount
    Required
    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.
    SAC-15
    352
    Description
    Required

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

    Usage notes

    Provincial Code and Tax Charge Code

    ABGST
    Alberta GST
    BCGST
    British Columbia GST
    MBGST
    Manitoba GST
    NBHST
    New Brunswick HST
    NFHST
    Newfoundland & Labrador HST
    NSHST
    Nova Scotia HST
    NTGST
    Northwest Territories GST
    NUGST
    Nunavut GST
    ONHST
    Ontario HST
    PEHST
    Prince Edward Island HST
    PQGST
    Quebec GST
    PQQST
    Quebec QST
    QCGST
    Quebec GST
    QCQST
    Quebec QST
    SKGST
    Saskatchewan GST
    YTGST
    Yukon GST
    TXI
    050

    Tax Information

    OptionalMax use 10

    To specify tax information

    Usage notes

    TXI is only to be used if billing tax. Vendors that charge GST or HST to HBC on their invoices must supply their GST or HST Registration Number. Vendors that charge GST and QST to HBC on their invoices must supply their GST and QST Registration Numbers.

    HBC requires a TXI segment to be sent with TXI01 = ‘GS’ and TXI09 = GST registration number, if the TXI segment is sent with TXI01 = ‘GS’ and TXI02 not = 0. HBC requires a TXI segment to be sent with TXI01 = ‘OH’ and TXI09 = QST registration number, if the TXI segment is sent with TXI01 = ‘OH’ and TXI02 not = 0. HBC requires a TXI segment to be sent with TXI01 = ‘ST’ and TXI09 = HST registration number, if the TXI segment is sent with TXI01 = ‘ST’ and TXI02 not = 0***

    Examples:
    TXIGS137.20CDON**1234567
    TXI
    LS*27.80
    CDQC*1234567
    TXI
    ST*52.26
    CDON****1234567

    Example
    TXI-01
    963
    Tax Type Code
    Required

    Code specifying the type of tax

    CP
    County/Parish Sales Tax

    Goods and Services Tax/GST

    CS
    City Sales Tax

    Goods and Services Tax/GST

    CT
    County Tax

    Goods and Services Tax/GST

    GS
    Goods and Services Tax

    Goods and Services Tax/GST

    LS
    State and Local Sales Tax

    Quebec Sales Tax/QST

    LT
    Local Sales Tax (All Applicable Sales Taxes by Taxing Authority Below the State Level)

    Quebec Sales Tax/QST

    OH
    Other Taxes

    Quebec Sales Tax/QST

    SP
    State/Provincial Tax

    Provincial Sales Tax/PST

    ST
    State Sales Tax

    Harmonized Sales Tax/HST

    VA
    Value Added Tax

    Harmonized Sales Tax/HST

    ZZ
    Mutually Defined

    Harmonized Sales Tax/HST

    TXI-02
    782
    Monetary Amount
    Optional
    Min 1Max 15

    Monetary amount

    • TXI02 is the monetary amount of the tax.
    TXI-04
    955
    Tax Jurisdiction Code Qualifier
    Required

    Code identifying the source of the data used in tax jurisdiction code

    CD
    Customer defined
    TXI-05
    956
    Tax Jurisdiction Code
    Required
    Min 1Max 10

    Code identifying the taxing jurisdiction

    Usage notes

    2-Character province or state abbreviation.

    TXI-09
    325
    Tax Identification Number
    Required
    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

    ISS Loop
    RequiredMax >1
    ISS
    060

    Invoice Shipment Summary

    RequiredMax use 1

    To specify summary details of total items shipped in terms of quantity, weight, and volume

    Usage notes

    Example: ISS5EA11LB

    Example
    If either Weight (ISS-03) or Unit or Basis for Measurement Code (ISS-04) is present, then the other is required
    ISS-01
    382
    Number of Units Shipped
    Required
    Min 1Max 10

    Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

    ISS-02
    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
    ISS-03
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    ISS-04
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

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

    CTT
    070

    Transaction Totals

    RequiredMax 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.
    Usage notes

    Example: CTT*12

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    Usage notes

    Number of IT1 segments.

    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

    Invoice Excluding SDQ Segments

    ST*810*2037
    BIG*20220823*50156307*20220401*15814390596******506546662
    CUR*BY*CAD
    N1*BY**92*0596
    N1*SU**92*070935
    ITD*08*15*2*20220902*10**60
    IT1*2*7*EA*59.4*WE*UP*190108853445*VN*1017320K-CHE-01
    PID*F****K NEUMEL II 1017320K CHESTNUTSIZE01
    IT1*1*6*EA*59.4*WE*UP*190108853407*VN*1017320K-CHE-13
    PID*F****K NEUMEL II 1017320K CHESTNUTSIZE13
    IT1*5*11*EA*59.4*WE*UP*190108853377*VN*1017320K-CHE-04
    PID*F****K NEUMEL II 1017320K CHESTNUTSIZE04
    IT1*3*7*EA*59.4*WE*UP*190108853452*VN*1017320K-CHE-02
    PID*F****K NEUMEL II 1017320K CHESTNUTSIZE02
    IT1*7*1*EA*59.4*WE*UP*190108853391*VN*1017320K-CHE-06
    PID*F****K NEUMEL II 1017320K CHESTNUTSIZE06
    IT1*4*9*EA*59.4*WE*UP*190108853414*VN*1017320K-CHE-03
    PID*F****K NEUMEL II 1017320K CHESTNUTSIZE03
    TDS*275201*243540*269697*5504
    CAD*M***NLGO*SPEEDWAY LOGISTICS**BM*0053822179
    SAC*C*H770***31661**********ONHST
    TXI*ST*316.61**CD*ON****1234567890
    ISS*41*EA*69.58*LB
    CTT*6
    SE*25*2037

    Invoice Including IT1 and SDQ Segments

    ST*810*1221
    BIG*20220823*152036540*20220808*18068240596******4705026
    CUR*BY*CAD
    N1*BY**92*0596
    N1*SU*Candy Company*92*073643
    ITD*05*15**20220823*90**90******0
    DTM*011*20220816
    IT1*1*672*EA*1.61*WE*UP*071570013202*VN*55199
    SDQ*EA*92*VT1101*24*VV1111*24*VT1118*24*VT1119*24*VT1127*24*EY1135*24*EY1147*24*VV1161*24*TW1112*24*TW1113*24
    SDQ*EA*92*TW1140*24*TR1517*24*TR1518*24*TQ1523*24*TQ1524*24*TR1527*24*TQ1542*24*TQ1544*24*CX1136*24*CX1150*24
    SDQ*EA*92*TR1512*24*TQ1514*24*TR1526*24*TR1532*24*TR1546*24*TQ1547*24*TQ1631*24*TR1633*24
    IT1*2*2448*EA*2.18*WE*UP*071570006730*VN*46112
    SDQ*EA*92*VT1101*48*VT1104*48*VV1108*48*VT1109*48*VV1111*48*CX1116*48*EY1125*48*VT1127*48*VT1131*48*VT1142*48
    SDQ*EA*92*EY1145*48*EY1147*48*VT1162*48*VV1171*48*EY1183*48*TW1112*48*TW1140*48*TQ1515*48*TR1517*48*TR1518*48
    SDQ*EA*92*TQ1522*48*TQ1524*48*TR1527*48*TR1530*48*TQ1541*48*TQ1542*48*TR1543*48*TQ1550*48*TQ1575*48*TQ1576*48
    SDQ*EA*92*CX1138*48*CX1144*48*CX1150*48*CX1164*48*TR1512*48*TQ1514*48*TR1526*48*TR1532*48*TQ1533*48*TQ1535*48
    SDQ*EA*92*TR1546*48*TQ1547*48*TQ1554*48*TR1560*48*TQ1601*48*TR1606*48*TR1610*48*TR1613*48*TR1633*48*TR1649*48
    SDQ*EA*92*LS1617*48
    TDS*737636*641856*737636*0
    CAD*M***MANI*Manitoulin**BM*4705026
    SAC*C*D360***95780**********ONHST
    TXI*ST*957.80**CD*ON****1234567890
    ISS*3120*EA*335.37*LB
    CTT*2
    SE*60*1221

    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.