Office Depot
/
Invoice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Office Depot. Contact Office Depot for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Office Depot 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 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
    BIG
    020
    Beginning Segment for Invoice
    Max use 1
    Required
    CUR
    040
    Currency
    Max use 1
    Optional
    N1 Loop
    ITD
    130
    Terms of Sale/Deferred Terms of Sale
    Max use 1
    Optional
    DTM
    140
    Date/Time Reference
    Max use 10
    Optional
    FOB
    150
    F.O.B. Related Instructions
    Max use 1
    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

    Example: BIG2000050112345~~3567123-0210}

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

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    Must be in the same format as received on 850, i.e. “3567123-0210” is correct, “3567123” is incorrect.

    CUR
    040

    Currency

    OptionalMax use 1

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

    Usage notes

    Monetary values are assumed to be expressed in U.S. currency unless the CUR segment is used to specify a different currency.

    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
    N1 Loop
    OptionalMax >1
    N1
    070

    Name

    RequiredMax use 1

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

    Usage notes

    Example: N1ST~~930210}

    Example
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    N1-03
    66
    Identification Code Qualifier
    Optional

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

    93
    Code assigned by the organization originating the transaction set
    N1-04
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
    Usage notes

    Must be in same format as received on 850, i.e. “0210” is correct, “210” is incorrect.

    N3
    090

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Usage notes

    Example: N3~8601 S.W. 40TH STREET}

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

    Address information

    N4
    100

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Usage notes

    Example: N4MIAMIFL~33155}

    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)

    ITD
    130

    Terms of Sale/Deferred Terms of Sale

    OptionalMax use >1

    To specify terms of sale

    Usage notes

    Example: ITD032~29091}

    Example
    ITD-01
    336
    Terms Type Code
    Optional

    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
    03
    Fixed Date
    09
    Proximo
    ITD-02
    333
    Terms Basis Date Code
    Optional

    Code identifying the beginning of the terms period

    2
    Delivery Date
    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
    Optional
    Min 1Max 3

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

    DTM
    140

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Example: DTM01120000501}

    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
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    FOB
    150

    F.O.B. Related Instructions

    OptionalMax use 1

    To specify transportation instructions relating to shipment

    Usage notes

    Example: FOBPPOR}

    Example
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    CC
    Collect
    CF
    Collect, Freight Credited Back to Customer
    DF
    Defined by Buyer and Seller
    PC
    Prepaid but Charged to Customer
    PO
    Prepaid Only
    PP
    Prepaid (by Seller)
    FOB-02
    309
    Location Qualifier
    Optional

    Code identifying type of location

    • FOB02 is the code specifying transportation responsibility location.
    DE
    Destination (Shipping)
    OR
    Origin (Shipping Point)

    Detail

    IT1 Loop
    OptionalMax >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: IT148EA3.7VAAS302IN0373738UP~051131069060}

    Example
    If either Quantity Invoiced (IT1-02), Unit or Basis for Measurement Code (IT1-03) or Unit Price (IT1-04) are present, then the others are required
    If either Product/Service ID Qualifier (IT1-06) or Product/Service ID (IT1-07) is present, then the other is required
    If either Product/Service ID Qualifier (IT1-08) or Product/Service ID (IT1-09) is present, then the other is required
    If either Product/Service ID Qualifier (IT1-10) or Product/Service ID (IT1-11) is present, then the other is required
    IT1-02
    358
    Quantity Invoiced
    Optional
    Min 1Max 10

    Number of units invoiced (supplier units)

    Usage notes

    Quantity must be in order units.

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

    IT1-04
    212
    Unit Price
    Optional
    Min 1Max 15

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

    IT1-06
    235
    Product/Service ID Qualifier
    Optional

    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.
    VA
    Vendor's Style Number
    IT1-07
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Usage notes

    Must be in same format as received on 850, i.e. if 850 PO107 vendor product # is 38633, “38633” is correct and “38-633” is incorrect. And all 3 cross references must come back.

    IT1-08
    235
    Product/Service ID Qualifier
    Optional

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

    IN
    Buyer's Item Number
    IT1-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    IT1-10
    235
    Product/Service ID Qualifier
    Optional

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

    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    IT1-11
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    Summary

    TDS
    010

    Total Monetary Value Summary

    RequiredMax use 1

    To specify the total invoice discounts and amounts

    Usage notes

    Example: TDS~112233}

    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).
    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 send if no allowances or charges.

    Examples:
    SACAH850~~~3588~~~~~~~02}

    SACAE740~~~2301~~~~~~~02}
    SACAH850~~~3588~~~~~~~02

    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
    Optional

    Code identifying the service, promotion, allowance, or charge

    B210
    Co-op Credit
    B720
    Cooperative Advertising/Merchandising Allowance (Performance)
    C040
    Delivery
    D200
    Freight Charges to Destination
    D240
    Freight
    D360
    Goods and Services Tax Charge
    E550
    Market Development Funds
    E730
    New Item Allowance
    E740
    New Store Allowance
    F750
    Processing Charge
    F800
    Promotional Allowance
    F970
    Rebate
    H000
    Special Allowance
    H850
    Tax
    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.
    SAC-12
    331
    Allowance or Charge Method of Handling Code
    Optional

    Code indicating method of handling for an allowance or charge

    02
    Off Invoice
    06
    Charge to be Paid by Customer
    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.
    Usage notes

    Example: CTT~2}

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

    Total number of line items in the transaction set

    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

    Sample

    ST~810~100001}
    BIG~20000501~12345~~3567123-0210}
    CUR~BY~CAD}
    N1~ST~~93~0210}
    N3~8601 S.W. 40th Street}
    N4~Miami~FL~33155}
    ITD~03~2~2~~90~~91}
    DTM~011~20000501}
    FOB~PP~OR}
    IT1~~48~EA~3.7~~VA~AS302~IN~0373738~UP~051131069060}
    IT1~~12~P2~45~~VA~42222~IN~0456654~UP~50021200069395}
    TDS~68172}
    SAC~A~H850~~~3588~~~~~~~02}
    CTT~2}
    SE~15~100001}

    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.