972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Finance

BANSTA Banking status

The UN/EDIFACT message used between banks and customers for enquiries, answers and status information at application level.

Sent by
Bank or customer
Received by
Customer or bank
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT BANSTA message?

BANSTA is the UN/EDIFACT banking status message. The directory defines it as a message sent by a financial institution to its customer, by a customer to its institution, or between institutions, for all kinds of enquiries, answers and status information at application level.

Its most common use is reporting the processing status of payment files: accepted, rejected, partly rejected or executed, with reasons for any rejection. Treasury teams rely on it to know quickly whether payments sent to the bank will actually go out.

How the EDIFACT BANSTA message worksDiagram of the UN/EDIFACT BANSTA Banking status message. Bank or customer sends it to customer or bank. It usually follows PAYMUL, PAYORD, PAYEXT and DIRDEB. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG4 loop with LIN (Line item). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT BANSTA message worksBanking status: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSPAYMULMultiple payment orderPAYORDPayment orderPAYEXTExtended paymentorderDIRDEBDirect debitBANSTASENDERBank or customerRECEIVERCustomer or bankCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage BANSTAUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG4 · repeats up to 999LINLine item+ 6 conditional groups, starting with:RFFFIINADSEQAUTBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for BANSTA. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT BANSTA message worksDiagram of the UN/EDIFACT BANSTA Banking status message. Bank or customer sends it to customer or bank. It usually follows PAYMUL, PAYORD, PAYEXT and DIRDEB. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: the required SG4 loop with LIN (Line item). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT BANSTAmessage worksBanking status: who sends it, where it fits andwhat the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSPAYMULMultiple payment orderPAYORDPayment orderPAYEXTExtended payment orderDIRDEBDirect debitBANSTASENDERBank orcustomerRECEIVERCustomer orbankCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message BANSTA (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG4 · repeats upto 999LINLine item+ 6 conditional groups, starting with:RFFFIINADSEQAUTBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for BANSTA.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends BANSTA, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around BANSTA and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Reporting acceptance or rejection of payment orders
  • Answering a customer's enquiry about a transaction
  • Reporting execution status of payments

Where it fits in the message flow

Usually follows PAYMUL Multiple payment orderPAYORD Payment orderPAYEXT Extended payment orderDIRDEB Direct debit
This message BANSTA Banking status

Structure

Mandatory segments in BANSTA (directory D.21A)

In UN/EDIFACT directory D.21A, the BANSTA message has 33 segment positions arranged in 9 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • DTM
  • SG4 (LIN)
  • UNT

Practical example

BANSTA in practice

A manufacturer sends its bank a PAYMUL with 200 supplier payments. The bank's validation finds two payments with invalid account numbers. It sends a BANSTA accepting 198 payments and rejecting the two with reason codes. The treasury team corrects the beneficiary details and resends the two payments the same day.

Implementation

Implementation considerations for BANSTA

  • Map status and reason codes to actions in treasury systems.
  • Reconcile status reports with the payments sent.
  • Alert people when rejections arrive near cut-off times.
  • Check whether the bank uses BANSTA or an ISO 20022 status report.

How ECOM helps

Automate BANSTA with ECOM

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related finance messages

All 37 finance messages

Need help with BANSTA?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us