How Can We Help?

Search for answers or browse our documentation.

BTS Dashboard

< Back

SWIFT and NACHA Batch Maintenance Screen

This program is only used by the SWIFT and NACHA BTS formats.

The files extracted by BTS SWIFT formats are XML files and the NACHA files are fixed length text.

SWIFT Feedback Files

The feedback files from SWIFT are also XML files. These feedback files need to be placed in the XML dashboard path as setup in the SWIFT Bank format setup

In order to process these feedback files, the BTS Dashboard on the BTS menu can be run. The screen will look as per figure 1

Figure 1

Selecting the Status Update button on the screen in figure 1 will process available files in the XML dashboard path and update the status of the corresponding records in the BTS SWIFT system

Selecting the Status Auto Update button on the screen in figure 5 will begin polling the XML dashboard path for available files to process and should update files be encountered, the process will update the status of the corresponding records in the BTS SWIFT system with all the updated Batches for Bank entries being highlighted in green text and the polling process will exit with the first updated (green) entry highlighted. The entries highlighted in green will revert back  to black text when the dashboard program is exited.
The user will be unable to use any of the dashboard functionality until an update XML file is located when the Status Auto Update process will stop executing and the first updated (green) entry will be highlighted..
The user could exit the Status Auto Update process by selecting the Status Auto Update button.

Awaiting Authorisation

If the Payment approval switch has been set in the BTS control for SWIFT or NACHA, when the BTS extract is run, the extract file will not be created and the user will see the screen as per figure 2

 

 

 

Figure 2

In order to release these payments, the BTS Payment Approval on the new BTS menu can be run. This program will look as per figure 3

Figure 3

Payment Approval

Selecting the Payment Approval button on the screen in figure 3 will release the selected batch and the BTS payment file will be created. The following message as per figure 4 will be seen that shows the user what the file name being extracted is

 

 

 

Figure 4

BTS DLL and WCF (Only currently used for Mulesoft)

BTS Dynamic Link Library (DLL) and Windows Communication Foundation (WCF) Processing

Sending – DLL:
Should the BTS format being used make use of API’s to push the files through to the banking  institution, BTS will make use of a Dynamic Link Library (DLL) process which will be called into by the BTS extract process and should the push process fail due to, amongst other things, communication failure, the associated Batches for Bank entries will be represented in red text and it will be required to re-extract the associated EFT batches once the cause for the failure has been resolved.
Receiving – WCF:
Should the BTS format being used make use of a Windows Communication Foundation (WCF) to receive the payment response files from the banking  institution, BTS will make use of a WCF service which, once installed and activated, will accept the payment response files and present them to the BTS Dashboard for importing to update the Batched for Bank status entries.
Should the BTS Dashboard attempt to import payment status update files and identify that the WCF service is flagged as inactive, an error message will be generated as per Figure 5.

 

 

 

Figure 5

Table of Contents