Return to EDIFACT D96B Messages page.Banking status message
0. INTRODUCTIONThis specification provides the definition of the Banking status message (BANSTA) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. 1. SCOPE1.1. Functional DefinitionA BANSTA message is sent by a financial institution to its customer and/or vice versa and among financial institutions. It is used for all kind of enquiries, answers and status information at application level. 1.2. Field of ApplicationThis message may be applied for both national and international transactions. It is based on universal practice and is not dependent on the type of business or industry. 1.3. PrinciplesA BANSTA message must always refer to a specific previously-sent message.
2. REFERENCESSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONSSee UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION4.1. Data Segment ClarificationThis section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements. The following semantic principles apply to the message and are intended to facilitate the understanding and implementation of the message: The Banking Status message is structured in three levels: A, B and C.
0010 UNH, Message headerA service segment starting and uniquely identifying a message. The message type code for the Banking status message is BANSTA. Note: Banking status messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of messageA segment by means of which the sender must uniquely identify the BANSTA message using its type and number and its function (e.g. response, enquiry, status etc.). 0030 DTM, Date/time/periodA segment specifying the date and, if required, the time the message is created. 0040 BUS, Business functionA segment identifying certain characteristics of the Banking Status message, such as its business function. 0050 Segment Group 1: RFF-DTMA group of segments identifying a previously-sent message, and/or customer to customer reference and related dates. 0060 RFF, ReferenceA segment specifying the reference of the previously-sent message. 0070 DTM, Date/time/periodA segment identifying the creation date of the referenced message. 0080 Segment Group 2: FII-CTA-COMA group of segments identifying the financial institutions involved in the Banking Status message, routing functions and contacts. 0090 FII, Financial institution informationA segment identifying the financial institution(s) associated with the transaction, in coded or uncoded form and their function. 0100 CTA, Contact informationA segment identifying a person or a department for the party specified in the leading FII segment to whom communication should be directed. 0110 COM, Communication contactA segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment. 0120 Segment Group 3: NAD-CTA-COMA group of segments identifying the name(s) and adress(es) of non-financial parties involved in the transaction, their function and their contacts. 0130 NAD, Name and addressA segment identifying the names and addresses of the non-financial parties associated with the Banking Status message, in coded or uncoded form, and their function. 0140 CTA, Contact informationA segment identifying a person or department for the party specified in the NAD segment and to whom communication should be directed. 0150 COM, Communication contactA segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment. 0160 Segment Group 4: LIN-SG5-SG6A group of segments identifying a message or transaction and the status of the referred message/transaction, as well as any reasons clarifying the status. 0170 LIN, Line itemA segment identifying the beginning of the details related to the previously-sent message by a sequential line number. 0180 Segment Group 5: RFF-DTMA group of segments specifying reference number(s), date/or time needed in order to identify a referenced message or transaction. 0190 RFF, ReferenceA segment providing references of the message/transaction to be referred to. 0200 DTM, Date/time/periodA segment identifying the date/time of the referred message or transaction. 0210 Segment Group 6: SEQ-GIS-DTM-MOA-CUX-PCD-FTX-DOC-SG7-SG8A group of segments identifying the status, and any reasons clarifying this status, of the referred message/transaction. 0220 SEQ, Sequence detailsA segment identifying the beginning of the specification of the status and related details about the message/transaction by a sequential number. 0230 GIS, General indicatorA segment specifying the processing status of a referenced message/transaction in a coded form. It is used in conjunction with one or more of the following segments or groups clarifying the detailed reply or status/information. 0240 DTM, Date/time/periodA segment identifying dates and/or times related to information in the GIS-segment. 0250 MOA, Monetary amountA segment identifying the amount(s) associated with the related information in the GIS-segment. 0260 CUX, CurrenciesA segment identifying the currency associated with the related information in the GIS segment. 0270 PCD, Percentage detailsA segment identifying the percentage associated with the related information in the GIS segment. 0280 FTX, Free textA segment specifying free form data associated with the related information in the GIS segment. 0290 DOC, Document/message detailsA segment identifying the documents associated with the related information in the GIS segment. 0300 Segment Group 7: FII-CTA-COMA group of segments identifying the financial institution(s) associated with the related information in the GIS segment. 0310 FII, Financial institution informationA segment identifying the financial institution(s) associated with the related information in the GIS segment. 0320 CTA, Contact informationA segment identifying a person or a department for the party specified in the leading FII segment to whom communication should be directed. 0330 COM, Communication contactA segment identifying communication type(s) and number(s) of person(s) or departments(s) specified in the associated CTA segment. 0340 Segment Group 8: NAD-CTA-COMA group of segments identifying the name and address of non-financial parties associated with the related information in the GIS segment. 0350 NAD, Name and addressA segment identifying names and address of non-financial parties associated with the related information in the GIS segment. 0360 CTA, Contact informationA segment identifying a person or a department for the party specified in the leading NAD segment to whom communication should be directed. 0370 COM, Communication contactA segment identifying communication type(s) and number(s) of person(s) or departments(s) specified in the associated CTA segment. 0380 CNT, Control totalA segment identifying the kind of control-checks and the total according to the coded form. 0390 Segment Group 9: AUT-DTMA group of segments specifying details of any authentication (validation) procedures applied to the BANSTA message. 0400 AUT, Authentication resultA segment specifying the details of any authentication (validation) procedures applied to the BANSTA message. 0410 DTM, Date/time/periodA segment identifying the validation date/time. 0420 UNT, Message trailerA service segment ending a message, giving the total number of segments in the message and the control reference number of the message. 4.2. Data segment index (Alphabetical sequence by tag)
4.3. Message structure4.3.1. Segment table
Return to EDIFACT D96B Messages page. |