Sony’s Global Treasury Transformation

Sony Group implemented the SAP S/4HANA Treasury system successfully around the world in 2020. This project is called METRO Project in Sony Group.


Sony decided to start Digital Transformation (DX) of global treasury functions by launching the METRO Project officially in May 2018 and completed it by October 2020, working remotely under the COVID-19 global pandemic.

One of the biggest achievements of this project is the automation of the FX trading process. It is impressive to see how Sony’s FX dealers can trade large volume of FX deals with banks efficiently and effectively within a few minutes by using SAP S/4HANA Treasury and SAP’s TPI (Trading Platform Integration) connecting automatically with 360T Trading platform.
In this article, Sony’s project management team and Zanders partners will explain about this project.

Power of creativity and technology

Sony strives to fulfil its purpose to “fill the world with emotion, through the power of creativity and technology”, under its corporate direction of “getting closer to people”. To evolve and grow further, Sony strives to provide innovative products and contents full of emotional experiences in order to enrich people’s lives through the power of technology, across its six business segments consist of Game & Network Services, Music, Pictures, Electronics Products & Solutions, Imaging & Sensing Solutions, and Financial Services.

New-generation technologies made it possible for Sony Group to improve the global treasury platforms such as Payment-On-Behalf Of (POBO), Zero Balance Accounts (ZBA) sweeping, and Internal cash-less payments, Internal FX and Money Market deals settled via In-House-Cash accounts.

To improve FX hedging process, Sony introduced cutting-edge technologies such as SAP S/4HANA Treasury, SAP’s TPI connecting automatically with 360T Trading platform, to achieve the end-to-end automation of FX trading process.

To improve banking connectivity, Sony adopted the most advanced generation of banking technologies such as SWIFT for Corporates and ISO 20022 standards to connect with global banks smoothly for payment requests and bank statements via SWIFT network, which makes it possible for Sony’s cash management teams to grasp the latest status of cash position in a timely manner, even when the employees are forced to work from home in a tele-commuting era under COVID-19.

Additionally, Sony has implemented SAP In-House-Cash (IHC) for its treasury centers as In-House-Banks to support Sony subsidiaries in each region.

Sony’s journey for global treasury transformation

Sony Group has been making impressive efforts in the field of finance and treasury for a long time. Since 2000, Sony Global Treasury Services Plc (SGTS UK) has been established and operated in the United Kingdom as a global treasury center for Sony Group. SGTS UK has been providing POBO, ZBA sweeping, Internal cash-less payments, Internal FX and MM deals settled via internal accounts for Sony Group companies based on in-house treasury system developed by the Sony IS team. Cash and FX risk management were centralized in SGTS UK.

As Sony’s business grew in various business segments globally, it was necessary and rational to centralize funds and foreign exchange risks into SGTS UK. Before 1999, each regional finance/treasury center had managed FX and cash management individually, so it was a significant improvement by centralizing into SGTS UK. SGTS UK was deemed to be one of the most advanced in-house-bank of its kind around the world.

In 2016, SGTS UK transferred cash management functions for group companies in the USA to Sony Capital Corporation (SCC), to strengthen access to the US capital market, and to enhance flexibility to any changes in laws and regulations in the USA.

We departed from single global treasury center model and transformed into three main treasury center models by standardizing, simplifying, and automating treasury operations across all the treasury centers.

Hiroyuki Ishiguro, General Manager of Sony Group Corporation HQ Finance

quote

Challenge

Decision to transform

In October 2017, Sony started a project planning to rebuild its global treasury management structures across the globe. By December 2017, after an RFP process among the shortlisted SAP consultants, Sony decided that Zanders would be the best SAP Treasury expert to advise and support in this project. Together with Zanders, Sony opted for SAP S/4HANA Treasury based on ‘Fit & Gap’ analysis.

In May 2018, Sony decided to start the METRO Project officially.

Mr. Hiroyuki Ishiguro, General Manager of Sony Group Corporation HQ Finance (‘SGC HQ Fin’), explains: “We decided to start DX in Sony’s global treasury operations, considering more diversified business segments in Sony Group, rapid changes of corporate treasury and banking activities in each region, innovations of financial technologies, and limitations of legacy treasury systems that could not so effectively support Sony’s group companies especially in the USA and Japan. We departed from single global treasury center model and transformed into three main treasury center models by standardizing, simplifying, and automating treasury operations across all the treasury centers.”

Mr. Ishiguro served as the project owner, led the project management team, and worked together with the project members from overseas based in eight countries. With the introduction of the METRO Project, Sony Group built a Treasury Management System (TMS) that supports all segments of the Sony Group’s business domain, excluding finance segment, providing treasury services for nearly 350 companies worldwide in Sony Group. The METRO Project was set in motion.

Technology risk

The legacy in-house systems had a technology risk, because it was developed with old programming languages and had been in operation since 2000.

Mr. Ishiguro also comments: “In the project planning phase, it was a challenge to justify the importance of METRO Project and to justify IT investment for TMS. Technology risk urged us to start the planning phase to kick off the METRO Project. Our previous legacy treasury systems were in-house systems developed long time ago. The technology risk would be a real risk at the end of December 2020, so we needed to take urgent action to transform the existing legacy systems into a new TMS. We needed to have a very solid and stable TMS to manage the cash management and FX risk management for Sony’s global businesses. This meant a large scale of IT investment.”


Solution

Choosing SAP and Zanders

Sony decided to choose SAP S/4HANA Treasury, as the “best” TMS fitting well with Sony’s requirements based on the FIT & GAP analysis.

Mr. Takehiro Yagi, Senior Project Manager of SGC HQ Fin, explains why: “We performed a fit-gap analysis on various options, including ERP type treasury systems like SAP, treasury-specialized TMS, and an inhouse developments. Zanders gave us a lot of valuable insights into each TMS at the FIT&GAP analysis. SAP S/4HANA Treasury was chosen as the best fit for Sony’s Treasury as a result. SAP S/4 HANA Treasury would ‘FIT’ with most of our requirements to cover Sony’s global treasury services with multiple treasury centers model. SAP had flexibility to achieve Sony’s unique requirements with custom enhancements. Furthermore, SAP S/4HANA Treasury could achieve integration with accounting systems effectively, because a lot of Sony group companies have been using SAP as an accounting platform.”

The most important condition was to choose SAP Treasury experts who have deep knowledge and wide experiences in global implementation of SAP S/4 HANA Treasury for both TRM and IHC modules for regional treasury centers. Zanders won the RFP process in a shortlist of world-famous SAP partner companies. As a result, Sony decided to select Zanders as the SAP implementation partner.

Sony faced serious shortage of SAP Treasury experts. In fact, the lack of SAP experts was one of the biggest challenges for METRO Project. It caused significant delays from the original master schedule, and it caused quality issues from the lack of knowledge and expertise in SAP Treasury. The close collaboration between Sony and Zanders proved to be a key success factor of the METRO Project.

Mr. Ishiguro adds: “As of 2017, there were only few experts in Japan who could develop SAP Treasury related modules in global implementation projects. We evaluated several global consulting firms and analyzed their proposals and considered if they can deliver what we wanted to achieve. However, in many cases their proposals were limited to a general update. Zanders comprehensively understood our treasury requirements in each key operation area and provided appropriate and concrete proposals.”

SAP global implementation in two waves

Then the project started with the planning phase. Mr. Takaaki Miura, Finance Manager in SGC HQ Fin, explains: “In order to obtain official approval, we developed comprehensive project plans. To minimize any impacts to Sony group companies at the ‘Go-Live’, we decided to implement SAP Treasury in two waves, as recommended by Zanders. We started explaining our project plan and built good consensus across the major stakeholders within Sony Group HQ. ROI was the most important factor when discussing with the Sony’s management. METRO Project obtained the official approval from Sony management in May 2018.”

In February 2020, the SAP IHC module was implemented in Sony Group globally as Wave 1. In August 2020, the TRM module was implemented globally as Wave 2.

To finalize user requirements, all the key members gathered in Tokyo from around the world to discuss on a face-to-face basis. Project team also visited Sony IS teams in India to discuss business requirements directly and to resolve critical issues effectively in Wave 1. To kick-start User Acceptance Tests, the project team visited each office of treasury centers for deep-dive discussions and user trainings, also in Wave 1.

Mr. Ishiguro explains: “Wave 1 go-live was just before the COVID-19 global pandemic. Up to the Wave 1 implementation we could do all the work in face-to-face meetings in Tokyo, the Netherlands, USA, UK or India. So, we have accumulated our experiences by implementing Wave 1 on a face-to-face basis. The COVID-19 virus spread around the world, affecting Wave 2 of METRO Project. It was a tough time for us to proceed with all the preparation activities on a remote basis. But by making the best use of our comprehensive implementation experiences from Wave 1, we could successfully proceed with all the activities for Wave 2, even on a remote basis.”

Zanders gave us a lot of valuable insights into each TMS at the FIT&GAP analysis.

Takehiro Yagi, Senior Project Manager of Sony Group Corporation HQ Finance

quote

Performance

More sophisticated treasury operations

Now, Sony’s Treasury team is looking back with satisfaction on the project.

Mr. Yagi explains: “Now, we have visibility into global treasury activities from all regions, which is a real improvement. The treasury management system, METRO, was implemented as our global treasury platform with sophisticated technologies, greatly improved from the previous legacy in-house TMS systems. Our project members gained huge insights and experiences during the project, by working closely together with the Zanders team, all the partner banks, our IT teams and all the treasury members. That proved to be significant contributions to the development of human resources who can globally promote DX projects in the finance and treasury fields, which will continue to be needed in the future.”

Mr. Ishiguro agrees: “It is very important for both finance/treasury members and IT members to collaborate closely. It is also very important to promote young and mid-career employees actively, to provide opportunities for good trainings and for good ‘learning’ by direct and active participation to the project tasks.”

Mr. Miura adds: “One of the benefits of implementing METRO is that we can operate straight-through-processing (STP) in the FX trading process. Previously a lot of manual inputs needed to execute an FX trade with a bank, here and there, for the same deal. Now FX dealers can execute FX deals with banks who quoted best price effectively in a fully automated manner. We experience the improvements every day.”

Mr. Yagi agrees: “Our new SAP S/4HANA Treasury is much more advanced than our previous legacy treasury systems. SAP is much faster, more transparent and designed more effectively and efficiently, fully automated in various operations. Our previous application did not have any payment functionalities, so we had to enter payments separately manually into a separate E-banking system. SAP makes payment runs automatically, with timely status update of payment files. We have fewer issues or errors in METRO, all operations are run in a transparent manner, which prevents from fraud and other risks. The treasury system makes it possible to disclose financial information quickly to Sony management, the external auditor or investors if necessary.”

Mr. Ishiguro: “I strongly feel that we have been enjoying benefits of standardized treasury operations across regional treasury centers after the implementation of SAP Treasury. All three main treasury centers – in Japan, USA and UK – have been using the same treasury platform, and achieved a very good and stable operation, from various perspectives.”

A unique project

Apart from the pandemic restrictions, several elements made this project unique.

Firstly, the METRO Project was the first global IT system implementation project involving all business segments (except the Financial Services segment) of Sony Group. The project was unique because both Wave 1 and Wave 2 went live in a Big-Bang go-live approach around the world.

Secondly, it is unique because it was a ‘GLOBAL’ treasury transformation project with project members from eight countries. Treasury teams were in Tokyo, Singapore, Malaysia, UK, Poland and USA, and IT teams were in Bangalore, India, and the Zanders team was mainly in the Netherlands. As a result, the members of various nationalities have established a truly global project structure in which each project member was in charge of each task across the countries.

Ms Laura Koekkoek, partner at Zanders: “That global approach of this project, in which all regions and their personnel were combined, was really unique. And the whole collaboration between the different regions was really successful.”

Zanders partner, Ms Judith van Paassen adds: “The old systems already had the ambition of best practices processes in them but contained a technology risk. Now that there is a system to fully centralize, standardize and automate all processes is a big achievement.”

Mr. Ishiguro: “Whenever we discuss with Zanders, I remember we had very useful information available on key items, sometimes to deliver to the Sony senior management, or sometimes to resolve critical issues with a reasonable and solid solution, so we were able to proceed with the project with deep insights from SAP treasury experts.”

Next steps: From its new stable treasury basis, Sony's treasury is now ready for further steps for the future. In 2021, the system will be rolled out to Sony Group Corporation in Tokyo. Mr. Ishiguro lastly adds: “SAP S/4 HANA Treasury proved to be a very good TMS application for us. We would like to promote DX further, with close collaborations across our own Treasury members in each treasury center and our own SAP IT members, taking advantage of our experiences cultivated through METRO Project, in line with the mission of Sony Group Corporation, to ’lead and support the evolution of business through people and technology’."

Customer successes

View all Insights

Three major benefits of S/4 HANA Bank Account Management

September 2021
3 min read

With house bank accounts treated as master data instead of configuration objects including the latest enhancement, the bank account subledger concept, SAP S/4HANA Bank Account Management (BAM) aims to shift responsibility of bank account management life cycle from the technical teams to the cash and banking teams.


Bank accounts can now be created and maintained by the cash and banking responsible team, giving them more control over the timing of opening or closing of an account as well as expediting the overall process and limiting the number of users involved in the maintenance of the accounts.

Figure 1 – Launchpad BankApplications

The advantages of using the full version of BAM are multiple, but below we highlight three of the main reasons full BAM is a must have for the companies using one or multiple SAP environments.

Flexible workflows

Maintenance of bank account data can trigger workflows based on the organization’s requirements and the approval processes in place. With the workflows the segregation of duties can be enforced when maintaining a bank account.

Even though workflows are not a new functionality in S/4HANA, the fact that workflow templates are available and can be amended by defining preconditions, step sequences and recipients improves the approval process of bank accounts.

The workflows can be created and activated as completely new ones or based on the already existing templates . You can create a new workflow by copying an existing one and updating the parameters according to the new requirements.

All the requests to release or approve bank account changes are available as of S/4HANA 2020 in the My Inbox for Bank Accounts app, the dedicated inbox app where users can check the status of each request initiated by the users themselves or sent to them and act upon.

Easy data replication

One of the challenges multiple organizations have, especially those operating various SAP environments, is data synchronization and replication. We often come across situations when banks, house banks and bank accounts are not maintained in all relevant environments creating data inconsistencies and making processes more difficult than they already are.

One of the ways of avoiding these types of situations is by replicating banks, house banks and bank accounts from production to quality assurance and to development environments using standard Idocs.

Figure 2 – Bank data replication in S/4 HANA

If the organization is operating on multiple SAP and non-SAP instances and running processes in a S/4 HANA side-car solution, the challenge of maintaining banks, house banks and bank accounts grows exponentially. Distributing the data via Idocs will not only keep all the systems coordinated, it will also decrease the amount of manual work and avoid situations when processes fail because of delays in keeping the data up to date in all relevant environments.

Figure 3 -Bank data replication across multiple environments

Simple way of managing cash pools

Cash pooling structures can easily be set up by the user and in this way the BAM solution is integrated with the process of making cash management transfers.

Even though the cash pooling and cash concentration in S/4HANA are managed using five different apps (shown in the figure below), the actual structure of the cash pool is defined directly in the Manage Bank Accounts app (Cash Pool tab).

Figure 4 – Five apps to manage cash pooling and cash concentration in S/4HANA

In the Cash Pool tab, the user can define the cash pool structure as per each company’s requirements. It is important to keep in mind the fact that a bank account can be assigned only to two different cash pools: once as the header account of a cash pool, and once in a different cash pool, as a subaccount.

The cash pools created in the system are not restricted to one company code but can be defined using various currency accounts belonging to multiple company codes. For each of the bank accounts included in a cash pool, a target balance as well as a minimum transfer amount can be defined in the Cash Pool tab of the Manage Bank Accounts app, with the mention that both (target balance as well as minimum transfer amounts) must be defined in the bank account currency.

During the cash concentration process, when bank transfers are generated, the payment methods defined in this tab will be picked up. Therefore, if required, two different payment methods can be assigned; the first for the structure where the bank account is acting as a header account and the second for the one where the account in scope is a subaccount. To pick them up from the drop-down list, the assigned payment methods must be initially setup in the system.

To conclude

Maintaining banks, house banks and bank accounts can be a difficult task especially in large organizations operating with different SAP and non-SAP environments. It can be time-consuming; it can involve multiple people from different parts of the organization (IT, master data, cash and banking etc.) and it can easily be prone to errors and mismatches if not correctly maintained and synchronized. Having one single source of truth for the bank accounts – which is easy to maintain, user-friendly, with appropriate controls in place and reporting capabilities, easy to replicate the data across different environments and which allows the user to create and maintain not only the bank accounts but also the cash pool structures – can save time, resources and simplify processes.

Corrections and reversals in SAP Treasury

December 2020
3 min read

With house bank accounts treated as master data instead of configuration objects including the latest enhancement, the bank account subledger concept, SAP S/4HANA Bank Account Management (BAM) aims to shift responsibility of bank account management life cycle from the technical teams to the cash and banking teams.


As part of an SAP Treasury system implementation or enhancement, we review existing business processes, define bottlenecks and issues, and propose (further) enhancements. Once we have applied these enhancements in your SAP system, we create a series of trainings and user manuals which layout the business process actions needed to correctly use the system.

“It’s only those who do nothing that make no mistakes, I suppose”

Joseph Conrad

quote

This legendary saying of Joseph Conrad is still very valid today, as everyone makes mistakes. Therefore, we help our clients define smooth, seamless and futureproof processes which consider the possibility of mistakes or requirements for correction, and include actions to correct them.

Some common reasons why treasury payments require corrections are:

  • No need for a cash management transfer between house bank anymore
  • Incorrect house/beneficiary bank details were chosen
  • Wrong currency / amount / value date / payment details
  • Incorrect payment method

One of our practices is to first define a flowchart structure in form of decision tree, where each node represents either a treasury process (e.g. bank-to-bank transfer, FX deal, MM deal, Securities etc.), a transaction status in SAP, or an outcome which represents a solution scenario.

We must therefore identify the scope of the manual process, which depends on the complexity of the business case. At each stage of the transaction life cycle, we must identify whether it may be stuck and how it can be rectified or reversed.

Each scenario will bring a different set of t-codes to be used in SAP, and a different number of objects to be touched.

Below is an example of a bank-to-bank cash management transfer which is to be cancelled in SAP.

Figure 1: Bank-to-bank payment reversal

Scenario 2: A single payment request created via t-code FRFT_B and an automatic payment run is executed (F111), BCM is used but the payment batching (FBPM1) is not yet executed.

Step 1: define the accounting document to be reversed

T-code F111, choose the payment run created (one of the options) -> go to Menu -> Edit -> Payments -> Display log (display list) -> note the document number posted in the payment run.

Step 2: Reverse the payment document

T-code FB08: Enter the document number defined in step 1, choose company code, fiscal year and reversal reason, and click POST/SAVE.

SAP creates the corresponding offsetting accounting document.

Step 3: Reverse clearing of the payment request

T-code F8BW: Enter the document number defined in step 1, choose company code, fiscal year and click EXECUTE

The result is the payment request is uncleared.

Step 4: Reverse the payment request

T-code F8BV: enter the payment request (taken from FTFR_B or F111 or F8BT) and press REVERSE.

This step will reverse the payment request itself. Also, you may skip this step if you tick “Mark for cancellation” in STEP 3.

Step 5: Optional step, depending on the client setup of OBPM4 (selection variants)

Delete entries in tables: REGUVM and REGUHM. This is required to disable FBPM1 payment batching in SAP BCM for the payment run which is cancelled. The execution of this step depends on the client setup.

Call functional module (SE37): FIBL_PAYMENT_RUN_MERGE_DELETE with:

  • I_LAUFD : Date of the payment run as in F111
  • I_LAUFI : Identification of the payment run as in F111
  • I_XVORL : empty/blank

The number of nodes and branches comprising the decision tree may vary based on the business case of a client. Multiple correctional actions may also be possible, meaning there is no unique set of the correctional steps applicable for all the corporates.

If you interested in a review of your SAP Treasury processes, their possible enhancements and the corresponding business user manuals, please feel free to reach out to us. We are here to support you!

Managing Virtual Accounts using SAP In-House Cash

December 2020
4 min read

How to setup virtual accounts in SAP, part III. In the previous part of this series on ‘How to setup virtual accounts in SAP’, we delved into the details of a scenario where virtual accounts are managed on GL account level using SAP FI module only. This article investigates how SAP In-house cash (SAP IHC) module can be used to manage virtual accounts in your ERP.


SAP IHC is a module that facilitates a full suite of payment factory processes. It can be seen as an intercompany position subledger with a set of fancy features like POBO payment routing, bank statement allocation, arms-length intercompany interest calculations, out of the box payment and bank statement interfaces with participants (Opco’s) etcetera.

The process where virtual accounts are managed in IHC is depicted below:

In this process, we rely on a simple set of building blocks:

  • In-house cash accounts to manage intercompany positions between Treasury and OpCo’s,
  • GL accounts to represent external cash and the IC positions.
  • Processing of external bank statements,
  • Distribution of internal bank statements from IHC towards the OpCo’s ERP system,
  • On the external bank statement for the Master Account, an identifier needs to be available that conveys to which virtual account the actual collection was originally credited. This identifier ultimately tells us which OpCo these funds originally belongs to and which IHC account to credit.

The idea here is that Treasury will receive the external bank statement and automatically post the receipts into the correct IHC account using the identifier. By posting items on the IHC account, the intercompany positions are updated. Then, at the end of the day, a set of internal bank statements is generated in IHC and sent through an interface to the OpCo’s ERP. The OpCo’s ERP processes these statements, clears out the customers invoices and updates the IC position with treasury.

The two major benefits of using IHC over the solution as described in the previous articles of this series are:

  1. The OpCo’s do not require any direct integration with the bank and can rely on internal interfacing with Treasury. Especially in companies with a fragmented ERP landscape this can become a valuable proposition.
  2. IHC can very aptly integrate virtual account management processes with internal netting payments, payments on behalf of (POBO) and payment in name of processes.

Implementing virtual accounts in SAP

In the explanation below we assume that the basic FI-CO settings for the company code a.o. are already in place. Also, it is by no means a complete inventory of all the settings that are required to get IHC up and running. It focusses more on the configurational parts that specifically cater for the VA requirements specifically.

Master data – general ledger accounts

Three sets of GL accounts need to be created: balance sheet accounts for the representation of the intercompany positions, one set for virtual account clearing purposes between the EBS and the IHC accounting process, and the GL account to represent the cash position with the external bank. These GL accounts need to be assigned to the appropriate company codes and can now be used to in the bank statement import process and the IHC accounting process.

In the Treasury entity we should create a single GL (per position currency) representing the IC position with all its OpCo’s because the granularity of IC position per OpCo is managed in the IHC subledger. This approach results in less of an increase of accounts in the chart of account.

Transaction code FS00

House bank maintenance bank account maintenance

In order to be able to process bank statements and generate GL postings in your SAP system, we need to maintain the house bank data first. A house bank entry comprises of the following information that needs to be maintained carefully:

  1. The house bank identifier: a 5-digit label that clearly identifies the bank branch.
  2. Bank country: The ISO country code where the bank branch is located.
  3. Bank key: The bank key is a separate bank identifier that contains information like SWIFT BIC, local routing code and address related data of your house bank.

Transaction code FI12

Secondly, under the house bank entry, the bank accounts can be created, including:

  1. The account identifier: a 5-digit label that clearly identifies the bank account.
  2. Bank account number and IBAN: This represents the bank account number as assigned to you by the bank.
  3. Currency: the currency of the bank account.
  4. G/L Account: the general ledger account that is going to be used to represent the balance sheet position on this bank account. Or the IC position with Treasury.

Transaction code FI12 in SAP ECC or NWBC in S/4 HANA

The idea here is that we maintain one house bank and bank account in the treasury company code that represents the Master account as held with your house bank. This house bank will have the G/L account assigned to it that represents the house banks external cash position.

In each of the OpCo’s company codes, we maintain one house bank and bank account that represents each of the IHC bank accounts as held with the treasury center. This house bank will have the G/L account assigned to it that represents the intercompany position with the Treasury entity.

Electronic bank statement settings

The electronic bank statement (EBS) settings will ensure that, based on the information present on the bank statement, SAP is capable of posting the items into the general or sub ledgers according to the requirements. There are a few steps in the configuration process that are important for this to work:

1) Posting rule construction

Posting rules construction starts with setting up Account symbols and assigning GL accounts to it. The idea here is to define at two account symbols, the first one to represent the external Cash position (BANK), and the second one for the virtual account clearing between IHC and EBS (VACLR)

A separate account symbol for customers is not required in SAP.

For the account symbol for BANK we do not assign a GL account number directly in the settings; instead we will assign a so-called mask by entering the value “+++++++++”. What this does in SAP is for every time the posting rule attempts to post to “BANK”, the GL account as assigned in the house bank account settings is used (FI12 or NWBC setting above).

For the account symbol VACLR we can assign a dedicated O/I clearing GL that is used to clear out the EBS posting against the IHC posting (more on that later). These GL accounts should have already been created in the first step (FS00).

Now that we have the account symbols prepared, we can start tying together these symbols into posting rules. We need to create 3 posting rules.

Posting rule 1 is going to debit the BANK symbol and it is going to credit VACLR symbol

Posting rule 2 is going to debit the BANK symbol and it is going to credit a BLANK symbol. The posting type however is going the be set to value 8 “Clear Credit Subledger Account”. What this setting is going to attempt is to clear out any open item sitting in the customer sub-ledger using algorithms. We will explain more on these algorithms below.

As you can imagine, posting rule 1 is applicable for the Treasury entity. Posting rule 2 is going to be used in the OpCo’s EBS process.

Transaction code OT83

2) Posting rule assignment

In the next step we can assign the posting rules to the so-called “Bank Transaction Codes” (or BTC’s like NTRF) that are typically observed in the body of the bank statements to identify the nature of the transactions.

To understand under which Bank Transaction Code these collections are reported on the statement, you typically need to carefully analyze some sample statement output or check with your bank’s implementation team for feedback.

Important to note here is to assign an algorithm to posting rule 2. This algorithm will attempt to search the payment notes of the bank statement for “reference numbers” which it can use to trace back the original customer invoice open item. Once SAP has identified the correct outstanding invoice, it can clear this one off and identify it as being paid.

If SAP is unsuccessful to automatically identify the open item, it can be manually post processed in FEBAN or FEB_BSPROC.

Transaction code OT83

3) Bank account assignment

In the last part, we can assign the posting rules assignments to the bank accounts. This way we can differentiate different rule assignments for different accounts if that is needed.

Transaction code OT83

4) Search strings

If the posting rule assignment needs more granularity than the level provided in step 2 above (on BTC level), we can setup search strings. Search strings can be configured to look at the payment notes section of the bank statement and find certain fixed text or patterns of text. Based on such search strings, we can then modify the posting behavior by for instance overruling the posting rule assignment as defined in step 2.

Whether this is required depends on the level of information that is provided by the bank in its bank statements.

Transaction code OTPM

Prepare IHC to parallel post certain bank statement items into IHC accounts

In IHC there are two ways to parallel post bank statement items into IHC accounts; as payment items or as payment orders.

This can be controlled by setting a specific function module on BTE2810. If we set function module “BKK_IHB_BASTA_IN_POST”, SAP will post an IHC payment item. If we assign “IHC_APPL_XBS_POST”, SAP will post an IHC payment order.

Additional information can be found in note 2370212.

In the subsequent part of the article we assume that we use the payment item logic.

Transaction BF42

IHC account determination from payment notes

In this section of the configuration we can determine which IHC account should be used to post the bank statement items towards using payment notes search strings.

For example, if the master account bank statement payment notes for VA collections for a particular VA contains a string “From VA 54353” and we know this belongs to IHC account “F4000EUR01”, we can setup a rule in this part of the configuration for that. This will ensure that all items on a bank statement containing this text string will get posted into IHC account F4000EUR01.

Maintenance view TBKKIHB1

Assign external BTC to posting category

Here we can identify the external banks BTC codes (NTRF, NCMZ a.o.) which are applicable for the VA movements to post into IHC. Secondly, we can identify with which posting category to post them into the IHC accounts.

Once we identified the BTC code related to our VA collections (e.g. NCMZ), we can link them to the correct posting categories here. You could use standard categories 90 (Balancing Ext. Acct (D)) for debits and 91 (Balancing Ext. Acct (C)) for credits.

Alternatively, you can setup and link your own custom posting categories here to more precisely control how our VA collections are posted into IHC. This is out of scope for this article though.

Importing and processing bank statements

We should now be in good shape to import our first statements. We could download them from our electronic banking platform. We could also be in a situation where we already receive them through some automated H2H interface or even through SWIFT. In any case, the statements need to be imported in SAP. This can be achieved through transaction code FF.5. The most important parameters to understand here are the following:

  1. File parameters: Here we define the filename and storage path where our statement is saved. We also need to define what format this file is going to be, i.e. MT940, CAMT.053 or one of the many other supported formats
  2. Posting Parameters: Here we can define whether the line items on the bank statements are going to be posted to general or sub-ledger.
  3. Algorithms: Here we need to set the range of customer invoice reference number (XBLNR) for the EBS Algorithm to search the payment notes for any such occurrence in a focused manner. If we would leave these fields empty, the algorithm would not work properly and would not find any open invoice for automatic clearing.

Once these parameters are maintained in the import variant, the system will start to load the statements and generate the required postings.

Transaction code FF.5 / FEBP

Display IHC account statement

Now that we successfully loaded an external bank statement, we can now check whether the items are posted into the IHC account. This can be done via transaction code F9K3. For each IHC account we can now look at the “Account Turnover” and observe all the VA collections that are posted on the account.

Transaction code F9K3

Prepare the IHC account for FINSTA statement distribution

We need to enable the distribution of internal IHC statements to the OpCo’s ERP on the IHC account master record. This can be achieved via F9K2. On the “Account Statement” tab we can adjust the statement format to “FINSTA” and dispatch type to “ALE” to ensure we are going to send FINSTA statements over an ALE connection. This would be the most common combination; other combinations can be configured and selected here as well.

Transaction code F9K2

Setting up ALE partner profiles

Finally, we can configure the system to determine to which system the FINSTA’s need to be send. This can be done in WE20, partner type GP (business partner).

Here we need to setup the outbound parameters for the FINSTA message type. An appropriate port needs to be selected that represents the ERP of the OpCo.

Transaction code WE20

Trigger the distribution of a FINSTA statement

Now that we have some transactions posted on the IHC account and the FINSTA settings enabled, we can trigger the system to send the FINSTA statements to the receiving ERP system. This can be done in F9N7.

Here we can select the correct IHC account and statement date and run the program to generate the FINSTA statement.

Once the finsta is generated and sent to the receiving ERP, it can be processed there via FEBP there.

Transaction code F9N7

Closing remarks

This is the third part of a series on how to set up virtual accounts in SAP. Please find below the other articles on this subject:

How to set up Intraday Bank Statement reporting in SAP

September 2020
9 min read

Intraday bank statement (IBS) reporting, a service that your house bank can provide your company, enables your cash manager to understand which debits and credits have cleared on your bank accounts throughout the current day. We explain how to implement it in SAP.


Intraday Bank Statements offers a cash manager additional insight in estimated closing balances of external bank accounts and therefore provides the information to manage the cash more tightly on the company’s bank accounts.

Compared to intraday bank statement reporting, end-of-day (EOD) bank statement reporting is only available the next calendar day. The information therefore always comes too late to be meaningful for cash management decisions – apart from providing an opening bank balance for the next day.

Business rationale behind IBS reporting

So, why would a Treasury typically start implementing IBS reporting in its cash management processes?

  1. Cash visibility: In general, IBS reporting will provide your cash management function an additional tool to improve cash visibility. Achieving cash visibility intrinsically might not be a goal of its own, but by achieving visibility, the cash manager now has information to make certain economically relevant decisions in certain situations.
  2. Managing cash: By creating cash visibility, we now have an opportunity to manage cash on our accounts in an intelligent way. In case we estimate a positive closing balance, we could decide to invest this surplus in, for example, a money market fund or overnight deposit to earn some return. In case of an expected deficit, we need to fund the account to ensure no EOD negative position happens. This can be achieved by transferring funds from another bank account (in same currency), swapping funds from another bank account (in different currency), or funding it from, for example, a facility drawdown.
  3. Reduced risk of delinquency: As we now implemented a process to increase control over our bank balances, we now have less chance of e.g. rejected payments due to insufficient available funds and therefore less chance of being delinquent on certain obligations to pay.
  4. Reduced requirements on overdraft facility: By reducing the chance of having insufficient funds on our account, the overdraft facility requirements can also be reduced.
  5. Timely clearing of open items: IBS can also be used to clear off open items throughout the day, as opposed to only rely on clearing from EOD statements. Benefit here is that KPI’s like days sales outstanding (DSO) will improve and that reconciliation effort is spread out more through time.

This article will now only focus on the cash management side; the IBS reconciliation process may be discussed another time. If you like to know more about bank reconciliation using intraday statements, feel free to reach out to us. We have a pre-developed solution that we can implement at your side.

IBS concepts

There are a few design considerations that need to be looked at before attempting to implementing this solution in SAP.

  1. Reporting formats: MT942, CAMT.052, BAI2 are formats that can be imported by SAP standard and are also supported by most banks to some degree. There may be some informational or structural benefits that one format has over the other which should be considered in the design.
  2. Reporting frequency: It is possible to agree with the bank on reporting frequencies of IBS. Ten times through working hours? Or one time only, half an hour before the payment cut-off time? In most cases, the bank will charge a fee for every statement it sends, so this should be considered in the design.
  3. Delta vs cumulative reporting: As it is possible for the bank to report multiple times a day, it is important to understand how the data is reported. There are two methodologies. In case of delta reporting, only new transactions are reported, relative to the previously distributed IBS. Alternatively, there is cumulative reporting, where all booked items are reported on the statement throughout the day. Delta reporting typically means that the data in your SAP system needs to be appended for every new IBS. Cumulative reporting means that every time you process an IBS in SAP, the data needs to be rebuilt completely.
  4. Data integration: The intraday data as provided by the bank needs to be integrated with already existing cash-relevant data to compile a proper reporting view of estimated closing balance for the day. This needs to happen in the cash management module of SAP (FF7* reports). The design of the structure of the cash management report should be carefully aligned with the liquidity structure (i.e. ZBA structure).
  5. Prevention of duplications: Integrating the intraday data with existing data should be designed with data duplication in mind. It is paramount that the data on the same cash movement is not counted twice from two sources and data duplication should always be prevented while designing the solution. For example, if we are not careful, a payment flow can be included in the report twice, once from the intraday statement when it is debited and once from the payment in transit GL in the SAP administration. This would result in a skewed estimated closing balance.

Ultimately, the goal here is to receive and upload intraday bank statements throughout the day and to load cash movement data into your SAP system. This cash-relevant data needs to be made visible through the cash management reports so that the cash manager can better estimate EOD balances and make intelligent decisions related to funding accounts or investing excess funds.

Setting up Intraday Bank Statement reporting in SAP

We will now go into detail on how to setup intraday statement reporting and assume that the basic FI-CO settings for e.g. the company code are already in place. We also assume that the EOD bank statement process has already been implemented. To learn how to set this up, please read this article on virtual accounts.

Cash Management

It is important to understand that intraday statement data is converted into so called ‘Memo Records’ once loaded in SAP. These memo records can be visualized in the cash management reports (FF7AN/FF7BN). We will now explain the necessary settings on the cash management report section to ensure that the intraday data can be made visible in these cash management reports.

Define planning levels

First, we need to define a planning level; a label that is assigned to all cash movements as reported on the intraday statement. The planning level is used to structure the data in the cash management reports.

The level is a two-digit label, freely definable. We set it to C1.

The sign we need to set to blank as cash movements reported on this level can be both positive and negative.

The source will be ‘BNK’. This ensures that this planning level is reported on both ‘cash position’ and ‘liquidity forecast’ in the FF7AN/FF7BN reports.

The descriptions are freely definable. We define it as ‘INTRADAY’.

Define planning types

A planning type is a label under which a ‘memo record’ is stored on the SAP database. A planning type is subsequently linked to a ‘planning level’ to ensure the underlying data can be visualized in the cash management reports.

First, we define the planning type label: we set it identical to the planning level; C1 and link it to planning level C1.

We need to define an archiving category. This defines the data retention period of the memo records. If the period is exceeded and the reorganization program is executed; the memo record data will be cleansed.

The auto-expiry option defines whether the memo record will expire automatically and becomes invisible in the cash management report output. This needs to be enabled. The idea here is that the intraday statement data will be superseded by the EOD statement data once this is loaded after midnight next calendar day. To ensure we do not double count identical cash movements from both sources, the intraday data needs to be expired.

Also, a number range and description need to be entered. No specific functional considerations are needed here.

Define grouping and maintain headers

A ‘grouping’ is a label that is used to structure the cash management report data in a meaningful manner for the user. The grouping can be selected in the cash management reports and is going to dictate how the data is shown to the user.

We will configure a grouping ‘CASHPOS’.

Maintain structure

Under the grouping we can now maintain the structure of the cash management data. For our report, we are including two components. The first component is the planning level., the second will be the GL account under which we record our bank account balances. This is the GL account we typically maintain in the house bank account data (table T012K, transaction FI13, NWBC).

For the first component we are going to add an entry as follows:

The grouping we set to ‘CASHPOS’.

The type we set to ‘E’ for planning level. Now we can define a planning level that is going to be relevant to our cash management report output.

We set the selection to C1 (our intraday planning level we defined earlier).

This setting will ensure all cash management data as stored under C1 planning level is going to be selected in the report output.

For the second component we are going to add an entry as follows:

The grouping we set to ‘CASHPOS’.

The type we set to ‘G’ for GL Account. Now we can define the bank GL account that is going to be relevant for our cash management report output.

The selection we are going to set to a GL account is saved in our bank account entry in table T012K.

This setting will ensure all cash management data as stored under the GL account and relevant for our bank account will be selected in the report output.

The combination of these two lines is going to ensure that we will only see the C1 data for our one bank account. We can add multiple lines to increase the scope of the reports output.

Importing and processing bank statements

We should now be in good shape to import our first intraday statements. We could download these statements from our electronic banking platform. Also, we could be in a situation where we already receive them through some automated H2H interface or even through SWIFT. In any case, the statements need to be imported in SAP. This can be achieved through e.g. transaction code FF.5. The most important parameters to understand here are the following:

  1. File parameters: Here we define the filename and storage path where our statement is saved. We also need to define what format this file is going to be; MT940, CAMT.053, or one of the many other supported formats
  2. Posting parameters: Here we can define whether the line items on the bank statements should be posted to general or sub-ledger. This section is not relevant for intraday statements, as SAP does not support GL postings and reconciliation from intraday statements out of the box.
  3. Cash management: This is the most important section, specifically for intraday statement processing. The fields and tick boxes control a few parameters:
  4. A/CM payment advice: This needs to be enabled to ensure that SAP creates the memo record data from the intraday statements.
  5. B/Summarization: This tick box controls whether a single memo record will be created for the whole delta balance as reported on the statement or for each reported debit and credit on the statement. If high volumes are expected, summarization can reduce the number of memo records and improve performance a bit. Obviously, it does reduce the data granularity.
  6. C/Planning type: Here we set the planning type under which the memo records are going to be recorded. In our sample we set this to C1.
  7. D/ Account balance: This needs to be set if we are loading intraday statements.
  8. Algorithms: Here we need to set the range of customer invoice reference number (XBLNR) for the electronic bank statement (EBS) algorithm, to search the payment notes for any such occurrence in a focussed manner. If we would leave these fields empty, the algorithm would not work properly and would not find any open invoice for automatic clearing. This section is not relevant for intraday statements as SAP does not support GL postings and reconciliation from intraday statements out of the box.

Once these parameters are maintained in the import variant, the system will start to load the statements and generate the required postings.

Transaction code: FF.5

Now we can check if the memo records are updated in table FDES.

Subsequently, we can check the FF7BN report for grouping ‘CASHPOS’ and observe the output.

FMO: prepared for expectations and estimates

International Financial Reporting Standard 9 (IFRS 9), introduced by the IASB in 2014 as the successor to IAS 39, became mandatory on January 1, 2018, affecting nearly all processes and systems, according to Paul Buijze of FMO, the Dutch development bank. How is this unique bank preparing for the change?


Since 1970, FMO has been investing in the private sector of developing countries and upcoming markets. It does this in sectors in which it believes the long-term impact will be the greatest: financial institutions, energy and agricultural sector. With regard to lending, FMO applies a number of criteria. Is the initiative bankable? Does it contribute to a better world? Is it dependent on FMO or can another bank do it as well?

IFRS 9 concerns a number of new accounting requirements for financial instruments and contains three pillars: classification and measurement of financial instruments, provision for possible credit losses on financial assets (impairment) and hedge accounting. The adjustments within the organization fall under the responsibility of the financial division, which is Buijze’s department. “As far as hedge accounting is concerned, the impact is not so relevant for us, but definitely for the other two,” says Buijze. For example, the rules require the bank to look at expected loan losses differently, including taking into account macroeconomic scenarios.


Auditable and executable

During the credit crunch, banks found that the value of assets or liabilities entered on the balance sheet were often too low. In addition, there was also a delay in adjusting the value in response to market developments. The idea that the value of assets or liabilities should reflect the market more closely only seems logical. The question, however, is whether this regulation will achieve this. “It probably will,” thinks Buijze. “But since it arose from a political discussion, it makes it that much more complex. In order to get a grasp on this complexity, we have appointed an external manager to this project. It affects every part of our organization and is a lot of work to not only process it through all the procedures, systems and reports, but also to make sure it is preserved.”

In 2015, FMO began to prepare at a relatively early stage. “That’s why we were able to take all the necessary steps in a constructive way,” explains Buijze. “That process started with the question: what exactly is IFRS 9 and what are we actually facing? After that we needed to verify which elements were already in place. The probability of default (PD), or the probability that a company will go bankrupt, was something we already had a good idea about. As well as the loss given default (LGD), which is loss through default. You need to build your entire framework on these basic elements. IFRS 9 requires a calculation of expected loss (EL) in the next 12 months. However, if the client’s creditworthiness deteriorates, you are responsible for the EL over the entire life cycle of that credit. But what does ‘deteriorate’ actually mean? Such things must be clear; it’s important that it’s auditable and executable.” That raises the question of how one determines the creditworthiness of a local bank in Zimbabwe, for example. No ratings exist for such a bank. Buijze says: “We do that with all the specialists here, through a ranking of the entire portfolio based on the estimated risks. So it’s a relative rating which we subsequently ‘map out’ from the well-known rating scores of Moody’s and Standard & Poor’s.”


Portfolio diversity

Compared with the Basel guidelines, IFRS 9 requires more a point in time, according to Martijn de Groot, director at Zanders. “We had to take a number of measures, especially when using the existing PDs as proof for IFRS 9. Nothing too major, but it must be well founded to obtain approval from the auditor and to be able to take part in the process.” Buijze nods in agreement, saying: “You have to thoroughly explain why certain decisions were made. A lot of banks have very specific problems. As a bank, we can’t do a lot of back testing because we have relatively few clients, and luckily we don’t lose many. To show the expected loss with only historical figures is difficult. You must also substantiate your findings theoretically.” FMO’s portfolio is much smaller but more diverse than that of the average bank. The balance sheet total exceeds €8 billion, with loans amounting to over €4 billion. However, this is distributed among approximately 700 clients in 80 countries.

“There are countries with a high-risk rating, where we’ve never lost a cent, although the expected loss is higher than zero,” explains Buijze. FMO’s expansive agriculture sector does have some consequences. De Groot says: “It means that you have to find a solution for everything for IFRS 9. Because the portfolio is so diverse, so are the effects. A life cycle or credit cycle needs to be modeled, but the FMO credit cycle, based on the total balance, is muted, less volatile, due to the diversity.”


Classification

In the world of FMO, modeling quickly results in highly theoretical levels, says Buijze. “There are no trustworthy figures from a lot of the countries in which we do business. How do you determine the credit cycle in Ukraine, for example? In any case, we try to find the balance: while complying with the standards of IFRS 9, we don’t want to fall into something which appears great in theory, but hardly relates to what’s happening in a country.” All financial instruments must be classified according to the IFRS 9 guidelines. On the liabilities side, there is no impact for FMO but there are implications for the bank’s financial assets. Buijze explains: “We have to separately determine the classification for each loan.” This classification means that loans are entered at cost price or at market value on the balance sheet. However, the market value decreases as the repayment capacity decreases. Because there is also an interest component, in addition to a credit component, the market value is more complex. “Luckily we haven’t needed to price that many loans at market value. We work with normal loans, mezzanine loans and private equity. And for the latter, very different rules apply.”


Fluctuations

One of the most miraculous things about IFRS 9, according to Buijze, is that you are obliged to make a choice for private equity investments. “Either everything goes through the balance sheet, so you never see anything in your profit and loss account (P&L), with the exception of paid dividends, even if you sell the investment at a nice profit, or everything goes through the P&L. That leads to some uncertainty, because valuations can fluctuate and are not always as accurate as possible. Consequently, you get huge fluctuations in your income statement. We finance
almost no listed companies, and should therefore, in valuation, mainly look at theoretical values based on what other companies are doing. If we finance a bank and all banks in that region are assessed at a lower value, then we will also asses the bank at a lower value. During the crisis, the large Dutch banks significantly decreased in value, while we were actually doing quite well. If FMO was valuated in the same way as ING at the time… Therefore, it is an approach, but it’s not spot-on. And that’s all because of your P&L.”


De Groot believes there’s something else involved: “The bulk of private equity isn’t in euros, which means that currency volatility also has an effect on the balance sheet value, which in turn is in euros. Previously, that result only went through selling by the P&L, meaning if it were actually realized. Under IFRS 9, it either never goes through the P&L, or every period your unrealized result also goes through the P&L.” In fact, this all means a higher volatility on the P&L.

That will apply to a lot of banks, but with us, it’s even more extreme because we have a relatively large portfolio in private equity.

Paul Buijze of FMO

quote

FMO has chosen to have put everything go through the P&L. “That was a difficult decision, but it involves almost a third of our activity;, so for reasons of transparency, this was too much not to include in the P&L.”


A glance at 2025

Finance is ultimately the most involved department in implementing the new reporting standards. “Zanders had the ‘spider-in-the-web’ job,” says Buijze. “They brought together collaborators within the organization and developed a tool to calculate the credit facilities and market values of loans. This tool also implemented shadow calculations to get a better sense of the choices made for IFRS 9. What does this mean for the periodic numbers? This provides better insight and we can intervene if necessary. We prefer to have the tool in the system itself, but the systems don’t offer this at the moment. In the next three years, the tool must at least have a sufficient level to make our P&L, and be signed off by the auditor. And after that, we hope that our source systems will have the capacity to do this themselves.”

In recent years, FMO has grown both in size and profitability. “Through the years, we’ve had a lot of up-swings,” says Buijze. “Because of the dollar, but fortunately, also because developments in a large part of the world we work in are going so well.”

Customer successes

View all Insights

The hybrid role of Treasury at Boskalis

As a maritime multinational, Boskalis is involved in large scale projects all over the world. Due to the complexity of these projects, the Treasury department has a strategic role within the company and is a role model for other multinationals.


In the first hundred years of its existence, Boskalis was purely a dredging company. In 2010 the company – to give it its full name Royal Boskalis Westminster NV- acquired a number of other companies and, as a result, evolved from a dredging to maritime service company offering various services to different markets. Over the course of a few years, Boskalis acquired haulage company SMIT Internationale, Fairmount, Dockwise and the dredging business of the German Strabag Wasserbau.

Evolved according to needs

Boskalis has a huge project organization; the company operates in more than 90 countries across 6 continents. As a result of this expansion, the complexity of treasury work increased as well, due to various currencies, local bank accounts, financial structures and different ERP systems. “At a certain time they all have to be in sync,” says Frank Rousseau, Boskalis’ Group Treasurer. Treasury plays a remarkable hybrid role in it all: on the one hand as a ‘holding-treasury’ – namely in the area of corporate finance and everything concerning take-overs – and on the other hand closely involved with projects, mainly financial risk management. Rousseau: “Advising the Board and at the same time being close to the business locally means we play a very central role.”

Rousseau also thinks that the treasury function at Boskalis is special. His department now has 16 people who work on cash management, corporate finance, project financing, bank guarantees and credit risk management. “Our people are often directly involved with projects. The treasury organization has evolved according to the needs of the company. There is a need for strong financial and operational risk management and support for the business units, such as identifying and covering currency risks, credit risks and fuel price risks. At the time a contract is signed, all such risks have to be covered; when the project is underway you can’t intervene. Getting the order book filled is easy, but filling it with revenue-generating work is a bit harder. There is no advantage in taking on work and then doing it badly. Risk management is therefore very important in our business.”


Quick involvement

Large projects involve the whole treasury department in one way or another. “For example, take the
construction of a new arm of the Suez canal, so that shipping can safely navigate in both directions. From 2014 onwards this has been a large project and we had to contend with local bank accounts; Egyptian pounds, which have a currency risk; and managing credit risks, financial securities, bank guarantee structures and fuel price risks. These sorts of things can lead to fluctuations in returns and costs and therefore Treasury is involved at many levels, which makes it really fascinating.”

Our people are often directly involved with projects. The treasury organization has evolved according to the needs of the company.

Frank Rousseau, Group Treasurer at Boskalis

quote

1300 people in total work at Boskalis’ head office in Papendrecht, supporting the company’s large
international projects. The fleet, the pools with crew, the researchers and contractors are all managed centrally. Even the preparation and implementation of tenders is done centrally, by, amongst others,
Treasury, Legal and Tax. “We are involved from the moment potential work is on the horizon up to contract negotiations. But also when the order is under way, for example with payments, the management of cash”, Rousseau explains. Execution of such local projects has to be managed centrally. “We don’t have any local organizations that can develop the necessary competencies; when one project is finished the project organization moves on to the next one. After the Egyptian project, half of the people go on to the next project in, let’s say, Oman. It is, in a way, hit and run work. We only have locations in Amsterdam and Singapore that act as a permanent base for a region.”


Atradius cover

Rousseau’s treasury organization reports to the CFO. Besides administrative and secretarial support, there is a team of four who deal with the daily cash management. Five others handle credit risk management and bank guarantees. Another team of five handles corporate finance, project finance and project development. Customer finance falls under project finance. “Public-Private Co-operation (PPS) is quite labor-intensive: if you tender for a Dutch PPS, you have to do so with a complete financing package. There are international clients – those outside the OECD countries – who have a project, but lack the financing or don’t know exactly how to develop the project. For example, in Panama we had Punta Pacifica, where a client wanted to put two islands off the coast of Panama city. As the client had insufficient funding for this, Boskalis participated with local banks. We were therefore not only contractor/guarantor for the complete execution of the project as far as the financers were concerned, but we also financed a part of the contract value. Treasury tries to add value in order to bring in a project.”


Another example is arranging a loan for clients with Atradius cover. “We did that last year in Colombia,” Rousseau explains. “We arranged bank financing for the client where the bank received credit insurance from the Dutch Export Credit Agency, covered by the Ministry of Finance. Credit risk for the bank is effectively carried by to the Dutch government. This is only possible in combination with a Dutch export product. In this way we try to do more projects by contributing to the economic feasibility of a project. In addition, we are broadening our approach to project development: we are offering parties who have a project in mind the chance to develop this together with Boskalis and make a business plan that is then financeable.” Although this is not a typical Treasury activity at first sight, it fits in the strategic scope of Treasury’s role in Boskalis.


New direction for cash management

In 2014 RBS, an important international house bank to Boskalis, decided to stop offering cash management and trade finance services outside the UK. This forced Boskalis to change direction. Rousseau: “We had decided some time ago to take a close look at our cash management, but when RBS pulled out we were triggered into taking action. And we realized then, in spring 2015, that we needed external help.” That’s how the relationship with Zanders came about.

Zanders' added value was in visualizing solutions and thinking strategically about where we wanted to be as company. They helped us to make choices, and with the set up of the whole organization.

Frank Rousseau, Group Treasurer at Boskalis

quote

An important step was selecting a new bank for cash management services. Boskalis and Zanders issued an RfP and, via a short list and various analyses, we finally chose BNP Paribas for international cash management and ABN AMRO for Dutch cash management. At the same time, the cash management structure and the payment process were improved by implementing a bank-independent, central payment hub, which provided more insight into our cash flows. Rousseau: “We can now send a report of our net financial position to the Board every day: where is our money? We have drastically reduced the approximately 700 bank accounts we had and we now have structures abroad to better centralize our cash. Furthermore: we previously had payments from all sorts of different electronic banking systems. That too is now centralized in a standard solution.”


Asian prize

Parallel to these changes, Zanders supported Boskalis with an upgrade and outsourcing of the treasury management system (TMS). “We had three balls in the air at the same time,” says Rousseau. “It was a big strategic project, certainly for our Treasury. It has improved our bank account structure, the payment process and the information flow. Every morning we now receive all balances for about 500 bank accounts electronically via MT940. Our TMS then generates a report which gives the CFO and me insight into our net financial position. In the UK we have just set up a cash pool and we are doing the same in Germany. In our central cash pool we have 19 currencies. Last year we took over VBMS, the former offshore wind company of Volker Wessels, and this component has also been included in the new structure. In these type of processes, Treasury used to be a follower, but now we are leading. We tell the business unit how its cash management should be structured.”

This year Boskalis won a prize from The Asset, a well known Asian trade journal, for ‘Best Cash Management Solution in Asia.’ Rousseau: “In Singapore, one of the few places where we have a permanent base, we have set up a structure with target balancing, so that every day a limited amount remains in the account whilst surplus funds are automatically transferred to the central cash pool in the Netherlands. This solution has won a nice prize and sector-wide recognition.”


Future expectations

Which plans and developments does Rousseau foresee in the future? “We obviously look at where
we can make more improvements, but we have made great inroads over the past two years. For Treasury, support for the business units - the wider role in project finance and project development – is most important. We have a new 3 year business plan for 2017-2019, in which we show that we want to grow in dredging activities and offshore energy, the new components which we have had for several years and in which we expect high growth. As far as credit risk is concerned, we are keeping an eye on the oil and gas sector.” The Board of Directors is close to the organization and to its projects. This means that all departments have a short communication line with them. “They have insight into all projects’ financial risks and how we can cover them,” Rousseau explains. “The people we have here are really good professionals, who can handle derivatives. If you see what we have set up for our cash management and with which people we meet new challenges, then we really are ready for the future.”

Do you want to know more about risk management for corporations? If so, contact us.

Customer successes

View all Insights

State-of-the-art financial risk management at Türk Telekom

Türk Telekom, with 175 years of history, is the first integrated telecommunications company in Turkey. Due to its long-term foreign currency funding structure, Türk Telekom has significant foreign exchange exposures. This initial situation, as well as several other factors, led Türk Telekom Treasury to embark on a Financial Risk Management (FRM) Transformation Project, which recently received industry-wide recognition as well as an Adam Smith Award.


As the country’s ‘Quadruple Player’, Türk Telekom offers a complete range of mobile, fixed voice, broadband, and TV services. With the vision of introducing new technologies and accelerating Turkey’s transformation into a true ‘knowledge society’, it offers services to over 38 million subscribers. Türk Telekom provides the information technologies that drive sustainable economic growth and community development. By investing heavily in fiber and mobile networks, Türk Telecom provides people with access to knowledge that, due to economic, social or physical reasons, may otherwise not be a part of this community. As such, Türk Telekom is truly a leading company in Turkey. Türk Telecom split its ownership after its privatization in 2005 and initial public offering in 2008: 15% free float on the Borsa İstanbul, 55% owned by Oger Telecom, and 30% owned by Turkish Government.

The challenge

Türk Telekom is exposed to material foreign exchange exposures due to its sizeable long-term foreign currency funding portfolio, denominated primarily in EUR and USD. Due to insufficient long-term Turkish lira liquidity in the domestic debt market and the high Turkish lira interest cost, access to foreign currency denominated funding is essential for the company. However, this simultaneously exposes the company to foreign currency risk because adverse foreign currency movements inflate Türk Telekom’s debt position and interest expenses significantly. In turn, this detrimentally effects the company’s overall financial position, credit profile, and ability to raise future liquidity to fund its large CAPEX program. “Türk Telekom had established a number of internal mechanisms to manage foreign currency risk, but a formalized risk management policy was still missing,” says Salih Fatih Güneş, Director of Treasury, Türk Telekom.

This was the starting point to define the scope and objectives of the Financial Risk Management Transformation Project in collaboration with the Enterprise Risk Management department.


The project

Türk Telekom decided to embark on a FRM Transformation Project, with the ambitious goal to create an ‘integrated’ and ‘holistic’ solution across the various risk relevant categories: market risk, credit risk towards financial counterparties, and overall company liquidity risk.

Given the complexity and involvement of multiple stakeholders, Türk Telekom required a multistage approach, each with distinct pre-defined deliverables. Türk Telekom invited a limited number of consulting firms to respond to their request for proposal. Salih Fatih Güneş:” We specifically wanted to work with a consulting boutique specialized in treasury and risk management.” Zanders translated Türk Telekom’s requirements into the following tailored project approach.


Best practices and innovation

Türk Telekom Treasury received an Adam Smith Award as a highly commended winner in the Best Foreign Exchange Solution category. The award recognized the following best practices and innovations:

  • A holistic approach towards risk management incorporating different risk categories
  • Use of a sophisticated, state-of-the-art risk quantification tool
  • The incorporation of a risk decision-support tool in which long-term funding/rating criteria are the main drivers
  • Joint effort between Treasury function and the Enterprise Risk Management function
  • Adoption of a Monte Carlo simulation model

The solution

Zanders delivered a state-of-the-art risk quantification tool, tailor made to capture Türk Telekom’s ‘risk bearing capacity’ in relation to its financial profile. The tool captures financial position data, relevant market risk variables (FX, interest), and appropriate risk models, and incorporates further customized stress, scenario, and simulation tests, including an at risk methodology that uses Monte Carlo simulation. It provides Türk Telekom with 5-year, forward-looking management information, which Türk Telekom uses to decode signals of adverse events at an early stage through key risk indicators and management consults to proactively steer the company’s credit profile. Türk Telecom based the tool on the overall financial strength and risk bearing capacity of the company as the central metrics to set risk limits and bandwidths linked to the outcome of the calculated financial risks.

In addition, Türk Telekom drafted a new Group Financial Risk Management Policy. This policy incorporates strategic and operational guidelines for Türk Telekom’s Financial Risk Management activities and clearly describes the key FRM principles and objectives, steering both strategic and operational decision-making. The new policy clearly states primary and secondary risk management objectives, with liquidity risk the key risk that other risk categories align to and resulting actions derive from.

Developing a state-of-the-art holistic risk quantification model along with new treasury policies, procedures, strategy, and governance is quite unique. In theory, it may sound straightforward, but in practice it is quite difficult to deal with multiple interlinked financial risks in a holistic manner.

Salih Fatih Güneş, Director of Treasury, Türk Telekom.

quote

Next to the industry recognition and Adam Smith Award, the project also improved internal visibility and recognition of treasury’s added value by senior management and other corporate functions. Salih Fatih Güneş concludes: “We have achieved this project in close cooperation with our consulting partner Zanders. It added value with its outside-in views, knowledge of best practice and especially with its pragmatic approach to delivering a concept into a practical, tailor-made solution.”

Customer successes

View all Insights

Navigating Uncertainty: An Interview with Arjen Pasma (PGGM) on How Pension Funds Prepare for Financial Market Risk

As companies become more responsible for the funds of others, risk management is of greater importance, noted Arjen Pasma during the Zanders Risk Management Seminar. How does the CRO of PGGM Investments handle the risks for his organization and his clients?


How does a pension company prepare for the risks and uncertainties inherent in financial markets?

“One of the best ways to prepare is by practicing. The financial industry is actually poorly prepared for the unknown, and can even be surprised by something entirely uncertain. The leading economists at the beginning of the 20th century did not have the big data or computer power we have today, but this has grown enormously over time; we are now able to simulate, optimize, and much more. We are now so enslaved to data and models that we are under the illusion that we have everything under control. Lehman had the most advanced risk management system in the world and it still went bankrupt. The biggest problem with risks is that they concern matters that are actually already known to you. A risk is a measurable uncertainty, yet uncertainty is an immeasurable risk. So when you are struck by an uncertain event, all those models are utterly useless. And when that happens, we are left dumbfounded; we do not know how to act and we forget to communicate - the most poisonous cocktail for trust in the financial sector. We can learn a lot from other professional groups. Pilots, for example, are trained how to act in unexpected, unfamiliar situations. Financial models are our autopilot, but a pilot must also be able to fly the plane when unexpected circumstances occur that the autopilot is unable to handle.”

Was the scenario for the Brexit already known at PGGM

“The Brexit scenario was one of our top five priority risk scenarios. We regularly meet with all investors and economists within the organization to discuss these types of scenarios. Last year, we already had a Grexit scenario which we made even more specific this year to prepare for a possible Brexit. Calculating probabilities is at that point completely futile; you must accept that events are going to occur which you never could have predicted. We assumed that the consequences of a Brexit would initially result in volatility in the stock markets in particular, which can be simulated easily, but the greatest uncertainty was what influence Brexit would have on the rest of Europe. We had previously discussed this ‘butterfly effect’ at length. Of course, the question that also remained was how this will affect our wallets; moreover, we examined our UK and British pound exposure. Our exposure to the pound is covered for nearly all of our clients, but other currencies could well be affected. That is why we also looked at European banks in terms of counterparty risks and credit risks. As for our immediate investments, we mostly looked at the infrastructure projects, because for these you are highly dependent upon the British government – regulatory risk is one the biggest risks there.”

But how can you practice for something that is mostly uncertain?

“We practice with a financial crisis team (which includes the board of PGGM, ed.) that is unexpectedly confronted with an uncertain situation. This is how you learn what can go wrong in a situation. You cannot, of course, devise scenarios for the unknown, but you can practice how you generally handle of unexpected situations.”

Is maintaining buffers the only way to provide some sort of hedge against these uncertainties?

“Based on the Value-at-Risk approach, you must maintain a buffer for something that may occur once every 200 years. When you do get hit, you will have sufficient capital to survive any blow. But the greatest weakness here is that the probability calculation on which this is based is flawed. Nassim Nicholas Taleb also referred to this in his book The Black Swan. Many risk management systems work well, but only when the market circumstances are similar to what they are designed for.”

And what role does interest play in this?

“We have not taken additional measures for interest. The hedges for it are completely tied up in ALM (asset and liability management) for most funds. When you think in terms of financial returns, with the current negative interest situation, it is strange that interest risk must be covered. But seen from the perspective of the Financial Assessment Framework (FAF), hedging the interest risk is necessary because interest rate changes could have major effects on the value of the obligations.”

But when you invest against 0% interest, any pension company surely must know that it won’t achieve that right?

“The FAF is not designed with a very low interest in mind; that is undisputedly true. Many funds are now also suffering under the enormous increase in obligations, which is still mostly an accounting effect. Pension funds must achieve a return of well over 0%, and they normally do, but no investment returns can match the interest effect. The funds with the best cover ratio are those that have hedged their interest risk in time; not necessarily the funds with the best returns on their investment portfolio. I believe these developments will now also bring about the necessary changes in the pension system at a rapid tempo. I don’t have the ultimate answer, but I think it’s good that the discussion about the sustainability of our system with a vastly changing job market is now really gaining momentum.”

What does this mean as seen from a risk management perspective?

“As pension fund management, you have a dual problem. On one hand you have to deal with a FAF and a short term risk of becoming hedged - the reduction of rights. While on the other hand, for the average pension fund, the long term risk you won’t achieve your organization’s objectives is much more relevant. Investing in government bonds with a negative return is then incredibly risky. An average pension fund, with members that are generally not very old, should primarily focus on the long term.”

JP Morgan published a study in which the interest rate could possibly come out at minus 4.5%. What would you advise your clients in this case?

“That is an example of thinking in scenarios. Such economic scenarios are also included in our models these are partly deterministic and partly stochastic. They do assume a low interest - even a negative interest in the short term in certain scenarios, but not in the long term. What I noticed about interest scenarios in many ALM models is the speed at which mean reversion occurs: the return to a long term average. In the short term you can assume any number of things, but if the model for long term interest takes on 4% after 5 years, you can ask yourself - certainly these days - how realistic can this be?”

Does PGGM also employ swap options, for example, against such interest risks?

“We have in the past, but most clients are not keen to invest in swap options. They are not easy to explain and you pay a large premium. In addition, you also have counterparty risk and liquidity risk - it is unmanageable. Smaller funds have a much easier time hedging on the short term than larger funds.”

Is there not enough room on the market?

“Well, there are some insurance companies with equally large balance sheets that are able to hedge themselves. So it is possible, apparently. But you do see signs - the buy-back programs also don’t help here - that market liquidity is declining, certainly for long-term government paper. You can also do a lot with interest swaps, but the developments there, too, make for a difficult market due to, among other factors, EMIR and the capital requirements for the banks that we deal with. What’s more, derivatives are not at all popular in public opinion and are still being dismissed by the media as dangerous and speculative instruments. Pension funds have to deal with this, too. You work in a kind of glass house; everyone has an opinion about it. I don’t envy the average manager.”

During the seminar, you said that pension funds have relatively little to do with legislation. Should this change in future?

“No, you can compare it to banks and insurance companies. In principle, legislation is useful: it ensures a level playing field among the market parties and is meant to protect the participants.”

PGGM also invests in illiquid products. How does PGGM control the reputation risk of this?

“We have been investing in illiquid products for a very long time and this has brought great results for our clients. We currently invest approximately one quarter of the portfolio in illiquid assets - a relatively high percentage. This is comprised of private equity, infrastructure, private real estate, structured credit and the like. A drawback is that such assets are not immediately tradeable, but for a fund with a long investment horizon, that’s less relevant. The costs are normally higher, but even after these costs, the investments make a substantial contribution to overall returns. The great advantage of private investments is that we can directly influence them. We can exercise influence on the ESG (environmental, social & governance) profile, especially for projects where sustainability plays a role. You might even say that I know more about an average private equity investment than I do about an average investment in a quoted company which we also invest in. But due to this big influence, we also have to deal with reputation risk, because there are always some projects where something is wrong, such as a renter that has
gone bankrupt. Our strategy is to always explain precisely what we do and what our role is.”

In closing: given all the uncertainties, how can we improve the level of trust in the financial sector?

“It is crucial that we as a sector learn to deal with ambiguity better. Organizations should write a concrete risk appetite, where you accept that events are going occur that all of you together have not foreseen. And we should start practicing how to handle unexpected events, just like the pilot example cited earlier. We must also recognize that existing models and processes may not be of any help. In doing so, you will be more transparent and trustworthy in your (crisis) communication. Because after all, who is going to believe the man who claims to have everything under control under any and all circumstances right down to fifth decimal place?”

Customer successes

View all Insights

Canadian National Railway Company (CN): On the right track to payments harmonization

CN’s project focused on streamlining its banking relationships, improving payments and collections, and adopting global-standard formats to enhance efficiency, reduce costs, and align its treasury and IT departments on a shared vision for the future.


Canada’s largest railway set out to simplify its payments and improve reconciliation with enhanced remittance data, while also reducing IT support costs. The project will run parallel with the Canadian Payments Association’s (CPA’s) initiative to modernize the system and introduce ISO 20022 formats. So, following a thorough request for information (RFI) and request for proposal (RFP) process with the banks, the Canadian National Railway Company (CN) now has its future vision for bank connectivity and global-standard payments, as well as a multi-year roadmap to establish best practices.

‘North America’s Railroad’

CN operates approximately 20,000 route miles of transcontinental railroad from Vancouver in the west to Halifax in the east, and all the way down to New Orleans on America’s southern coast. Its market cap of US$43bn (C$57bn), as of February 2016, makes ‘North America’s Railroad’, as it’s known, the biggest rail company in Canada in terms of both network and value. The majority of business, consisting of freight, takes place in North America, but CN’s reach extends much further, with operations and transport services in Asia and South America.

The group treasury, centralized in Montreal, takes care of cash management functions and does all FX hedging and cash pooling with the two main operating currencies, Canadian dollar and US dollar. This business model meant that CN needed a bank with a strong presence in the US and Canada, as well as an international footprint. In 2015, therefore, the company started to look into streamlining its banking relationships.

European perspective on Canada

Zanders was asked to provide guidance on both the RFI and RFP phases of the bank selection process. The aim was to choose one or two relationship banks for domestic and global operations. Due to the specifics of the Canadian market, the company chose one bank for its North American operations and one for the rest of the world. Zanders was an active ‘sparring’ partner in this process and supported CN throughout the RFP, during the evaluation of responses, decision-making, and selection phases.

The vision

Paul Tawel, who was senior manager of treasury operations at CN during the RFI and RFP process, explains how the project began: “Our main goal was to get a vision of best practices in different areas of treasury, so it originally started as a ‘quest for knowledge’. On our side, we had a lot of good processes in place but we wanted to learn more about protocols for bank communication.”

The project group at CN went through a questioning process, looking at all outsourced services and how it communicated with its banks. While they recognized that many of the protocols in place were already working well, there were areas that could be improved. Tawel, who has now retired from CN, adds: “We really wanted an internal vision and we now have that – we have put in place a cross-functional task force, including treasury, accounting, procurement, marketing, and IT to implement the vision and roadmap that we have developed. We have a timeline of three years to put these changes into practice. There are separate plans for AP, collections, and treasury. On the payables side, the vision can be implemented quite quickly.”

The job is ongoing, and CN is currently drawing up an action plan for three areas: payments and collections, payment format harmonization, and bank connectivity.

World-class payments and collections

During the research phase, which took place in mid-2015, running alongside the bank RFI and RFP, it became apparent that there were areas of payments and collections that could be optimized. Cheques are still a mainstay of CN’s collections in both Canada and the US, representing 43 per cent and 62 per cent of collections volume, respectively. Meanwhile, on the payments side, there was far less reliance on cheques (seven per cent of volume of payments in Canada, 10 per cent in the US), although there was still an opportunity to reduce volumes. Another factor on the collections side was the wide variability of remittance data sent by customers. “We want to eliminate cheques as much as possible. However, in North America, they are part of the culture, and suppliers demand them. The right communications strategy will be a key part of successfully encouraging suppliers and customers to accept another digital payment,” says Tawel.

Another important consideration was the unique payments environment in Canada, explains Mark van Ommen, associate director at Zanders: “We had to take the nature of the Canadian payments system into account. One of the challenges is that they are still very much cheque-driven, mainly on the receivables side, so that is a big difference in the Canadian environment.”

CN’s overall vision for payments and collections is to rationalize payment/collection methods and reduce cheques in receivables, while also increasing the level of pre-authorized debits. On the outbound payables side, as well as further reducing cheque usage, it was decided to leverage SAP technology.

Formats harmonization

CN also wished to simplify the way it communicates transaction data with its banks. The company currently uses a large number of formats, some of which were customized, and this increases payment and IT costs. Moreover, the Canadian clearing system doesn’t permit payment messages to contain all the data necessary, so that separate files are required for remittance.

However, the Canadian Payments Association (CPA) has now launched an initiative to modernize Canada’s core payments infrastructure, gradually replacing multiple formats – often based on Electronic Data Interchange (EDI) formats – with the international ISO 20022 standard payment formats. The design phase of the initiative is expected to be completed by the end of 2016, but implementation will take several years. The CPA will also adopt Extended Remittance Information (ERI), which will enable the reconciliation of payment remittances to be automated, saving companies such as CN significant resources.

Despite the CPA’s initiative to introduce standardized XML payment formats by 2020, CN had to consider the best option in the current environment. They chose to adopt CGI payment formats that provide combined payment and remittance info, enabling more efficient reconciliation and less complexity from an IT point of view. Van Ommen adds: “We were able to provide advice based on our experience of European XML standardized payment formats. Although the non-standard payments environment in Canada is a challenge, the CPA is intent on bringing this in line with global standards.”

Bank connectivity

The multiple payment format types, along with the company’s multiple host-to-host interfaces with various e-banking systems, mean there is a raised cost in terms of IT support – the so-called ‘cost of ownership’. The more systems and types of format are used, the greater the cost of making any modification to each system. CN wanted more independence.

Zanders partner Judith van Paassen worked closely with CN on this issue. She explains that: “The ‘cost of ownership’ of maintaining the current multiple types of file formats and bank connectivity was too high. CN needed more standardization to reduce this cost and to ‘future-proof’ its treasury and payments operations. But first, treasury and IT needed to convince other departments that this would be both necessary and beneficial.”

The solution put forward in CN’s vision and roadmap was to simplify the systems landscape and number of interfaces. CN already had Swift’s Alliance Lite2.0 in place but this was only used for treasury payments and wires and, in any case, was unsuitable for the volume of commercial payments for a company of CN’s size.

Tawel explained that the aim is to adopt a standardized, bank-agnostic communication channel for all bank communications: “We want to leverage our Swift communication platform, but in future we may need a Swift Service Bureau. This will take time, and as we are already on Swift, we see it as primarily an IT project.”

A communication strategy was needed across the organization to get all departments aligned with the best practice identified by treasury and IT in the areas of bank connectivity and payment formats harmonization. Van Paassen adds: “We advised the treasury and IT teams to view this project as a long-term strategy. It was a challenge to get departments such as A/R and A/P to support this vision, but CN’s treasury succeeded.”

CN was vindicated in its long-term strategy for banking relationships, bank connectivity, and payment formats. It has already been able to reduce its banking fees significantly via the bank RFI and RFP phase and in future expects to improve security and simplify the process of making commercial payments.

Vision and roadmap

Having already selected two relationship banks and with its vision for future bank connectivity and payments firmly established, CN is now planning the initial steps along its roadmap, which will take it up to 2021. In early 2016, treasury began looking at document solution design and payment formats. Van Paassen says: “The challenge will be in the implementation, but we are confident that we helped treasury see the bigger picture, which will enable them to make the necessary changes.”

A factor that was vital to the project’s success was getting buy-in from several different teams. While some departments initially questioned the need for the proposed changes, they reached a consensus, helped by the objective, fact-based methodology used during the RFI and RFP phase and the bank communication standardization project. Irene Kwan, senior manager, treasury operations, at CN, said that at the end of the project, treasury’s vision was shared and supported across all departments. She says: “The project was well received in the company. Everyone was on board and everyone was clear about what we wanted to achieve. In my view, it would be really beneficial to carry out projects on best practices more frequently.”

Would you like to know more about bank connectivity or other treasury challenges? Contact us today.

Customer successes

View all Insights

Fintegral

is now part of Zanders

In a continued effort to ensure we offer our customers the very best in knowledge and skills, Zanders has acquired Fintegral.

Okay

RiskQuest

is now part of Zanders

In a continued effort to ensure we offer our customers the very best in knowledge and skills, Zanders has acquired RiskQuest.

Okay

Optimum Prime

is now part of Zanders

In a continued effort to ensure we offer our customers the very best in knowledge and skills, Zanders has acquired Optimum Prime.

Okay
This site is registered on wpml.org as a development site.