23 April 2014

68780

Ganesh Guruvayur - Polaris Software Lab Ltd

6 | posts 11,991 | views 0 | comments

Multi Banking - Domestic Environment

02 January 2014  |  1780 views  |  0

The recent Payment Survey conducted by gtnews discusses the number of banking partners that corporates deploy. On an average in North America, the number of banking relationships range from 1 to 4 while in Europe, it is found to be as high as 20. It is widely believed that with the onset of SEPA in 2014, a wave of consolidation is expected to be witnessed. It would be interesting to see what the average number would level off to be in Europe. Even with a consolidation phenomenon, the need for low cost multi banking solutions will remain. While the SWIFT based connectivity models are being perfected, Host to Host connectivity, hitherto used by banks to fulfill ERP connectivity requirements of a corporate, has been deployed effectively by banks such as BNP Pariba to provide a conduit to its clients to other non-treasury banks.

How the model works?

Example: A corporate wanting to send bulk drawdown requests to its partner banks, sends the file over the H2H which is received by the Treasury Bank. This model entails using the H2H adaptor at both ends within the Treasury Bank’s environment. Client side component collects new files as they are generated by the accounting package or an ERP system on the corporate side, compresses / encrypts the file and transmits the same to the Treasury Bank over a public or dedicated network.

 The Treasury Bank, on file receipt, checks if decryption, decompression is needed, if the file carries any digital certificate that needs reading. Following this, the file is parsed followed by reference check of the file format preference of the partner bank to ascertain if file conversion is warranted. In-flight file conversion happens. A similar lightweight client side component also sits in the outgoing side of the Treasury Bank environment. This component works on the converted file and transmits the file to the destination partner bank.

 Typical considerations: Cost

An important consideration in the multi bank strategy of a corporate is the charges associated with traffic generated by the corporate on the different banking partners. SWIFT based SCORE (Standardized COrporate Environment) heavily hinges on the sender to receiver BIC code locations. If the two BICs belong to the same country, domestic charges apply. Corporates embracing the SWIFT based connectivity model, usually perform a cost analysis based on the study of the BIC locations, within the domestic landscape, of the recipient banks and the Treasury bank, to determine indicative charges for a sample real life mass of in-country multi bank traffic. Similarly before a corporate decides on a Host to Host based multi banking model, it can use the price catalogue from the Treasury Bank and estimate the bank fee linked cost for a given volume of traffic with an indicative mix of local service requests.

Multi bank model using H2H connectivity works well within the domestic environments in keeping the connectivity costs low. Treasury banks offering this model to their corporate clients and wanting to make a compelling pricing proposition could study the SWIFT pricing for domestic boundary based messages.

Host to Host based links to a treasury bank is reasonably wide spread and can be used to expand to handle the partner bank service request transmission through the Treasury Bank. This helps to elongate the investment in the Host to Host infrastructure both for the corporate and for the bank.

Typical considerations: Ease of Connectivity

Alliance Lite and Alliance Lite 2 are SWIFT provided connectivity adaptors that greatly simplify SWIFT connectivity and support both online and batch based requests and do not require connectivity infrastructure. Corporates connecting to SWIFT also consider SWIFT service bureaus to take care of the complexity involved in connectivity. In case of Host to Host based multi banking, the connectivity is through installation of a light weight client side component in the corporate customer’s environment.

Typical considerations: File Format

A significant volume of multi bank service requests are batched and sent in the form of files to the Partner Bank. Similarly statement of the account, transaction listing require file based responses to be sent back to the corporate. Thus file format design and transformation support becomes a critical ask from a multi banking support. Banking industry is realizing that challenges around getting clients to adopt a standardized format which ISO 20022 XML is coming to represent world over. Measure of message / file format compliance in the corporate community adoption is evident in SEPA zone. This being the case the ability to receive file formats that a corporate is comfortable with is an invaluable feature whichever approach is chosen. The host to host model requires the Treasury bank to be able to receive the files in client preferred format as well as transmit it in the partner preferred format requiring two step conversion.

 Typical considerations: Request Aggregation

 Another aspect of the host to host based multi banking model and which also impacts the cost is the ability to aggregate requests directed to multiple partner banks into a single consolidated file. This requires the Treasury Bank to be able to:

-       Detect if there are multiple destination banks in the file

-       File debulking

-       Regroup the randomly scattered records using partner bank identifier

-       Create separate child files for each partner bank

-       Transmit the child files to the partner banks

-       Receive response back from each partner bank

-       Aggregate responses into a single response file that corresponds to the original request

 

Typical considerations: Content Agnostic

A corporate would expect to be able to send and receive responses to all type of service requests to its partner banks via this Treasury Bank sponsored bridge. Below is a sample list:

  1. Intra day balance position from  Partner Bank
  2. End of day balance position from Partner Bank
  3. ACK / NACK from Partner Bank
  4. Payment Status Reports from Partner Bank
  5. Account Receivables file from Corporate to Partner Bank
  6. Virtual Card Account issuance request from Corporate to Partner Bank
  7. Truncated Check deposit and Image data
  8. Trade Finance requests – Documentary credits related life cycle based requests, Collection Bills etc

Host to Host based model usually supports all these different request types and therefore gets an uptick on this criterion.

 

Conclusion:

As the banks innovate to remain relevant for their clients as a treasury bank, low cost full featured multi banking support using host to host connectivity framework offers a compelling idea which will continue to prevail for some time to come.

 

TagsPaymentsTransaction banking

Comments: (0)

Comment on this story (membership required)
Log in to receive notifications when someone posts a comment

Latest posts from Ganesh

Creating A Supply Chain Aware Payments Platform

13 January 2014  |  2280 views  |  0  |  Recommends 0 TagsPaymentsTransaction banking

Centralized Payment Exception Management

04 January 2014  |  1703 views  |  0  |  Recommends 0 TagsPaymentsTransaction banking

Multi Banking - Domestic Environment

02 January 2014  |  1780 views  |  0  |  Recommends 0 TagsPaymentsTransaction banking

Partner Finance - Syndication in SCF

02 January 2014  |  2694 views  |  0  |  Recommends 0 TagsWholesale bankingTransaction banking

Creating Revenue from Corporate Payments Decision Support

02 January 2014  |  2015 views  |  0  |  Recommends 0 TagsPaymentsTransaction banking
name

Ganesh Guruvayur

job title

VP, Head, Hub Solutions

company name

Polaris Software Lab Ltd

member since

2014

location

New Jersey

Summary profile See full profile »

Ganesh's expertise

What Ganesh reads
Ganesh writes about

Who is commenting on Ganesh's posts