Frames | No Frames
Return to Stylus Studio EDIFACT home page.|
Return to Stylus Studio EDIFACT D93A Messages page.
BANKING STATUS MESSAGE
This specification provides the definition of the Banking Status Message (BANSTA) to be used in electronic data interchange (EDI) between partners involved in administration, commerce and transport.
1.1. Functional Definition
A BANSTA message is sent by the receiver of a previously sent message to report on the status of processing of this original message. It indicates, at the application level, the acceptance or rejection of the message or the ability for the receiver of the message to execute or not the instructions received.
Throughout this document the term 'Originator' refers to the sender of the original message to which the BANSTA message is responding; likewise, the term 'Recipient' refers to the sender of the Status message sent in response to the message generated by the 'Originator'.
1.2. Field of Application
This message type may be applied for both national and international settlements. It is based on universal practice and is not dependent on the type of business or industry.
This message type may be used to respond to any previously sent message.
It is a multi-purpose response providing status information based on universal practice and is not dependent of the type of business or industry.
previously sent message, such as a commercial or payment instruction, a request for information, etc. This message provides a means to report on errors and inconsistencies found in the original message at application level.
provide a non-repudiation response.
execution on original multi-instruction messages such as the Multiple Payment Order message (PAYMUL) or Direct Debit message (DIRDEB).
payment instructions. This message could be used for any response to a previously sent message when such response is needed and/or requested.
See UNTDID, Part 4 Section 2.5 UN/ECE UNSM - General Introduction, Section 1.
3. Terms and Definitions
See UNTDID, Part 4, Section 2.5 UN/ECE UNSM - General Introduction, Section 2.
4. Message Definition
4.1. Data Segment Clarification
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
0010 UNH, Message header
A service segment starting and uniquely identifying the message.
The message type code for the UN Status message is BANSTA.
Note: BANSTA messages conforming to this document must contain the following data in segment UNH, composite S009:
A group of segments for unique identification of the BANSTA message, the date and time, the type of BANSTA message (e.g. response to an original instruction, to a query, etc.) and its function.
0030 BGM, Beginning of message
A segment identifying the BANSTA message, its type and function.
0040 DTM, Date/time/period
A segment specifying the date and time of the status message.
A group of segments identifying the original message to which the Status message is referring. It may also refer to the query to which this Status information applies. When several queries have been sent, the date/time information identifies the specific query concerned.
0060 RFF, Reference
A segment identifying a previously sent message and/or query.
0070 DTM, Date/time/period
A segment identifying the date/time of the previously sent message and/or query.
A group of segments identifying the parties involved in the exchange of the message, and their contacts.
0090 NAD, Name and address
A segment identifying the party and its function.
0100 CTA, Contact information
A segment identifying a person or department for the party specified in the NAD segment and to whom communication should be directed.
0110 COM, Communication contact
A group of segments identifying the original message and/or part thereof. It indicates the acceptance or rejection of the original message and may provide a means to report on application errors, inconsistencies and queries.
0130 SEQ, Sequence details
A segment referring to the original message. and one or more specific line(s) or party(ies) of the original message.
A group of segments identifying the original message or part thereof.
0150 RFF, Reference
0160 DTM, Date/time/period
A segment identifying the date/time at which the reference was created.
A group of segments indicating the response of the receiving application and if relevant, an error. It can also indicate the purpose of a query.
0180 GIS, General indicator
A segment indicating if the original message has been accepted or rejected with or without error.
0190 DTM, Date/time/period
A segment identifying the date/time of the status of the processing at a given moment.
A group of segments identifying an error, providing a standard description of this error, and, if relevant, one to many documents related to this error.
0210 ERC, Application error information
A segment identifying the type of error detected in the original message.
0220 FTX, Free text
A segment giving additional information to the error or information coded in the ERC segment.
0230 DOC, Document/message details
A segment to indicate a related document or a request from the recipient of the message, to receive one or more specific document(s).
A group of segments specifying the details of authentication.
0250 AUT, Authentication result
A segment specifying the details of any authentication (validation) procedure applied to the BANSTA message.
0260 DTM, Date/time/period
A segment identifying the date and if necessary, the time of validation.
0270 UNT, Message trailer
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
4.2. Message Structure
4.2.1. Branching Diagram
4.2.2. Segment Table
4.3. Data Segment Index (Alphabetic Sequence)
Return to Stylus Studio EDIFACT D93A Messages page.