CIT Bank
/
Credit Confirmation
  • Specification
  • EDI Inspector
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 Confirmation

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
  • CIT 855 Out Credit Confirmations sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/cit-bank/credit-confirmation/01HBH400298H763RNWB1F2Z7KE
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 3
Required
DTM
150
Date/Time Reference
Max use 2
Required
DTM
150
Extract
Max use 1
Required
CTB
277
Restrictions/Conditions
Max use 2
Optional
N9 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
Identifier (ID)

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
Identifier (ID)

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
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
Identifier (ID)

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
Identifier (ID)

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

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
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
String (AN)

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
Identifier (ID)

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

BAK03 is a CIT system generated internal order reference number. BAK08 is the client order number as received on the credit request.
**First 14 characters of Order Number received on Credit Request. The On-Line System displays a max. of 8 chars.

Example
BAK-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

22
Information Copy
BAK-02
587
Acknowledgment Type
Required
Identifier (ID)

Code specifying the type of acknowledgment

AH
Acknowledge - Hold Status
BAK-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BAK04 is the date assigned by the purchaser to purchase order.
BAK-08
127
Reference Identification
Optional
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.
REF
050
Heading > REF

Reference Identification

RequiredMax use 3

To specify identifying information

Usage notes

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

B. A credit confirmation will contain exactly three REF segments – one for each of the following: Master Client Number, Client Number and CIT Customer Number.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

14
Master Account Number
23
Client Number
IT
Internal Customer 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

DTM
150
Heading > DTM

Date/Time Reference

RequiredMax use 2

To specify pertinent dates and times

Usage notes

A. A credit confirmation will contain exactly three DTM segments – one for each of the following: Delivery Start Date, Delivery End Date, and Confirmation Create Date and Time.

B. Elements DTM03, DTM05 and DTM06 are used only when DTM01 is ‘507’

Example
Variants (all may be used)
DTMExtract
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

375
Delivery Start
376
Delivery End
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

DTM
150
Heading > DTM

Extract

RequiredMax use 1

To specify pertinent dates and times

Usage notes

A. A credit confirmation will contain exactly three DTM segments – one for each of the following: Delivery Start Date, Delivery End Date, and Confirmation Create Date and Time.

B. Elements DTM03, DTM05 and DTM06 are used only when DTM01 is ‘507’

Example
Variants (all may be used)
DTMDate/Time Reference
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

507
Extract
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
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)

DTM-05
1250
Date Time Period Format Qualifier
Required
Identifier (ID)

Code indicating the date format, time format, or date and time format

TC
Julian Date Expressed in Format DDD
DTM-06
1251
Date Time Period
Required
String (AN)
Min 1Max 3

Expression of a date, a time, or range of dates, times or dates and times

CTB
277
Heading > CTB

Restrictions/Conditions

OptionalMax use 2

To specify restrictions/conditions (such as shipping, ordering)

Usage notes

Indicates customer credit line and amount approved for the credit request.

Example
CTB-01
688
Restrictions/Conditions Qualifier
Required
Identifier (ID)

Code identifying the type of restriction/condition

OR
Ordering
SR
Shipping
CTB-05
522
Amount Qualifier Code
Required
Identifier (ID)

Code to qualify amount

AAE
Approved Amount
GO
Credit Line
CTB-06
610
Amount
Required
Numeric (N2)
Min 1Max 15

Monetary amount

N9 Loop
RequiredMax 1
Usage notes

Indicates the status of the credit request at the time the confirmation was created. The status will consist of the action code (approved, declined, on hold, canceled) and up to five two-digit reason codes. Reason codes will not appear on approved orders, but will appear on other actions. See the Codes section at the end of this EDI Guide for complete listing of Action
Codes and Reason Codes.

N9
280
Heading > N9 Loop > N9

Reference Identification

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

KO
Customs Drawback Entry Number
N9-02
127
Reference Identification
Required
String (AN)
Min 2Max 2

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

N9-03
369
Free-form Description
Optional
String (AN)
Min 2Max 10

Free-form descriptive text

N9 Loop end
N1 Approver
RequiredMax 1
Usage notes

Used to identify the Client Customer Number and the Credit Officer information.

Variants (all may be used)
Buying Party (Purchaser)
N1
300
Heading > Approver > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

88
Approver
Optional
String (AN)
Min 1Max 30

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

91
Assigned by Seller or Seller's Agent
A1
Approver ID
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.
REF
340
Heading > Approver > REF

Reference Identification

RequiredMax use 1

To specify identifying information

Usage notes

Used only with N1 when N101 = 88

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

5D
Line of Credit Category
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 1

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

N1 Approver end
N1 Buying Party (Purchaser)
RequiredMax 1
Usage notes

Used to identify the Client Customer Number and the Credit Officer information.

Variants (all may be used)
Approver
N1
300
Heading > Buying Party (Purchaser) > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

BY
Buying Party (Purchaser)
Required
String (AN)
Min 1Max 30

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

91
Assigned by Seller or Seller's Agent
A1
Approver ID
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.
N1 Buying Party (Purchaser) end
Heading end

Summary

CTT Loop
RequiredMax 1
Usage notes

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

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

Contains original amount of the credit request. The approved amount is in the CTB segment.

Example
AMT-01
522
Amount Qualifier Code
Required
Identifier (ID)

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 Out Credit Confirmations sample

ISA*00* *00* *ZZ*CITICCPROD *01*RECEIVER *230911*0900*U*00401*000001712*0*P*>~
GS*PR*CITICCPROD*RECEIVER*20230911*0900*000000634*X*004010~
ST*855*000010280~
BAK*22*AH*232540459*20230911~
REF*14*4324234~
REF*23*612342348M~
REF*IT*42342~
DTM*375*20230911~
DTM*376*20231211~
DTM*507**0900**TC*254~
CTB*OR****GO*3423452~
CTB*SR****AAE*4234~
N9*KO*AA~
N1*BY*Acme INC*91*4234~
N1*88**A1*323~
REF*5D*3~
CTT*0~
AMT*TT*75000~
SE*17*000010280~
GE*1*000000634~
IEA*1*000001712~

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.