BCR Publishing
We are the leading provider of news, market intelligence, events and training for the global receivables finance industry.
Working with industry leading organisations, experts, governments and universities, BCR Publications delivers expertise in factoring, receivables and supply chain finance to a global audience.
BCR has long been a beacon of innovation and excellence in the realm of receivables finance, playing an instrumental role in shaping the industry’s international landscape. Through its comprehensive conferences, insightful publications, and thought leadership, BCR has facilitated crucial dialogues and connections among industry professionals, driving forward the development of receivables finance globally.
Follow BCR Publishing
Free passes
For corporate treasurer roles/functions!
How will Open Banking impact Treasury?
| 20-9-2019 | treasuryXL | BELLIN
With financial data increasingly digitized and moved to the cloud, disruptive approaches have become available to fintechs and corporates have gained access to new and revolutionary opportunities. One such opportunity is open banking, also known as API banking. In this article, we take a closer look at open banking and the potential benefits of current trends for treasurers. Karsten Kiefer, Product Manager and Solutions Manager at BELLIN, introduces us to the latest developments and assesses their impact on corporate treasury.
The European Payment Services Directive 2 (PSD2) sets rules for access to payment accounts but it has also caused great uncertainty. Is this the beginning of open banking for everyone in Europe? And what does the directive mean for treasury?
One of the provisions of PSD2 forces European banks to provide a standardized access interface, known as API, to third parties, which enables technical access to the bank’s customers’ accounts. This is an attempt by the regulator to break up the banks’ monopoly on account information and to boost competition amongst payment service providers.
The directive clearly stipulates the type of information banks have to give access to and the scope of services associated with it. For example, when it comes to payments PSD2 API access is restricted to SEPA single payments. Few banks, if any, will support bulk payments, FX payments etc. as additional services. This is why for the time being this technology is only of limited use to corporate treasury. It is definitely in no way comparable to established channels such as EBICS, H2H or SWIFT.
Where do you see the main advantages of open banking for treasury? When will corporate financial departments adopt open banking?
Changes have been flooding the international payments sector, and open banking is only one of the waves to ride. Demand is driven by developments in the consumer goods sector, where mobile, real-time payments are rapidly gaining ground, with providers springing up all over the place. 24/7/365 availability of payments services is highly relevant for treasurers. This has also been the driving force behind developments in connection with established channels, such as SWIFT or EBICS, including the SWIFT g4C technology that enables real-time information on payment transactions. For corporates who use a treasury management system with an integrated payments platform, open banking has already become a reality.
How does open banking with a treasury management system work?
A treasury management system with an integrated payments platform, such as tm5 by BELLIN, enables multi-channel access to banks. There are standardized channels for specific regions, such as EBICS, or the BELLIN SWIFT Service that provides access to the global SWIFT Network. Another connectivity option is direct host-to-host connections to specific banks and their networks. APIs represent an additional technology to connect banks and corporates, and in the future, this will become more and more relevant. Today, the BELLIN Payment Gateway enables access to real-time payment transaction information and a company’s global financial status.
Are there any challenges associated with API interfaces?
Many of the banks today that can connect via two or even three channels are working on APIs. So this will become an additional bank connectivity option. However, we need to bear in mind that such an API must bring added value and additional benefits. Otherwise, you are better off using one of the more established channels. Looking at the API specifications of several major banks in more detail, you will realize that there are minor standardization options at the moment. Everyone is talking about APIs but in fact, every bank has their own! Ultimately, it is irrelevant for the customer or the user which technological options we have available to connect a financial institution.
What new aspects does API connectivity bring and what makes it special?
The main difference is the way in which information is made accessible. Intraday account statements are a perfect example. Many banks provide this information at least once or twice a day, some more often. The times vary according to bank, which makes it difficult to gain a complete overview of your financial status at any one time. For EBICS and H2H connections, BELLIN has to actively retrieve this information for clients, while the banks send the data to a company’s BIC in the case of SWIFT Service customers. Corporates have little or no insight into any fluctuations outside these times.
API technology enables two systems to communicate directly. In theory, any API request to a bank requesting intraday account information or the current financial status could be processed and responded to in real time. This would be a huge leap towards the concept of an “instant treasury:” It would enable treasurers to trigger information directly and to receive the latest data at the touch of a button. Unfortunately, few banks are able to offer such a service, as it would require not just an interface but also powerful and modern banking systems.
So the flood of information triggered by APIs very quickly hits a wall, reined in by banking systems. Do you see any solutions to this problem?
So-called WebSocket interfaces are a step up from APIs. This technology would see a bank notify a client as soon as any relevant data has become available. Corporates could retrieve this information promptly and would always have the latest information. This is a very intelligent reversal of the logic described earlier and would get rid of any redundant data communication. Customers or their service providers would only ever communicate with a bank when the bank has notified them of available data. You could compare a notification that money has been credited to your account to notifications sent by LinkedIn or YouTube: As soon as something new happens, it’s shown to you and you’re notified.
Will these new technologies mean the end for existing solutions such as EBICS?
Not at all. EBICS is a great example. The EBICS standard is long established and thousands of corporate clients use it. Banks have invested a lot of money in these systems. Intelligent updates to these standards will be the key. The German Banking Industry Committee, the industry association of the German banking industry, is planning specifications for 2020 and working on introducing technology that will enable banks to notify corporate clients as soon as relevant data is available to be retrieved from the EBICS bank server. From a technological point of view, this will be a combination of the established EBICS protocol and the latest API technology. I think this is the perfect combination of old and new standards and brings enormous advantages to customers with little or no adjustments required.
What would you recommend treasurers do right now?
My advice would be to remain calm and wait it out. At the moment, APIs and the opportunities associated with them are being hyped up. But in reality, very few banks have actually developed new services.
At BELLIN, we develop and integrate APIs every day, whether it is to communicate with transaction repositories, to integrate SAP systems or to connect our BELLIN Connect app. We have decades of experience when it comes to banking communication and have just launched API projects with three major international banks. Our aim is to create viable use cases that add value to our treasury clients.
Authors:
Karsten Kiefer
As a Product Manager and Payments Specialist, Karsten Kiefer is responsible for any payments topics at BELLIN. The main focus of his work is on enhancing software functionality, supported payment formats and communications channels. Karsten has a background in IT and has over 20 years’ experience in the payments sector.
Anja has a PhD in German Philology and trained in a business communications agency before gaining valuable creative and marketing experience in a number of advertising agencies. For five years, she was in charge of the communications department of a renowned, private financial service provider. Her last position before joining BELLIN’s Global Marketing & Communications team in November 2014 was with Freiburg University where Anja was responsible for the marketing efforts of the EXIST business start-up program.
Using Blockchain for Legal Entity Identifiers or LEIs
| 19-09-2019 | Carlo de Meijer | treasuryXL
In one of its reports, GLEIF, the Swiss-based organisation which coordinates the management of the global Legal Identity Identifier (LEI-) system, suggested to use blockchain technology for identifying financial legal entities, as that would not only improve transparency and security but may also lead to broader global acceptance of the LEI.
This however raises a number of questions such as: Why could blockchain be of use for LEI and its users? What role could smart contracts thereby play? What benefits could blockchain bring for the LEI? And what does the most recent blockchain-based projects for the LEI tell us?
What is the LEI?
But first, what is the LEI? According to their website definition, “the Legal Entity Identifier or LEI is a 20-digit, alpha numeric code based on the ISO 17442 standard. It connects to key reference information, allowing 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’”.
In other words a LEI is a uniform way of keeping track of financial legal entities. They are global and have no borders at all for accurate and trusted identification of companies around the world. Looking in that way, the publicly available LEI data pool can be regarded as a global directory, which may greatly enhance transparency in the global marketplace.
The management of the LEI system is coordinated and supported by the above mentioned Global Legal Entity Identifier Foundation (GLEIF), while registrations are performed by so-called LOUs or Local Operating Units.
GLEIF and Blockchain
In their report on the LEI to the Financial Stability Board (FSB) in 2012, the GLEIF stated that “the design of the global LEI system would be premised on a ‘logically’ centralized (meaning not physically centralized) database that will appear to users to be from a single seamless system”.
GLEIF however recently recognised that the organizationally federated operating model used for the LEI in 2012, could be upgraded to a technically federated operating model: the distributed ledger model (DLT). This upgrade could potentially provide the same DLT platform for both the LEI and the UPI (Unified Payments Interface), of which the GLEIF is supposed to be the natural repository. This distributed design has always been a longer term goal for the global LEI system.
Present challenges for LEI
The LEI provides a global standard for the representation of identity as well as a standard validation rule set. Both elements however are subject of a very detailed compliance program in order to ensure proper issuance and maintenance of LEI and data quality.
Nowadays collection and storage of data is conducted in multiple country or regionally located operating units (LOUs). Each has their own databases (there are more than 30 at present in the LEI system and a large number of separate ones for each trade repository), and send their data daily in batch overnight processes. LEI data is sent to the GLEIF. Trade repositories send their data to multiple regulators and to central collection facilities depending on the jurisdiction. All regulators and trade repositories maintain their own data copies of identifiers for products and counterparties, and for trades.
This method bears in it a number of challenges, in terms of non-optimal transparency, security and risk issues where blockchain could be of help.
Blockchain and Identity Management
When it comes to use cases for blockchain, security is one of the serious items that comes in many minds. Identity management is one sector of industry that is supposed to provide high-level security to those who rely upon it to keep their data safe. But in reality security is not always what they get. The digital age has introduced new challenges in terms of preventing identity fraud and other criminal abuses for private people but increasingly also for corporates.
Nowadays there is an increased need for strong, multi-step security that identity management services should bring. The widespread adoption of blockchain technology to ensure that any number of these centralised databases are ‘not compromised’, should give enough arguments for the identity management industry to embrace this technology.
Some use cases for identity management
There are a number of interesting blockchain use cases in the identity management field. These include issues like identity verification, non-custodial login solutions, self-sovereign identity, secure identities for the decentralised web etc. These use cases have all proved their usefulness in such an environment.
Identity verification
Blockchain’s multi-step, multi-factor identification processes have proven to work and are already implemented by a number of companies. Admittedly, it is hard to imagine why the blockchain authentication model has not (yet) gained more mainstream adoption, especially considering the stakes of stolen identities and credentials.
Non-custodial login solutions
With non-custodial logins based on the blockchain, there is no longer need of a central entity who holds the power over user names, pass words, and the database that controls them. By removing the custodian of these credentials and replacing them with public and private keychains for logins, the former centralised entity can still ensure that ‘those logging in are who they say they are’, without holding a central database that hackers can easily acquire and use as ransom money.
Reduce third parties’ involvement
Blockchains could also help reduce the number of third parties while still maintaining a user’s identity. One solution could be that a user would store their data and identifiers on a blockchain which they could use throughout the internet, instead of granting each site or service their personal data and credential time. A second proposal is built on a similar blockchain containing the user’s data but allow third parties to access the data with their consent.
Smart contracts for Identification services
Using blockchain for the identification services including the LEI would preferably be in the form of so-called smart contracts. These contracts are ‘included and coded’ applications and data representing the life-cycle processes of a trade. It is stored and activated across a networked database – the distributed ledger – which itself is networked across the Internet.
In other words, a smart contract is self-actuating, based on standardized contract terms that is translated into standard trade life-cycle processes imbedded in coded applications. The smart contract acts on standardized data sets, setting its outputs in conformity to each participant’s processing requirements.
A smart contract requires data standards, including the LEI and its reference data for each participant in the supply chain; the UPI (Unified Payments Interface) and its reference data; and the UTI (Unique Transaction Identifier). It also requires process standards for each event in the life-cycle of a trade.
How could smart contracts be used for the LEI?
But how can smart contracts be used for the LEI? The central point of using smart contracts for the LEI is to treat a single record for any entity to be identified by some key as ‘atomic’. This in the sense of being administered as a single unit of data, by the authority that assigns the keys. Then the representation of a single ‘atomic’ record can be considered as a state for a single smart contract.
Each such contract would offer a method for accessing the representation, and a dynamic data structure that holds ‘revisions’ of the representation. That is, when the record changes globally, its new representation would be added to the state of the contract. Such contract can hold many revisions of the representation, bound only by the capabilities of the network’s global storage, called ‘entity contract’. Together with entity contracts, someone can devise one or more ‘master contracts’, that keep track of individual entity contracts and make accessing an easier process.
What approach for the LEI?
The use of permissioned and private blockchains or distributed ledgers for identity management purposes such as the LEI will require mapping between real world entities. This is hosted via cryptographic algorithms creating public/private keys pairs linked to reference data. The owner of the private key can write into the chain.
This however raises a number of major issues: Firstly, are we going to see multiple digital IDs depending on the application or are we going to use one ID to access all applications. And second, what is the appropriate management for all these IDs.
There are a number of possible scenarios:
One could use identity labels i.e. unique keys in the blockchain/DLT application. That means using the LEI in a distributed ledger system for tracking financial instruments. This is de facto the standard approach due to legal and regulatory requirements.
Another scenario is using blockchain/DLT for managing the LEI creation and management itself. This however should be seen as a longer term project. There are still many open questions but this approach bears interesting aspects for the further evolution of the LEI system.
MakoLab LEI.INFO and Graphchain Proof of Concept
An interesting project that should be taken seriously for further development is the MakoLab LEI.INFO system. Polish-based MakoLab, a Digital Solution Agency for the industry, last June announced the deployment of their production grade Blockchain-based LEI system.
This was the result of two Proof of Concepts (PoCs) for a radically new blockchain LEI system, based on the private Hyperledger Indy blockchain, using the innovative GraphChain database that is much more flexible than any standard existing system available today. These PoCs allowed MakoLab to investigate deeply the possibility to construct a system which represents the ‘highest level of both technological and organisational security’ and is completely decentralised.
Hyperledger Indy Framework
Given the vulnerability of the data, the suggested architecture for LEI is that of a so-called consortium type of blockchain that works on Hyperledger Indy. This is a blockchain model where the consensus process is controlled by a pre-selected set of nodes. The network of Hyperledger Indy nodes thereby runs as a private, permissioned blockchain for the Global LEI System.
In this model different nodes are used. User nodes that participate in the global blockchain as passive users. They can see all the data stored in it, but cannot create or edit anything. Registration nodes having all the properties of the User nodes plus the ability to provisionally add new LEIs to the system. However, such newly added LEIs are not visible on the system until the LOU nodes confirm them through the ‘Proof of Authority’ mechanism. And LOU nodes that have all the properties of the Registration nodes plus the capacity to confirm the new or modified LEIs as valid. Application of the blockchain technology with LOUs running their own nodes, would make the LEI system much safer and more reliable.
GraphChain
End June MakoLab announced the full production version of the innovative GraphChain for the LEI.INFO infrastructure. They thereby created a conceptual proposal how the entire LEI system could run on GraphChain. GraphChain should be seen as a new innovation of creating a blockchain compliant distributed database. The main idea behind GraphChain is to use blockchain mechanisms on top of an abstract RDP (Resource Description Framework) graph data model, that is used for data publishing and interchange on the web.
GraphChain is thereby defined as a linked chain of named graphs specified by the GraphChain ontology and an ontology for data graph part of the GraphChain; a set of general mechanism for calculating a digest of the named RDF graphs; and as a set of network mechanisms that are responsible for the distribution of the named RDF graphs among the distributed peers and for achieving the consensus.
The data graph model describes the semantics, or meaning of information and stores these data as a network of objects with materialised links between them, thereby managing highly interconnected data. It thereby uses graph structures with nodes, edges and properties to represent and store data.
LEI.INFO system
The new functionality allows cryptographic verification of the accuracy or usefulness of the underlying LEI data. The LEI.INFO system uses the RDF graph data model to express LEI reference data as semantic data, that can be verified against the network of Hyperledger Indy Blockchain. This LEI.INFO platform allows to get instant access to the database of entities holding LEI’s and as a result to find a reliable supplier, partner or customer.
LEI.INFO offers a wide range of LEI-related services including a new LEI registration process, resolution of the LEI codes for both humans and software agents, Data Analytics Solutions and integration services for KYC and financial information consolidation applications.
What may blockchain bring for the LEI?
From what is said before, it should not be difficult to see how blockchain and a single database that could be updated in real-time, securely maintained through encryption technology, distributed and shared by all of the participants could benefit those organisations who use the LEI. The reconciliation of the various copies of what is intended to be identical data sets could be done in real-time.
Managing LEI on blockchain delivers transparency and ensures the necessary trust and certainty optimal for combatting financial crimes, streamlining various administrative processes like onboarding, and truly knowing corporate customers, partners, and other businesses. This could ‘revolutionise’ the oversight of the financial industry. As a result of this all, it may lead to firmly reduced resources and costs of the validation process required for conducting due diligence about those entities.
McKinsey, the global consultancy estimates that the largest financial institutions alone can each save $1 billion in costs through a simplified portfolio of data repositories. ISDA members, many being the largest of financial institutions, are envisioned as direct beneficiaries of such savings.
Going forward
Blockchain technology could be of great help for the Global LEI system. The MakoLab project is thereby a very interesting one that deserves further investigation.
This LEI.INFO project however is just a first step in their research and development process with this technology. Taking into consideration the growing potential of the solution, MakoLab is “working on further-enhancing the LEI resolver with other top-class solutions – semantics particularly – as well as translating blockchain into other business areas” .
In the end such an architecture of the new LEI system will enable ‘thousands of registration authorities from multiple countries to participate in the new LEI creation’, thereby opening the path for the true global adoption of the system.
Carlo de Meijer
Economist and researcher
10 Steps for an effective and efficient credit card policy
16-9-2019 | Marco Lassche |
Corporate credit cards are often used by employees to pay their expenses during business trips.
In this article we explain how you can easily control the use of corporate credit cards.
Advantages of business credit cards
The advantage for the employee is that she does not first have to pre-finance the expenses herself and later declare the costs based on a stack of crumpled receipts.
Advantages of business credit cards for the company are countless:
By using a number of simple tools, many more benefits are added:
10 Steps to implement a good credit card policy
A good credit card policy is essential for optimizing credit card use within a company. So make sure that it is clear beforehand what the rules of the game. Equally important, maintain them as well. It is also important that the management confirms itself to the credit card policy. Management should be a good role model.
10 Steps:
Cost savings on credit cards
Easy and quick gains:
Other cost savings:
There are more cost savings to realize. E.g. there are still a lot of companies in which employees can book their flights and hotels on their own preferred website and pay it by the corporate credit card. To get better insight and cost control you can consider the implementation of a corporate travel portal, in which the employee can still book on its own, but you can control costs much better.
Please feel free to contact me if you need any further information or assistance in setting up a framework to control your corporate credit card costs.
Marco Lassche
Founder and Owner of at Bedrijfskostenexpert
Treasurer and Project Manager at Van Caem Klerks Group
treasuryXL Ambassador