X12 855 Credit Request
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- PR
- Purchase Order Acknowledgement (855)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
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.
Code identifying purpose of transaction set
- 22
- Information Copy
Code specifying the type of acknowledgment
- AK
- Acknowledge - No Detail or Change
Identifying number for Purchase Order assigned by the orderer/purchaser
Date expressed as CCYYMMDD
- BAK04 is the date assigned by the purchaser to purchase order.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BAK08 is the seller's order number.
Date expressed as CCYYMMDD
- BAK09 is the date assigned by the sender to the acknowledgment.
Code specifying the type of transaction
- BH
- Bill and Hold Goods
Office Number
To specify identifying information
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.
Code qualifying the Reference Identification
- 3J
- Office Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Reference Identification
To specify identifying information
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.
Code qualifying the Reference Identification
- 14
- Master Account Number
- 23
- Client Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
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).
Number of days until total invoice amount is due (discount not applicable)
Date/Time Reference
To specify pertinent dates and times
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.
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.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
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.
Code identifying the major duty or responsibility of the person or group named
- CR
- Customer Relations
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Summary
Transaction Totals
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.
This segment is required for EDI; fill hash total count with zero (0).
Total number of line items in the transaction set
Monetary Amount
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.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
CIT 855 Inbound Credit Request Sample
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.