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.

Bank connectivity – Making the right choices

July 2020
3 min read

In this article we explore some methods to connect corporate ERP or treasury systems with partner banks. In addition, it explores some trends on how SWIFT is accessed and covers SAP’s Multi-Bank Connectivity tool.


Bank connectivity options

Within the space of bank connectivity, there is a range of choices that corporates face when deciding the best way to integrate banks towards their ERP or treasury platforms.

E-banking

The most historic option, with users logging into online banking platforms to extract bank reporting and initiate payments. Banking platforms have evolved, with some offering electronic statement download (which can be readily imported into ERPs), and payment status monitoring. Whilst a readily available, easy-to-use solution, it has issues with controls and requires separate platforms for each bank.

SWIFT

SWIFT provides global coverage to a wide range of banks. It is seen as the global standard in bank connectivity, and from a bank perspective we have seen the membership increase.
There are two channels available:

ChannelMessage Types
FINSWIFT MT Messages – e.g. MT101, MT940
FileACTAny Message Type – typically ISO20022

SWIFT FileAct is suited to AP Payments, as ISO20022 message standards permit high volumes of payments in files. SWIFT FIN is more commonly used for treasury integration, due to the historic use of SWIFT MT messages. As ISO20022 is more widely adopted, SWIFT FileAct will become the default choice for messaging channel.

A useful tool to identify if your partner banks are onboard is SWIFT’s Readiness Portal.

EBICS

Originally developed as a financial messaging transmission vehicle for Germany, EBICS has been later extended to France and Switzerland. It provides wide coverage of banks within these countries, but is not in use outside of these countries.

It generally has a lower total cost of ownership than SWIFT. The geographic restrictions mean that this is commonly used for corporates who have strong focus in the German, French or Swiss Market. For corporates operating on a global basis, EBICS does not tend to provide the bank coverage that is required.

Host-to-host (H2H)

H2H connections are direct connections from a corporate’s integration system towards a specific bank.

H2H connections are most suitable where corporates engage with a single core bank who can support local services and branch coverage in all relevant markets. These can have a lower total cost of ownership compared to using SWIFT, but this solution has a level of bank lock-in.

Direct to clearing house (UK BACS)

Within the UK, the primary clearing house is BACS, which ensures settlements of payments between debtor and creditor banks.

It is common practice in the UK for corporates to make payment instructions & direct debit instructions directly to the local clearing house BACS, where the partner bank acts as a sponsor. This requires a BACS service bureau who can act as a gateway into the BACS network. This is commonly known as “direct transmission”.

An alternative to this transfer method is “indirect transmission” where payments and direct debits are sent to the partner bank, via any of the preceding methods before being submitted to BACS itself.

API connectivity

Triggered by the PSD2 initiative, banks are now offering API connectivity.

One of the issues with API connectivity is that modern API design is targeted towards JSON formats, whilst ISO20022 is an xml-based schema. Due to low levels of standardization across different banks and countries, this has meant that ERPs and treasury platforms may require bespoke functionality to cater for these bank-specific APIs.

It is likely that these will become the future of bank connectivity, but will require some level of standardization, which could possibly come under the SWIFT umbrella.

Access to SWIFT

Connectivity of corporates to the SWIFT network has expanded over the last years from the largest corporates with high volumes of bank connections, to small-to-medium corporates with lower volumes of bank connections. To access the global SWIFT network, there are 4 main options that corporates can leverage:

  • In-house – SAG
    SWIFT Alliance Gateway (SAG) was the standard connection offered to corporates. It requires specialist SWIFT knowledge and has high complexity. This is no longer encouraged by SWIFT.
  • Outsourced – SSB
    SWIFT Service Bureaus (SSBs) remove the complexities of establishing the connection to the SWIFT network. SSBs certified by SWIFT manage the hardware and access configuration. Nowadays approximately 50% of all corporates access SWIFT through a SSB.
  • In-house – Alliance Lite 2
    SWIFT introduced Alliance Lite2 to enable smaller corporates to connect to the network. SWIFT proprietary software, installed locally, in combination with a hard token, transfers messages to the SWIFT network. Since each transmission may require an approval, this option is not fit for corporates with high payment volumes/STP-rates.
  • Outsourced – Alliance Lite2 embedded within Business Application
    Applications (L2BA) Since 2012, SWIFT has offered Alliance Lite2 including business applications for treasury management systems, bank connectivity providers and in-house banking/payment factory providers. Even though this option is relatively new, it gained popularity very quickly, with corporates looking to externalize bank connectivity whilst keeping total cost of ownership to a minimum.

For corporates having joined SWIFT since January 2018, 64% have opted for the SWIFT Cloud Alliance Lite 2 options. It is likely that the adoption of the embedded Alliance Lite 2 is behind this trend.

SAP Multi-Bank Connectivity

SAP Multi-Bank Connectivity (MBC) is SAP’s offering of a SWIFT connection embedded within Business Applications. SAP MBC is offered as a software-as-a-service solution by SAP. This is a revived form of SAP’s Financial Services network, which was launched in 2015, but with an enhanced offering such as integrated SWIFT connection.

Embedded within the SAP Cloud Platform, it provides capability for exchange of financial messaging with partner banks. As well as connectivity to the SWIFT network through an embedded version of Alliance Lite 2, this integration platform offers connectivity to partner banks through EBICS and H2H connections.

From a technical perspective, SAP MBC can perform transmissions using SFTP, REST, SOAP and AS2. We have seen evidence of corporate group IT policies dictating preferred transmission methods, so it is important that bank connectivity tools accommodate these. The platform has 99% up-time, and various failover mechanisms in place.

SAP MBC is particularly relevant to those corporates who are looking to move towards SAP as a strategic software vendor. With many corporates embarking on S/4 HANA transformation, it is a popular consideration.

We expect to see this offering as strong competition to SWIFT Service Bureaus going forward, especially where corporates are not leveraging the value-add services that SSBs offer.

VEON’s transformation to an optimized treasury

VEON’s treasury transformation, in partnership with Zanders, centralized its operations and implemented a new Treasury Global Operating Model to streamline processes, improve control, and adapt to the complexities of operating in diverse international markets.


With more than 235 million customers worldwide spread across a diverse group of countries, VEON's business is complex in nature. As a consequence, the organization instigated a large-scale transformational program in 2016, in order to take its financial function to a higher level. This also meant a radical change process for treasury activities.

VEON consists of a large number of separate telecommunications companies (telcos). From its head office in Amsterdam, the multinational provides telecommunications and digital services, with different local trademarks, in countries that include Italy, Pakistan, Bangladesh, Algeria and various CIS countries, such as Russia, Ukraine, Uzbekistan and Kazakhstan. Shares in the company are traded on the Nasdaq in New York and Euronext in Amsterdam.

More than mobile

In recent years, VEON has taken over several telcos, but also sold off others. “We are focusing on a number of key markets, where we want to be number one or two,” says Maarten Michalides, director of corporate finance at VEON. “When, for example, we took over a large Egyptian company, GTH, we immediately divested various parts of it located in a number of more southern African countries.” As an example, VEON is the market leader in Pakistan. In addition, the company has a local banking license and, therefore, provides financial services as well. “In such countries, relatively few people have a bank account,” says Michalides. “Because, in terms of systems, the telecoms infrastructure is very similar to that of a bank (we also have customers' name and address data and account balances), and customers are paying with their mobile phones. It is therefore only logical that telcos have a competitive advantage with regard to financial services. We provide them in Pakistan, but also in countries such as Russia and Ukraine.”

In addition, VEON focuses on developments involving new digital opportunities and enables customers to access all kinds of services via the VEON app. This is an important growth strategy for the company, says Michalides. “The growing capabilities of telephones increasingly enable, not just local, but also international service providers to enter the market. Our aim is to progressively transform from a traditional telecom company to digital service provider.”

Transformational program

As a result of this strategic change, VEON faced a major challenge: the entire finance organization had to become more cost-efficient, more standardized and more business-focused. Part of this plan was the centralization of the operational finance activities in a number of shared service centers (SSCs), which had already started. “This was necessary not only for the sake of efficiency, but also from a quality and control perspective,” explains Michalides. Spread across various countries, more than 40,000 VEON employees were used to working with their own systems and according to their own procedures and processes. “This generally works well on a stand-alone basis, but in the end it is logical for a large international group to harmonize,” he adds. That is why in 2016, when the company was still called Vimpelcom, it launched a large-scale program to transform its finance function.

This broader project made it necessary for the treasury team to initiate a treasury transformation project in order to design a new Treasury Global Operating Model (TGOM), in which the treasury organization, processes, supporting systems and activities were redefined. In other words, the various treasury departments within VEON were to become uniform and harmonized on the basis of this TGOM.

Local presence

As a consequence, the entire company is currently undergoing a transformation phase, says Michalides. “We are moving towards more central purchasing, implementing a single ERP system that everyone in the organization will use, and we are setting up new SSCs in a number of places, merging overlapping operational activities. This is occurring one step at a time and cannot be done quickly, due to certain factors including regulations and the company’s history. Treasury cannot be left behind in this transformation. With about 150 people, our treasury organization seemed huge, but half of it was actually Accounts Receivable or involved in other financial-administrative services.”

VEON uses more than 100 banks and 1,000 bank accounts. Local bank accounts and relations are really necessary in many countries, notes Michalides. “In some countries, we have to set up the financing locally, as local approval by banks and governments is needed to get things done. Local legislation and status of the banking system therefore make it difficult to centralize. This also means that we cannot simply cut back from 75 to 10 treasurers, as would be possible for a telco operating in the West. We are going to reduce the number considerably, but it is more important that we have a grip on the operation, so we know exactly what happens, when and by whom. That is the primary goal in the treasury project that we are undertaking.”

Open-heart surgery

When this project was identified, Michalides' department went in search of support. “We knew, for example, that our current treasury management system (TMS) was no longer going to help us and should be renewed. We knew that it was necessary to gain more control over the treasury activities of the entire company. We also knew that the rest of the company was working on a finance transformation. Working with the group treasurer, I proceeded to identify a consulting company that was completely dedicated to treasury – hence not distracted by other services such as accountancy, software and the like. Personally, I had good experiences with Zanders when working at Heineken and Corio. We made an appointment and received a convincing presentation, clearly showing how much experience they already had with regard to treasury transformation. We had known for a while that we had much to do and that it would be far-reaching. And, if you are undergoing open heart surgery and are vulnerable, it is nice to know that the surgeon can recognize what he is going to see and knows exactly what he is doing. It was therefore an easy choice for us.”

A new treasury system

A number of important steps were taken shortly afterwards, starting with a review and assessment of the current treasury organization, processes and systems in all relevant countries as well as at group treasury level. Then a preliminary treasury global operating model was defined and a fit-gap analysis was performed to assess the current state of treasury and what needed to be done to reach the target state. “We subsequently arrived at a blueprint and a roadmap of what the treasury function should look like between now and a few years hence,” explains Michalides. “This took place with proper consultation and a great deal of local involvement. Despite the fact that each country manages treasury in its own manner, the outcome has become a uniform plan that is supported and recognized by everyone.”

This plan indicates that the various treasury departments will have to operate more in accordance with shared principles, while taking into account the many local requirements and restrictions on currencies, tax and central bank rules. A crucial part of the TGOM is a crystal clear definition of the vision, the objectives and the scope of treasury within VEON, as well as clear policies and procedures, and the definition and assignment of roles and responsibilities at all levels within the treasury organization.

Michalides says: “In addition, the use of our treasury system turned out to be too non-committal, so we have defined a vision for a new single TMS; one system that can be managed centrally, communicates well with other systems and is therefore not without obligation. In the end, we want automatic payments and accounting, which means that control will also run faster and more effectively.”

“Viewed from a treasury perspective, the intended new system needs to support the entire process end-to-end,” Zanders consultant Job Wolters explains. “This means that, after logging in, you immediately see the current financial positions, and recognize the financial risks that exist. You can use it to analyze, provide support for decisions and execution, and to record your financial transactions – and then you have the link to accounting, the banks and reporting to senior management.”

Relevant streams

The selection of the new TMS is a very important cornerstone of the TGOM implementation project, Michalides emphasizes. “The organization and processes at the various SSCs must function in a more streamlined manner.” In addition, the team is busy setting up an in-house bank, an entity in Luxembourg that will act as the SSC for the corporate head office in Amsterdam, which operates more as the strategic function. The SSCs have the execution function, while Luxembourg has to play an exemplary role for the various local treasury departments. From Michalides’ young, international team, someone is involved in every project stream: the TGOM implementation, the TMS implementation, a bank rationalization and a cash flow forecasting project.

“The project is being undertaken by VEON and Zanders,” says Michalides. “It has been well thought out beforehand, allowing it to be executed in logical steps – an integral approach. For the overall project, we appointed an internal project manager, who provides support from VEON to Zanders, helping to find their way through the organization. This turned out to be a brilliant move, which is working very well. Since we are constantly being overtaken by the issues of the day, we ourselves cannot give the support that such an important and far-reaching project needs.”

Involving all countries

The role of treasury in the more general sense has recently changed within organizations, notes Michalides. “Especially with regard to systems and processes. More and more companies are centralizing the treasury function. This is also a logical move once you become more internationally active, an expansion that requires more centralization and therefore transformation as well. However, VEON is also a special company in this area; there are few Western companies with such a deep-rooted presence in complicated countries. Our offices have really grown out of their local environments.”

Looking back at recent developments, Michalides has some tips for other treasuries: “The success of a large complex project is mainly about good preparation. In addition, the involvement of the countries where you are established has proved to be very important. You must take your time for that, and remain well aware of their situation and processes. People appreciate it very much when they are involved in something so important.”

Would you like to know more about treasury transformation? Contact us today.

Customer successes

View all Insights

LyondellBasell: Remodeling risk to protect cash flows from business decisions

LyondellBasell leveraged a Cash Flow at Risk (CFaR) study to enhance its management of commodity and currency risks while guiding strategic decision-making.


“In which fields is it still possible to add value from a treasury point of view?” That was one of the questions LyondellBasell’s director of financial risk management, Frank van Es, asked himself when he reviewed the activities of the treasury department. As a result of his question, LyondellBasell analyzed its commodity and currency risk exposure with a Cash Flow at Risk (CFaR) study, which was conducted by Zanders.

Unprecedented volatility in financial markets has made corporates more aware of the importance of sound risk management. Events such as the so called ‘Brexit’ referendum on the 23 June 2016, after which stocks, commodities and currencies fluctuated by about 10 percent, could be harmful for the daily business operations of corporates.

Potential Cash Flow

While managing credit and market risk is a core competence for financial institutions, corporates are exposed to a myriad of financial risks (including FX, interest rate, and commodity price risk) as a result of their business operations. An important difference between financial institutions and corporates in terms of risk management is that financial institutions consider the risk in terms of portfolio value and balance sheet fluctuations, whereas corporates prefer to measure the risk in potential cash flow and profit downfall. Some corporates accept financial risks and have a reactive approach, while others create a competitive advantage by mitigating risk with strategic corporate risk management. With financial derivatives and risk transfer contracts, corporates can reduce risk and create value from a business perspective.

Commodity and Currency Risk

LyondellBasell is one of the world’s largest plastics, chemical, and refining companies and a member of the S&P 500. It is a traditional manufacturing company with a wide range of production possibilities at its 57 sites globally. For risk management purposes, the business of LyondellBasell can be simplified to the procurement of feedstocks needed in multiple manufacturing processes and the sale of finished products to its clients, i.e. mainly the purchasing of oil derivative products and selling intermediate chemicals and plastics. Coming with the purchase and sales, market price risk is introduced in the form of commodity and currency risk.

LyondellBasell has conducted several risk studies in the past to quantify the risks in their business model. Due to changes in the company and the petrochemical market, such as the change in pricing structure from quarterly to monthly price quotation, as well as changes in assets and products produced, LyondellBasell decided to conduct a limited CFaR study to better reflect its current business models. Besides quantifying the financial risks, the company wanted to explore further applications for strategic decision-making in order to reduce risk by hedging exposures or revising business models.

Worst Case Scenario

CFaR is a widely adopted method to quantify risk and is highly suitable for corporates. The CFaR measures, with a given probability, the unexpected negative movement of the cash flow. While being used to measure the potential cash flow downfall, the CFaR can be interpreted as a ‘worst case scenario’. By forming a risk appetite, a corporate could decide if the measured risk is acceptable or if it exceeds its risk allowance. To reduce risk, hedging strategies can be evaluated using scenario analysis. Hedging involves corporates purchasing financial derivatives to insure against unfavorable price movements.

To test the impact of such a decision, the risk measurements could be calculated in a ‘what if’ scenario under the strategic decision. The comparison between the scenarios with and without the hedge provides insight into the risk profile and costs of the strategic decision. The corporate could then decide if it is worth the costs to reduce the risk.

Key Risk Factors

The project at LyondellBasell started by mapping out a portion of the business to determine how cash flows are formed and how they interact with each other. Zanders translated purchases and sales systems to a measurable cash flow. Such mapping is useful for many corporates as these links are not immediately clear and are hidden within the organization. This is often caused because operations at corporates are divided into several divisions, such as purchase and sales divisions. Therefore, it is easy to lose visibility of the company’s cash flows.

Once this insight is created, the key risk factors which mainly impact the cash flows can be identified. It is important to distinguish the key risk factors since it is not feasible to model the entire company. After deciding which risk factors are incorporated, the CFaR can be measured using a Monte-Carlo simulation method. This method models the commodity prices and exchange rates with an econometric model and simulates future price paths.

By simulating many price paths, say 10,000 times, a large dataset is created where the worst-case scenario is evaluated to determine the risk and correlations between individual risks. The analysis was in line with Van Es’s expectation about LyondellBasell’s risk exposure. He says: “The model confirmed our gut feeling about our risk exposure and validated the correlations between commodity prices and exchange rates.”

Applications for Strategic Decision-Making

Together with LyondellBasell, Zanders took the next step towards strategic decision-making using its own customized risk model. In general, stakeholders are always initially skeptical about the idea of treasury getting actively engaged in the business. However, at LyondellBasell, they learned that although the model is a simplification of reality and should not be followed blindly, it can be used as an indication for business decisions. There is now more support and acceptance at LyondellBasell since the model helps the company to understand their figures and it verifies their ideas about correlation.

The business now has a tool that can help calculate the effect of production decisions on cash flows and risk, and can determine if they have to shift the business to create more cash flow stability. Zanders created applications for strategic decision-making for hedging strategies. For exposures that needed to be hedged, Van Es was interested in determining which percentage needed hedging, and whether exchange rate and commodity price should be hedged in tandem or could be hedged separately.

Correlations between market prices play an important role in making these decisions since they form a natural offset in risks. Zanders evaluated combined hedging strategies of commodity and currency and calculated the optimal hedging ratio in terms of risk reductions and costs.

Step by Step

Supported by the CFaR study, LyondellBasell is shifting its risk management into a higher gear. “There is an integration of ERM in treasury and we are creating a financial risk management department that will focus on modeling risks and developing financial strategies,” says Van Es. “We will implement hedging strategies step by step: better walk before you run. The implementation process will be challenging as we have to cross several barriers. For example, we need to execute currency and commodity trades and maybe have to set up a separate trading structure for this. There are many risks we have to manage, but we are the champions of risk management at treasury! We have shown our additional value with this project.”

Would you like to know more? Contact us today.

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

Building Trust and Driving Integration: Endemol Shine Group’s Holistic Risk Management Journey

Bart-Jan Roelofsz shares insights on merging Endemol and Shine’s risk management practices, aligning financial strategies, and navigating challenges in a dynamic entertainment landscape.


As well as being a member of the board of the DACT (Dutch Association of Corporate Treasurers), Bart-Jan Roelofsz is mainly known as group treasurer and insurance manager at Endemol Shine. This entertainment group is the result of a merger between Endemol and Shine. The merger means that the Shine companies have now adopted Endemol’s holistic approach to risk management. But what does that mean in practice? We asked Bart-Jan to explain.

Endemol took over the Shine Group at the end of 2014. What exactly does the joint venture do?

“We now have our own offices in nearly 40 countries but there’s quite a market beyond those countries as well. There are three aspects to our operational activities: creating, producing and distributing formats. The production activities involve scripted and non-scripted productions. The scripted productions, such as Humans, Ripper Street and Black Mirror, have production budgets that can run to over EUR 5 million per episode. Some examples of non-scripted shows are reality TV series such as Big Brother and game shows such as Deal or No Deal. Once a production has been completed, we distribute these ‘finished programs’ around the globe. In addition to these distribution activities we also license formats or concepts to third parties. These are then allowed to produce a show in a country where we don’t have an office ourselves.”

To what extent has the operational side of the ‘old’ Endemol changed as a result?

“The scripted and non-scripted activities haven’t really changed since the merger with the Shine Group; they have primarily just multiplied considerably. What’s important is that the programs that come from Shine complement the programs that Endemol already had. That’s great, because our financing model is largely based on – indirect – advertising revenues. In the food world, there were brands that didn’t particularly advertise around Endemol’s programs, but the big food brands are very interested in advertising around a program such as Master Chef, one of Shine’s best known programs. So the two libraries of formats that we had didn’t result in any mutual cannibalism. Moreover, our distribution division was already big, but can now distribute Shine’s entire catalog as well – which triggered a huge growth spurt in 2015 compared with previous years.”

How are the two organizations integrated financially?

“The Shine Group’s revenues were half the amount of Endemol’s, so it was a relatively big takeover. There was a geographical overlap in seven countries, so we had to physically integrate the various local entities in those countries. It was only in the four Scandinavian countries that there was virtually no overlap. The accounting guidelines also had to be adapted. Shine reported using US GAAP, not IFRS, and it also had a split financial year. To minimize the liquidity risk within the group, it was also important to concentrate as much liquidity as possible. Endemol already did a lot of cash upstreaming, but that wasn’t the case in the Shine organization. Endemol had been using a manual, international cash concentration structure for many years. When operating companies make funding requests, our responsiveness as an in-house bank is so good that they’re confident in placing temporarily excess cash with group treasury. Because the Shine Group had a historical mistrust of the practice, it was difficult to introduce cash upstreaming, but the great thing is that we gained that trust. So we are able to increasingly align Shine’s liquidity targets with those of the Endemol organization.”

What’s the situation regarding the Endemol Shine Group’s currency exposure?

“Each operating company works more or less in its own local currency, so local FX exposure is limited. By grouping their data into the four main currencies in which we operate, we have a better insight into the FX exposure of the entire Endemol Shine Group. That exposure stems chiefly from our external financing which, in terms of currency mix, is not in line with our organization’s cumulative currency mix; our financing is relatively US dollar-heavy – outweighing the share that we earn in US dollar-denominated countries. There are three reasons why the long-term FX risk is important to us. First of all, because of our refinancing exposure in 2020 and 2021. Then there’s the FX exposure on our interest charges and, finally, the exposure on our leverage ratio, as per the definition in our financing documentation. We are trying to prevent currency fluctuations influencing the leverage ratio. As a non-listed organization, partly private equity owned, we have agreed with our shareholders that protecting this leverage ratio is the primary objective.”

Endemol has implemented a holistic approach to risk management. What exactly does that entail?

“Risk management demands an integral approach, because it’s not just about financial risks but also operational and reputational risks, for example. Last summer we set up a multidisciplinary risk committee with people who have certain responsibilities within the existing organization – such as treasury/insurance, compliance/legal, IT, tax, controlling and HR – and who pool their resources on the committee. I now coordinate this committee as risk officer.

As well as identifying, analyzing and mitigating risks in a cross-disciplinary manner, the risks are also reported. Reporting to our executive board doesn’t pass through one of its members, but directly to the full board. In my opinion, within any organization, treasury has the mindset and position needed to coordinate a more holistic risk approach that embraces more than just the financial risks, making it the best choice for that task.

Our risk committee looks at the risks we encounter from the perspective of various disciplines. We compare those risks with our risk bearing capacity (RBC), keeping in mind that components of that RBC have been allocated to previously identified risks. To give you a practical example of such a ‘broader’ risk, we are increasingly using drones, carrying airborne cameras, for our productions. In the insurance world, these are usually still classed as ‘aircraft’. But we aren’t using them to transport people or freight. What’s more, insurers see the use of drones for photography and video recording as high risk in light of the violation of privacy rights – especially among American insurers. We deal with this risk on a daily basis, around the world. Finding suitable coverage calls for flexibility in an insurer – and that takes time... What do you do as an organization while you don’t have that coverage? Have compliance draw up guidelines stating that drones may not be used? As ridiculous as that may sound, you have to estimate the risk involved. The scenario, for instance, of a drone causing a multiple vehicle accident is a possibility, but how great is that probability? Can we mitigate this? Should we organize training specifically for personnel, can the controls be hacked, how do you express that in monetary terms, and how does it relate to our RBC?

All of these issues involved a variety of departments – HR, IT, controls. When determining our RBC, we take into account aspects such as our liquidity, non-committal or even firm profit expectations, as well as financial ratios in our financing documentation, which is treasury’s domain. We even consider whether we have already assigned a portion of the RBC to other risks.”

Is the methodology adopted at insurance companies, which involves looking at probability and impact, also used in treasury? Are risks considered in the same way?

“Absolutely. There’s no difference between mapping treasury or operational risks (which may or may not be insurable), or determining their potential impact using scenario and sensitivity analyses. What you then do with that information may differ. For instance: an organization can accept the FX risk – or hedge it – but it may also try to pass it on to its customers. The liability risk of a potential infringement of third-party intellectual property rights is our core business and we can only accept it or insure it, but not pass it on to third parties. I believe that the process of accepting risks, deliberately allocating the RBC to those risks, and monitoring and reporting on them could be done much better by lots of companies. And that includes us, by the way.”

Looking at the company that was absorbed in 2000 by Telefónica, is the strategy nowadays very different from what it was then?

“Telefónica, which bought Endemol after a bidding war with KPN and World Online, was actually light years ahead of the game. Telefónica wanted to set itself apart from the other telecom companies, not just in terms of price, quality and network, but also in terms of content they wanted to offer their subscribers something extra: access to Endemol content. And the vision they had is now the reality: being able to view content on mobile devices. Both as a replacement for television – i.e. generally available content – but also specific, subscriber-only content. The only thing they were wrong about back then was the speed of the rollout of the 3G and then the 4G network.

In 2007, Endemol was sold to a consortium of three parties: Goldman Sachs, Mediaset and Cyrte Investments. What made this special was the fact that it was one of the last leveraged finance deals before the financial and economic crisis erupted. One of the mandated lead arrangers (MLAs) at the time was Lehman Brothers. We experienced the complications of the bankruptcy of an MLA first hand – absolutely fascinating!

Between 2008 and 2014 the Endemol organization practically had to reinvent itself. Our revenues plummeted as a direct consequence of the sharp decline in the advertising market. But by producing programs far more efficiently, our profit margins actually grew during that period. In 2015, with the new shareholders and capital structure, we focused on integrating Shine into the Endemol organization, and we are now ready for the future. We’re able to roll out new ideas really fast; we are ‘lean and mean’. With our shareholders’ support, we can continue investing at an accelerated pace in the further growth of our organization.”

Bart-Jan joined Endemol as cash manager in 2002. Prior to that, he worked as a cash & treasury management consultant at ING. As from 2007, he became responsible for group insurances as well as group treasury. Since mid-2015, as group risk officer, he is also responsible for the risk committee.

Would you like to know more about cash flow forecasting and/or risk management? Contact us today.

Customer successes

View all Insights

IOM’s Roadmap to an improved treasury

IOM’s treasury transformation focused on streamlining bank relationships, implementing new systems, and establishing governance frameworks to better support its expanding migration management efforts.


The International Organization for Migration (IOM) is the principal intergovernmental agency in the field of migration. Due to increasing migratory flows over the past decade, which have escalated in recent months, the organization realized that its treasury needed a transformation in order to continue supporting the organization and its cause.

The IOM is committed to the principle that humane and orderly migration benefits both migrants and society. The organization was established in 1951, then known as the Provisional Intergovernmental Committee for the Movement of Migrants from Europe (PICMME), which helped people resettle in Western Europe following the chaos and displacement of the Second World War.

In subsequent years, the organization underwent a succession of name changes to the Intergovernmental Committee for European Migration (ICEM) in 1952, the Intergovernmental Committee for Migration (ICM) in 1980, and the International Organization for Migration (IOM) in 1989. These name changes reflect the organization’s transition from a logistics operation to a migration agency. The IOM’s members currently include 157 states and 10 observer states. It has offices in more than 150 countries and at any one time has more than 2,500 active projects ongoing.

It works to help ensure the orderly and humane management of migration, to promote international cooperation on migration issues, to assist in the search for practical solutions to migration problems, and to provide humanitarian assistance to migrants in need, including refugees, displaced persons, or other uprooted people. The organization works closely with several partners in four broad areas of migration management: migration and development, facilitating migration, regulating migration, and addressing forced migration. The IOM assists in meeting the growing operational challenges of migration management. It aims to advance the understanding of migration issues and encourages social and economic development through migration, while upholding the human dignity and well-being of migrants.

Differing paces

In 2008 and 2009, the organization went through a major transformation. “As recently as 10 years ago, the organization was still executing payments manually at its headquarters – payment by payment,” says Malcolm Grant, head of treasury at the IOM. With a new enterprise resource planning (ERP) system, the IOM took its first step towards improving its treasury. But more change was needed. While migration activities were growing – leading to increases in staff, projects, and donation allocation – treasury didn’t grow at the same pace as the rest of the organization. On top of that, in the years thereafter, the financial crisis resulted in a sharp increase of compliance requirements. “Due to all these developments, our treasury was way behind where it should have been.

The impact of the organization’s growth in an outdated system environment was that people looked for solutions by firefighting; they built up several different systems and various ways of working. For example, new bank accounts were added, instead of using existing bank accounts and relationships. We found ourselves with more than 700 accounts and over 150 bank relationships. We needed to bring treasury back to the heart of the organization – a huge challenge, because we needed more people, more up-to-date technology and improved governance.”

Due to the tight funding in the years following 2009, it was a slow process, says Grant: “From a treasury point of view, we look like a corporate; we get money in, we pay it out and invest it. A corporate has a profit motive, a different set of values and different stakeholders. So there are cultural differences and due to political issues some things don’t happen as quickly.”

A treasury blueprint for the future

Eventually, the organization’s management was persuaded to review its treasury. Grant explains: “So in 2012, we initiated the ‘treasury review’ project. We wanted a comprehensive wide-reaching review that tackled just about all key areas of treasury. Therefore, we asked some consultant firms for treasury advice and after some meetings we hired Zanders to reinforce and challenge our assumptions. And it turned out to be a great step; they added deep knowledge of treasury, markets, and best practices, and together we built a very strong business case showing what needed to be done in our strategic planning to overhaul our treasury.”

Based on the organization’s strategy, Zanders helped IOM in writing a blueprint for the future, based on a number of areas such as treasury management, financial risk management, and treasury governance. “And a few months later we started our ‘global treasury design’ project, aimed at scaling up our treasury operations. But then the question was how to get there. So, how could all issues be improved?”

Treasury risk committee & governance

But before IOM’s treasury realized these three objectives on the technical side, it had already looked at some of the ‘no-cost’ recommendations. Grant says: “In terms of structure, we were very keen to make sure we had a written treasury policy – we now have one. We also lacked an annual treasury plan, which we have now introduced. And one of the most important aspects was setting up a treasury risk committee, which brings together some senior managers in finance and one from operations. They have now been meeting quarterly for two years and it has added enormously to treasury transparency. Moreover, it’s a two-way channel; it has also been a very effective channel for feedback into senior management – to show what treasury is doing and what we want to achieve in the near future. As a result of the review, some serious and valuable changes have been made.”

Grant’s treasury department worked hard to realize the targets as described in the roadmap. He needed some assistance in finding the organization’s banking partners for its cash management, to solve the problem of a too widely dispersed bank portfolio and bank account structure.

“We need to see what money is where,” says Grant. “We don’t see certain key collections in our accounts. Different field offices have different cultures; some are very proactive and engaged in centralized cash management, yet others aren’t. Therefore visibility is very important and a big challenge.”

Simplifying bank relationships

So, last year, IOM asked Zanders to conduct a European Cash Management RFP. Grant notes: “The number of bank relationships was over 150 across our organization. When we did the European RFP, we had 39 countries in scope with 38 different banking parties in those countries. Depending on the region, you could begin to centralize payments. We don’t need to have bank accounts all over Europe, for example. So instead of having 38 bank partners, in the future we may only have five or six.”

Based on IOM’s requirements, five banks were shortlisted for its cash management bank selection project with a pan-European scope. Zanders helped to write the RFP document, was part of the bank selection, managed the evaluation process, and supported the recommendation to senior management. IOM now has just two banking partners and has started the implementation with both banks. “And it’s going very well. We have good support from our internal IT team, which is extremely important. We did a lot of homework and research in Europe, mission by mission, to establish all treasury requirements and banking needs in detail.”

The strategic recommendations that Zanders gave were gathered in a roadmap for IOM’s treasury, with a prioritization of projects and focus areas. Grant adds: “We started by looking at three key achievable short-term objectives – things we could do within one year. The first was to bring on board the foreign exchange trading platform, 360T. The second was to bring on board a treasury management system (TMS). Third was to conduct a cash management RFP (request for proposal) in Europe for banking services. These objectives have been met; the systems are now live and working. There is still some additional TMS functionality to bring on board, but the initial level of functionality related to reporting and basic payment processing is available.”

The end of the beginning

“Our department is now about a third of the way to where we want to be. Centralizing payments and having payment factories, for example, is still years away for IOM; that demands a phased approach. In terms of payments, reconciliation, pooling, and technical architecture, we are improving our basic structures; we are looking at in-house banking (IHB) and payment factories. You need to walk before you can run. To illustrate it in an appropriate quote from Winston Churchill: ‘This is not the end, it may not even be the beginning of the end but it is the end of the beginning.’ I think that’s where we are now.”

Despite the many tough challenges for IOM’s treasury department, working for an organization in the field of migration gives Grant both energy and satisfaction. “Treasury is a humble servant of the dedicated workers doing the tough job in the field. We are just here to take a potential set of problems away from them. By, for example, ensuring that they have enough liquidity so they can do what they need to do, ensuring they do not get into trouble with local compliance, get best value in buying local currency, and ensuring they have proper banking partners and accounts. Our advice and expertise is a key area of support to the local missions, thereby ensuring that the mission activities in the field are not held up due to treasury issues.”

IOM’s key strategic focus areas:

  • Migration management; helping migrants in any way possible regarding security.
  • Operations and emergencies: ready to react rapidly to emergency events such as earthquakes or military actions. IOM is not a refugee agency – that work is done by the UN – however it works closely together with UNHCR.
  • International cooperation and partnerships: including relationships with donors. IOM is very active in the development of international migration law. It has a team of lawyers and a department working on clarifying, establishing, and modifying international law, as far as it relates to migrants.

Customer successes

View all Insights

Actiam: Compliant with a new risk management framework

ACTIAM enhanced its risk management framework to comply with AIFMD, supported by Zanders, improving internal processes and sustainable investment practices.


The new EU directive regulating alternative investment funds management (AIFMD) meant that asset manager ACTIAM had to make substantial changes to its risk management, a major operation that had to be carried out in a short period of time.

ACTIAM was founded on 1 July 2014 after a merger between SNS Asset Management (SNS AM) and SNS Beleggingsfondsen Beheer (SBB, Investment funds management). The company now has more than EUR 50 billion assets under management for insurers, banks and pension funds. Among them are Reaal, Zwitserleven, ASN Bank and SNS Bank. “Responsible asset management is our specialism,” says Rob Verheul, COO at ACTIAM. “We manage all our investment categories in a responsible fashion. We have made doing business in a responsible way core to our investment process. It is in our DNA and we are proud of it. “ACTIAM originates from the Hollandse Koopmansbank (Dutch Merchant Bank) and has more than earned its reputation as a responsible asset manager. It has managed the ASN equity fund for more than 20 years. In 2013, this fund was awarded the Golden Bull for the best investment fund, and in 2015 was deemed the best equity fund in the world. Verheul says: “We do not invest in companies who do not trade in a sustainable way and we let people know through our website which companies we exclude. The universe in which we invest is therefore not as big as that of many other players, but we have already proved that social and financial returns go hand in hand.”


According to Bart Harmsen, head of risk management at ACTIAM, it is not a question of just excluding the insufficiently sustainable companies. “We try to encourage these companies to become more sustainable. We keep many lines of contact open in order to bring about improvements in that area.”

Growth ambition

As a part of VIVAT Insurance, ACTIAM considers Zwitserleven and Reaal (also part of VIVAT Insurances) just as much a client as ASN Bank and SNS Bank, says Verheul. “We have also close commercial contracts with them, just as with our other external clients. We have seen that the combination of professionalism, flexibility and sustainability has created a lot of interest for our funds from institutional investors. The legislator gives us a helping hand here, since pension funds are required to use part of their capital for sustainable investments.”
As administrator of institutional investment funds, ACTIAM’s name is well-known in this market segment. Our ambition is to grow in the retail market as well, says Verheul. “We are investigating whether funds for institutional investors could also be made suitable for retail investors. Our name recognition among a larger audience will then grow as a matter of course.”

Tougher demands

Under VIVAT Insurances, ACTIAM operates independently, with its own license, policy and statutory board. “Even though SNS AM and SBB have worked together for years, with this merger we are creating one expertise centre for our clients,” Verheul explains. “By doing this, we are creating even more commercial and operational strength and we can more easily comply with legislation and regulations.” Tougher demands on fund management as a result of new legislation and regulations in the AIFMD (Alternative Investment Fund Managers Directive) were important reasons for the merger. This legislation requires that a fund manager may not outsource both its portfolio management and its risk management. Verheul explains: “The fund manager (SBB) would therefore have to go to great lengths to rig up its risk management. Asset management was already outsourced to ACTIAM (at the time SNS AM). If we had not integrated SBB and SNS AM, the cost to the client would have been much higher than it is now. The costs of the merger are small by comparison. We are trying to absorb these by working more efficiently.”

Gap analysis


The AIFMD legislation sets out best practices in the area of risk and liquidity management, among others. As far as ACTIAM was concerned, this guideline had an impact on many different levels. “Most of them were under control,” says Verheul, “but we were not able to make the changes for the risk management part on our own. We could see that the scale of changes necessary within risk management was too great for our own staff to contend with. We had discussions with a number of contenders, but Zanders was selected fairly quickly. During the very first meeting they showed their pragmatic, down to earth approach. No standard consultant-talk, but serious people who gave the impression they would get on with it and deliver something of real useful value.”


Time was of the essence: ACTIAM had to be AIFMD compliant by 22 July 2014 and have its risk policy implemented, otherwise obtaining the license would be under threat. So, article for article, a speedy start was made on analyzing the legal texts; what was written down exactly, and what is the impact of them for ACTIAM? And as far as the risk management parts were concerned, where were the gaps as far as the guidelines went? And that’s how the risk management and risk methodology were assessed, a process during which hundreds of pages were read and analyzed. Zanders consultant Mark van Maaren says: “Early on we involved the front office, as well as others, in the development of risk policies, risk methodology and risk reporting. They made a valuable contribution and their involvement facilitated the acceptance of the risk framework.” During the whole process the strategy was developed gradually and the levels of risk became clearer. Beforehand, Verheul expressed progress in terms of a target figure: “We wanted to achieve 6.5 on reaching compliance, then we wanted to take our time in order to make it an 8.” In that way the inaccuracies in some reports, which were a result of tight deadlines, were corrected, while the reporting process itself was speeded up.

With constant to-ing and fro-ing, i.e. by involving front office, a large number of issues were solved.

Jasper van Eijk, Partner at Zanders

quote

This way most of the interest rate sensitivities on fixed interest instruments could be calculated, but a number of rates differed to what front office saw. By constantly going back to departments involved, the results were fine-tuned.

Internal involvement

In a short time frame a lot had to happen on both sides, but the interaction was ideal, Verheul thinks. “And what is so good is that we have improved the whole ACTIAM risk management framework. We are much more aware of the whole spectrum since it had much more impact than just the AIFMD part.” Harmsen nods in agreement: “The risk policy was also immediately adopted by the business and, as a result, the quality of thinking in terms of risk in the organization was given an enormous boost.” Van Maaren adds: “ACTIAM’s board’s strong commitment was an important factor in the success of the project. All directors gave up a lot of time to review and discuss the risk strategy, the preparation of risk reports and the development of risk methodology. Quick decisions were also made where there were issues within the project.” Van Eijk also felt the interaction within the organization was a success factor. “This was at all levels within the organization. The formulated policy had to take form by setting up models, methods and systems. But due to the limited timeframe we had to do this in parallel. This demands good co-ordination to get all cross-references tied in. Thanks to a pragmatic approach and the broad internal involvement, this was achieved.” The deadline was reached; ACTIAM was AIFMD compliant as of 22 July 2014.

Stick to the plan

For monitoring risk, ACTIAM used the existing risk management system, Dimension, from supplier Simcorp, of which Zanders implemented the new risk module. Verheul says: “We want the whole organization to use this system and the starting point was to include the whole risk reporting process in this system. Zanders firstly evaluated the suitability of this module for implementation of risk reporting together with ACTIAM and Simcorp before starting the implementation process.”
It symbolizes the secret of success of the whole journey, Verheul thinks: “Make considered choices and then stick to the plan. Don’t fall into the trap of implementing another system just because a report is easier to print for example, as this always leads to different problems. In retrospect, it all went very well, but there was a lot of pressure on everyone involved. All in all we are very pleased with the whole project. If we had to do it again then we would do it the same way.”


Want to know more about risk strategy and/or risk management systems? Contact us today.

Customer successes

View all Insights

Argos: new oil for wheels of treasury

Argos transformed its treasury operations by implementing IT2, leveraging best-practice processes with Zanders’ guidance to enhance efficiency, integration, and strategic financial management.


In order to be able to integrate a number of activities and improve efficiency, the oil company Argos decided to implement a new treasury management system (TMS).They chose IT2 and were very satisfied with the result. This best-practice implementation provides an excellent example for other corporates, showing how such a project should be tackled.

Argos is a young oil company that combines the storage and distribution of oil with the international trade in, and sale of, mineral oils and biofuels. The roots of the company go back to 1918, when Ad van der Sluijs opened a bicycle shop in Geertruidenberg and decided to sell petrol there, too. This turned out to be a good business move because the Van der Sluijs Group went on to become a big player in the areas of sales, storage, and transport of mineral oils in the nineties.

In 2009, the group merged with FNR+, which, with its companies Frisol, North Sea Petroleum, and Reinplus Vanwoerden, is a market leader in bunkering and trading. Hence the North Sea Group came into existence. In 2011, the North Sea Group joined forces with Argos Oil. Since then, the logo is displayed at the head office in the Rotterdam harbor Waalhaven, as well as on the signs outside around 70 Dutch petrol stations and – due to the lubricants sold by the company – on the shirts of the Argos Shimano team during the Tour de France races in 2012 and 2013.

In the Western European downstream oil market, Argos is now the largest independent player (since it is not stock-market listed or state-affiliated).

More rigid

In 2015, Argos has more than 500 employees, with branches in several different European countries as well as offices in Brazil, Hong Kong, and Singapore. The turnover of the company lies between EUR 14 billion and 16 billion per year.

“Around the time of the merger between FNR+ and the Van der Sluijs Group, from which the North Sea Group was born, I started working here,” says Jan Tijmen Donkelaar, Argos’s manager of finance projects. “The market and the company have been constantly moving since then. New business was created by the merger and the internal structure also changed. In the treasury department, you need to keep up with all those developments, which entails a great deal of adjustment and steering. That requires flexibility in the set-up of your system.”

A treasury department was built up in the North Sea Group, whereby two activities needed to be integrated: the trade activities and the bunker activities, where all the LCs (letters of credit: the guarantees for oil products) were settled. That integration of the two activities gave rise to a department with a front office, a middle office, and a back office.

Donkelaar was given the task of supervising that process. “That concerned the middle office, involving setting up the processes, and I started there by implementing an online trading platform (FXall) for currency transactions.”

For the selection of a new TMS, Argos asked Zanders to advise during the request for proposal (RFP). Donkelaar notes: “The shortlist put forward by Zanders included IT2, Bellin, and SunGard. SunGard offered greater flexibility in the connection with third-party systems, while IT2 placed greater focus on the support of best-practice processes during the implementation. The latter was a better fit with our needs, and so finally we selected IT2.”

Near real-time

One important reason for choosing IT2 was that it is ‘near real-time’. Donkelaar explains: “The FX deals, for example, are fed into our system every five minutes. That isn’t live, of course, but it’s certainly fast enough for Argos.” Bart Timmerman, consultant at Zanders, adds: “Where banks require genuine real-time data, near real-time is fast enough for corporate treasuries. There are multiple currency dealers at banks, and every deal needs to be directly visible to the other traders.” At Argos, all the commodity traders are connected to FXall, an electronic trading platform for currency and money market instruments. Donkelaar says: “When our oil traders do a deal that requires FX risk cover, they put the deal into FXall. The transaction is then sent from there to treasury, which subsequently makes a transaction with a bank. The currency risk arising from oil trades is therefore covered by the traders themselves. In addition, treasury looks at the overall position on a daily basis, and the risk arising thereby is also covered. Cash optimization – if, for example, a swap needs to be made overnight – is carried out by treasury itself.”

Phased approach

Argos decided to take on the project leadership itself on the implementation of IT2. Zanders was asked to assist Argos with the implementation of the best-practice processes. The optimal set-up of the treasury processes in IT2 from a software point of view, while keeping in mind the demands from the business, is determined and fixed in the blueprinting phase – the first phase following the purchase and technical installation of the system. The oil company chose to implement a phased approach. Donkelaar says: “We started with the basics: the things we needed for our daily position management and for our LCs and guarantee summaries. This meant, for example, that we recorded all the FX deals and all the money market transactions with banks in IT2. We also wanted to build up all the historical data into the system from January 1, 2013, such as all the FX data, all the LCs and all the guarantees. From that point we could then continue to build further on the payment process and set up the accounting module, which links bookkeeping to the system. In addition, the introduction of a clear, logical division of functions and data integrity was high on the agenda.” It is an approach that is typical for this type of project, says Timmerman: “Certainly in situations where speed is needed and capacity is limited. There wasn’t a capacity problem at Argos, but treasury relied on Excel. The first thing you need to make sure of is that the basic functionality works quickly, so that the deals and cash management can be carried out well. You can then roll out the flow of payments, followed by coupling that to accounting.” “IT2 placed focus on the support of best-practice processes during the implementation” 5 Jan Tijmen Donkelaar (right) and Bart Timmerman The Argos head office in the Rotterdam harbour.

Intercompany efficiency

In this way, IT2 functions as a symbolic umbrella under which increasing numbers of functionalities can be introduced by making connections within the organization. Timmerman continues: “For the benefit of the set-up of your accounting module, you need to keep in mind that the codes you use within the organization – for example in the ERP system – can also be found in IT2. This means that during the first phase of such a project, you need to make choices concerning the set-up, which prove to be important at a later stage.” Treasury often has specific accounts, such as in-house bank accounts, and for specific products, such as interest-rate derivatives and LCs. All transactions in that area must be recorded in the general ledger and, with the accounting module, IT2 offers a means for generating the necessary journal entries in the system and exporting these to a general ledger such as Navision. “In addition, the system can also be used as a sub-ledger”, says Timmerman. “This means having your own general ledger system that, instead of journal lines, exports balance sheet items to the bookkeeping program – which can make it even easier for the accounting department.” Internal settlements can be made via an in-house banking structure, meaning that the cash management is far more efficient and savings are made on transaction costs. “The annual turnover of Argos is between 14 and 16 billion euros”, says Donkelaar. “There are around 3 billion euros of intercompany settlements. An internal structure has therefore been set up for this, and that is also picked up by the accounting module. Instructions are processed automatically; the straight-through processing (STP) has been improved enormously, which in turn leads to greater efficiency.”

Best practice

Argos’s treasury needed to change over from an Excel-based environment to a new treasury system. Within treasury there was already a lot of in-depth knowledge to set up treasury processes. However, there was also a lack of experience with system implementations. Donkelaar says: “IT2 was able to provide good support on a technical level, but we needed more substantive advice for translating the business processes and the reports. We therefore asked Zanders to help with the connection to the business, on the basis of best-practice principles. Once the blueprint had been set out and approved, we organized a number of work sessions for each different part under the supervision of Bart Timmerman, whereby firstly the system was set up and then an extensive users’ acceptance test was carried out.” Once this cycle had been completed, the system went live. “But even after the system had gone live, Zanders provided us with coaching in that area on a number of occasions, and we also received additional advice from IT2. This is a good example for other corporates as to how this should be approached.” The same approach was also applied with setting up the accounting module. Donkelaar says that the knowledge that was gained was subsequently documented. “We had three people who were directly involved with the implementation of the accounting module. This meant that all the accounting templates were tested extensively and we now have our own user’s guide of 175 pages, in which every type of transaction is described. This means that when new members of staff come to work for us, they can be trained more quickly and will therefore be able to use the module sooner.” According to Timmerman, that documented knowledge is one of the success factors of the project. “Argos also knew very clearly what it wanted. We were therefore able to carry out the set-up to a greater extent from the point of view of best practice. Still, the availability of people within the treasury organization can make or break a project such as this. Only the people who work at the corporate have the relevant specific knowledge. That is why the transfer of knowledge is so important; when a problem arises, you need to be able to solve that internally.”

More than expected

The efficiency achieved with the new system also implies a correlation between the purchase of IT2 6 “We now have our own user’s guide, in which every type of transaction is described” Jan Tijmen Donkelaar and Bart Timmerman and the number of staff in the treasury department. “No, that isn’t an immediate result,” says Donkelaar. “We wanted to achieve better capital management for treasury, meaning that we can look more strategically at the way in which money is handled; for example, the choice between paying in advance or giving guarantees in the form of LCs. And that also applies to financing arrangements: how do you deal with your working capital, and via which flows do you allow that to work? We previously did that far more on an ad hoc basis, but now with IT2 we have a much better view of that. This has meant that we’ve been able to greatly reduce the number of bank accounts. These are things that you may not immediately have in mind with a new system, but which that new system actually makes possible.”

Timmerman nods in agreement: “I often notice that many treasurers don’t immediately realize the full potential of a TMS. The implementation of a TMS usually leads to a high level of STP, which makes processes quicker, more efficient, and less subject to mistakes. The TMS offers the possibility of building more checks into the treasury processes, as well as regularly and simply being able to report on key performance indicators (KPIs). The focus shifts, as it were, from gathering data to analyzing data, not least of all, due to the time saved by the TMS. This leads to the creation of other possibilities for optimizing your working capital management. And that is an important advantage for every corporate.”

Would you like to know more about the TMS solutions of IT2? Contact us today.

Customer successes

View all Insights

GlobalCollect transfers to SWIFT Alliance Lite2 for Corporates

From managing offline payments to navigating complex global transactions, GlobalCollect overcame the challenge of adopting SWIFT to streamline payments for businesses worldwide, making international transactions simpler and more cost-effective.


A transfer to a new system is usually a complicated and time-consuming process. This particularly rings true for a company like GlobalCollect, which processes hundreds of thousands of online transactions for banks all over the world on a daily basis. How did this payment service provider (PSP) tackle the complicated challenge of adopting SWIFT as its new system?

In 1994, the current GlobalCollect was set up as a division within the old TPG Post company to ensure a well-organized payment system for parcel deliveries. Back then it was dealing with offline payments, such as cash on delivery, but when digitalization took off, the postal company decided to go online with its payment services. Now, GlobalCollect is a fast-growing company, independent of TPG Post, which processes worldwide online payments for retailers operating internationally. This PSP offers them one platform so that they do not have to deal with the complexity of various foreign banks and their payment systems.

Connections and conversions

Michael Roos, vice president of merchant boarding at GlobalCollect, says that the market for PSPs has quickly become ‘professionalized’. “The industry has developed enormously over the past 10 years, also as far as legal and statutory regulations are concerned. We fall under the supervision of the Dutch central bank, De Nederlandsche Bank, and are affected by the EU’s Payment Services Directive (PSD). Companies who conduct business abroad, such as airlines or online retailers, need to receive payments from abroad. That adds to the complexity as it is a huge challenge setting up all the connections. You not only have to deal with the local banker, but also with all sorts of foreign banks.” A PSP not only has all those necessary local connections but is able to offer the client various payment methods via one point of access. “As a company you then have not only the local payment method, such as iDeal in the Netherlands, but also those in other countries where you have customers.”

Since GlobalCollect processes many millions of transactions each month, it is able to compete on price – something a single company cannot do with only several hundred transactions. Customers enjoy a more favorable rate – despite working with an intermediary – than they would with a bank. Besides dealing with the complexity of connections, GlobalCollect’s clients enjoy large-scale benefits for other services, such as currency conversion. “Collection of foreign currency can be outsourced,” Roos adds. “If you get paid in Brazilian real, which is not freely convertible, we do the conversion. Clients then have quicker access to their money in their own currency.”

New for corporates

 When GlobalCollect was starting up, it began with a few bank interfaces. “But after about 15 years we had more than 50 interfaces within an out-of-date infrastructure. In order to bring this infrastructure up to a technological standard that was market compliant, we decided that SWIFT was the best solution. But to get started we didn’t have the required know-how and manpower. So when we looked around for a company with plenty of expertise we hit on Zanders. I had spoken to Sander van Tol about three or four years ago and remembered that Zanders knew a lot about SWIFT. In the spring of 2012 I met Jill Tosi and in October the project kicked off.” Zanders taught GlobalCollect about the possibilities and impossibilities of SWIFT. “And Zanders was the right choice,” says Roos. Originally, SWIFT was a connectivity channel for banks, and since 2000 it has also become available to corporates. When GlobalCollect decided to start using SWIFT’s Alliance Lite2, a new cloud-based SWIFT communication tool, it was new to the market. Roos says: “As one of the first adopters, we were working with a completely new SWIFT system.

The interfaces particularly were new and unknown.” GlobalCollect’s reason for acquiring SWIFT was twofold. On the technical side, the number of interfaces had to be reduced. On the other hand, SWIFT had to standardize formats and the provision of information. Roos adds: “In order to be able to profit from the systems we had to have good information. Good information is standardized in IT, and so we ended up with SWIFT. The way information was shared with banks had to be standardized as much as possible. This was our starting point with a kick-off on various workflows.”

Fully-fledged tool

The challenge for GlobalCollect was mainly in connecting to banks. The old interfaces had to be replaced with new ones. Whereas SWIFT has everything standardized, it appeared that the banks did not. Roos explains: “Banks who want to connect via SWIFT each send their own technical implementation document; where one sends a single Excel-sheet with technical details, another sends a 20-page contract.” Roos noticed that SWIFT, banks, and corporations were not necessarily used to dealing with each other in this context. “Particularly outside of developed markets, the banks have not come that far yet and there is a good deal of indifference. This makes project-based work and estimation of turnaround times difficult. We approached a number of banks and looked to see which ones reacted the fastest and in the most professional way, and we started with them. This is not what you would normally do. I think we got off to a good start, but the migration path will take a number of months to complete.” The time required for testing individual connections and carrying out test cases can be very long. Roos says: “SWIFT is a fully-fledged tool and the parties used to working with it are large financial institutions. For us as a young, upcoming, dynamic industry, we really have to adapt to the banks – it’s a completely different culture.”

Change of format

With the huge amount of transactions involved, a transfer to another system is risky. “Therefore we ran the two systems in parallel during the migration,” he explains. “We also deliberately decided to link the largest parties first, leaving the legacy system running as we integrated SWIFT into the organization.” This means that a back-up is not necessary. “SWIFT is a unique system, with relatively large numbers of redundancy channels and recovery scenarios, so that it can guarantee unique processing.”

According to Zanders consultant Jill Tosi, this is because SWIFT is owned by the banks: “They have so much trust in their system that they assume responsibility for payments. SWIFT has such a robust system with minimal failure percentages, that customers can put complete trust in its information process.”

At the time of transferring to the new system, GlobalCollect had a lot of IT projects on the go. The SWIFT implementation was also part of a much larger project, Process Excellence, where several systems had to be modernized in order to meet market standards. “There was a lot of pressure on the IT department at GlobalCollect,” Tosi says. “The electronic banking systems were all stand-alone, i.e. not integrated into the daily processes. There were about 50 electronic banking systems, and someone had to log into each one separately with a different token each day. For one or two that is feasible, but 50 is too many.” And Roos adds: “The whole idea was to continue with significantly fewer interfaces – preferably one. And we are still very busy with that.”

While GlobalCollect was carrying out the migration to the new system, the banks were right in the middle of the SEPA migration. “That had consequences for the introduction of new formats within SWIFT,” Roos says. “We had to make a decision: do we go for MT940, the old standard for bank statements, or do we go for CAMT 053, the XML-successor of MT940? XML is a future-proof format but is not offered by all banks. As a consequence of SEPA, some banks will have to be migrated twice: firstly to MT940 and then to XML. An interesting aside is that where SWIFT offers the version 2.0 solution to corporations, many banks are just not ready for SWIFT connectivity with businesses. A number of large Anglo-Saxon banks have indicated that MT940 interfaces are not yet available for a direct connection to SWIFT Alliance Lite2 with corporates.”

Business as usual

The SWIFT migration to large banks is over and this year other banks will follow. After the first three banks, Zanders withdrew from the process. "It is now more like business as usual,” says Roos. "Zanders not only did the implementation, but was also responsible for the learning curve in our company. We have become self-supporting as far as SWIFT is concerned.” After the SWIFT project, Zanders also helped GlobalCollect with the selection and implementation of a new treasury management system (TMS) and a reconciliation tool. "Messages coming from SWIFT could be uploaded to our TMS straight away,” Roos says. "The same goes for our reconciliation system. If we didn’t have the standardization of the SWIFT system, it would have been much harder. In the banks’ own technical file formats there is a degree of standardization, but it’s not complete. It is clear to us that getting the standard functionality working would not have been possible without the successful implementation of SWIFT Alliance Lite2.”

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.