Treasurers dealing with multiple jurisdictions, scattered banking landscape, and local requirements face many challenges in this regard. Japan is one of the markets where bank connectivity is indeed a challenge, especially when it comes to connecting with local banks.

Traditional options

The initial reaction from treasurers not familiar with local market conventions might be to seek connection through the SWIFT network. However, in Japan only a handful of banks offer SWIFT connectivity. Second natural choice is the Host-to-Host connection (H2H). This is the classic File Transfer Protocol (FTP), or preferably the secured version (sFTP) setup. Some will say old fashioned, rather than classic, since it is as old as the internet. Nonetheless, it is still popular, and frankly quite often the best fit for the purpose. However, if there are dozens of local banks to connect to, it can be difficult to be expected to connect to each of them with a direct H2H. While this could be technically feasible, it would be nothing short of a nightmare to maintain, with the initial setup being time-consuming in the first place.

Other solutions

There is an answer, or should we rather say ANSER, to this question. ANSER, an abbreviation of ‘Automatic answer Network System for Electrical Request’, is a data transfer system provided by NTT Data Corporation since 1981, which links banks with firms.[1] ANSER then is a way to connect a corporate client to the bank. The system has been around for a while, and together with Cash Management Service (CMS) centers it is a part of the so-called Firm Banking solution in Japan. Since its inception, ANSER offered a wider range of services, through which corporates could access their banking information. Among the offered channels are telephone, fax, firm banking terminal, and personal computer. With the ever-increasing need for speedy and accurate information exchange, the more traditional ways, such as telephone and fax, gave way to the more sophisticated and automated solution, namely eBAgent.

eBAgent making use of API

The said eBAgent is a proprietary middleware platform offered by NTT Data. The solution establishes an automated connection with banks through the above-mentioned ANSER network. In short, eBAgent offers a gateway to multiple local banking partners in Japan utilizing the ANSER network. The remaining part for the corporate is then to establish a connection between the TMS and eBAgent, and secure appropriate contracts with the eBAgent provider, NTT Data, as well as the banks.

As for the connection protocol, the choice is between the classic sFTP, or Application Programming Interface (API). The latter has the real-time advantage, with less lag between the pick-and-drop sFTP connection. API seems to be a choice for an increasing number of corporates these days in this area. What is also interesting, apart from the API connection, are the supported formats for transfers and bank statements. In addition to the local Japanese ZENGIN, the protocol also offers data transmission in a proprietary XML format. This XML format is actually quite simple, with a very limited amount of tags. In addition to this, unlike the ISO 20022 standard, it contains only one level of tags, without the nesting function. Depending on the exact ERP/TMS infrastructure, eBAgent can also provide conversion services from and to the IS 20022 standard. As for the connection to eBAgent, the whole setup seems easier said than done. However, some TMS providers, in response to the demand from the market, started offering off-the-shelf solutions for a plug-and-play connection to eBAgent. Kyriba and Reval already offer it, with SAP set to roll out its solution on the S/4HANA and Multi Bank Connectivity (MBC) platform in early 2024.

Various ways to connect TMS / ERP with banks in Japan

How to connect with local banks in Japan?

It all depends on the exact landscape of banks and systems. It may just as well turn out that a hybrid solution would be best suited. There is no one-size fits all, as each corporate is unique, thus careful consideration and design will be paramount for a stable and reliable connection with banks. One thing is certain, solutions that involve obtaining bank statement information and enact payments by telephone or fax are simply no longer sufficient. In this day and age, when much sensitive information is exchanged between corporates and banks, having a reliable, automated solution is indispensable.

If you would like to know more, do not hesitate to get in touch with Michal Zelazko via m.zelazko@zandersgroup.com or via + 81 (0) 8 3255 9966

[1] https://www.boj.or.jp/en/paym/outline/pay_boj/pss0305a.pdf

WPP has treasury operations on three continents and each center has its own individual needs. The company needed to devise a request for proposals (RFP) for implementing a new treasury management system (TMS) and Swift-based bank communication that would serve the diverse needs of each regional office. Zanders worked on this project from an early stage, helping WPP to write a cohesive RFP and providing objective advice at the selection stage.

The biggest marketing company in the world, with 2,400 offices and operations in 107 countries, WPP has four main treasury centers. With headquarters in London and three regional treasury centers in Brussels, New York, and Hong Kong, the requirements of each hub differed considerably. The process of writing an RFP that would meet, combine, and harmonize the needs across the London, Brussels, and New York treasury offices was the first conundrum.

An RFP to meet all TMS requirements

Zanders was involved in the RFP from the outset, having come through a consultant selection process. Paul Delaney, director of treasury at WPP’s London headquarters, says: “We felt Zanders were best qualified to help us in the project, and they had good feedback from other companies with similar requirements.”

It was Zanders’ task to become very familiar with the organization, processes, and system requirements of each of WPP’s three treasury centers, and they did this by visiting each office and spending three days assessing their needs. Three Zanders consultants were working on the project throughout: Thomas Pels, David Kelin, and Laurens Tijdhof, all of whom worked with the treasury staff at WPP to write up an RFP that would set the company on its way to selecting a new TMS. “It was a joint effort between WPP and ourselves to make sure that we went into great detail and got all the questions we needed for the RFP,” explains Thomas Pels, of the Zanders’ Brussels office.

We felt it was important to bring in an independent view partly because, as a treasury department, we aren’t necessarily up-to-date with the changes in TMSs and aren’t best-placed to make an objective assessment of what best suits our needs.

Paul Delaney, Director of Treasury at WPP.

Paul Delaney believes that bringing Zanders on board was the right way to manage the project. “We felt it was important to bring in an independent view partly because, as a treasury department, we aren’t necessarily up-to-date with the changes in TMSs and aren’t best-placed to make an objective assessment of what best suits our needs,” he says. This is an opinion echoed in each of WPP’s treasury offices. David Hughes, WPP’s director of treasury operations in New York, points out that Zanders facilitated the RFP process between the three offices: “That is something I think we would have had a really hard time doing if we didn’t have Zanders – they were able to take an objective point of view.”

Three treasury centers – one global TMS

The most important requirement for the TMS from the London headquarters’ point of view was to have an updated reporting function, says Felicity Ronayne, UK treasury operations manager in WPP’s London office. “We wanted a system we could all use that was up-to-date, with really good report-writing features and a cash position worksheet that we could access across all regions.”

The heavy reliance on checks, zero-balancing, and WPP’s large number of US operating companies meant that the needs of the US office varied significantly from the offices in Europe. David Hughes notes: “We sometimes have over USD 100 million checks clearing in the morning, so one of our needs was for controlled check disbursement funding notification to be included in the workstation cash positioning. We also need to maintain a lot of inter-company schedules on the treasury workstation and another big difference is our reliance on zero-balancing from the operating company accounts to the main WPP account – in the US it is the basis of everything we do.”

The requirements for the Belgium office were slightly different. Veronique Freymann, European treasury manager at WPP’s Brussels office, notes: “The Belgium team manages more than 2000 accounts of the 750 entities in more than 15 countries. Furthermore, we manage the cash pools (zero-balancing, notional, and multi-currency), the group account structure, inter-company loans, and the group’s guarantees. For this, the possibility to have cash forecast information delivered via the web was one of the major requirements.”

Zanders managed to combine all the different regional requirements into one global RFP document. The RFP resulted in three potential TMS providers, but WPP finally chose IT2. The system is being implemented gradually across the headquarters and two regional centers. It is near completion in New York and Brussels, while implementation in the London office will begin with static data in Q4 2012.

Veronique Freymann says: “The implementation of IT2 is gradual – so we have started to upload data from bank statements, which enables us to use some tools already. We will start with the inter-company loans and it will be a step-by-step process.”

The TMS in the New York office will be fully functional by the first quarter of 2012, although they will be testing it and running parallel with it before then.

Choosing a Swift Service Bureau (SSB) provider

As well as playing an active part in the TMS selection, WPP’s Brussels office also led the process in selecting an SSB provider. David Kelin, director at Zanders’ London office, points out that the TMS selection and the choice of SSB provider were complementary projects. “When we were looking at the TMS, we also assessed WPP’s banking relationships and communications – we established early on that an SSB would be necessary and that Alliance Lite would not be sufficient for WPP’s needs.”

WPP eventually chose Swiss provider BBP to provide their Swift bank communication. The selection of the SSB was completed in August but it has not gone live yet. WPP’s Brussels office is currently transmitting data across to the new SSB system, and it will become effective before the end of 2011.

As with the TMS selection process, Zanders was instrumental in helping WPP to understand their needs for Swift and then choose the right product. “We are the end users, so we know what we want, but we don’t know what advantages one solution offers compared to others,” says Thierry Lenders, European treasury manager at WPP’s Brussels office.

It is expected that the SSB will bring significant benefits for the Brussels office. Veronique Freymann notes: “SwiftNet gives a single channel of communication between us and the banks, so it will be a lot easier for us.” For now, WPP is reserving judgment on whether the SSB will be needed in its other treasury centers. Paul Delaney says: “It was evident that we needed the SSB in Brussels, but it is not yet clear if we will get the same benefits from it in New York and London. We are watching what happens in Brussels closely and we’ll make a proper assessment once it’s fully installed there.”

Bringing the project to a happy conclusion

This has been a long and complex project. What began as a challenging RFP in 2010 then became the selection and implementation of a TMS and an SSB. The project is ongoing, and several months remain before both IT2 and the SSB are fully functional.

We were very impressed with the quality of the people at Zanders and the depth of their knowledge. Most of all, we really appreciate the fact that the same three Zanders consultants have seen the project through from beginning to end.

David Hughes, Director of Treasury Operations.

For more information on selecting a Treasury Management System or on the process of choosing a Swift Service Bureau provider, contact us.