A guide to optimize SAP Treasury business partner design and maintenance 

December 2023
8 min read

In SAP Treasury, business partners represent counterparties with whom a corporation engages in treasury transactions, including banks, financial institutions, and internal subsidiaries.


Additionally, business partners are essential in SAP for recording information related to securities issues, such as shares and funds. 

The SAP Treasury Business Partner (BP) serves as a fundamental treasury master data object, utilized for managing relationships with both external and internal counterparties across a variety of financial transactions; including FX, MM, derivatives, and securities. The BP master data encompasses crucial details such as names, addresses, contact information, bank details, country codes, credit ratings, settlement information, authorizations, withholding tax specifics, and more. 

Treasury BPs are integral and mandatory components within other SAP Treasury objects, including financial instruments, cash management, in-house cash, and risk analysis. As a result, the proper design and accurate creation of BPs are pivotal to the successful implementation of SAP Treasury functionality. The creation of BPs represents a critical step in the project implementation plan. 

Therefore, we aim to highlight key specifics for professionally designing BPs and maintaining them within the SAP Treasury system. The following section will outline the key focus areas where consultants need to align with business users to ensure the smooth and seamless creation and maintenance of BPs. 

Structure of the BPs: 

The structure of BPs may vary depending on a corporation's specific requirements. Below is the most common structure of treasury BPs: 

Group BP – represents a parent company, such as the headquarters of a bank group or corporate entity. Typically, this level of BP is not directly involved in trading processes, meaning no deals are created with this BP. Instead, these BPs are used for: a. reflecting credit ratings, b. limiting utilization in the credit risk analyzer, c. reporting purposes, etc. 

Transactional BP – represents a direct counterparty used for booking deals. Transactional BPs can be divided into two types: 

   - External BPs – represent banks, financial institutions, and security issuers. 

   - Internal BPs – represent subsidiaries of a company. 

Naming convention of BPs 

It is important to define a naming convention for the different types of BPs, and once defined, it is recommended to adhere to the blueprint design to maintain the integrity of the data in SAP. 

Group BP ID: Should have a meaningful ID that most business users can understand. Ideally, the IDs should be of the same length. For example: ABN AMRO Group = ABNAMR or ABNGRP, Citibank Group = CITGRP or CITIBNK. 

External BP ID: Should also have a meaningful ID, with the addition of the counterparty's location. For example: ABN AMRO Amsterdam – ABNAMS, Citibank London – CITLON, etc. 

Internal BP ID: The main recommendation here is to align the BP ID with the company code number. For example, if the company code of the subsidiary is 1111, then its BP ID should be 1111. However, it is not always possible to follow this simple rule due to the complexity of the ERP and SAP Treasury landscape. Nonetheless, this simple rule can help both business and IT teams find straightforward solutions in SAP Treasury. 

The length of the BP IDs should be consistent within each BP type. 

Maintenance of Treasury BPs 

1. BP Creation: 

Business partners are created in SAP using the t-code BP. During the creation process, various details are entered to establish the master data record. This includes basic information such as name, address, contact details, as well as specific financial data such as bank account information, settlement instructions, WHT, authorizations, credit rating, tax residency country, etc. 

Consider implementing an automated tool for creating Treasury BPs. We recommend leveraging SAP migration cockpit, SAP scripting, etc. At Zanders we have a pre-developed solution to create complex Treasury BPs which covers both SAP ECC and most recent version of SAP S/4 HANA. 

2. BP Amendment: 

Regular updates to BP master data are crucial to ensure accuracy. Changes in addresses, contact information, or payment details should be promptly recorded in SAP. 

3. BP Release: 

Treasury BPs must be validated before use. This validation is carried out in SAP through a release workflow procedure. We highly recommend activating such a release for the creation and amendment of BPs, and nominating a person to release a BP who is not authorized to create/amend a BP.  
BP amendments are often carried out by the Back Office or Master Data team, while BP release is handled by a Middle Office officer.  

4. BP Hierarchies: 

Business partners can have relationships as described, and the system allows for the maintenance of these relationships, ensuring that accurate links are established between various entities involved in financial transactions. 

5. Alignment: 

During the Treasury BP design phase, it is important to consider that BPs will be utilized by other teams in a form of Vendors, Customers, or Employees. SAP AP/AR/HR teams may apply different conditions to a BP, which can have an impact on Treasury functions. For instance, the HR team may require bank details of employees to be hidden, and this requirement should be reflected in the Treasury BP roles. Additionally, clearing Treasury identification types or making AP/AR reconciliation GL accounts mandatory for Treasury roles could also be necessary.  

Transparent and effective communication, as well as clear data ownership, are essential in defining the design of the BPs. 

Conclusion 

The design and implementation of BPs require expertise and close alignment with treasury business users to meet all requirements and consider other SAP streams.  

At Zanders, we have a strong team of experienced SAP consultants who can assist you in designing BP master data, developing tools to create/amend the BPs meeting strict treasury segregation of duties and the clients IT rules and procedures. 

ISO 20022 XML version 9 – So what’s new?

December 2023
8 min read

In SAP Treasury, business partners represent counterparties with whom a corporation engages in treasury transactions, including banks, financial institutions, and internal subsidiaries.


But the adoption of ISO 20022 XML messaging goes beyond SWIFT’s adoption in the interbank financial messaging space – SWIFT are currently estimating that by 2025, 80% of the RTGS (real time gross settlement) volumes will be ISO 20022 based with all reserve currencies either live or having declared a live date. What this means is that ISO 20022 XML is becoming the global language of payments. In this fourth article in the ISO 20022 series, Zanders experts Eliane Eysackers and Mark Sutton provide some valuable insights around what the version 9 payment message offers the corporate community in terms of richer functionality.  

A quick recap on the ISO maintenance process?

So, XML version 9. What we are referencing is the pain.001.001.09 customer credit transfer initiation message from the ISO 2019 annual maintenance release. Now at this point, some people reading this article will be thinking they are currently using XML version 3 and now we talking about XML version 9. The logical question is whether version 9 is the latest message and actually, we expect version 12 to be released in 2024. So whilst ISO has an annual maintenance release process, the financial industry and all the associated key stakeholders will be aligning on the XML version 9 message from the ISO 2019 maintenance release. This version is expected to replace XML version 3 as the de-facto standard in the corporate to bank financial messaging space.

What new functionality is available with the version 9 payment message?

Comparing the current XML version 3 with the latest XML version 9 industry standard, there are a number of new tags/features which make the message design more relevant to the current digital transformation of the payment’s ecosystem. We look at the main changes below:

  • Proxy: A new field has been introduced to support a proxy or tokenisation as its sometimes called. The relevance of this field is primarily linked to the new faster payment rails and open banking models, where consumers want to provide a mobile phone number or email address to mask the real bank account details and facilitate the payment transfer. The use of the proxy is becoming more widely used across Asia with the India (Unified Payments Interface) instant payment scheme being the first clearing system to adopt this logic. With the rise of instant clearing systems across the world, we are starting to see a much greater use of proxy, with countries like Australia (NPP), Indonesia (BI-FAST), Malaysia (DuitNow), Singapore (FAST) and Thailand (Promptpay) all adopting this feature.
  • The Legal Entity Identifier (LEI): This is a 20-character, alpha-numeric code developed by the ISO. It connects to key reference information that enables clear and unique identification of legal entities participating in financial transactions. Each LEI contains information about an entity’s ownership structure and thus answers the questions of 'who is who’ and ‘who owns whom’. Simply put, the publicly available LEI data pool can be regarded as a global directory, which greatly enhances transparency in the global marketplace. The first country to require the LEI as part of the payment data is India, but the expectation is more local clearing system’s will require this identifier from a compliance perspective.
  • Unique End-to-end Transaction Reference (commonly known as a UETR): This is a string of 36 unique characters featured in all payment instruction messages carried over the SWIFT network. UETRs are designed to act as a single source of truth for a payment and provide complete transparency for all parties in a payment chain, as well as enable functionality from SWIFT gpi (global payments innovation)1, such as the payment Tracker.
  • Gender neutral term: This new field has been added as a name prefix.
  • Requested Execution Date: The requested execution date now includes a data and time option to provide some additional flexibility.
  • Structured Address Block: The structured address block has been updated to include the Building Name.

In Summary

Whilst there is no requirement for the corporate community to migrate onto the XML version 9 message, corporate treasury should now have the SWIFT ISO 20022 XML migration on their own radar in addition to understanding the broader global market infrastructure adoption of ISO 20022. This will ensure corporate treasury can make timely and informed decisions around any future migration plan.

Notes:

  1. SWIFT gpi is a set of standards and rules that enable banks to offer faster, more transparent, and more reliable cross-border payments to their customers.

Blockchain-based Tokenization for decentralized Issuance and Exchange of Carbon Offsets

November 2023
8 min read

In SAP Treasury, business partners represent counterparties with whom a corporation engages in treasury transactions, including banks, financial institutions, and internal subsidiaries.


Carbon offset processes are currently dominated by private actors providing legitimacy for the market. The two largest of these, Verra and Gold Standard, provide auditing services, carbon registries and a marketplace to sell carbon offsets, making them ubiquitous in the whole process. Due to this opacity and centralisation, the business models of the existing companies was criticised regarding its validity and the actual benefit for climate action. By buying an offset in the traditional manner, the buyer must place trust in these players and their business models. Alternative solutions that would enhance the transparency of the process as well as provide decentralised marketplaces are thus called for.

The conventional process

Carbon offsets are certificates or credits that represent a reduction or removal of greenhouse gas emissions from the atmosphere. Offset markets work by having companies and organizations voluntarily pay for carbon offsetting projects. Reasons for partaking in voluntary carbon markets vary from increased awareness of corporate responsibility to a belief that emissions legislation is inevitable, and it is thus better to partake earlier.

Some industries also suffer prohibitively expensive barriers for lowering their emissions, or simply can’t reduce them because of the nature of their business. These industries can instead benefit from carbon offsets, as they manage to lower overall carbon emissions while still staying in business. Environmental organisations run climate-friendly projects and offer certificate-based investments for companies or individuals who therefore can reduce their own carbon footprint. By purchasing such certificates, they invest in these projects and their actual or future reduction of emissions. However, on a global scale, it is not enough to simply lower our carbon footprint to negate the effects of climate change. Emissions would in practice have to be negative, so that even a target of 1,5-degree Celsius warming could be met. This is also remedied by carbon credits, as they offer us a chance of removing carbon from the atmosphere. In the current process, companies looking to take part in the offsetting market will at some point run into the aforementioned behemoths and therefore an opaque form of purchasing carbon offsets.

The blockchain approach

A blockchain is a secure and decentralised database or ledger which is shared among the nodes of a computer network. Therefore, this technology can offer a valid contribution addressing the opacity and centralisation of the traditional procedure. The intention of the first blockchain approaches were the distribution of digital information in a shared ledger that is agreed on jointly and updated in a transparent manner. The information is recorded in blocks and added to the chain irreversibly, thus preventing the alteration, deletion and irregular inclusion of data.

In the recent years, tokenization of (physical) assets and the creation of a digital version that is stored on the blockchain gained more interest. By utilizing blockchain technology, asset ownership can be tokenized, which enables fractional ownership, reduces intermediaries, and provides a secure and transparent ledger. This not only increases liquidity but also expands access to previously illiquid assets (like carbon offsets). The blockchain ledger allows for real-time settlement of transactions, increasing efficiency and reducing the risk of fraud. Additionally, tokens can be programmed to include certain rules and restrictions, such as limiting the number of tokens that can be issued or specifying how they can be traded, which can provide greater transparency and control over the asset.

Blockchain-based carbon offset process

The tokenisation process for carbon credits begins with the identification of a project that either captures or helps to avoid carbon creation. In this example, the focus is on carbon avoidance through solar panels. The generation of solar electricity is considered an offset, as alternative energy use would emit carbon dioxide, whereas solar power does not.

The solar panels provide information regarding their electricity generation, from which a figure is derived that represents the amount of carbon avoided and fed into a smart contract. A smart contract is a self-executing application that exist on the blockchain and performs actions based on its underlying code. In the blockchain-based carbon offset process, smart contracts convert the different tokens and send them to the owner’s wallet. The tokens used within the process are compliant with the ERC-721 Non-Fungible Token (NFT) standard, which represents a unique token that is distinguishable from others and cannot be exchanged for other units of the same asset. A practical example is a work of art that, even if replicated, is always slightly different.

In the first stage of the process, the owner claims a carbon receipt, based on the amount of carbon avoided by the solar panel. Thereby the aggregated amount of carbon avoided (also stored in a database just for replication purposes) is sent to the smart contract, which issues a carbon receipt of the corresponding figure to the owner. Carbon receipts can further be exchanged for a uniform amount of carbon credits (e.g. 5 kg, 10 kg, 15 kg) by interacting with the second smart contract. Carbon credits are designed to be traded on the decentralised marketplace, where the price is determined by the supply and demand of its participants. Ultimately, carbon credits can be exchanged for carbon certificates indicating the certificate owner and the amount of carbon offset. Comparable with a university diploma, carbon certificates are tied to the address of the owner that initiated the exchange and are therefore non-tradable. Figure 1 illustrates the process of the described blockchain-based carbon offset solution:

Figure 1: Process flow of a blockchain-based carbon offset solution

Conclusion

The outlined blockchain-based carbon offset process was developed by Zanders’ blockchain team in a proof of concept. It was designed as an approach to reduce dependence on central players and a transparent method of issuing carbon credits. The smart contracts that the platform interacts with are implemented on the Mumbai test network of the public Polygon blockchain, which allows for fast transaction processing and minimal fees. The PoC is up and running, tokenizing the carbon savings generated by one of our colleagues photovoltaic system, and can be showcased in a demo. However, there are some clear optimisations to the process that should be considered for a larger scale (commercial) setup.

If you're interested in exploring the concept and benefits of a blockchain-based carbon offset process involving decentralised issuance and exchange of digital assets, or if you would like to see a demo, you can contact Robert Richter or Justus Schleicher.

Embracing Risk Management Excellence: An Interview with Zanders’ New Partner, Brecht van den Driessche

October 2023
8 min read

In SAP Treasury, business partners represent counterparties with whom a corporation engages in treasury transactions, including banks, financial institutions, and internal subsidiaries.


Today, we engage in a conversation with Brecht van den Driessche, a new addition to the Zanders team, to explore his motivations for joining Zanders and his vision for the future of risk management.

Q: Why did you choose Zanders?

A: I've been familiar with Zanders for over a decade, and what has consistently impressed me is the professionalism and deep expertise in Risk Management demonstrated by its people. Consultancy is inherently a people-centric business, and the combination of professionalism with an engaging and enjoyable working environment was a key factor in my decision to join the Zanders team.

Q: What are your focus areas and goals for the short term and long term?

A: The landscape of expectations for Risk Managers and their regulators is rapidly evolving. Recent events such as the collapse of Silicon Valley Bank and the takeover of Credit Suisse by UBS have highlighted the critical importance of proper Risk Management. Financial institutions must invest in a centralized risk function and supporting systems to enhance transparency and real-time Risk Management. Worldwide, there is a clear trend among banks to centralize data, improve Risk Management systems, and perform more frequent, granular, and standardized risk calculations and disclosures. Regulators are increasingly pushing banks to move away from spreadsheets and manage their financial risks with professional, often vendor-based systems. As a result, banks are moving away from legacy systems and heavily investing in new Risk Management Systems.

My primary focus is to assist our customers in embracing further digitalization to maximize the benefits of these investments. This includes strategic benchmarking, optimization, selection, and the implementation of fit-for-purpose Risk Management systems. To achieve this, we collaborate closely with a select group of world-leading suppliers of risk technology.

The ultimate goal is for Zanders to become the go-to expert for our clients, providing them with robust Risk Management systems to effectively manage financial risks and make informed decisions.

Q: How were your first weeks at Zanders?

A: Right from day one, I felt the positive energy and warmth that characterizes the Zanders team. Simultaneously, around 20 new colleagues embarked on their Zanders journeys across Europe, and the onboarding process was exceptionally smooth. I've already had the pleasure of meeting many colleagues, clients, and partners, and I am genuinely convinced that my decision to join Zanders was the perfect career move.

Q: Anything you want to share with the outside world about this career move?

A: If you're curious about our ambitions and how we can help you achieve yours, don't hesitate to reach out. Drop me a message, and let's connect.

In a world of ever-evolving risks and escalating expectations in risk management, Zanders plays a pivotal role in helping organizations navigate these challenges, propelling them toward success. With our unwavering focus on professionalism, expertise, and a commitment to embracing digitalization, we stand as a trusted partner for those in the finance industry. To learn more about us, please visit our About Zanders page.

How to manage SWIFT MT/MX Migration in SAP 

October 2023
8 min read

In SAP Treasury, business partners represent counterparties with whom a corporation engages in treasury transactions, including banks, financial institutions, and internal subsidiaries.


SWIFT now supports the exchange of ISO 20022 XML or MX message via the so-called FINplus network. In parallel, the legacy MT format messages remain to be exchanged over the ‘regular’ FIN network; The MT flow for message categories 1 (customer payments), 2 (FI transfers) and 9 (statements) through the FIN network will be decommissioned per November 2025. 

As such, between March 2023 and November 2025, financial institutions need to be able to receive and process MX messages through FINplus on the inbound side, and optionally send MX messages or MT messages for outbound messaging. After that period, only MX will be allowed.  

CBPR+ and HVPS+ 

Another important aspect of the MX migration is the development of the CBPR+ and HVPS+ specifications within the ISO20022 XML standard. These specifications dictate how an XML message should be populated in terms of data and field requirements for Cross Border Payments (CBPR+) and Domestic High Value Payments (HVPS+). Note that HVPS+ refers to domestic RTGS clearing systems and a number of countries are in the process of making the domestic clearing systems native ISO20022 XML-compliant.  

Impact for Corporates 

As of today, there should be no immediate need for corporates to change. However, it is advised to start assessing impact and to start planning for change if needed. We give you some cases to consider: 

  1. A corporate currently exchanging e.g. MT101/MT103/MT210 messages towards its house bank via SWIFT FIN Network to make cross border payments, e.g. employing a SWIFT Service Bureau or an Alliance connection. This flow will cease to work after November 2025. If this flow is relevant to your company, it needs attention to be replaced. 
  2. Another case is where, for example, an MT101 is exchanged with a house bank as a file over the FileAct network. Now it depends purely on the house bank’s capabilities to continue supporting this flow after 2025; it could offer a service to do a remapping of your MT message into an MX. This needs to be checked with the house banks. 
  3. The MT940 message flow from the house bank via FIN also requires replacement. 
  4. With respect to the MT940 file flow from house bank via FileAct, we expect little impact as we think most banks will continue supporting the MT940 format exchange as files. We do recommend to check with your house bank to be sure. 
  5. High Value Payments for Domestic Japanese Yen using Zengin format; the BOJ-NET RTGS clearing system has already completed the migration to ISO20022 XML standard. Check with your house bank when the legacy payment format will become unsupported and take action accordingly.  

These were just some examples and should not be considered an exhaustive list.  

    In addition, moving to the ISO20022 XML standard can also provide some softer benefits. We discussed this in a previously published article

    Impact on your SAP implementation 

    So you have determined that the MT/MX migration has impact and that remediating actions need to be taken. What does that look like in SAP? 

    First of all, it is very important to onboard the bank to support you with your change. Most typically, the bank needs to prepare its systems to be able to receive a new payment file format from your end. It is good practice to first test the payment file formatting and receive feedback from the banks implementation manager before going live with it.  

    On the incoming side, it is advisable to first request a number of production bank statements in e.g. the new CAMT.053 format, which can be analyzed and loaded in your test system. This will form a good basis for understanding the changes needed in bank statement posting logic in the SAP system.  

    PAYMENTS 

    In general, there are two ways of generating payment files in SAP. The classical one is via a payment method linked to a Payment Medium Workbench (PMW) format and a Data Medium Exchange (DME) tree. This payment method is then linked to your open items which can be processed with the payment run. The payment run then outputs the files as determined in your DME tree. 

    In this scenario, the idea is to simply setup a new payment method and link it to a desired PMW/DME output like pain.001.001.03. These have long been pre-delivered in standard SAP, in both ECC and S/4. It may be necessary to make minor mapping corrections to meet country- or bank-specific data requirements. Under most circumstances this can be achieved with a functional consultant using DME configuration. Once the payment method is fully configured, it can be linked to your customer and vendor master records or your treasury business partners, for example. 

    The new method of generating payment files is via the Advanced Payment Management (SAP APM) module. SAP APM is a module that facilitates the concepts of centralizing payments for your whole group in a so-called payment factory. APM is a module that’s only available in S/4 and is pushed by SAP AG as the new way of implementing payment factories. 

    Here it is a matter of linking the new output format to your applicable scenario or ‘payment route’.  

    BANK STATEMENTS 

    Classical MT940 bank statements are read by SAP using ABAP logic. The code interprets the information that is stored in the file and saves parts of it to internal database tables. The stored internal data is then interpreted a second time to determine how the posting and clearing of open items will take place. 

    Processing of CAMT.053 works a bit differently, interpreting the data from the file by a so-called XSLT transformation. This XSLT transformation is a configurable mapping where a CAMT.053 field maps into an internal database table field. SAP has a standard XSLT transformation package that is fairly capable for most use cases. However, certain pieces of useful information in the CAMT.053 may be ignored by SAP. An adjustment to the XSLT transformation can be added to ensure the data is picked up and made available for further interpretation by the system. 

    Another fact to be aware of is the difference in Bank Transaction Codes (BTC) between MT940 and CAMT.053. There could be a different level of granularity and the naming convention is different. BTC codes are the main differentiator in SAP to control posting logic.  

    SAP Incoming File Mapping Engine (IFME) 

    SAP has also put forward a module called Incoming File Mapping Engine (IFME). It serves the purpose as a ‘remapper’ of one output format to another output format. As an example, if your current payment method outputs an MT101, the remapper can take the pieces of information from the MT101 and save it in a pain.001 XML file.  

    Although there may be some fringe scenarios for this solution, we do not recommend such an approach as MT101 is generally weaker in terms of data structure and content than XML. Mapping it into some other format will not solve the problems that MT101 has in general. It is much better to directly generate the appropriate format from the internal SAP data directly to ensure maximum richness and structure. However, this should be considered as a last resort or if the solution is temporary. 

    SAP Treasury conference in Amsterdam 

    October 2023
    8 min read

    In SAP Treasury, business partners represent counterparties with whom a corporation engages in treasury transactions, including banks, financial institutions, and internal subsidiaries.


    Of the many attending corporates and partners were offered the opportunity to hear the latest ins and outs of treasury transformation with S/4HANA.  

    Next to the enhancements in S/4HANA Treasury, customers had a clear need to understand what it could means for their Treasury and how they could achieve it. The conference provided an excellent opportunity to exchange ideas with each other and learn from the many case studies presented on treasury transformation.  

    Treasury Transformation with SAP S/4HANA 

    Alongside Ernst Janssen, Digital Treasury and Banking Manager at dsm-firmenich, Zanders director Deepak Aggarwal presented the value drivers for treasury in an S/4HANA migration. The presentation also included the different target architecture and deployment options, as Ernst talked about the choices made at dsm-firmenich and the rationale behind them in a real-life business case study. Zanders has a long-standing relationship with DSM going back as far as 2001, and has supported them in a number of engagements within SAP treasury. 

    In addition, there were similar other presentations on treasury transformation with S/4HANA.  BioNTech presented the case study on centralization of their bank connectivity via APIs for both inbound and outbound bank communication. They are also the first adopters of the new In-House Bank under Advanced Payment Management (APM) solution and integrate the Morgan Money trading platform for money market funds. ABB and PwC talked about their treasury transformation journey on centralization of cash management in a side-car, functionality enhancement through APM, and integration with Central Finance system for balance sheet FX management. Alter Domus and Deloitte presented their treasury transformation via S/4HANA Public Cloud including integrated market data feed and Multi-Bank Connectivity. 

    Digital and Streamlined Treasury Management System 

    Christian Mnich from SAP laid out the vision of SAP Treasury and Working Capital Management solution as an agile, resilient and sustainable solution delivering end-to-end business processes to all customers in all industries. Christian referred to the market challenges of high inflation and rising interest rates calling for a greater need of bank resiliency and cash forecasting to reduce dependencies on business partners and improve cash utilization while avoiding dipping into debt facilities. The sustainability duties like ESG reporting and carbon offsetting appear to be more relevant than ever to meet global assignments. SAP’s 2023 product strategy was presented with Cloud ERP (public or private) at the core, Business Technology Platform as integration and extension layer, and the surrounding SAP and ecosystem applications, delivering end-to-end integrated processes to the business. 

    Trading Platform Integration 

    Another focus area was SAP Integration with ICD for Money Market Funds (MMFs) through Trading Platform Integration (TPI) application. MMFs are seen as an attractive alternative to deposits, yielding better returns and diversifying risk through investment in multiple counterparties. Quite often the business is restricted on MMF dealing as a result of system limitations and overhead due to the manual processes. Integration with ICD via TPI offers benefits of single sign on, automated mapping from ICD to SAP Treasury, auto-creation of securities transaction in SAP, email notification and integrated reporting in SAP Treasury. 

    Embedded Receivables Finance 

    Lastly, SAP integration with Taulia was another focus area to facilitate liquidity management in the companies. Taulia was presented as driving Working Capital Management (WCM) in the companies through its WCM platform and Taulia Multi Funder for efficient share of wallet or discovery of new liquidity. The embedded receivables finance solution in Taulia automates the receivables sales process by automating the status updates of all invoices in Taulia platform and the seller ERP.  

    If you are interested in joining SAP Treasury conferences in future, or any of the topics covered, please do reach out to your Zanders’ contacts. 

    How Royal FloraHolland grew a global cash management bank relationship from scratch

    In a changing global floriculture market, Royal FloraHolland created a new digital platform where buyers and growers can connect internationally. As part of its strategy to offer better international payment solutions, the cooperative of flower growers decided to look for an international cash management bank.


    The floriculture market is changing to trading that increasingly occurs directly between growers and buyers. Our role is therefore changing too

    Wilco van de Wijnboom, Royal FloraHolland’s Manager Corporate Finance

    quote

    Royal FloraHolland is a cooperative of flower and plant growers. It connects growers and buyers in the international floriculture industry by offering unique combinations of deal-making, logistics, and financial services. Connecting 5,406 suppliers with 2,458 buyers and offering a solid foundation to all these players, Royal FloraHolland is the largest floriculture marketplace in the world.

    The company’s turnover reached EUR 4.8 billion (in 2019) with an operating income of EUR 369 million. Yearly, it trades 12.3 billion flowers and plants, with an average of at least 100k transactions a day.

    The floriculture cooperative was established 110 years ago, organizing flower auctions via so-called clock sales. During these sales, flowers were offered for a high price first, which lowered once the clock started ticking. The price went down until one of the buyers pushed the buying button, leaving the other buyers with empty hands.


    Challenge

    The Floriday platform

    Around twenty years ago, the clock sales model started to change. “The floriculture market is changing to trading that increasingly occurs directly between growers and buyers. Our role is therefore changing too,” Wilco van de Wijnboom, Royal FloraHolland’s manager corporate finance, explains. “What we do now is mainly the financing part – the invoices and the daily collection of payments, for example. Our business has developed both geographically and digitally, so we noticed an increased need for a platform for the global flower trade. We therefore developed a new digital platform called Floriday, which enables us to deliver products faster, fresher and in larger amounts to customers worldwide. It is an innovative B2B platform where growers can make their assortment available worldwide, and customers are able to transact in various ways, both nationally and internationally.”

    The Floriday platform aims to provide a wider range of services to pay and receive funds in euros, but also in other currencies, and across different jurisdictions. Since it would help treasury to deal with all payments worldwide, Royal FloraHolland needed an international cash management bank too. Van de Wijnboom: “It has been a process of a few years. As part of our strategy, we wanted to grow internationally, and it was clear we needed an international bank to do so. At the same time, our commercial department had some leads for flower business from Saudi-Arabia and Kenya. Early in 2020, all developments – from the commercial, digital and financing points of view – came together.”


    Solution

    RfP track record

    Royal FloraHolland’s financial department decided to contact Zanders for support. Selecting a cash management bank is not something we do every day, so we needed support to find the right one,” says Pim Zaalberg, treasury consultant at Royal FloraHolland. “We have been working together with Zanders on several projects since 2010 and know which subject matter expertise they can provide. They previously advised us on the capital structure of the company and led the arranging process of the bank financing of the company in 2017. Furthermore, they assisted in the SWIFT connectivity project, introducing payments-on-behalf-of. They are broadly experienced and have a proven track record in drafting an RfP. They exactly know which questions to ask and what is important, so it was a logical step to ask them to support us in the project lead and the contact with the international banks.”

    Zanders consultant Michal Zelazko adds: “We use a standardized bank selection methodology at Zanders, but importantly this can be adjusted to the specific needs of projects and clients. This case contained specific geographical jurisdictions and payment methods with respect to the Floriday platform. Other factors were, among others, pre-payments and the consideration to have a separate entity to ensure the safety of all transactions.”

    Strategic partner

    The project started in June 2020, a period in which the turnover figures managed to rebound significantly, after the initial fall caused by the corona pandemic. Van de Wijnboom: “The impact we currently have is on the flowers coming from overseas, for example from Kenya and Ethiopia. The growers there have really had a difficult time, because the number of flights from those countries has decreased heavily. Meanwhile, many people continued to buy flowers when they were in lockdown, to brighten up their new home offices.”

    Together with Zanders, Royal FloraHolland drafted the goals and then started selecting the banks they wanted to invite to find out whether they could meet these goals. All questions for the banks about the cooperative’s expected turnover, profit and perspectives could be answered positively. Zaalberg explains that the bank for international cash management was also chosen to be a strategic partner for the company: “We did not choose a bank to do only payments, but we needed a bank to think along with us on our international plans and one that offers innovative solutions in the e-commerce area. The bank we chose, Citibank, is now helping us with our international strategy and is able to propose solutions for our future goals.”

    The Royal FloraHolland team involved in the selection process now look back confidently on the process and choice. Zaalberg: “We are very proud of the short timelines of this project, starting in June and selecting the bank in September – all done virtually and by phone. It was quite a precedent to do it this way. You have to work with a clear plan and be very strict in presentation and input gathering. I hope it is not the new normal, but it worked well and was quite efficient too. We met banks from Paris and Dublin on the same day without moving from our desks.”

    Van de Wijnboom agrees and stresses the importance of a well-managed process: “You only have one chance – when choosing an international bank for cash management it will be a collaboration for the next couple of years.”

    We have been working together with Zanders on several projects since 2010 and know which subject matter expertise they can provide

    Pim Zaalberg, Treasury Consultant at Royal FloraHolland

    quote

    RfP track record

    Royal FloraHolland’s financial department decided to contact Zanders for support. Selecting a cash management bank is not something we do every day, so we needed support to find the right one,” says Pim Zaalberg, treasury consultant at Royal FloraHolland. “We have been working together with Zanders on several projects since 2010 and know which subject matter expertise they can provide. They previously advised us on the capital structure of the company and led the arranging process of the bank financing of the company in 2017. Furthermore, they assisted in the SWIFT connectivity project, introducing payments-on-behalf-of. They are broadly experienced and have a proven track record in drafting an RfP. They exactly know which questions to ask and what is important, so it was a logical step to ask them to support us in the project lead and the contact with the international banks.”

    Zanders consultant Michal Zelazko adds: “We use a standardized bank selection methodology at Zanders, but importantly this can be adjusted to the specific needs of projects and clients. This case contained specific geographical jurisdictions and payment methods with respect to the Floriday platform. Other factors were, among others, pre-payments and the consideration to have a separate entity to ensure the safety of all transactions.”

    Strategic partner

    The project started in June 2020, a period in which the turnover figures managed to rebound significantly, after the initial fall caused by the corona pandemic. Van de Wijnboom: “The impact we currently have is on the flowers coming from overseas, for example from Kenya and Ethiopia. The growers there have really had a difficult time, because the number of flights from those countries has decreased heavily. Meanwhile, many people continued to buy flowers when they were in lockdown, to brighten up their new home offices.”

    Together with Zanders, Royal FloraHolland drafted the goals and then started selecting the banks they wanted to invite to find out whether they could meet these goals. All questions for the banks about the cooperative’s expected turnover, profit and perspectives could be answered positively. Zaalberg explains that the bank for international cash management was also chosen to be a strategic partner for the company: “We did not choose a bank to do only payments, but we needed a bank to think along with us on our international plans and one that offers innovative solutions in the e-commerce area. The bank we chose, Citibank, is now helping us with our international strategy and is able to propose solutions for our future goals.”

    The Royal FloraHolland team involved in the selection process now look back confidently on the process and choice. Zaalberg: “We are very proud of the short timelines of this project, starting in June and selecting the bank in September – all done virtually and by phone. It was quite a precedent to do it this way. You have to work with a clear plan and be very strict in presentation and input gathering. I hope it is not the new normal, but it worked well and was quite efficient too. We met banks from Paris and Dublin on the same day without moving from our desks.”

    Van de Wijnboom agrees and stresses the importance of a well-managed process: “You only have one chance – when choosing an international bank for cash management it will be a collaboration for the next couple of years.”


    Performance

    Future plans

    The future plans of the company are focused on venturing out to new jurisdictions, specifically in the finance space, to offer more currencies for both growers and buyers. “This could go as far as paying growers in their local currency,” says Zaalberg. “Now we only use euros and US dollars, but we look at ways to accommodate payments in other currencies too. We look at our cash pool structure too. We made sure that, in the RfP, we asked the banks whether they could provide cash pooling in a way that was able to use more currencies. We started simple but have chosen the bank that can support more complex setups of cash management structures as well.” Zelazko adds: “It is an ambitious goal but very much in line with what we see in other companies.”

    Also, in the longer term, Royal FloraHolland is considering connecting the Floriday platform to its treasury management system. Van de Wijnboom: “Currently, these two systems are not directly connected, but we could do this in the future. When we had the selection interviews with the banks, we discussed the prepayments situation – how do we make sure that the platform is immediately updated when there is a prepayment? If it is not connected, someone needs to take care of the reconciliation.”

    There are some new markets and trade lanes to enter, as Van de Wijnboom concludes: ”We now see some trade lanes between Kenya and The Middle East. The flower farmers indicate that we can play an intermediate role if it is at low costs and if payments occur in US dollars. So, it helps us to have an international cash management bank that can easily do the transactions in US dollars.”

    Zanders Transfer Pricing Suite

    Would you like to hear more about the bank selection process or other treasury-related challenges? Then please contact Michal Zelazko.

    Customer successes

    View all Insights

    MODEC’s step to an automated FX hedging process

    In a changing global floriculture market, Royal FloraHolland created a new digital platform where buyers and growers can connect internationally. As part of its strategy to offer better international payment solutions, the cooperative of flower growers decided to look for an international cash management bank.


    The floriculture market is changing to trading that increasingly occurs directly between growers and buyers. Our role is therefore changing too

    Wilco van de Wijnboom, Royal FloraHolland’s Manager Corporate Finance

    quote

    Royal FloraHolland is a cooperative of flower and plant growers. It connects growers and buyers in the international floriculture industry by offering unique combinations of deal-making, logistics, and financial services. Connecting 5,406 suppliers with 2,458 buyers and offering a solid foundation to all these players, Royal FloraHolland is the largest floriculture marketplace in the world.

    The company’s turnover reached EUR 4.8 billion (in 2019) with an operating income of EUR 369 million. Yearly, it trades 12.3 billion flowers and plants, with an average of at least 100k transactions a day.

    The floriculture cooperative was established 110 years ago, organizing flower auctions via so-called clock sales. During these sales, flowers were offered for a high price first, which lowered once the clock started ticking. The price went down until one of the buyers pushed the buying button, leaving the other buyers with empty hands.


    Challenge

    The Floriday platform

    Around twenty years ago, the clock sales model started to change. “The floriculture market is changing to trading that increasingly occurs directly between growers and buyers. Our role is therefore changing too,” Wilco van de Wijnboom, Royal FloraHolland’s manager corporate finance, explains. “What we do now is mainly the financing part – the invoices and the daily collection of payments, for example. Our business has developed both geographically and digitally, so we noticed an increased need for a platform for the global flower trade. We therefore developed a new digital platform called Floriday, which enables us to deliver products faster, fresher and in larger amounts to customers worldwide. It is an innovative B2B platform where growers can make their assortment available worldwide, and customers are able to transact in various ways, both nationally and internationally.”

    The Floriday platform aims to provide a wider range of services to pay and receive funds in euros, but also in other currencies, and across different jurisdictions. Since it would help treasury to deal with all payments worldwide, Royal FloraHolland needed an international cash management bank too. Van de Wijnboom: “It has been a process of a few years. As part of our strategy, we wanted to grow internationally, and it was clear we needed an international bank to do so. At the same time, our commercial department had some leads for flower business from Saudi-Arabia and Kenya. Early in 2020, all developments – from the commercial, digital and financing points of view – came together.”


    Solution

    RfP track record

    Royal FloraHolland’s financial department decided to contact Zanders for support. Selecting a cash management bank is not something we do every day, so we needed support to find the right one,” says Pim Zaalberg, treasury consultant at Royal FloraHolland. “We have been working together with Zanders on several projects since 2010 and know which subject matter expertise they can provide. They previously advised us on the capital structure of the company and led the arranging process of the bank financing of the company in 2017. Furthermore, they assisted in the SWIFT connectivity project, introducing payments-on-behalf-of. They are broadly experienced and have a proven track record in drafting an RfP. They exactly know which questions to ask and what is important, so it was a logical step to ask them to support us in the project lead and the contact with the international banks.”

    Zanders consultant Michal Zelazko adds: “We use a standardized bank selection methodology at Zanders, but importantly this can be adjusted to the specific needs of projects and clients. This case contained specific geographical jurisdictions and payment methods with respect to the Floriday platform. Other factors were, among others, pre-payments and the consideration to have a separate entity to ensure the safety of all transactions.”

    Strategic partner

    The project started in June 2020, a period in which the turnover figures managed to rebound significantly, after the initial fall caused by the corona pandemic. Van de Wijnboom: “The impact we currently have is on the flowers coming from overseas, for example from Kenya and Ethiopia. The growers there have really had a difficult time, because the number of flights from those countries has decreased heavily. Meanwhile, many people continued to buy flowers when they were in lockdown, to brighten up their new home offices.”

    Together with Zanders, Royal FloraHolland drafted the goals and then started selecting the banks they wanted to invite to find out whether they could meet these goals. All questions for the banks about the cooperative’s expected turnover, profit and perspectives could be answered positively. Zaalberg explains that the bank for international cash management was also chosen to be a strategic partner for the company: “We did not choose a bank to do only payments, but we needed a bank to think along with us on our international plans and one that offers innovative solutions in the e-commerce area. The bank we chose, Citibank, is now helping us with our international strategy and is able to propose solutions for our future goals.”

    The Royal FloraHolland team involved in the selection process now look back confidently on the process and choice. Zaalberg: “We are very proud of the short timelines of this project, starting in June and selecting the bank in September – all done virtually and by phone. It was quite a precedent to do it this way. You have to work with a clear plan and be very strict in presentation and input gathering. I hope it is not the new normal, but it worked well and was quite efficient too. We met banks from Paris and Dublin on the same day without moving from our desks.”

    Van de Wijnboom agrees and stresses the importance of a well-managed process: “You only have one chance – when choosing an international bank for cash management it will be a collaboration for the next couple of years.”

    We have been working together with Zanders on several projects since 2010 and know which subject matter expertise they can provide

    Pim Zaalberg, Treasury Consultant at Royal FloraHolland

    quote

    RfP track record

    Royal FloraHolland’s financial department decided to contact Zanders for support. Selecting a cash management bank is not something we do every day, so we needed support to find the right one,” says Pim Zaalberg, treasury consultant at Royal FloraHolland. “We have been working together with Zanders on several projects since 2010 and know which subject matter expertise they can provide. They previously advised us on the capital structure of the company and led the arranging process of the bank financing of the company in 2017. Furthermore, they assisted in the SWIFT connectivity project, introducing payments-on-behalf-of. They are broadly experienced and have a proven track record in drafting an RfP. They exactly know which questions to ask and what is important, so it was a logical step to ask them to support us in the project lead and the contact with the international banks.”

    Zanders consultant Michal Zelazko adds: “We use a standardized bank selection methodology at Zanders, but importantly this can be adjusted to the specific needs of projects and clients. This case contained specific geographical jurisdictions and payment methods with respect to the Floriday platform. Other factors were, among others, pre-payments and the consideration to have a separate entity to ensure the safety of all transactions.”

    Strategic partner

    The project started in June 2020, a period in which the turnover figures managed to rebound significantly, after the initial fall caused by the corona pandemic. Van de Wijnboom: “The impact we currently have is on the flowers coming from overseas, for example from Kenya and Ethiopia. The growers there have really had a difficult time, because the number of flights from those countries has decreased heavily. Meanwhile, many people continued to buy flowers when they were in lockdown, to brighten up their new home offices.”

    Together with Zanders, Royal FloraHolland drafted the goals and then started selecting the banks they wanted to invite to find out whether they could meet these goals. All questions for the banks about the cooperative’s expected turnover, profit and perspectives could be answered positively. Zaalberg explains that the bank for international cash management was also chosen to be a strategic partner for the company: “We did not choose a bank to do only payments, but we needed a bank to think along with us on our international plans and one that offers innovative solutions in the e-commerce area. The bank we chose, Citibank, is now helping us with our international strategy and is able to propose solutions for our future goals.”

    The Royal FloraHolland team involved in the selection process now look back confidently on the process and choice. Zaalberg: “We are very proud of the short timelines of this project, starting in June and selecting the bank in September – all done virtually and by phone. It was quite a precedent to do it this way. You have to work with a clear plan and be very strict in presentation and input gathering. I hope it is not the new normal, but it worked well and was quite efficient too. We met banks from Paris and Dublin on the same day without moving from our desks.”

    Van de Wijnboom agrees and stresses the importance of a well-managed process: “You only have one chance – when choosing an international bank for cash management it will be a collaboration for the next couple of years.”


    Performance

    Future plans

    The future plans of the company are focused on venturing out to new jurisdictions, specifically in the finance space, to offer more currencies for both growers and buyers. “This could go as far as paying growers in their local currency,” says Zaalberg. “Now we only use euros and US dollars, but we look at ways to accommodate payments in other currencies too. We look at our cash pool structure too. We made sure that, in the RfP, we asked the banks whether they could provide cash pooling in a way that was able to use more currencies. We started simple but have chosen the bank that can support more complex setups of cash management structures as well.” Zelazko adds: “It is an ambitious goal but very much in line with what we see in other companies.”

    Also, in the longer term, Royal FloraHolland is considering connecting the Floriday platform to its treasury management system. Van de Wijnboom: “Currently, these two systems are not directly connected, but we could do this in the future. When we had the selection interviews with the banks, we discussed the prepayments situation – how do we make sure that the platform is immediately updated when there is a prepayment? If it is not connected, someone needs to take care of the reconciliation.”

    There are some new markets and trade lanes to enter, as Van de Wijnboom concludes: ”We now see some trade lanes between Kenya and The Middle East. The flower farmers indicate that we can play an intermediate role if it is at low costs and if payments occur in US dollars. So, it helps us to have an international cash management bank that can easily do the transactions in US dollars.”

    Contact

    Would like to know more about our treasury system support in Asia? Then please contact Michiel Putman Cramer via +81 3 6892 3047.

    How to connect with local banks in Japan?

    September 2023
    8 min read

    In SAP Treasury, business partners represent counterparties with whom a corporation engages in treasury transactions, including banks, financial institutions, and internal subsidiaries.


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

    Traditional options

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

    Other solutions

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

    eBAgent making use of API

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

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

    Various ways to connect TMS / ERP with banks in Japan

    How to connect with local banks in Japan?

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

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


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

    The implications of the EMIR Refit

    September 2023
    8 min read

    In SAP Treasury, business partners represent counterparties with whom a corporation engages in treasury transactions, including banks, financial institutions, and internal subsidiaries.


    The EMIR Refit was originally introduced with the goal of simplifying regulations, and these new requirements took effect in 2019. Following the EMIR Refit, there has been a subsequent round of amendments and updated technical guidelines. In this article, we highlight the key changes. 

    ESMA has published the final reporting guidelines for the updated EMIR refit to take effect on 29 April 2024 (Europe) and 30 September 2024 (UK). These changes, while strivinging to streamline and standardise the reporting across Trade repositories, will add some initial challenges in setting up the new report and reporting format. 

    Although a significant number of corporates rely on the financial counterparty to report on their behalf, these changes can still cause a major headache for corporates that continue reporting by themselves or need to report internal trades. 

    Key changes  

    The first major change concerns the number of fields that can be reported on. Currently there are 129 reportable fields, under the updated legislation there is a withdrawal of 15 and 89 new fields. This brings the new report to a hefty 203 reportable fields. 

    There will be an introduction of more counterparty-specific fields. These fields will require a deeper understanding of and communication with all counterparties. New counterparty data that will be required includes a Clearing Threshold and Corporate Sector. 

    The way that these fields will be reported is under huge review. The updated legislation will remove the CSV file, a business staple due to its ease of creation and flexibility, and replace the file with an XML submission using ISO 20022 standards. This move to XML will give corporates the headache of building the necessary XML file. One benefit of the XML format is that it will make moving between Trade Repositories easier as there will be a uniform file specification.  

    Introducing UPI 

    Another major change concerns the introduction of a Unique Product Identifier (UPI). The UPI is aimed at reducing the misreporting of products, ISINs, CFI codes, and other classifications. The UPI will be controlled and issued by the Derivatives Service Bureau (DSB). With a central database of identifiers, this should reduce misreporting. It is also hoped that the use of a centrally managed UPI will lead to a reduction in the number of reportable fields in the future . A downside to this change is that companies will need to sign up with the DSB and a fee will be charged for each UPI. There is a general consensus that with the introduction of the UPI, the UTI is likely to be phased out and removed in the future. 

    One easily missed detail on the new requirements is the necessity to update all outstanding trades to the new reporting format and level of detail, within 6 months of the go-live. This can be problematic for firms that don’t have the necessary data points for the historic trades and will require a review to bring these trades up to the required reporting standard. 

    In summary, there are large changes in the number of fields needing to be reported, much more granularity required from dealing counterparties, and a change of file type to XML. 

    Reporting validations and final report can be found on the ESMA website

    With our experience in EMIR and EMIR Refit legislation we can help with the transition to the new reporting requirements. 

    Please contact Keith Tolfrey or Wilco Noteboom for further insights. 

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