CIT Bank
/
Invoice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from CIT Bank. Contact CIT Bank for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
CIT Bank 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
    https://www.stedi.com/app/guides/view/cit-bank/invoice/01HBGPQMZFMYSPDD22D9GBEE24
    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
    REF
    050
    Reference Identification REF01 14 23
    Max use 2
    Required
    REF
    050
    Reference Identification Rest All
    Max use 4
    Optional
    YNQ
    055
    Yes/No Question
    Max use 2
    Optional
    N1 Loop Buyer BY
    ITD
    130
    Terms of Sale/Deferred Terms of Sale
    Max use 1
    Required
    DTM
    140
    Date/Time Reference
    Max use 2
    Required
    FOB
    150
    F.O.B. Related Instructions
    Max use 1
    Optional
    detail
    IT1 Loop
    IT1
    010
    Baseline Item Data (Invoice)
    Max use 1
    Required
    IT3
    030
    Additional Item Data
    Max use 1
    Optional
    PID 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
    String (AN)
    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
    String (AN)
    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
    Identifier (ID)
    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
    String (AN)
    Min 15Max 15

    Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

    ISA-07
    I05
    Interchange ID Qualifier
    Required

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

    ZZ
    Mutually Defined
    ISA-08
    I07
    Interchange Receiver ID
    Required
    String (AN)
    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
    Numeric (N0)
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Identifier (ID)
    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
    Identifier (ID)
    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
    String (AN)
    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
    String (AN)
    Min 2Max 15

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    String (AN)
    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
    Numeric (N0)
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Identifier (ID)
    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
    Heading > ST

    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
    Numeric (N)
    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
    Heading > BIG

    Beginning Segment for Invoice

    RequiredMax use 1

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

    Usage notes

    A. Use BIG07 with ‘CR’ to indicate a credit memo. BIG02 can be a new credit memo number.
    The original invoice number, to which the credit memo refers, is indicated in a REF
    segment element.
    B. Invoice number has a maximum length of 8 characters for CIT usage. If length is greater
    than 8 positions, truncation from the left will occur to retain uniqueness.

    Example
    BIG-01
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

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

    Identifying number assigned by issuer

    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
    Required
    String (AN)
    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.
    CR
    Credit Memo
    REF
    050
    Heading > REF

    Reference Identification REF01 14 23

    RequiredMax use 2

    To specify identifying information

    Usage notes

    A. REF segments are used to identify each of the following: Master Client Number, Client Number, Trade Style, Department Number, Internal Vendor Number, and Credit Memo Original Invoice Number.
    C. Both a REF01 ‘14’ with Master Client Number and REF01 ‘23’ with specific Client Number are required. Even though you may have a single client number setup with CIT, you still need two REF segments, even if they are both the same.
    D. If item is a credit memo include REF ‘OI’ with the original invoice number to which the credit memo refers. Enter “CREDIT” if unknown.
    E. The other REF01 types are conditional depending on the data or setup with CIT.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    14
    Master Account Number
    23
    Client Number
    REF-02
    127
    Reference Identification
    Required
    String (AN)
    Min 1Max 30

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

    REF
    050
    Heading > REF

    Reference Identification Rest All

    OptionalMax use 4

    To specify identifying information

    Usage notes

    A. REF segments are used to identify each of the following: Master Client Number, Client Number, Trade Style, Department Number, Internal Vendor Number, and Credit Memo Original Invoice Number.
    C. Both a REF01 ‘14’ with Master Client Number and REF01 ‘23’ with specific Client Number are required. Even though you may have a single client number setup with CIT, you still need two REF segments, even if they are both the same.
    D. If item is a credit memo include REF ‘OI’ with the original invoice number to which the credit memo refers. Enter “CREDIT” if unknown.
    E. The other REF01 types are conditional depending on the data or setup with CIT.

    Example
    Variants (all may be used)
    REFReference Identification REF01 14 23
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    3J
    Office Number
    DP
    Department Number
    IA
    Internal Vendor Number
    OI
    Original Invoice Number
    REF-02
    127
    Reference Identification
    Required
    String (AN)
    Min 1Max 30

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

    YNQ
    055
    Heading > YNQ

    Yes/No Question

    OptionalMax use 2

    To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

    Usage notes

    A. Conditionally used to indicate special Factoring Fee Code or Client Risk Code. Use this segment only when CIT ECS representative requests you to do so. Otherwise, omit the segment if neither item is used.
    B. If YNQ08 = ‘54’ a value of 1,2,3 or 4 is used to indicate different factoring fees for assignments. Use only when CIT ECS representative requests you to use this field. Items with different factoring fees must be separated into to different assignments (see N9 segment for assignment number information).
    C. If YNQ08 = ‘G’ then one of the following risk codes must be used: 1 – indicates Client Risk, S - indicates Split Risk, 2 - indicates Bill & Hold Approved, 3 – indicates Bill & Hold Client Risk

    Example
    If Industry Code (YNQ-09) is present, then Code List Qualifier Code (YNQ-08) is required
    YNQ-02
    1073
    Yes/No Condition or Response Code
    Required

    Code indicating a Yes or No condition or response

    • YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N" indicates the statement is denied.
    Y
    Yes
    YNQ-08
    1270
    Code List Qualifier Code
    Optional

    Code identifying a specific industry code list

    54
    Type of Bill Code
    G
    Risk Class
    YNQ-09
    1271
    Industry Code
    Optional
    String (AN)
    Min 1Max 1

    Code indicating a code from a specific industry code list

    N1 Loop Buyer BY
    RequiredMax 1
    Usage notes

    A. N1 segments are required for each: Buying Party (customer) information and Ship To location information.
    B. Buying Party Identification Code, or Customer Number, is the client’s customer identifier. We maintain a cross-reference table that identifies your customers in our system. With the customer information provided in these N1, N2, N3, N4 and PER segments we are able to maintain an up to date cross-reference from your customer number to our customer number.
    C. The Ship To location should contain the Retailer’s Store number if known – mandatory for chain stores.
    D. This is the start of the loop of 2 sets of N1, N2, N3, N4 and PER segments.

    Variants (all may be used)
    N1 Loop ShipTo ST
    N1
    070
    Heading > N1 Loop Buyer BY > N1

    Name

    RequiredMax use 1

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

    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

    BY
    Buying Party (Purchaser)
    N1-02
    93
    Name
    Required
    String (AN)
    Min 1Max 30

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

    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
    Optional
    String (AN)
    Min 2Max 15

    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
    Heading > N1 Loop Buyer BY > N2

    Additional Name Information

    OptionalMax use 1

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

    Example
    N2-01
    93
    Name
    Optional
    String (AN)
    Min 1Max 30

    Free-form name

    N3
    090
    Heading > N1 Loop Buyer BY > N3

    Address Information

    RequiredMax use 1

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    String (AN)
    Min 1Max 30

    Address information

    N3-02
    166
    Address Information
    Optional
    String (AN)
    Min 1Max 30

    Address information

    N4
    100
    Heading > N1 Loop Buyer BY > N4

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    String (AN)
    Min 2Max 17

    Free-form text for city name

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

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

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

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

    N4-04
    26
    Country Code
    Optional
    Identifier (ID)
    Min 2Max 3

    Code identifying the country

    PER
    120
    Heading > N1 Loop Buyer BY > PER

    Administrative Communications Contact

    OptionalMax use 1

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

    Usage notes

    Used to identify customer phone number. Required only with the N1 loop for Buyer (N101=BY). Missing phone number may delay setup of new customer accounts. Note field length – please remove dashes, slashes, parentheses, etc. and provide number only.

    Example
    PER-01
    366
    Contact Function Code
    Required

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

    CR
    Customer Relations
    PER-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Required

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Required
    String (AN)
    Min 1Max 10

    Complete communications number including country or area code when applicable

    N1 Loop Buyer BY end
    N1 Loop ShipTo ST
    RequiredMax 1
    Usage notes

    A. N1 segments are required for each: Buying Party (customer) information and Ship To location information.
    B. Buying Party Identification Code, or Customer Number, is the client’s customer identifier. We maintain a cross-reference table that identifies your customers in our system. With the customer information provided in these N1, N2, N3, N4 and PER segments we are able to maintain an up to date cross-reference from your customer number to our customer number.
    C. The Ship To location should contain the Retailer’s Store number if known – mandatory for chain stores.
    D. This is the start of the loop of 2 sets of N1, N2, N3, N4 and PER segments.

    Variants (all may be used)
    N1 Loop Buyer BY
    N1
    070
    Heading > N1 Loop ShipTo ST > N1

    Name

    RequiredMax use 1

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

    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-02
    93
    Name
    Required
    String (AN)
    Min 1Max 30

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

    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
    Optional
    String (AN)
    Min 2Max 15

    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
    Heading > N1 Loop ShipTo ST > N2

    Additional Name Information

    OptionalMax use 1

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

    Example
    N2-01
    93
    Name
    Optional
    String (AN)
    Min 1Max 30

    Free-form name

    N3
    090
    Heading > N1 Loop ShipTo ST > N3

    Address Information

    RequiredMax use 1

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    String (AN)
    Min 1Max 30

    Address information

    N3-02
    166
    Address Information
    Optional
    String (AN)
    Min 1Max 30

    Address information

    N4
    100
    Heading > N1 Loop ShipTo ST > N4

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Required
    String (AN)
    Min 2Max 17

    Free-form text for city name

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

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

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

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

    N4-04
    26
    Country Code
    Optional
    Identifier (ID)
    Min 2Max 3

    Code identifying the country

    PER
    120
    Heading > N1 Loop ShipTo ST > PER

    Administrative Communications Contact

    OptionalMax use 1

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

    Usage notes

    Used to identify customer phone number. Required only with the N1 loop for Buyer (N101=BY). Missing phone number may delay setup of new customer accounts. Note field length – please remove dashes, slashes, parentheses, etc. and provide number only.

    Example
    PER-01
    366
    Contact Function Code
    Required

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

    CR
    Customer Relations
    PER-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Required

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Required
    String (AN)
    Min 1Max 10

    Complete communications number including country or area code when applicable

    N1 Loop ShipTo ST end
    ITD
    130
    Heading > ITD

    Terms of Sale/Deferred Terms of Sale

    RequiredMax use 1

    To specify terms of sale

    Usage notes

    A. We maintain a 3 digit terms code cross-reference for each client. This term code must appear in the first 3 characters of the ITD12 element. If terms code is fewer than 3 characters use spaces to fill the 3 positions. The remaining positions of this element (4-40) are for a free form terms description.
    B. Use ‘000’ for Credit Memo terms.

    Example
    ITD-12
    352
    Description
    Required
    String (AN)
    Min 1Max 40

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

    DTM
    140
    Heading > DTM

    Date/Time Reference

    RequiredMax use 2

    To specify pertinent dates and times

    Usage notes

    A. Indicates date goods were shipped and/or as-of date, if applicable.
    B. As-of Date is only used to override Invoice Date for terms and aging calculations.
    C. Contact ECS representative for information on how to specify an invoice due date under
    special terms circumstances.

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    011
    Shipped
    600
    As Of
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    FOB
    150
    Heading > FOB

    F.O.B. Related Instructions

    OptionalMax use 1

    To specify transportation instructions relating to shipment

    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
    PA
    Advance Prepaid
    PB
    Customer Pick-up/Backhaul
    PC
    Prepaid but Charged to Customer
    PO
    Prepaid Only
    PP
    Prepaid (by Seller)
    N9 Loop
    RequiredMax 1
    N9
    240
    Heading > N9 Loop > N9

    Reference Identification

    RequiredMax use 1

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    A. Used to indicate batch Assignment Number and Assignment Date. Assignment Number must not repeat for transmissions within the same day.
    B. This is a required segment. Some EDI translators require an MSG segment if this N9 segment is used. If so, include MSG with generic comment like “CIT Invoices”.
    Example: MSG*CIT Invoices~
    C. Assignment Number should be exactly 4 characters and cannot be all zeroes (0000).

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    A3
    Assignment Number
    N9-02
    127
    Reference Identification
    Required
    String (AN)
    Min 4Max 4

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

    N9-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    MSG
    250
    Heading > N9 Loop > MSG

    Message Text

    OptionalMax use 10

    To provide a free-form format that allows the transmission of text information

    Example
    MSG-01
    933
    Free-Form Message Text
    Required
    String (AN)
    Min 1Max 264

    Free-form message text

    N9 Loop end
    Heading end

    Detail

    IT1 Loop
    RequiredMax 2000000
    Usage notes

    A. Element 235/234 combinations should be interpreted to include products and/or services.
    B. IT101 is the purchase order line item identification.

    IT1
    010
    Detail > IT1 Loop > IT1

    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

    A. Element 235/234 combinations should be interpreted to include products and/or services.
    B. IT101 is the purchase order line item identification.

    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
    If either Product/Service ID Qualifier (IT1-12) or Product/Service ID (IT1-13) is present, then the other is required
    IT1-01
    350
    Assigned Identification
    Required
    String (AN)
    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
    Decimal number (R)
    Min 1Max 10

    Number of units invoiced (supplier units)

    IT1-03
    355
    Unit or Basis for Measurement Code
    Required
    Identifier (ID)
    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
    Required
    Decimal number (R)
    Min 1Max 15

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

    IT1-05
    639
    Basis of Unit Price Code
    Optional
    Identifier (ID)
    Min 2Max 2

    Code identifying the type of unit price for an item

    IT1-06
    235
    Product/Service ID Qualifier
    Optional
    Identifier (ID)
    Min 2Max 2

    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.
    IT1-07
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    IT1-08
    235
    Product/Service ID Qualifier
    Optional
    Identifier (ID)
    Min 2Max 2

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

    IT1-09
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    IT1-10
    235
    Product/Service ID Qualifier
    Optional
    Identifier (ID)
    Min 2Max 2

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

    IT1-11
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    IT1-12
    235
    Product/Service ID Qualifier
    Optional
    Identifier (ID)
    Min 2Max 2

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

    IT1-13
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    IT3
    030
    Detail > IT1 Loop > IT3

    Additional Item Data

    OptionalMax use 1

    To specify additional item details relating to variations between ordered and shipped quantities, or to specify alternate units of measures and quantities

    Usage notes

    Used to confirm if shipment was made in full.

    Example
    If either Number of Units Shipped (IT3-01) or Unit or Basis for Measurement Code (IT3-02) is present, then the other is required
    IT3-01
    382
    Number of Units Shipped
    Optional
    Decimal number (R)
    Min 1Max 10

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

    IT3-02
    355
    Unit or Basis for Measurement Code
    Optional
    Identifier (ID)
    Min 2Max 2

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

    IT3-03
    368
    Shipment/Order Status Code
    Optional

    Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction

    BK
    Back Ordered from Previous Order
    BP
    Shipment Partial, Back Order to Ship on (Date)
    CL
    Complete
    CM
    Shipment Complete with Additional Quantity
    CP
    Partial Shipment on (Date), Considered No Backorder
    CS
    Shipment Complete with Substitution
    IC
    Item Canceled
    IS
    Item Represents Substitution from Original Order
    PID Loop
    OptionalMax 3
    PID
    060
    Detail > IT1 Loop > PID Loop > PID

    Product/Item Description

    RequiredMax use 1

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

    Usage notes

    Used to indicate details about the item sold. Possible information available are color, size, and any free-form description. May provide up to 3 PID segments.

    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-02
    750
    Product/Process Characteristic Code
    Optional

    Code identifying the general class of a product or process characteristic

    08
    Product
    73
    Vendor color description
    74
    Vendor size description
    PID-05
    352
    Description
    Optional
    String (AN)
    Min 1Max 80

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

    PID Loop end
    IT1 Loop end
    Detail end

    Summary

    TDS
    010
    Summary > TDS

    Total Monetary Value Summary

    RequiredMax use 1

    To specify the total invoice discounts and amounts

    Usage notes

    A. TDS01 is the total amount of the invoice, including charges (freight, for example) less allowances, before any discounts. Implied decimal point; send $4554.20 as 455420
    B. If invoice has terms discount, TDS02 is the amount discounted if different than invoice amount. TDS02 is not needed if there is no payment terms discount.
    C. Use TDS04 to indicate any special, non-terms discount. TDS04 will override any other terms discount, if present. TDS04 is rarely used.

    Example
    TDS-01
    610
    Amount
    Required
    Numeric (N2)
    Min 1Max 10

    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
    Numeric (N2)
    Min 1Max 10

    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-04
    610
    Amount
    Optional
    Numeric (N2)
    Min 1Max 10

    Monetary amount

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

    Carrier Detail

    RequiredMax use 1

    To specify transportation details for the transaction

    Usage notes

    At least the CAD05 is required.

    Example
    CAD-04
    140
    Standard Carrier Alpha Code
    Optional
    Identifier (ID)
    Min 2Max 4

    Standard Carrier Alpha Code

    CAD-05
    387
    Routing
    Required
    String (AN)
    Min 1Max 35

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

    SAC Loop
    OptionalMax 3
    SAC
    040
    Summary > SAC Loop > SAC

    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

    A. Used to indicate freight charges and other special charges or allowances covering the invoice.
    B. If the SAC segment is used, then SAC01, SAC02, and SAC05 are required.
    C. When indicating a miscellaneous value use SAC15 to describe it.
    D. We can accommodate up to 3 SAC segments.
    E. Do not use the SAC segment if no additional charges or allowances exist.

    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

    D240
    Freight
    H740
    Tax - Sales and Use
    ZZZZ
    Mutually Defined
    SAC-05
    610
    Amount
    Required
    Numeric (N2)
    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

    05
    Charge to be Paid by Vendor
    06
    Charge to be Paid by Customer
    PP
    Prepaid
    SAC-15
    352
    Description
    Optional
    String (AN)
    Min 1Max 80

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

    SAC Loop end
    ISS Loop
    RequiredMax 1
    ISS
    060
    Summary > ISS Loop > ISS

    Invoice Shipment Summary

    RequiredMax use 1

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

    Example
    ISS-01
    382
    Number of Units Shipped
    Required
    Decimal number (R)
    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

    CT
    Carton
    ISS Loop end
    CTT
    070
    Summary > CTT

    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

    This segment is intended to provide hash totals to validate transaction completeness and correctness.

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Numeric (N0)
    Min 1Max 6

    Total number of line items in the transaction set

    SE
    080
    Summary > SE

    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
    Numeric (N0)
    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
    Numeric (N)
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    Summary end

    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
    Numeric (N0)
    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
    Numeric (N0)
    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
    Numeric (N0)
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Numeric (N0)
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    CIT 810 Invoice

    ISA*00* *00* *01*SENDER *ZZ*CITICCPROD *230912*2317*U*00401*000000001*0*P*>~
    GS*IN*SENDER*CITICCPROD*20230912*2317*000000001*X*004010~
    ST*810*0001~
    BIG*20230912*24243234*20230910*234234~
    REF*14*423~
    REF*23*6143248M~
    REF*IA*4234~
    N1*BY*2342 INC*92*234~
    N3*PO BOX 34234~
    N4*ORANFG*OH*12344-039*US~
    N1*ST*David K~
    N3*232 PENN Road~
    N4*ORANGE*NJ*06122-104*US~
    ITD************ NET 60~
    DTM*011*20230912~
    N9*A3*0753**20230912~
    MSG*CIT Invoices~
    IT1*1*1*PR*58.80*WE*UP*124234*****VN*324134~
    PID*F*74***7.5~
    PID*F*08***4234~
    PID*F*73***200~
    TDS*5880~
    CAD*****RF5~
    ISS*1*CT~
    CTT*1~
    SE*24*0001~
    GE*1*000000001~
    IEA*1*000000001~

    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.