CIT Bank
/
Credit Request
  • 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 855 Credit Request

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) 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 a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

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/credit-request/01HBH3ZQ1N7P81A0Y3KS8B5XM0
    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
    BAK
    020
    Beginning Segment for Purchase Order Acknowledgment
    Max use 1
    Required
    REF
    050
    Reference Identification
    Max use 2
    Required
    REF
    050
    Reference Identification
    Max use 1
    Optional
    ITD
    130
    Terms of Sale/Deferred Terms of Sale
    Max use 1
    Required
    DTM
    150
    Date/Time Reference
    Max use 2
    Required
    N1 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
    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-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

    PR
    Purchase Order Acknowledgement (855)
    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).
    855
    Purchase Order Acknowledgment
    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

    BAK
    020
    Heading > BAK

    Beginning Segment for Purchase Order Acknowledgment

    RequiredMax use 1

    To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates

    Usage notes

    A. The client order number in BAK08 will be returned on the credit confirmation to allow you to match orders to confirmations. The On-Line system displays a maximum of 8 characters.

    B. Use BAK10 only if holding goods (not shipping) but billing now.

    Example
    BAK-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    22
    Information Copy
    BAK-02
    587
    Acknowledgment Type
    Required

    Code specifying the type of acknowledgment

    AK
    Acknowledge - No Detail or Change
    BAK-03
    324
    Purchase Order Number
    Optional
    String (AN)
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    BAK-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BAK04 is the date assigned by the purchaser to purchase order.
    BAK-08
    127
    Reference Identification
    Required
    String (AN)
    Min 1Max 22

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

    • BAK08 is the seller's order number.
    BAK-09
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BAK09 is the date assigned by the sender to the acknowledgment.
    BAK-10
    640
    Transaction Type Code
    Optional

    Code specifying the type of transaction

    BH
    Bill and Hold Goods
    REF
    050
    Heading > REF

    Reference Identification

    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 and Trade Style.

    B. 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 you still need two REF segments.

    C. The other REF01 type, ‘3J’ is only used if you have trade styles setup within your client number.

    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

    OptionalMax use 1

    To specify identifying information

    Usage notes

    A. 'REF' segments are used to identify each of the following: Master Client Number, Client Number and Trade Style.

    B. 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 you still need two REF segments.

    C. The other REF01 type, ‘3J’ is only used if you have trade styles setup within your client number.

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

    Code qualifying the Reference Identification

    3J
    Office Number
    REF-02
    127
    Reference Identification
    Optional
    String (AN)
    Min 1Max 30

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

    ITD
    130
    Heading > ITD

    Terms of Sale/Deferred Terms of Sale

    RequiredMax use 1

    To specify terms of sale

    Usage notes

    Used to indicate the number of days from invoice date to due date. This is not the same as the invoice terms code; rather it is the net number of days. Value must not be zero (0).

    Example
    ITD-07
    386
    Terms Net Days
    Required
    Numeric (N0)
    Min 1Max 3

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

    DTM
    150
    Heading > DTM

    Date/Time Reference

    RequiredMax use 2

    To specify pertinent dates and times

    Usage notes

    Use two DTM segments to identify a shipment start and completion date range, one for the start date, the other for the complete date. If just one DTM segment is transmitted we will use same date for start and complete date.

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    375
    Delivery Start
    376
    Delivery End
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    N1 Loop
    RequiredMax 1
    Usage notes

    Buying Party Identification Code, or Customer Number, is the client’s customer identifier. We maintain a cross-reference table that identifies your customers in the CIT 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 the our customer number.

    N1
    300
    Heading > N1 Loop > N1

    Name

    RequiredMax use 1

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

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

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

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

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

    91
    Assigned by Seller or Seller's Agent
    N1-04
    67
    Identification Code
    Required
    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
    310
    Heading > N1 Loop > 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
    320
    Heading > N1 Loop > 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
    330
    Heading > N1 Loop > 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
    350
    Heading > N1 Loop > 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. Missing phone number will delay setup of new customer accounts. Note field length of 10 – 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 end
    Heading end

    Summary

    CTT Loop
    RequiredMax 1
    CTT
    010
    Summary > CTT Loop > CTT

    Transaction Totals

    RequiredMax use 1

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

    • The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
    Usage notes

    This segment is required for EDI; fill hash total count with zero (0).

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

    Total number of line items in the transaction set

    AMT
    020
    Summary > CTT Loop > AMT

    Monetary Amount

    RequiredMax use 1

    To indicate the total monetary amount

    • If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction amount as calculated by the sender.
    Example
    AMT-01
    522
    Amount Qualifier Code
    Required

    Code to qualify amount

    TT
    Total Transaction Amount
    AMT-02
    782
    Monetary Amount
    Required
    Decimal number (R)
    Min 1Max 15

    Monetary amount

    CTT Loop end
    SE
    030
    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 855 Inbound Credit Request Sample

    ISA*00* *00* *01*SENDER *ZZ*CITICCPROD *230912*1101*U*00401*000102488*0*P*>~
    GS*PR*SENDER*CITICCPROD*20230912*1101*000001042*X*004010~
    ST*855*0001~
    BAK*22*AK*e23123213*20230809****424323*20230912~
    REF*14*6142348M~
    REF*23*613238M~
    ITD*******90~
    DTM*375*20231110~
    DTM*376*20231210~
    N1*BY*ACME*91*3123~
    N3*I-880~
    N4*312312*NJ*94540~
    CTT*0~
    AMT*TT*90045~
    SE*13*0001~
    GE*1*000001042~
    IEA*1*000102488~

    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.