Join the Community

22,974
Expert opinions
43,866
Total members
415
New members (last 30 days)
180
New opinions (last 30 days)
28,978
Total comments

Financial contract data capture - thought you were done, well think again!

In early March the European Banking Authority (EBA) published a consultation paper outlining draft regulatory standards for the minimum set of data that institutions should hold on their contracts within the European Union. 

Rather than requiring a few scant details that can easily be covered off by any in-flight programmes to patch-up data, the draft demands a whole lot more.

Current collateral remediation and other audit point clean-ups that focus on small numbers of document types are unlikely to be enough.

While not enshrined in law just yet, it's pretty clear this requirement is not going away and what is even clearer is that those companies who embrace the regulatory changes as part of achieving resource efficiency will gain the advantage over those that adopt a follower stance.

Benefits for 'leader' organisations range from de-duplication of data capture effort through to more efficient and standardised negotiation in legal, all the way to multi-million dollar collateral optimisation gains and better pre-trade analytics data.​

To see the draft look at the EBA site.​

Below are some thoughts on those features that 'leader' organisations will seek.​

Next-generation contract data management platform – 10 must-have features:

  1. Counterparty centric view, looking across all contracts

  2. Ability to rapidly on-board new contract types and extend existing ones

  3. Integration with your internal client reference data platforms

  4. Compliant with external client reference data such as LEIs

  5. An application programming interface to connect up to your key systems

  6. A direct and accurate link between the data and the text in the contract

  7. Pre-defined reports covering the key requirements

  8. Access to the data from your preferred BI and Analytics platform

  9. Entitlements model to comply with jurisdictional restrictions on data access

  10. Workflow providing a controlled and transparent process

External

This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.

Join the Community

22,974
Expert opinions
43,866
Total members
415
New members (last 30 days)
180
New opinions (last 30 days)
28,978
Total comments

Trending

Igor Kostyuchenok

Igor Kostyuchenok SVP of Engineering at Mbanq

Stablecoins are the Death of SWIFT?

Steve Haley

Steve Haley Director of Market Development and Partnerships at Mojaloop Foundation

Bridging the Gap Between Closed-Loop and Open-Loop Payments Systems

Elaine Mullan

Elaine Mullan Head of Marketing and Business Development at Corlytics

RegTech’s carrot and stick dilemma and what really makes financial firms jump?

Now Hiring