Adobe
/
Invoice
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from Adobe. Contact Adobe for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
Adobe 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 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
    NTE
    030
    Note/Special Instruction
    Max use 100
    Optional
    CUR
    040
    Currency
    Max use 1
    Optional
    REF
    050
    Taxing Authority Identification Number
    Max use 12
    Optional
    REF
    050
    Customer Order Number
    Max use 12
    Optional
    REF
    050
    Vendor Order Number
    Max use 12
    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
    detail
    IT1 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
    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: BIG200701290013833622200701294150223D**DI00

    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

    Usage notes

    It is recommended that the invoice number be unique for a period of not less than one (1) year.

    BIG-03
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BIG03 is the date assigned by the purchaser to purchase order.
    BIG-04
    324
    Purchase Order Number
    Optional
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BIG-07
    640
    Transaction Type Code
    Optional

    Code specifying the type of transaction

    • BIG07 is used only to further define the type of invoice when needed.
    Usage notes

    This data element is used only when special identification of the invoice is needed, between trading partners, to support business needs.

    DI
    Debit Invoice
    BIG-08
    353
    Transaction Set Purpose Code
    Optional

    Code identifying purpose of transaction set

    00
    Original
    NTE
    030

    Note/Special Instruction

    OptionalMax use 100

    To transmit information in a free-form format, if necessary, for comment or special instruction

    Usage notes

    Example: NTEGENtext

    Example
    NTE-01
    363
    Note Reference Code
    Optional

    Code identifying the functional area or purpose for which the note applies

    GEN
    Entire Transaction Set
    NTE-02
    352
    Description
    Required
    Min 1Max 80

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

    CUR
    040

    Currency

    OptionalMax use 1

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

    Usage notes

    If the CUR segment is not used, monetary values are assumed to be expressed in the currency of the country of the transaction originator.

    Example: CURSEUSD*0.05

    Example
    CUR-01
    98
    Entity Identifier Code
    Required

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

    SE
    Selling 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
    CUR-03
    280
    Exchange Rate
    Optional
    Min 4Max 10

    Value to be used as a multiplier conversion factor to convert monetary value from one currency to another

    REF
    050

    Taxing Authority Identification Number

    OptionalMax use 12

    To specify identifying information

    Usage notes

    In this Header position of the Invoice X12 EDI document, this segment is used for reference numbers relating to the Invoice. There is one reference number per segment. The REF segment can loop 12 times at this Header level.

    Example
    Variants (all may be used)
    REFCustomer Order NumberREFVendor Order Number
    At least one of Reference Identification (REF-02) or Description (REF-03) is required
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    ("CO") - This is typically used in a fulfillment situation.

    ("IA") - Identification Number assigned to the supplier, by the buyer for use within the buyer's system.

    ("IT") - Identification Number assigned to the buyer, by the supplier for use within the supplier's system.

    ("TC") - Finance Terms between vendor and flooring company. When used, REF02 contains the vendors term code, REF03 may optionally be used to send a textual description.

    61
    Taxing Authority Identification Number
    REF-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

    REF-03
    352
    Description
    Optional
    Min 1Max 80

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

    REF
    050

    Customer Order Number

    OptionalMax use 12

    To specify identifying information

    Usage notes

    In this Header position of the Invoice X12 EDI document, this segment is used for reference numbers relating to the Invoice. There is one reference number per segment. The REF segment can loop 12 times at this Header level.

    Example: REFCO12345

    Example
    At least one of Reference Identification (REF-02) or Description (REF-03) is required
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    ("CO") - This is typically used in a fulfillment situation.

    ("IA") - Identification Number assigned to the supplier, by the buyer for use within the buyer's system.

    ("IT") - Identification Number assigned to the buyer, by the supplier for use within the supplier's system.

    ("TC") - Finance Terms between vendor and flooring company. When used, REF02 contains the vendors term code, REF03 may optionally be used to send a textual description.

    CO
    Customer Order Number
    REF-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

    REF-03
    352
    Description
    Optional
    Min 1Max 80

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

    REF
    050

    Vendor Order Number

    OptionalMax use 12

    To specify identifying information

    Usage notes

    In this Header position of the Invoice X12 EDI document, this segment is used for reference numbers relating to the Invoice. There is one reference number per segment. The REF segment can loop 12 times at this Header level.

    Example
    At least one of Reference Identification (REF-02) or Description (REF-03) is required
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    ("CO") - This is typically used in a fulfillment situation.

    ("IA") - Identification Number assigned to the supplier, by the buyer for use within the buyer's system.

    ("IT") - Identification Number assigned to the buyer, by the supplier for use within the supplier's system.

    ("TC") - Finance Terms between vendor and flooring company. When used, REF02 contains the vendors term code, REF03 may optionally be used to send a textual description.

    VN
    Vendor Order Number
    REF-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

    REF-03
    352
    Description
    Optional
    Min 1Max 80

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

    N1 Loop
    OptionalMax >1
    N1
    070

    Name

    RequiredMax use 1

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

    Usage notes

    It is strongly encouraged that the trading partners codify all addresses within their systems through use of N103 and N104. The use of codes would eliminate the need for transmittal of the N2, N3 and N4 segments below.

    Example: N1BTCOMPUTER RESELLER911234567891234

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

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

    Usage notes

    ("BO") - For domestic purchase order, this is the manufacturer's sales office. For an import purchase order, this is the sales office that interacts with the manufacturer's/buyer's agent.

    ("BY") - Should be used only if "Buying Party" ("BY") is different than "Bill To: ("BT").

    ("SE") - Used by flooring companies when forwarding copies of invoices to dealer/buyer.

    BT
    Bill-to-Party
    BY
    Buying Party (Purchaser)
    CA
    Carrier
    DU
    Resale Dealer
    EN
    End User
    II
    Issuer of Invoice
    PR
    Payer
    SE
    Selling Party
    SO
    Sold To If Different From Bill To
    ST
    Ship To
    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)

    Usage notes

    CompTIA recommends the use of a Dun & Bradstreet (DUNS) Number to identify the trading partners. D & B assigns a nine-digit identifier to each trading partner. The trading partner then assigns a four-digit (DUNS+4) code to uniquely identify the specific location, e.g., 0000 may be corporate offices, 0001 may be a central warehouse, 0002 may be one of the trading partners' sites.

    91
    Assigned by Seller or Seller's Agent
    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.
    N2
    080

    Additional Name Information

    OptionalMax use 2

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

    Usage notes

    Example: N2*BUYER

    Example
    N2-01
    93
    Name
    Required
    Min 1Max 60

    Free-form name

    N2-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N3
    090

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Usage notes

    Example: N3*123 MAIN STREET

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

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    100

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Usage notes

    Example: N4CEDAR RAPIDSIA*524032140

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    Code (Standard State/Province) as defined by appropriate government agency

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

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

    N4-04
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    Usage notes

    For US and Canadian locations CompTIA does not recommend the use of N404. For non-US/Canadian locations the two-character country code qualifier established by ISO 3166 (E/F) should be used. ISO 3166 : 1988 (E/F) is available from: American National Standards Institute, 11 West 42nd Street, New York, NY 10036, Telephone: 212 642-4900, FAX: 212 302-1286.

    PER
    120

    Administrative Communications Contact

    OptionalMax use 3

    To identify a person or office to whom administrative communications should be directed

    Usage notes

    In this Header position of the Invoice X12 EDI document, this segment identifies the parties responsible for originating the invoice.

    Example: PERCNJSMITH

    Example
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    Usage notes

    ("RE") - This is the contact name if a problem occurs in paying the invoice.

    CN
    General Contact
    PER-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    ITD
    130

    Terms of Sale/Deferred Terms of Sale

    OptionalMax use >1

    To specify terms of sale

    Usage notes

    In this Header position of the Invoice X12 EDI document, this segment is used to specify terms of the invoice. In the transitional period for the microcomputer industry, from paper to full automated EDI transactions, there may be a perceived need to send text data with the terms. Clearly the goal is to have the entire microcomputer industry participating in EDI. Therefore, if text data is needed to be sent for terms, ITD 12 will contain the free form text. If additional text is needed, additional ITD segments should be used.

    Example: ITD14345Up to 03/15/2007 without deduction

    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.
    14
    Previously agreed upon
    ITD-02
    333
    Terms Basis Date Code
    Optional

    Code identifying the beginning of the terms period

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

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

    ITD-12
    352
    Description
    Optional
    Min 1Max 80

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

    DTM
    140

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    In this Header position of the Invoice X12 EDI document, this segment identifies the pertinent shipping date.

    Example: DTM01120070129

    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

    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

    At the Item Level, this segment can be used to identify either the basic unit (SKU) or at a bundle/kit/product configuration level which is further broken down into components. The components would be listed in the SLN loop following this segment.

    For example, a computer (item level) may have individual components which may be separately identified (CPU, hard disk, monitor, keyboard, etc.). Another example could be a group of software products which have been grouped together for sale as one unit, e.g., a spreadsheet program and a report writer or a virus program with a utility program.

    In this Detail position of the Invoice X12 EDI document, this segment identifies the quantity, unit price, and product codes of the items being invoiced. CompTIA recommends the use of UPC code in UCC/EAN formats. Product descriptions would appear in a corresponding and subsequent PID segment.

    Partners P.O. Line Item Number will be sent in the IT101 in the invoice when applicable. If Partner P.O. Line Item Number does not exist in Adobe’s Ordering System, then Adobe’s Invoice Line Item Number will be sent.

    For Adobe's AVL 5.0 Licensing Program (October 2009), the Adobe SKU in the IT107 will extend to 15 digits.

    Examples:
    IT10000102773EA41CPVP09972555BP1234567UP*5029766636242 (Adobe Shrink Wrap SKU)

    IT10000102773EA41CPVP09972555A4BP1234567UP*5029766636242 (Adobe AVL 4.5 Licensing ProgramSKU)

    IT10000102773EA41CPVP65008841AB02A00BP1234567UP*5029766636242 (Adobe AVL 5.0 LicensingProgram SKU - Post October 2009)

    Example
    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-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • IT101 is the purchase order line item identification.
    Usage notes

    Original Line Number from PO.

    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

    Usage notes

    Unit of Measure listed should be the same unit of measure listed in the Purchase Order.

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

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

    Usage notes

    Rate charged per unit of measure less discount percent, but not to include order level discounts or allowances. The price is expressed in dollars. The decimal point is required if the price is not in whole dollars. The price would be sent with a decimal point only when needed, e.g., $15.95 would be sent as "15.95", and $29.00 would be sent as "29". To indicate free goods, use a single zero (0) with code NC as the value in IT105.

    IT1-05
    639
    Basis of Unit Price Code
    Optional

    Code identifying the type of unit price for an item

    Usage notes

    This data element is used to clarify or alter the basis of unit price. The unit price expressed in IT104 is always in the same terms as the unit of measure in IT103, unless otherwise specified in IT105.

    CP
    Current Price (Subject to Change)
    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.
    Usage notes

    CompTIA recommends the use of supplier part numbers in either UPC, EAN, or Code 39 with FACT Data Identifier formats. Transitional use of the customer's part numbers may facilitate the cross-referencing of supplier part numbers to the customer's part numbers. The customer's part numbers should be phased out and replaced with supplier part numbers. All suppliers will need either a manufacturer's identification assigned by the Uniform Code Council or the appropriate EAN authority or a publisher identification assigned by the appropriate ISBN agency. Contact CompTIA for information on these coding structures.

    Use VX when using a "bundle" or "kit" number to indicate that SLN segments will follow with related component numbers.

    The vendor's Mfr. ID# is used conditionally when IT106 reflects "MG".

    VP
    Vendor's (Seller's) Part Number
    IT1-07
    234
    Product/Service ID
    Optional
    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)

    BP
    Buyer's Part 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

    PID Loop
    OptionalMax >1
    PID
    060

    Product/Item Description

    RequiredMax use 1

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

    Usage notes

    In the Detail position of the Invoice X12 EDI document, this segment identifies free-format product descriptions.

    Example: PIDF***ACRO,8.0,WIN,AOO,UE,1PK,N/A

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

    Semi-structured data may be both codes and text. If "X" is used, the structure may be mutually defined between the trading partners.

    F
    Free-form
    PID-05
    352
    Description
    Optional
    Min 1Max 80

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

    Summary

    TDS
    010

    Total Monetary Value Summary

    RequiredMax use 1

    To specify the total invoice discounts and amounts

    Usage notes

    Example: TDS*16000

    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

    Example: TXIST00****novalCustomer VAT Number

    Example
    If either Tax Jurisdiction Code Qualifier (TXI-04) or Tax Jurisdiction Code (TXI-05) is present, then the other is required
    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

    ST
    State Sales Tax
    TXI-02
    782
    Monetary Amount
    Optional
    Min 1Max 15

    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-04
    955
    Tax Jurisdiction Code Qualifier
    Optional
    Min 2Max 2

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

    TXI-05
    956
    Tax Jurisdiction Code
    Optional
    Min 1Max 10

    Code identifying the taxing jurisdiction

    TXI-06
    441
    Tax Exempt Code
    Optional

    Code identifying exemption status from sales and use tax

    0
    Exempt (For Export)
    1
    Yes (Tax Exempt)
    2
    No (Not Tax Exempt)
    3
    Exempt (For Resale)
    4
    Not Exempt/For Resale
    5
    Exempt (Not For Resale)
    6
    Not Exempt, Not For Resale
    7
    Direct Pay ID
    8
    Exempt (Sale to U.S. Government)
    9
    Exempt (Per State Law)
    A
    Labor Taxable, Material Exempt
    B
    Material Taxable, Labor Exempt
    C
    Not Taxable
    V
    Exempt from State Property Tax
    W
    Other Property Tax Exemption
    X
    Exempt - Letter on file
    TXI-07
    662
    Relationship Code
    Optional
    Min 1Max 1

    Code indicating the relationship between entities

    • TXI07 is a code indicating the relationship of the price or amount to the associated segment.
    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

    Customer VAT Number.

    TXI-10
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    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

    At this Summary level within the Invoice X12 EDI document, this segment will indicate in ITA01 if it is allowances or charges. One segment per allowance or charge. This segment applies to the entire transaction. The allowances/charges specified at the summary level are exclusive of the allowances/charges specified in any other areas; they are not the sum of the allowances/charges specified in the detail areas. ITA07 is required when using the ITA segment in the microcomputer industry. This will resolve any differences between the sender's and receiver's system calculations of amounts, e.g., rounding errors when allowances/charges are expressed in percentages or rates.

    Example: SACCD240***888

    Example
    At least one of Service, Promotion, Allowance, or Charge Code (SAC-02) or Agency Qualifier Code (SAC-03) is required
    If either Agency Qualifier Code (SAC-03) or Agency Service, Promotion, Allowance, or Charge Code (SAC-04) is present, then the other is required
    If either Allowance/Charge Percent Qualifier (SAC-06) or Percent (SAC-07) is present, then the other is required
    If either Unit or Basis for Measurement Code (SAC-09) or Quantity (SAC-10) is present, then the other is required
    If Quantity (SAC-11) is present, then Quantity (SAC-10) is required
    If Reference Identification (SAC-13) is present, then at least one of Service, Promotion, Allowance, or Charge Code (SAC-02) or Agency Service, Promotion, Allowance, or Charge Code (SAC-04) is required
    If Option Number (SAC-14) is present, then Reference Identification (SAC-13) is required
    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

    D240
    Freight
    SAC-03
    559
    Agency Qualifier Code
    Optional
    Min 2Max 2

    Code identifying the agency assigning the code values

    SAC-04
    1301
    Agency Service, Promotion, Allowance, or Charge Code
    Optional
    Min 1Max 10

    Agency maintained code identifying the service, promotion, allowance, or charge

    • SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction to further the code in SAC02.
    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-06
    378
    Allowance/Charge Percent Qualifier
    Optional
    Min 1Max 1

    Code indicating on what basis allowance or charge percent is calculated

    SAC-07
    332
    Percent
    Optional
    Min 1Max 6

    Percent expressed as a percent

    SAC-08
    118
    Rate
    Optional
    Min 1Max 9

    Rate expressed in the standard monetary denomination for the currency specified

    • SAC08 is the allowance or charge rate per unit.
    SAC-09
    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

    SAC-10
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    • SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.
    • SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion, allowance, or charge.
    • In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance, charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.
    SAC-11
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SAC-12
    331
    Allowance or Charge Method of Handling Code
    Optional
    Min 2Max 2

    Code indicating method of handling for an allowance or charge

    Usage notes

    "01" Used when customer is invoicing supplier for miscellaneous services provided.

    SAC-13
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    • SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
    SAC-14
    770
    Option Number
    Optional
    Min 1Max 20

    A unique number identifying available promotion or allowance options when more than one is offered

    • SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.
    SAC-15
    352
    Description
    Optional
    Min 1Max 80

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

    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

    In this Summary position of the Invoice X12 EDI document, this segment identifies the number of line items reported.

    Example: CTT*1

    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*166061414
    BIG*20070129*0013833070*20070129*V8748745***DI*00
    NTE*GEN*If 0% VAT is charged and your VAT ID number is displayed above, this
    NTE*GEN*is either an exempt or a reverse charge transaction.
    NTE*GEN*This supply is exempt from VAT according to the section 64 of the Czec
    NTE*GEN*h VAT Act.
    CUR*SE*USD
    REF*61*noval*Adobe VAT Number
    REF*CO*121212
    REF*VN*0070861270
    N1*II*ADOBE SYSTEMS INCORPORATED*91*0000012137
    N2*ADOBE SYSTEMS INCORPORATED
    N3*345 PARK AVENUE
    N4*SAN JOSE*CA*95110*US
    N1*BY*SOFTWARE.*91*0000012137
    N2*SOFTWARE
    N3*111 MAIN DR
    N4*PLANO*TX*75075*US
    N1*BT*SOFTWARE.*91*0000012137
    N2*SOFTWARE
    N3*111 MAIN DR
    N4*PLANO*TX*75075*US
    N1*PR*SOFTWARE*91*0000012137
    N2*SOFTWARE
    N3*111 MAIN DR
    N4*PLANO*TX*75075*US
    N1*ST*SHIP TO PARTNER*91*0050480425
    N2*SHIP TO
    N3*122 MAIN AVE
    N4*SANTA CLARA*CA*95050*US
    PER*CN*JOHN DOE
    N1*SE*ADOBE SYSTEMS INCORPORATED*91*ADUS
    N2*ADOBE SYSTEMS INCORPORATED
    N3*345 Park Avenue
    N4*SAN JOSE*CA*95110*US
    N1*EN**91*0020064630
    N1*DU**91*0010013997
    ITD*14*3*****35*****Up to 03/05/2007 without deduction
    DTM*011*20070129
    IT1*000010*1*EA*160*CP*VP*65008841AB02A00*BP*7167946*UP*883919019161
    PID*F****ACRO,8.0,WIN,AOO,UE,1PK,N/A
    TDS*16000
    TXI*ST*0*0******noval*Customer VAT Number
    CTT*1
    SE*44*166061414

    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.