Cryptocurrencies and Blockchain: Navigating Risk, Compliance, and Future Opportunities in Corporate Treasury

June 2023
5 min read

The world of finance is changing rapidly. The adoption of cryptocurrencies, digital assets or other Blockchain-based solutions by corporations is already well underway.


As a result of the growing importance of this transformative technology and its applications, various regulatory initiatives and frameworks have emerged, such as Markets in Crypto-Assets Regulation (MiCAR), the Distributed Ledger Technology (DLT) Pilot Regime, and the Basel Committee on Banking Supervision (BCBS) crypto standard were launched, demonstrating the growing importance and adoption at both a global and national level. Given these trends, treasuries will be impacted by Blockchain one way or the other – if they aren’t already.

With the advent of cryptocurrencies and digital assets, it is important for treasurers to understand the issues at hand and have a strategy in place to deal with them. Based on our experience, typical questions that a treasurer faces are how to deal with the volatility of cryptocurrencies, how cryptocurrencies impact FX management, the accounting treatment for cryptocurrencies as well as KYC considerations. These developments are summarized in this article. 

FX Risk Management and Volatility

History has shown that cryptocurrencies such as Bitcoin and Ether are highly volatile assets, which implies that the Euro value of 1 BTC can fluctuate significantly. Based on our experience, treasurers opt to sell their cryptocurrencies as quickly as possible in order to convert them into fiat currency – the currencies that they are familiar and which their cost basis is typically in. However, other solutions exist such as hedging positions via derivatives traded on regulated financial markets or conversions into so-called stablecoins1

Accounting Treatment and Regulatory Compliance 

Cryptocurrencies, including stablecoins, require careful accounting treatment and compliance with regulations. In most cases cryptocurrencies are classified as “intangible assets” under IFRS. For broker-traders they are, however, classified as inventory, depending on the circumstances. Inventory is measured at the lower of cost and net realizable value, while intangible assets are measured at cost or revaluation. Under GAAP, most cryptocurrencies are treated as indefinite-lived intangible assets and are impaired when the fair value falls below the carrying value. These impairments cannot be reversed. CBDCs, however, are not considered cryptocurrencies. Similarly, and the classification of stablecoins depends on their status as financial assets or instruments. 

KYC/KYT Considerations

The adoption of cryptocurrencies and Blockchain technology introduces challenges for corporate treasurers in verifying counterparties and tracking transactions. When it comes to B2C transactions, treasurers may need to implement KYC (Know Your Customer) processes to verify the age and identity of individuals, ensuring compliance with age restrictions and preventing under-aged purchases, among other regulatory requirements. Whilst the process differs for B2B (business-to-business) transactions, the need for KYC exists nevertheless. However in the B2B space, the KYC process is less likely to be made more complex by transactions done in cryptocurrencies, since the parties involved are typically well-established companies or organizations with known identities and reputations. 

Central Bank Digital Currencies

(CBDCs) are emerging as potential alternatives to privately issued stablecoins and other cryptocurrencies. Central banks, including the European Central Bank and the Peoples Banks of China, are actively exploring the development of CBDCs. These currencies, backed by central banks, introduce a new dimension to the financial landscape and will be another arrow in the quiver of end-customers – along with cash, credit and debit cards or PayPal. Corporate treasurers must prepare for the potential implications and opportunities that CBDCs may bring, such as changes in payment options, governance processes, and working capital management.

Adapting to the Future

Corporate treasurers should proactively prepare for the impact of cryptocurrencies and Blockchain technology on their business operations. This includes educating themselves on the basics of cryptocurrencies, stablecoins, and CBDCs, and investigating how these assets can be integrated into their treasury functions. Understanding the infrastructure, processes, and potential hedging strategies is crucial for treasurers to make informed decisions regarding their balance sheets. Furthermore, treasurers must evaluate the impact of new payment options on working capital and adjust their strategies accordingly. 

Zanders understands the importance of keeping up with emerging technologies and trends, which is why we offer a comprehensive range of Blockchain services. Our Blockchain offering covers supporting our clients in developing their Blockchain strategy including developing proofs of concept, cryptocurrency integration into Corporate Treasury, support on vendor selection as well as regulatory advice. For decades Zanders has helped corporate treasurers navigate the choppy seas of change and disruption. We are ready to support you during this new era of disruption, so reach out to us today.  

Meet the team 

Zanders already has a well-positioned, diversified Blockchain team in place, consisting of Blockchain developers, Blockchain experts and business experts in their respective fields. In the following you will find a brief introduction of our lead Blockchain consultants. 

ISO 20022 XML (Pain.001.001.09) – Introduction of the Structured Address

May 2023
5 min read

The world of finance is changing rapidly. The adoption of cryptocurrencies, digital assets or other Blockchain-based solutions by corporations is already well underway.


However, possibly the most important point for corporates to be aware of is the planned move towards explicit use of the structured address block. In this second article in the ISO 20022 series, Zanders experts Eliane Eysackers and Mark Sutton provide some valuable insights around this industry requirement, the challenges that exists and an important update on this core topic. 

What is actually happening with the address information? 

One of the key drivers around the MT-MX migration are the significant benefits that can be achieved through the use of structured data. E.g., stronger compliance validation and support STP processing.  The SWIFT PMPG1 (Payment Market Practice Group) had advised that a number of market infrastructures2  are planning  to mandate the full structured address with the SWIFT ISO migration. The SWIFT PMPG had also planned to make the full structured address mandatory for the interbank messages – so effectively all cross-border payments. The most important point to note is that the SWIFT PMPG had also advised of the plan to reject non-compliant cross border payment messages from November 2025 in line with the end of the MT-MX migration. So, if a cross border payment did not include a full structured address, the payment instruction would be rejected. 

What are the current challenges around supporting a full structured address? 

Whilst the benefits of structured data are broadly recognised and accepted within the industry, a one size approach does not always work, and detailed analysis conducted by the Zanders team revealed mandating a full structured address would create significant friction and may ultimately be unworkable. 

Diagram 1: Challenges around the implementation of the full structured address. 

From the detailed analysis performed by the Zanders team, we have identified multiple problems that are all interconnected, and need to be addressed if the industry is to achieve its stated objective of a full structured address. These challenges are summarized below:  

  • Cost of change: The 2021 online TMI poll highlighted that 70% of respondents confirmed they currently merge the building name, building number, and street name in the same address line field. The key point to note is that the data is not currently separated within the ERP (Enterprise Resource Planning) system. Furthermore, 52% of these respondents highlighted a high impact to change this data, while 26% highlighted a medium impact. As part of Zanders’ continued research, we spoke to two major corporates to gain a better sense of their concerns. Both provided a high-level estimate of the development effort required for them to adapt to the new standard: ½ million euros. 
  • Fit for Purpose: From the ISO 20022 expert group discussions, it was recognized that the current XML Version 9 message would need a significant re-design to support the level of complexity that exists around the address structure globally.  
  • Vendor Support: Whilst we have not researched every ERP and TMS (Treasury Management System) system, if you compare the current structured address points including field length in the XML Version 9 message with the master data records currently available in the ERP and TMS systems, you will see gaps in terms of the fields that are supported and the actual field length. This means ERP and TMS software vendors will need to update the current address logic to fully align with the ISO standard for payments – but this software development cannot logically start until the ISO address block has been updated to avoid the need for multiple software upgrades.
  • Industry Guidelines: Whilst industry level implementation guidelines are always a positive step, the current published SWIFT PMPG guidelines have primarily focused on the simpler mainstream address structures for which the current address structure is fine. By correctly including the more complex local country address options, it will quickly highlight the gaps that exist, which mean compliance by the November 2025 deadline looks unrealistic at this stage. 
  • Regulatory Drivers: At this stage, there is still no evidence that any of the in-country payments regulators have actually requested a full structured address. However, we have seen some countries start to request minimum address information (but not structured due to the MT file format), such as Canada and US. 
  • Time to Implement: We must consider the above dependencies that need to be addressed first before full compliance can logically be considered, which means a new message version would be required. Whilst industry discussions are ongoing, the next ISO maintenance release is November 2023, which will result in XML version 13 being published. If we factor in time for banks to adopt this new version (XML Version 13), time for software vendors to develop the new full structured address including field length and finally, for the corporates to then implement this latest software upgrade and test with their banking partners, the November 2025 timeline looks unrealistic at this point in time.

A very important update 

Following a series of focused discussions around the potential address block changes to the XML Version 9 message, including the feedback from the GLEIF3 the ISO payment expert group questioned the need to support a significant redesign of the address block to enable the full structured address to be mandated. The Wolfsberg Group4 also raised concerns about scale of the changes required within the interbank messaging space.

Given this feedback, the SWIFT PMPG completed a survey with the corporate community in April. The survey feedback highlighted a number of the above concerns, and a change request has now been raised with the SWIFT standards working group for discussion at the end of June. The expectation is that the mandatory structured address elements will now be limited to just the Town/City, Postcode, and country, with typical address line 1 complexity continuing to be supported in the unstructured address element. This means a blended address structure will be supported.    

Is Corporate Treasury Impacted by this structured address compliance requirement? 

There are a number of aspects that need to be considered in answering this question. But at a high level, if you are currently maintaining your address data in a structured format within the ERP/TMS and you are currently providing the core structured address elements to your banking partners, then the impact should be low. However, Zanders recommends each corporate complete a more detailed review of the current address logic as soon as possible, given the current anticipated November 2025 compliance deadline. 

In Summary 

The ISO 20022 XML financial messages offer significant benefits to the corporate treasury community in terms more structured and richer data combined with a more globally standardised design. The timing is now right to commence the initial analysis so a more informed decision can be made around the key questions. 

Notes: 

  1. The PMPG (payment market practice group) is a SWIFT advisory group that reports into the Banking Services Committee (BSC) for all topics related to SWIFT. 
  1. A Market Infrastructure is a system that provides services to the financial industry for trading, clearing and settlement, matching of financial transactions, and depository functions. For example, in-country real-time gross settlement (RTGS) operators (FED, ECB, BoE). 
  1. Global Legal Entity Identifier Foundation (Established by the Financial Stability Board in June 2014, the GLEIF is tasked to support the implementation and use of the Legal Entity Identifier (LEI). 
  1. https://www.wolfsberg-principles.com/sites/default/files/wb/pdfs/wolfsberg-standards/1.%20Wolfsberg-Payment-Transparency-Standards-October-2017.pdf 
https://www.wolfsberg-principles.com/sites/default/files/wb/pdfs/wolfsberg-standards/1.%20Wolfsberg-Payment-Transparency-Standards-October-2017.pdf

Grip on your EVE SOT

May 2023
5 min read

The world of finance is changing rapidly. The adoption of cryptocurrencies, digital assets or other Blockchain-based solutions by corporations is already well underway.


Over the past decades, banks significantly increased their efforts to implement adequate frameworks for managing interest rate risk in the banking book (IRRBB). These efforts typically focus on defining an IRRBB strategy and a corresponding Risk Appetite Statement (RAS), translating this into policies and procedures, defining the how of the selected risk metrics, and designing the required (behavioral) models. Aspects like data quality, governance and risk reporting are (further) improved to facilitate effective management of IRRBB.

Main causes of volatility in SOT outcomes

The severely changed market circumstances evidence that, despite all efforts, the impact on the IRRBB framework could not be fully foreseen. The challenge of certain banks to comply with one of the key regulatory metrics defined in the context of IRRBB, the SOT on EVE, illustrates this. Indeed, even if regularities are assumed, there are still several key model choices that turn out to materialize in today’s interest rate environment:

  • Interest rate dependency in behavioral models: Behavioral models, in particular when these include interest rate-dependent relationships, typically exhibit a large amount of convexity. In some cases, convexity can be (significantly) overstated due to particular modeling choices, in turn contributing to a violation of the EVE SOT criterium. Some (small and mid-sized) banks, for example, apply the so-called ‘scenario multipliers’ and/or ‘scalar multipliers’ defined within the BCBS-standardized framework for incorporating interest rate-dependent relationships in their behavioral models. These multipliers assume a linear relationship between the modeled variable (e.g., prepayment rate) and the scenario, whereas in practice this relationship is not always linear. In other cases, the calibration approach of certain behavioral models is based on interest rates that have been decreasing for 10 to 15 years, and therefore may not be capable to handle a scenario in which a severe upward shock is added to a significantly increased base case yield curve.
  • Level and shape of the yield curve: Related to the previous point, some behavioral models are based on the steepness (defined as the difference between a ‘long tenor’ rate and a ‘short tenor’ rate) of the yield curve. As can be seen in Figure 1, the steepness changed significantly over the past two years, potentially leading to a high impact associated with the behavioral models that are based on it. Further, as illustrated in Figure 2, the yield curve has flattened over time and recently even turned into an inverse yield curve. When calculating the respective forward rates that define the steepness within a particular behavioral model, the downward trend of this variable that results due to the inverse yield curve potentially aggravates this effect.

Figure 1: Development of 3M EURIBOR rate and 10Y swap rate (vs. 3M EURIBOR) and the corresponding 'Steepness'

Figure 2: Development of the yield curve over the period December 2021 to March 2023.

  • Hidden vulnerability to ‘down’ scenarios: Previously, the interest rates were relatively close to, or even below, the EBA floor that is imposed on the SOT. Consequently, the ‘at-risk’ figures corresponding to scenarios in which (part of) the yield curve is shocked downward, were relatively small. Now that interest rates have moved away from the EBA floor, hidden vulnerability to ‘down’ scenarios become visible and likely the dominating scenario for the SOT on EVE.
  • Including ‘margin’ cashflows: Some banks determine their SOT on EVE including the margin cashflows (i.e., the spread added to the swap rate), while discounting at risk-free rates. While this approach is regulatory compliant, the inclusion of margin cashflows leads to higher (shocked) EVE values, and potentially leads to, or at least contributes to, a violation of the EVE threshold.

What can banks do?

Having identified the above issues, the question arises as to what measures banks should consider. Roughly speaking, two categories of actions can be distinguished. The first category encompasses actions that resolve an inadequate reflection of the actual risk. Examples of such actions include:

  • Identify and re-solve unintended effects in behavioral models: As mentioned above, behavioral models are key to determine appropriate EVE SOT figures. Next to revisiting the calibration approach, which typically is based on historical data, banks should assess to what extent there are unintended effects present in their behavioral models that adversely impact convexity and lead to unrepresentative sensitivities and unreliably shocked EVE values.
  • Adopt a pure IRR approach: An obvious candidate action for banks that still include margins in their cashflows used for the EVE SOT, is to adopt a pure interest rate risk view. In other words, align the cashflows with its discounting. This requires an adequate approach to remove the margin components from the interest cashflows.

The second category of actions addresses the actual, i.e., economic, risk position of bank. One could think of the following aspects that contribute to steering the EVE SOT within regulatory thresholds:

  • Evaluate target mismatch: As we wrote in our article ‘What can banks do to address the challenges posed by rising interest rates’, a bank’s EVE is most likely negatively affected by the rise in rates. The impact is dependent on the duration of equity taken by the bank: the higher the equity duration, the larger the decline in EVE when rates rise (and hence a higher EVE risk). In light of the challenges described above, a bank should consider re-evaluating the target mismatch (i.e. the duration of equity).
  • Consider swaptions as an additional hedge instrument: Convexity, in essence, cannot be hedged with plain vanilla swaps. Therefore, several banks have entered into ‘far out of the money’ swaptions to manage negative convexity in the SOT on EVE. From a business perspective, these swaptions result in additional, but accepted costs and P&L volatility. In case of an upward-sloping yield curve, the costs can be partly offset since the bank can increase its linear risk position (increase duration), without exceeding the EVE SOT threshold. This being said, swaptions can be considered a complex instrument that presents certain challenges. First, it requires valuation models – and expertise on these models – to be embedded within the organization. Second, setting up a heuristic that adequately matches the sensitivities of the swaptions to those of the commercial products (e.g., mortgages) is not a straightforward task.

How can Zanders support?

Zanders is thought leader in supporting banks with IRRBB-related topics. We enable banks to achieve both regulatory compliance and strategic risk goals, by offering support from strategy to implementation. This includes risk identification, formulating a risk strategy, setting up an IRRBB governance and framework, policy or risk appetite statements. Moreover, we have an extensive track record in IRRBB and behavioral models, hedging strategies, and calculating risk metrics, both from a model development as well as a model validation perspective.

Are you interested in IRRBB related topics? Contact Jaap KarelseErik Vijlbrief (Netherlands, Belgium and Nordic countries) or Martijn Wycisk (DACH region) for more information.

SAP Analytics Cloud – Liquidity Planning in SAC

May 2023
3 min read

Liquidity planning in SAP Analytics Cloud (SAC) is quite likely SAP’s response to the modernization of Cash Flow Forecasting (CFF) in Corporate Treasury, a key area in today’s treasury trends.


While SAC is a planning tool to be considered, it requires further exploration to evaluate its fit with business requirements and how it could unlock opportunities to potentially streamline the CFF process across the organization. For the organizations already using SAP BPC (Business Process & Consolidation) for planning, SAC could be seen as another ‘kid on the block’. It is important for them to have a clear business case for SAC.

In this article, we introduce SAC liquidity planning solution focusing on its integrated and predictive planning capabilities. We explain the concerns of corporate treasuries that have invested heavily in SAP BPC (either as standalone instance or embedded on S/4 HANA) and discuss the business case for SAC under different scenarios of extending the BPC planning solution to SAC.

What is SAC?

SAC is the analytics and planning solution within SAP Business Technology Platform which brings together analytics and planning with unique integration to SAP applications and smooth access to heterogeneous data sources.

Among the key benefits of SAC are Extended Planning & Analysis (xP&A) and Predictive Planning based on machine learning models. While xP&A integrates (traditional) financial and operational planning resulting in one connected plan that also meets the needs of operational departments, predictive planning augments decision making through embedded AI & ML capabilities.

Extended Planning & Analysis (xP&A)

Historically, the corporate planning has been typically biased towards finance and it was quite inadequate for operational departments who have to resort to local planning in silos for their own decision making. The xP&A approach goes beyond finance and integrates strategic, financial and operational planning in one connected plan. Planning under xP&A also moves beyond budgeting and rolling forecasts to a more agile and collaborative planning process which is near real-time with faster reaction times.

SAC can be seen as the technology enabler for xP&A, as follows:

  • It brings together financial, supply chain, and workforce planning in one connected plan deployed in the cloud;
  • Unified planning content with a single version of the truth that everyone is working on (plans are fit for purpose for the individual departments and at the same time integrated into one connected plan);
  • Predictive AI and ML models enables more realistic forecasts and facilitate near real-time planning & forecasting;
  • Smart analytics features like scenario planning prepare for contingencies and quick reaction;
  • SAC integrates with a wide range of data sources like S/4HANA , SuccessFactors, SAP IBP, Salesforce etc.

Predictive Planning

SAC Predictive planning model produces forecasts based on time series. The model is trained with historic data where a statistical algorithm will learn from the data set, i.e. find trends, seasonal variations and fluctuations that characterize the target variable. Upon completion of training, the model produces the forecast as the detailed time series chart for each segment.

In addition to using historical costs to make a prediction, influencer variables can be used to improve the predictive forecasts. Some examples of influencers are energy price when forecasting the energy cost, weather on the day and workday/weekend classification when forecasting daily bike hires.

Influencers are part of the data set and when included in the forecasting model, they contribute towards determining the ‘trend’. They improve the predictive forecasts which can be measured by drop in MAPE (Mean Absolute Percentage Error) and a smaller confidence interval (difference between the Error Max and the Error Min).

Business cases for extension of SAP BPC to SAC

While it may be easier to evaluate the benefits of SAC in a greenfield implementation, it could be challenging to create a suitable business case for customers already using SAP BPC, either standalone or embedded, and interesting to understand how they can preserve their existing assets in a brownfield implementation.

Below we have provided the business case for the 3 planning scenarios for extending the BPC planning to SAC:

Figure: Decomposition of forecast into trend, cycle and fluctuation (left out after trend and cycle are extracted)

Scenario 1: Move planning use cases from BPC to SAC

The ‘Move’ scenario involves re-creation of planning models in SAC. Some of the existing work can be leveraged on; for example, a planning model in SAC can be built through a query coming out of SAP BPC which re-creates the planning dimensions with all their hierarchies. The planning scenarios require more effort as the planning use cases are realized in a different way in SAC than BPC. Functionalities  such as disaggregations, version management and simulation are also conceptually different in SAC (compared to BPC).

Note: The re-creation of planning models in SAC through queries from BPC are more relevant for the embedded BPC model, running on SAP BW belonging to S/4 HANA NetWeaver. The integration under a standalone BPC model (using a standalone SAP BW) may not be supported and should be investigated with the vendor.

The key value drivers for this scenario include all the benefits of SACsuch as predictive planning and machine learning, xP&A, modern UX and smart analytics. SAC features on version control, real-time data analysis, lower maintenance cost and faster performance are also possible in the SAP BPC embedded model (advantages over BPC standalone model only).

Scenario 2: Complement existing BPC planning with SAC as planning UX

Here, SAC is used as a tool for entering planning data and data analysis. Data entered in SAC (e.g. via data entry form) is persisted directly in the SAP BPC planning model. LIVE planning is supported only in SAP BPC embedded model (one of the benefits of BPC embedded over standalone).

The key value drivers for this scenario are modern UX and smart analytics (from the firstt scenario), while the functional plans are maintained in BPC.

Scenario 3: Extend BPC with SAC for new functional plans

In this scenario, new functional planning is done in SAC on top of BPC, data is stored in both systems and replicated in both directions.

Key value drivers for this scenario are predictive planning and xP&A (to some extent). A specific use case for the first one is where planning data is brought into SAC, predictive forecasting applied on top of the planned data together with any manual adjustments and data is replicated back to BPC. A use case for the second one is where financial planning done in BPC is integrated with the operational planning done exclusively in SAC.

In conclusion

SAC can be seen as SAP’s vision for Extensible Planning & Analysis (xP&A) as it unifies planning across multiple lines of business while ensuring that plans are meaningful and can be put to action. The predictive time series, AI and ML based models of SAC are key enablers for a near real-time and driver-based planning.

For customers already using BPC (standalone or embedded on S/4 HANA) there are possibilities to complement the existing planning process through SAC. However, to exploit the full benefits in xP&A, it is important to understand the integrated planning approach of SAC which is conceptually different from BPC. While the immediate requirement in a BPC complement scenario could be to realize the current use cases in SAC (in a different way), it makes sense to maintain a strategic outlook, e.g. when creating the planning models in SAC, to achieve the full transformation in future.

References: 

Top 10 reasons to move from SAP Business Planning and Consolidation to SAP Analytics Cloud

White-Paper-Extended-Planning-and-Analysis-2022.pdf (fpa-trends.com)

Extended Planning and Analysis | xP&A (sap.com)

SAP Analytics Cloud | BI, Planning, and Predictive Analysis Tools

Hands-On Tutorial: Predictive Planning | SAP Blogs

Predictive Planning – How to use influencers | SAP Blogs

SAP BPC Move to SAC: Benefits & Scenarios of moving SAP BPC planning scenarios to SAP Analytics Cloud | SAP Blogs

Financial planning : SAP Analytics Cloud to replace SAP Business Planning & Consolidation ? | SAP Blogs

Complement Your SAP Business Planning and Consolidation with SAP Analytics Cloud | SAP Blogs

SAP Business Planning & Consolidation for S/4HANA – In a Nutshell | SAP Blogs

Preventing a next bank failure like Credit Suisse: More capital is not the solution

May 2023
3 min read

Liquidity planning in SAP Analytics Cloud (SAC) is quite likely SAP’s response to the modernization of Cash Flow Forecasting (CFF) in Corporate Treasury, a key area in today’s treasury trends.


After the collapse of Credit Suisse and the subsequent orchestrated take-over by UBS, there are widespread calls for increasing capital requirements for too big too fail banks to prevent future defaults of such institutions. However, more capital will not prevent the failure of a bank in a bank-run like Credit Suisse experienced in the first quarter of 2023.

A solid capital base is clearly important for a bank to maintain the trust of its clients, counterparties and lenders, including depositors. At the end of 2022, Credit Suisse had a BIS Common Equity Tier 1 (CET1) capital ratio of 14.1% and a CET1 leverage ratio of 5.4%, in line with its peers and well above regulatory minimum requirements. For example, UBS had a CET1 capital and leverage ratio of 14.2% and 4.4%, respectively. Hence, the capital situation by itself will not have been the reason that depositors and lenders lost trust in the bank, withdrew money in large amounts, refrained from rolling over maturing funding and/or asked for additional collateral.

Why capital does not help

Already during 2022, Credit Suisse experienced a large decrease in funding from customer deposits, falling by CHF 160 billion from CHF 393 billion to CHF 233 billion during the year. In the first quarter of 2023, a further CHF 67 billion of customer deposits were withdrawn. Even if capital could be used to cope with funding outflows (which it cannot, as we will clarify shortly), the amount will never be sufficient to cope with outflows of such magnitude. For comparison, at the end of 2021, Credit Suisse’s CET1 capital was equal to CHF 38.5 billion.

But, as mentioned, capital does not help to cope with funding outflows. A reduction in funding (liabilities) must be either replaced with new funding from other lenders or by a corresponding reduction in assets (e.g., cash or investments), leaving the amount of capital (equity) in principle unchanged[1]. If large amounts of funding are withdrawn at the same time, as was the case for Credit Suisse in 2022, it is usually not feasible to find replacement funding quickly enough at a reasonable price. In that case, there is no alternative to reducing cash and/or selling assets[2].

In such a scenario, leverage and capital ratios may actually improve, since the available capital will then support a smaller amount of assets. This is what happened at Credit Suisse during 2022. Although the amount of CET1 capital decreased from CHF 38.5 billion to CHF 35.3 billion (-8.4%), its leverage exposure[3] decreased by 27%. Consequently, the bank’s CET1 leverage ratio improved from 4.3% to 5.4%. Risk-weighted assets (RWA) also decreased, but only by 6%, resulting in a small decrease in the CET1 capital ratio from 14.4% to 14.1%. The changes in CET1 capital, leverage exposure and RWA are depicted in Figure 1.

Figure 1: Development in CET1 capital, leverage exposure and risk-weighted assets (RWA) at Credit Suisse between end of December 2021 and end of December 2022 (amounts in CHF million). Source: Credit Suisse Annual Reports 2021 and 2022.

Cash is king

In a situation of large funding withdrawals, it is critical that the bank has a sufficiently large amount of liquid assets. At the end of 2021, Credit Suisse reported CHF 230 billion of liquid assets, consisting of cash held at central banks (CHF 144 billion) and securities[4] that could be pledged to central banks in exchange for cash (CHF 86 billion). At the end of 2022, the amount of liquid assets had decreased to just over CHF 118 billion. Hence, a substantial part of the withdrawal of deposits was met by a reduction in liquid assets. The remainder was met with cash inflows from maturing loans and other assets on the one hand, and replacement with alternative funding on the other.

Lack of sufficient liquid assets was one cause of bank problems during the financial crisis in 2007-08, resulting in extensive liquidity support by central banks. With the aim to prevent this from happening again, the final Basel III rules require banks to satisfy a liquidity coverage ratio (LCR) of at least 100%. This LCR intends to ensure that a bank has sufficient liquidity to sustain significant cash outflows over a 30-day period. The regulatory rules prescribe what cash outflow assumptions need to be made for each type of liability. For example, the FINMA rules for the calculation of the LCR (see FINMA ordinance 2015/2) prescribe that for retail deposits an outflow between 3% and 20% needs to be assumed, with the percentage depending on whether the deposit is insured by a deposit insurance scheme, whether it is on a transactional or non-transactional account, and whether it is a ‘high-value’ deposit. Other outflow assumptions apply to unsecured wholesale funding, secured funding, collateral requirements for derivatives as well as loan and liquidity commitments. The amount of available liquid assets needs to be larger than the cash outflows calculated in this way, net of contractual cash inflows from loans, reverse repos and secured lending within the next 30-day period (all weighted with prescribed percentages). In that case, the LCR exceeds 100% (it is calculated as the amount of liquid assets divided by the difference between assumed cash outflows and contractual cash inflows with prescribed weightings).

At the end of 2022, Credit Suisse had an LCR of 144%, compared to 203% at the end of 2021. Hence, the amount of liquid assets relative to the amount of assumed net cash outflow decreased substantially but remained well above 100%.

Figure 2 compares the balances of the individual liability categories that are subject to cash outflows in the LCR calculation:

  1. The first column depicts the actual balances at the end of December 2021.
  2. The second column shows what the remaining balances would be after applying the cash outflow assumptions in the LCR calculation to the December 2021 balances.
  3. The third column represents the actual balances at the end of December 2022.

This comparison is not fully fair as we compare the actual balances between the start and the end of the full year of 2022, whereas the assumed cash outflows in the LCR calculation relate to a 30-day period. However, Credit Suisse communicated that the largest outflows occurred during the month of October 2022, so the comparison is still instructive.

Figure 2: Comparison of balances of liability categories[5] that are subject to cash outflow assumptions in the LCR calculation: Actual balances at the end of December 2021 (first column), balances that result when applying the LCR cash outflow assumptions to the December 2021 balances (second column) and actual balances at the end of December 2022 (third column). Source: Credit Suisse Annual Reports 2021 and 2022.

In aggregate, the actual balances at the end of 2022 are higher than the balances that would result after applying the LCR cash outflow assumptions (CHF 714 billion vs CHF 633 billion, compared to CHF 872 billion at the end of 2021). However, for ‘Retail deposits and deposits from small business customers’ and ‘Unsecured wholesale funding’, the actual outflow was higher than assumed in the LCR calculation. This was more than compensated by an increase in secured wholesale funding and lower outflows in other categories than assumed in the LCR calculation.
In summary, the amount of liquid assets that Credit Suisse had were sufficient to absorb the large withdrawal of funds in October 2022 without the LCR falling below 100%. Trust then seemed to be restored, but only until a new wave of withdrawals took place in March of this year, necessitating a request for liquidity support from the Swiss National Bank (SNB). Unfortunately, the liquidity support by the SNB apparently did not suffice to save Credit Suisse.

What if worse comes to worst?

That both retail depositors and wholesale lenders lost trust in Credit Suisse and withdrew large amounts of money cannot be attributed to its capital and leverage ratios by itself, because they were well above minimum requirements and in line with – if not higher than – those of its peers. Apparently, depositors and lenders lost trust because of doubts that are not visible on a balance sheet, for example:

  • Doubts whether the bank would be able to stop losses quickly enough when executing the planned strategy, after a loss of CHF 7.2 billion in 2022.
  • Doubts about the management quality of the bank after incurring large losses in isolated incidents (Archegos, Greensill).
  • Doubts whether provisions taken for outstanding litigation cases would cover the ultimate fines.

Once such and other material doubts arise, possibly fed by rumors in the market, a bank may end up in a negative spiral of fund withdrawals. In such a situation, it will be unclear to lenders and depositors what the actual financial situation is, even though the last reported figures may have been solid. This unclarity will accelerate further withdrawals. As the developments at Credit Suisse have shown, even a very large pool of liquid assets (for Credit Suisse at the end of 2021 more than twice the amount of net cash outflows assumed in the LCR calculation and almost one-third the size of its balance sheet) will then not be enough. Since such a lack of confidence can escalate within a matter of days, as was the case not only for Credit Suisse but for example also for the Silicon Valley Bank as well as Northern Rock in 2008, there is no time to implement a recovery or resolution plan that the bank may have prepared.

Short of implementing a sovereign-money (‘Vollgeld’) banking system, which has various drawbacks as highlighted for example by the Swiss National Bank (SNB), the only realistic solution to save a bank in such a situation is for the government and/or central bank to step in and publicly commit to providing all necessary liquidity to the bank. It is important to note that this does not have to lead to losses for the government (and therefore the tax payer) as long as the capital situation of the bank in question is adequate. For all we know, that was the case at Credit Suisse.

Footnotes
[1] Only if assets are reduced at a value that differs from the book value (e.g., investments are sold below their book value), then this difference will be reflected in the amount of capital.

[2] In the first quarter of 2023, the Swiss National Bank (SNB) supported Credit Suisse with emergency liquidity funding. As a result, short-term borrowings increased from CHF 12 billion to CHF 118 billion during the quarter. This prevented that Credit Suisse had to further reduce its cash position and/or sell assets, possibly at a loss compared to their book value.

[3] The leverage exposure is equal to the bank’s assets plus a number of regulatory adjustments related mainly to derivative financial instruments and off-balance sheet exposures.

[4] At Credit Suisse, these were mostly US and UK government bonds.

[5] The categories ‘Additional requirements’, ‘Other contractual funding obligations’ and ‘Other contingent funding obligations’ comprise mostly (contingent) off-balance sheet commitments, such as liquidity and loan commitments, guarantees and conditional collateralization requirements.

A comparison between Survival Analysis and Migration Matrix Models

May 2023
3 min read

Liquidity planning in SAP Analytics Cloud (SAC) is quite likely SAP’s response to the modernization of Cash Flow Forecasting (CFF) in Corporate Treasury, a key area in today’s treasury trends.


This article provides a thorough comparison of the Survival Analysis and Migration Matrix approach for modeling losses under the internal ratings-based (IRB) approach and IFRS 9. The optimal approach depends on the bank’s situation, and this article highlights that there is no one-size-fits-all solution.

The focus of this read is on the probability of default (PD) component since IFRS 9 differs mainly with regards to the PD component as compared to the IRB Accords (Bank & Eder, 2021), and that most time and effort is given to this component.

Did you implement one approach and are you now wondering what the other approach would have meant for your IFRS 9 modeling? This article compares the two approaches of IFRS 9 modeling and can, thereby, support in answering the question if this approach is still the best approach for your institution.

Background

As of January 2018, banks reporting under IFRS faced the challenge of calculating their expected credit losses in a different way (IASB, 2023). Although IFRS 9 describes principles for calculating expected credit losses, it is not prescribed exactly how to calculate these losses. This in contrast to the IRB requirements, which prescribe how to calculate (un)expected credit losses. As a consequence, banks had to define the best approach to comply with the IFRS 9 requirements. Based on our experience, we look at two prominent approaches, namely: 1) Survival Analysis and 2) the Migration Matrix approach.

Survival Analysis approach

In the credit risk domain, the basic idea behind Survival Analysis is to estimate how long an obligor remains in the portfolio as of the moment of calculation. Survival Analysis models the time to default instead of the event of default and is therefore considered appropriate for modeling lifetime processes. This approach looks at the number of obligors that are at risk at a certain moment in time and the number of obligors that default during a certain period after that moment. Results are used to construct a cumulative distribution function of the time to default. Finally, the marginal probabilities can be obtained, which, after multiplication with the LGD and EAD, yield an estimation of the expected losses over the entire lifetime of a product.

Survival Analysis is particularly useful in addressing censoring in data, which occurs when the event of interest has not occurred yet for some individuals in the data set. Censoring is generally present in the realm of lifetime PD estimations of loans. Especially mortgage loan data is usually heavily censored due to its large maturity. Therefore, defaults may not yet have occurred in the relatively small data span available.

Various extensions of Survival Analysis are proposed in academic literature, enabling the inclusion of individual characteristics (covariates) that may or may not be varying over time, which is relevant if macroeconomic variables have to be included (PIT vs. TTC). For more background on Survival Analysis used for IFRS 9 PD modeling, please refer to Bank & Eder (2021).

We encounter Survival Analysis models frequently at institutions where credit risk portfolios are not (yet) modeled through advanced IRB models. This is due to the fact that IRB models, more specifically the PD models, form a very good basis for the Migration Matrix approach (see next paragraph). In the absence of IRB models, we observe that many institutions chose for the Survival Analysis approach in order to end with one single model, rather than two separate models.

One of the issues when using the Survival Analysis approach is that banks need to develop IRB and IFRS 9 PD models independently, which generally require different data sources and structures, and various methodologies for calculating PD. Consequently, inconsistencies in the estimated PD have been observed due to the utilization of different models and misalignment of IRB and IFRS 9 results. An example of such an inconsistency is an observed increase in estimated creditworthiness according to the IRB PD model, while the IFRS 9 PD decreases. Therefore, banks that chose to independently develop IRB and IFRS 9 PD models have regularly encountered difficulties in explaining these differences to regulators and management.

Migration Matrix approach

The existing infrastructure for estimating the expected loss for capital adequacy purposes, as prescribed by IRB, may be used as source to accommodate the use of IFRS 9 provision modeling. This finding is supported by a monitoring report published by the EBA, which indicates that 59% of the institutions examined have a dependence of their IFRS 9 on their IRB model (EBA, 2021).
IRB outcomes can be used as feeder model for IFRS 9 by utilizing migration matrices. Migration matrices can be established based on the existing rating system, i.e. the IRB rating system used for capital requirements. Each of these ratings can be seen as a state of a Markov Chain, for which the migration probabilities are illustrated in a Migration Matrix. Consequently, along with the probability of default, transformations in creditworthiness may also be observed. A convenient feature of this approach is the ability to extend the horizon on which the PD is estimated by straightforward matrix multiplication. This is especially useful for complying with both IRB and IFRS 9 regulations, where 12-month and multi-period predictions are required, respectively.

Estimating the PD under IRB and IFRS 9 comes with an additional challenge; PDs for capital are required to be Through-The-Cycle (TTC), while IFRS 9 requires them to be Point-In-Time (PIT), depending on macro-economic conditions. A popular model that facilitates the conversion between these two objectives is the Single Factor Vasicek Model (Vasicek, 2002).This model shocks the TTC Migration Matrix with a single risk factor, Z, which is dependent on macroeconomic risk drivers. Consequently, PIT migration matrices are attained, conditional on a future value of Z. Forecasting Z multiple periods ahead enables one to create a series of PIT transition matrices that can be viewed as a time-inhomogeneous Markov Chain. Subsequently, lifetime estimates of the PDs can be calculated by multiplying these matrices.

One of the main issues in applying the migration matrix approach is that you cannot redevelop or recalibrate IRB and IFRS 9 models in parallel. You require to first finish the IRB model before you finish your IFRS 9 model.

Comparison Migration Matrix approach and Survival Analysis

We will now zoom in on the differences between the two approaches mentioned above. This doesn’t imply that these approaches do not share characteristics. Commonalities are, amongst other, that both approaches yield an estimate for future PD, can incorporate macro-economic expectations and are often used during stress test exercises. Table 1 presents a summary of the key features of both the Migration Matrix approach and Survival Analysis, and their interrelationships. The Migration Matrix approach is characterized by its use of a unified PD structure. When estimating different PDs for IRB and IFRS 9, this allows for a simpler explanation on why these differ. Survival Analysis offers the advantage of estimating PD on a per-obligor basis, as opposed to the Migration Matrix approach, which calculates the average PD per rating category. Accordingly, the Migration Matrix approach operates under the assumption that obligors within the same rating category possess similar average PDs over the long term which might not be true.

Whilst the above constitute the primary differences, the two approaches demonstrate many variations across the diverse categories in Table 1. Accordingly, each situation may require a distinct optimal approach implying the absence of a universal best practice.

Table 1: Migration Matrix approach vs Survival Analysis

The table of differences indicates that selecting the best approach can be challenging as both approaches have their respective advantages and disadvantages. Therefore, there is no one-size-fits-all solution, and the optimal choice depends on the specific institution’s situation. Fortunately, our experts in this field are available and eager to collaborate with you in identifying and implementing the best possible modeling approach for your institution.

References:

Bank, M., & Eder, B. (2021). A review on the Probability of Default for IFRS 9. Available at SSRN 3981339.
Gae-Carrasco, C. (2015). IFRS 9 Will Significantly Impact Banks’ Provisions and Financial Statements. Moody’s Analytics Risk Perspectives.
IASB (2023). IFRS 9 Financial Instruments. Retrieved from https://www.ifrs.org/issued-standards/list-of-standards/ifrs-9-financial-instruments/
Vasicek, O. (2002). The distribution of loan portfolio value. Risk, 160-162.

CEO Statement: Why Our Purpose Matters

May 2023
3 min read

Liquidity planning in SAP Analytics Cloud (SAC) is quite likely SAP’s response to the modernization of Cash Flow Forecasting (CFF) in Corporate Treasury, a key area in today’s treasury trends.


The Zanders purpose

Our purpose is to deliver financial performance when it counts, to propel organizations, economies, and the world forward.

Recently, we have embarked on a process to align more effectively what we do with the changing needs of our clients in unprecedented times. A central pillar of this exercise was an in-depth dialogue with our clients and business partners around the world. These conversations confirmed that Zanders is trusted to translate our deep financial consultancy knowledge into solutions that answer the biggest and most complex problems faced by the world's most dynamic organizations. Our goal is to help these organizations withstand the current macroeconomic challenges and help them emerge stronger. Our purpose is grounded on the above.

"Zanders is trusted to translate our deep financial consultancy knowledge into solutions, answering the biggest and most complex problems faced by the world's most dynamic organizations."

Laurens Tijdhof

quote

Our purpose is a reflection of what we do now, but it's also about what we need to do in the future.

It reflects our ongoing ambition - it's a statement of intent - that we should and will do more to affect positive change for both the shareholders of today and the stakeholders of tomorrow. We don't see that kind of ambition as ambitious; we see it as necessary.

The Zanders’ purpose is about the future. But it's also about where we find ourselves right now - a pandemic, high inflation and rising interest rates. And of course, climate change. At this year's Davos meeting, the latest Disruption Index was released showing how macroeconomic volatility has increased 200% since 2017, compared to just 4% between 2011 and 2016.

So, you have geopolitical volatility and financial uncertainty fused with a shifting landscape of regulation, digitalization, and sustainability. All of this is happening at once, and all of it is happening at speed.

The current macro environment has resulted in cost pressures and the need to discover new sources of value and growth. This requires an agile and adaptive approach. At Zanders, we combine a wealth of expertise with cutting-edge models and technologies to help our clients uncover hidden risks and capitalize on unseen opportunities.

However, it can't be solely about driving performance during stable times. This has limited value these days. It must be about delivering performance despite macroeconomic headwinds.

For over 30 years, through the bears, the bulls, and black swans, organizations have trusted Zanders to deliver financial performance when it matters most. We've earned the trust of CFOs, CROs, corporate treasurers and risk managers by delivering results that matter, whether it's capital structures, profitability, reputation or the environment. Our promise of "performance when it counts" isn't just a catchphrase, but a way to help clients drive their organizations, economies, and the world forward.

"For over 30 years, through the bears, the bulls, and black swans, financial guardians have trusted Zanders to deliver financial performance when it matters most."

Laurens Tijdhof

quote

What "performance when it counts" means.

Navigating the current changing financial environment is easier when you've been through past storms. At Zanders, our global team has experts who have seen multiple economic cycles. For instance, the current inflationary environment echoes the Great Inflation of the 1970s. The last 12 months may also go down in history as another "perfect storm," much like the global financial crisis of 2008. Our organization's ability to help business and government leaders prepare for what's next comes from a deep understanding of past economic events. This is a key aspect of delivering performance when it counts.

The other side of that coin is understanding what's coming over the horizon. Performance when it counts means saying to clients, "Have you considered these topics?" or "Are you prepared to limit the downside or optimize the upside when it comes to the changing payments landscape, AI, Blockchain, or ESG?" Waiting for things to happen is not advisable since they happen to you, rather than to your advantage. Performance when it counts drives us to provide answers when clients need them, even if they didn't know they needed them. This is what our relationships are about. Our expertise may lie in treasury and risk, but our role is that of a financial performance partner to our clients.

How technology factors into delivering performance when it counts.

Technology plays a critical role in both Treasury and Risk. Real-time Treasury used to be an objective, but it's now an imperative. Global businesses operate around the clock, and even those in a single market have customers who demand a 24/7/365 experience. We help transform our clients to create digitized, data-driven treasury functions that power strategy and value in this real-time global economy.

On the risk management front, technology has a two-fold power to drive performance. We use risk models to mitigate risk effectively, but we also innovate with new applications and technologies. This allows us to repurpose risk models to identify new opportunities within a bank's book of business.

We can also leverage intelligent automation to perform processes at a fraction of the cost, speed, and with zero errors. In today's digital world, this combination of next generation thinking, and technology is a key driver of our ability to deliver performance in new and exciting ways.

"It’s a digital world. This combination of next generation of thinking and next generation of technologies is absolutely a key driver of our ability to deliver performance when it counts in new and exciting ways."

Laurens Tijdhof

quote

How our purpose shapes Zanders as a business.

In closing, our purpose is what drives each of us day in and day out, and it's critical because there has never been more at stake. The volume of data, velocity of change, and market volatility are disrupting business models. Our role is to help clients translate unprecedented change into sustainable value, and our purpose acts as our North Star in this journey.

Moreover, our purpose will shape the future of our business by attracting the best talent from around the world and motivating them to bring their best to work for our clients every day.

"Our role is to help our clients translate unprecedented change into sustainable value, and our purpose acts as our North Star in this journey."

Laurens Tijdhof

quote

Demystifying blockchain security risks

May 2023
3 min read

Liquidity planning in SAP Analytics Cloud (SAC) is quite likely SAP’s response to the modernization of Cash Flow Forecasting (CFF) in Corporate Treasury, a key area in today’s treasury trends.


To fully leverage the benefits of this technology, it’s essential to understand and address security threats when implementing blockchain solutions.

As a decentralized distributed ledger technology, blockchain can add value as a platform that integrates a corporate’s operational processes with its treasury processes. This could drive treasury efficiencies and reduce cycle times. Also, compared to centralized systems, blockchain provides benefits of enhanced security. However, these benefits also have a downside. Recent reports of large-scale hacks and frauds involving hundreds of millions of dollars have shed light on the potential security risks associated with blockchain.

Phishing attacks

One of the most prevalent security risks are phishing attacks on crypto wallets. A crypto wallet is a software that securely stores and manages crypto assets, enabling users to send and receive digital assets. These attacks trick users into providing their private keys, a password to access the crypto funds, which can then be used to steal their crypto assets.

It’s worth noting that most successful phishing attacks are the result of incorrect user behavior, such as clicking on malicious links and providing login credentials. While this is a widespread IT security risk and not specifically related to the security of the blockchain technology itself, it remains a critical risk worthy of attention.

Options to protect against phishing are using a two-factor authentication system, having good security awareness trainings for users and/or using the security services of a reputable custodian.

Smart contracts exploits

Smart contracts are self-executing contracts with the terms of the agreement written directly into code and are run on a blockchain network such as Ethereum, Solana or Avalanche among others. They offer a high level of transparency and security, but they are also vulnerable to hacking and exploitation if not written correctly. A well-publicized example of this was the hack of a Compound smart contract, a blockchain protocol on the Ethereum network that enables algometric money markets, where a vulnerability in the code allowed the hacker to steal a large amount of Compound tokens.1

To prevent such incidents, it’s crucial to have independent security audits performed on all smart contracts and to follow best practices for smart contract development. Another line of defense is to opt for insurance with a specialized blockchain insurance company which can provide coverage against losses caused by platform failures, smart contract exploits or other risks.

Bridge hacks

Approximately 50% of exploits in value terms in decentralized finance occur on bridges.2 Bridges are connecting mechanisms that allow different blockchain networks to communicate with each other and are gaining popularity for their ability to facilitate seamless asset transfers and integrate the features provided by the different blockchains.

Two main types of bridges exists:

  • Centralized Bridges: Use of central party, offers a straightforward solution but requires trust in the third party and often not transparent.
  • Decentralized Bridges: Use of smart contracts provide increased transparency but may be prone to vulnerabilities due to the complexity of their design.

Due to the large amounts of funds locked in these bridges it made them attractive targets for hackers. Therefore it is advisable to conduct thorough research when selecting a bridge to work with and to regularly monitor the security measures in place.

Ponzi schemes & fraud

A Ponzi scheme is a type of crypto fraud that promises high returns with little to no risk. In this type of fraud, early investors are paid returns from the investments of later investors, creating the illusion of a profitable investment opportunity. Eventually, the scheme collapses when there are not enough new investors to pay the returns promised to earlier ones. Famous examples are Bitconnect and Plus tokens which caused multibillion losses and over two millions investors impacted.3 Another prevalent form of fraud in the blockchain industry is the misappropriation of customer funds by insiders or company leadership, as evidenced by the ongoing FTX case4, involving 8 billion dollars, where fraud allegations have been raised.

To avoid falling victim to Ponzi schemes or fraud, companies and retail investors dealing in cryptocurrency must perform due diligence before investing in any opportunity. This includes verifying the authenticity of the investment opportunity and the individuals behind it. Companies should also avoid investments that promise guaranteed high returns with little to no risk, as these are often warning signs.

Blockchain network security

Despite these challenges, blockchain technology as a whole is relatively secure. The decentralized nature of blockchain networks makes it more difficult for malicious actors to manipulate or attack the system, as there is no central point of control that can be targeted. Additionally, cryptographic techniques such as hashing, digital signatures, and consensus algorithms help to ensure the integrity and security of the data stored on the blockchain. The robustness of this technology is evident from the fact that popular and established networks such as Bitcoin and Ethereum have not faced any successful exploits or attacks over the years . However, there have been instances of successful hacks and attacks on less popular blockchain networks.

In conclusion

The utilization of blockchain technology in various industries has the potential to revolutionize the way we conduct transactions and manage data. However, it’s imperative to weigh the benefits against the potential security risks. From phishing attacks on wallets to Ponzi schemes and smart contract risks, organizations must take the necessary precautions to ensure their assets are protected including:

  • Use two-factor authentication, have security awareness trainings, and/or use services from a reputable custodian to protect against phishing attacks on crypto wallets.
  • Have independent security audits of your smart contracts and consider taking specialized insurance.
  • Conduct thorough research when selecting a bridge and regularly monitor the security measures in place.
  • Perform due diligence before investing and avoid promises of high returns with little risk.
  • Be cautious when dealing with less popular blockchain networks.

Zanders Blockchain Consulting Services
For Treasurers, the need for reliable and real-time data is great when working with multiple (external) stakeholders on a single process. Blockchain offers valuable support in this regard. It can also help with the creation of smart contracts or the use of crypto within the payment process. Since recently, Zanders offers blockchain consulting services to support corporates, financial institutions and public sector entities in reaping the benefits of blockchain and managing its additional security risks. By focusing on understanding the why of its application, and drafting a blueprint of the preferred solution, we can help define the business case for using blockchain. Subsequently, we can help selecting the best technology platform and third parties.
If you would like to discuss how blockchain, digital assets or Web3 can impact your business, please reach out to our experts, Ian Haegemans, Robert Richter or Justus Schleicher via +31 88 991 02 00.

Sources
(1) https://www.coindesk.com/business/2021/10/03/66m-in-tokens-added-to-recently-hacked-still-vulnerable-compound-contract
(2) Report: Half of all DeFi exploits are cross-bridge hacks (cointelegraph.com)
(3) https://blockchain.news/news/chinese-police-arrest-kingpins-plus-token-bitcoin-scam-worth-5-7-billion
(4) https://www.ft.com/content/6613eadb-eea0-42f8-8d92-fe46ad8fcf8c

ISO 20022 MT MX migration – What does this really mean for Corporate Treasury?

April 2023
3 min read

Liquidity planning in SAP Analytics Cloud (SAC) is quite likely SAP’s response to the modernization of Cash Flow Forecasting (CFF) in Corporate Treasury, a key area in today’s treasury trends.


The start of the migration from the SWIFT FIN format to the new ISO 20022 XML format, which is a banking industry migration that must be completed by November 2025.

Whilst at this stage the focus is primarily on the interbank space, there will be some impact on corporate treasury within this migration period. Zanders experts Eliane Eysackers and Mark Sutton demystify what is now happening in the global financial messaging space, including the possible impacts, challenges and opportunities that could now exist.

What is changing? 

The SWIFT MT-MX migration is initially focused on a limited number of SWIFT FIN messages within the cash management space – what are referred to as category 1 (customer payments and cheques), 2 (financial institution transfers) and 9 (cash management and customer status) series messages. This can translate to cross border payments (e.g., MT103, MT202) in addition to the associated balance and transaction reporting (e.g., MT940, MT942) within the interbank messaging space.   

Is corporate treasury impacted during the migration phase? 

This is an interesting and relevant question. Whilst the actual MT-MX migration is focused on the interbank messaging space, which means existing SWIFT SCORE (Standardised Corporate Environment), SWIFT MACUGs (member administered closed user groups) and of course proprietary host to host connections should not be impacted directly, there could be a knock-on effect in the following key areas:  

  •  The first issue pertains to cross-border payments, which are linked to the address data required in interbank payments. As the financial industry is looking to leverage more structured information, this could create a friction point as both the MT101 and MT103 SWIFT messages that are used in the corporate to bank space only supports unstructured address data. This problem will could also exist where a legacy bank proprietary file format is being used, as these have also typically just offered unstructured address data. This could mean corporates will need to update the current address logic and possibly the actual file format that is being used in the corporate to bank space. 
  • Secondly, whilst banking partners are expected to continue providing the MT940 end of day balance and transaction report post November 2025, there is now a risk where a corporate is using a proprietary bank statement consolidation service. Today, a global corporate might prefer not to connect directly to its local in-country banking partners as payment volumes are low. Under these circumstances the local in-country banks might be sending the MT940 bank statement to the core banking partner, who will then send this directly to the corporate.  However, after November 2025, these local in-country banks will not be able to send the MT940 statement over the SWIFT interbank network, it will only be possible to send the camt.053 xml bank statement to the core banking partner. So from November 2025, if the core banking partner cannot back synchronise the camt.053 statement to the legacy MT940 statement, this will require the corporate to also migrate onto the camt.053 end of day bank statement or consider other alternatives.  
  • Finally, from November 2025, the camt.053 xml bank statement will be the defacto interbank statement format. This provides the opportunity for much richer and more structured statement as the camt.053 message has almost 1,600 fields. There is therefore an opportunity cost if the data is force truncated to be compatible with the legacy MT940 statement format.

So, what are the benefits of moving to ISO20022 MX migration

At a high level, the benefits of ISO 20022 XML financial messaging can be boiled down into the richness of data that can be supported through the ISO 20022 XML messages. You have a rich data structure, so each data point should have its own unique xml field. Focusing purely on the payment’s domain, the xml payment message can support virtually all payment types globally, so this provides a unique opportunity to both simplify and standardise your customer to bank payment format. Moving onto reporting, the camt.053 statement report has almost 1,600 fields, which highlights the richness of information that can be supported in a more structured way. The diagram below highlights the key benefits of ISO20022 XML messaging. 

Fig 1: Key benefits of ISO20022 XML messaging

What are the key challenges around adoption for corporate treasury? 

Zanders foresees several challenges for corporate treasury around the impact of the SWIFT MT to MX migration, primarily linked to corporate technical landscape and system capabilities, software partner capabilities and finally, partner bank capabilities. All these areas are interlinked and need to be fully considered. 

What are my next steps? 

ISO20022 is now the de-facto standard globally within the financial messaging space – SWIFT is currently estimating that by 2025, 80% of the RTGS volumes will be ISO 20022 based with all reserve currencies either live or having declared a live date.  

However, given the typical multi-banking corporate eco-system, Zanders believes the time is now right to conduct a more formal impact assessment of this current eco-system. There will be a number of key questions that now need to be considered as part of this analysis, including: 

  • Considering the MT-MX migration will be using the xml messages from the 2019 ISO standards release, what are my partner banks doing around the adoption of these messages for the corporate community?
  • If I am currently using XML messages to make payments, do I need to change anything? 
  • Do I currently use a statement reporting consolidator service and how will this be impacted? 
  • How is my address data currently set-up and does my existing system support a structured address? 
  • What are my opportunities to drive greater value out this exercise? 

In Summary 

The corporate treasury community can reap substantial benefits from the ISO 20022 XML financial messages, which offer more structured and comprehensive data in addition to a more globally standardized format. Making the timing ideal for corporates to further analyse and assess the positive impact ISO 20022 can have on the key questions proposed above 

Global disruptions demand Treasuries to act fast

April 2023
3 min read

Liquidity planning in SAP Analytics Cloud (SAC) is quite likely SAP’s response to the modernization of Cash Flow Forecasting (CFF) in Corporate Treasury, a key area in today’s treasury trends.


 In today’s world, supply chain disruptions are consequences of operating in an integrated and highly specialized global economy. Along with affecting the credit risk of impacted suppliers, these disruptions are demanding Treasuries to operate with increased working capital.

In March 2021, a vessel was forced aground due to intense winds at Egypt’s Suez Canal, creating a bottleneck involving 100 ships. Given that the Suez Canal accommodates 12% of global trade and the fact that one-tenth of the daily total global oil consumption was caught in the bottleneck, it was no surprise that the international oil market was rattled, and numerous supply chains were affected.1

A butterfly effect

This is reminiscent of a concept known as butterfly effect, where a minor fluctuation such as a butterfly flapping its wings proves to have an effect, however small, on the path a tornado takes on the other side of the globe.

To further complicate matters, this disruption transpired when the global shipping industry was already destabilized due to the coronavirus pandemic.This pandemic affected the global economy and supply chains in particular like no other event in the past several decades. Entire cities were locked down and many businesses were at a standstill. It may be impossible to predict black swan events that disrupt global supply chains. However, it is possible to reach fairly accurate assumptions about certain supply chains based on knowledge at hand.

Leveraging supply chains

The Russian invasion of Ukraine will no doubt impact the industries that have suppliers in Ukraine. Another lockdown in China will have repercussions for the supply chains intertwined there. With these types of constraints on the supply chains, procurement divisions are stocking up on inventory and raw materials, which in turn further aggravates the inflation problem the global economy is currently facing. Issues like these are demanding many treasurers to operate with increased working capital, along with affecting the credit risk of impacted suppliers. Treasurers around the world should act fast to take advantage of the financial benefits that today’s global economy is bestowing on organizations that are quick to adapt to the constantly changing business environment. Treasurers can even start leveraging supply chains to work in their favor by utilizing Supply Chain Finance (SCF) solutions.

Decreasing the DSO

What does the concept of SCF mean and what are its implications? Let’s start with the different parties involved in a typical SCF transaction, like reverse factoring. We have the supplier, the buyer, and the bank. Let’s suppose the buyer enters an agreement to purchase goods from the supplier. In most cases, the supplier will ship the goods to the buyer on credit. The payment terms may vary from 10 days to 60 or more days. The average number of days it takes a company to receive payment for a sale is known as days sales outstanding (DSO). The objective of companies is to keep the DSO as low as possible. This implies that the supplier is receiving its payments quickly from the buyer and has a positive effect on the cash conversion cycle (CCC) of the supplier. The CCC indicates how many days it takes a company to convert cash into inventory and back into cash during the sales process. Unfortunately, many companies struggle with a high DSO, which suggests they are either experiencing delays in receiving payments or have long payment terms. A high DSO can lead to cash flow problems, but implementing a SCF solution might be wise response. Having a healthy working capital is a cornerstone to building a successful business, especially for growing and/or leveraged companies.

Why cash flow is crucial

American billionaire businessman Michael Dell once acknowledged: “We were always focused on our profit and loss statement. But cash flow was not a regularly discussed topic. It was as if we were driving along, watching only the speedometer, when in fact we were running out of gas.3

A company may be profitable, but if it has poor cash flow, it will struggle to meet its liabilities or properly invest its excess cash. Because cash is a crucial element to a successful business, companies will strategically hold onto it as long as possible. If their credit terms indicate that they have 30 days to pay an invoice, it is quite likely that they will wait as close to the deadline as possible before they make the payment.

Furthermore, a buyer with a strong credit rating and powerful brand recognition may demand more generous credit terms. These considerations affect a financial ratio known as days payable outstanding (DPO). The DPO indicates the average time that a company takes to pay its invoices. A higher DPO implies that a company can maximize its working capital by retaining cash for a longer duration. This cash can be used for short-term investments or other purposes that a company determines will optimize its finances. However, a high DPO can also indicate that the company is struggling to meet its financial obligations.

An example

The diagram below depicts a scenario where the supplier invoices the buyer, hoping to receive payment in 30 days. Unfortunately, the buyer needs funds for its operating activities, and furthermore must borrow from the bank to meet its liabilities. It is also possible that the buyer pays late so it can hold onto cash longer or due to roadblocks in the invoice approval process. In the meantime, the supplier is also experiencing cash flow challenges, and it too borrows from the bank. (Of course, both the buyer and the supplier could also use a revolving credit line to access capital, but to simplify this example, we will assume they are borrowing from the bank). The buyer eventually approves the invoice for payment on day 55 and the supplier receives the payment on day 60. The buyer has a high DPO at the expense of the supplier also having a high DSO.

Figure 1: A scenario of a supplier hoping to receive payment in 30 days.

Reverse factoring

What can a company do if it is struggling with its working capital? Suppose a supplier has a dozen buyers, some which pay on time, but others unfortunately are facing their own cash flow problems and are not able to pay within the agreed terms. Wouldn’t it be nice to receive payment within a week from some of the buyers to avoid having a cash flow problem? SCF offers a solution.

To help illustrate this concept, let’s explore a more familiar financial concept known as factoring. With factoring, a company sells its accounts receivable to a third party. SCF is sometimes knowns as ‘reverse factoring’, because a supplier will leverage a buyer’s strong credit rating and select certain invoices to be paid early by a third-party financier, typically a bank. The buyer would then be responsible for paying the bank. In certain types of SCF arrangements, instead of paying an invoice in 30 days, the bank will offer the buyer to pay in, let’s say, 60 days – but for a fee. This could potentially increase the buyer’s DPO.

The supplier, on the other hand, receives its payment sooner from the bank – reducing its DSO – than it would have from the buyer, but at a discount. It is important to note that the discount should be less than the interest the supplier would have incurred if it had borrowed from the bank. This is possible because the discount is calculated based on the creditworthiness of the buyer, instead of the supplier. Many suppliers who lack credit or have poor credit would find this an advantageous option to access cash. However, not all suppliers may be able to reap the benefits of an SCF agreement. For them, borrowing from a bank or factoring receivables are additional options they can explore.

Dynamic discounting

Another term often used when discussing these types of financing options is dynamic discounting. This is similar to reverse factoring in that a supplier receives early payment on an invoice at a discount. However, unlike SCF, dynamic discounting is financed by the buyer as opposed to a third-party financier. Due to the complexity of SCF arrangements between the suppler, the buyer, and the bank, a company often uses the expertise of banks or the capability of a Treasury Management System (TMS). Below is a diagram of what an SCF solution would look like utilizing a TMS:

Whether a company should implement a TMS, which vendor it should utilize, and determining if SCF is a viable solution for that organization are complex questions. Furthermore, because of the globalized environment that companies operate in and the impact of crises like the coronavirus pandemic or a bottleneck at a major canal, an increasing number of organizations are turning to the expertise of consultants to help navigate these intricate matters.

Zanders’ SCF solutions

Zanders is a world-leading consultancy firm specializing in treasury, risk, and finance. It employs over 250 professionals in 9 countries across 4 continents. Powered by almost 30 years of experience and driven by innovation, Zanders has an extensive track record of working with corporations, financial institutions, and public sector entities. Leveraging this extensive background, Zanders can evaluate the assorted options that organizations are exploring to enhance their treasury functions.

With its unique market position, Zanders is able to engage in projects ‘from ideas to implementation’. Whether organizations are trying to stay afloat in today’s challenging global economy or seeking to stay ahead of the curve, they should reap the benefits of modern technology and various SCF solutions that are currently being offered in today’s dynamic business environment. Amid a rapidly changing world being transformed by technological advancement, Zanders welcomes the opportunity to assist clients achieve their treasury and finance objectives.

If you’re interested in learning more about Supply Chain Finance and how your Treasury can properly anticipate disruptions in global supply chains, please reach out to Arif Ali via +1 6467703875.

Footnotes:

[1] https://www.nytimes.com/2021/03/24/world/middleeast/suez-canal-blocked-ship.html

[2] https://www.bbc.com/news/world-middle-east-56505413

[3] https://cfoperspective.com/profit-vs-cash-flow/

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.