When evaluating whether to buy or build in-house software, you need to consider two main factors - the levels of capital and human investment both initially and into the future. Often, the perceived key benefit of an in-house system is that it can be built to the specific wishes of the organisation, using existing knowledge to meet new and changing standards. However, in practice, this is both difficult to achieve and, even more so to maintain. 

Cost and speed of SupTech implementation 

Self-built SupTech software requires a significant investment. By comparison, a Commercial off-the-Shelf (COTS) solution supplied by a third-party vendor can be competitively priced, with fixed cost options available for five to ten years and can be implemented in a total of six to twelve months from project kick-off to solution go-live. 

When you invest in SupTech software, the development of the solution is carried out by all the users together with the provider, reducing development costs dramatically and increasing opportunities for helpful improvements. For example, by working with us you gain the benefit of our experience with 30 other government entities, such as central banks and prudential authorities, worldwide at no additional cost - this would be difficult to replicate with an internal team. 

Through 20 years of practical experience exclusive to the world of financial regulation, we have developed our implementation methodology. This is a structured approach that includes five steps resulting in shorter project timeframes, allowing a quicker return on investment. 

Having the right expertise 

Having technical know-how is a key factor in the build or buy decision. Regulators should consider whether they already have the right skills and expertise available, or whether they have the time to train and upskill their teams to build and implement a project from beginning to end.  

In contrast, implementing a third-party vendor solution means that years of expertise is included in the service. Many organisations underestimate the level of internal expertise required to build a bespoke system that will always meet regulatory standards. In practice, developing an in-house software solution for financial regulation has been shown to be extremely difficult to achieve and maintain.  

We have built a team of domain specialists, subject matter experts and industry thought leaders over the last 20 years. Every customer is assigned a dedicated project team and works closely with us in tailoring the solution to fit their specific needs.  

Protecting sensitive data 

With the ever-growing threat of cybersecurity risks, regulators also need to weigh up the consequences of possible data breaches. Building systems in-house require rigorous trials, testing and must be proven to be extremely secure. Because of the sensitive nature of the data, a security breach of any kind would be highly damaging.  

Software providers work diligently to ensure data protection is of the highest quality.  

Security is paramount and is built into our solution from the ground up. For example, encryption, authorisation, authentication, and strong password settings are all inherent features of our software. Our software is regularly submitted to rigorous penetration testing by independent third parties to comply with the best and latest security practices. In over 20 years of service for tax authorities, central banks and financial regulators, we have never had a security breach. 

Maintenance and development 

Regulators must ask themselves whether they have the resources to ensure that their systems can be maintained and developed. An out-of-the-box system that updates instantly can help future-proof your systems. 

Understanding whether systems can react quickly to updates on all aspects of regulatory standards is key. Resources must extend and develop the system when the specifications, standards and user guides are changed by external organisations. 

We provide comprehensive training programmes and refresher courses for users to ensure they exploit all capabilities of the tool, making their job more efficient. This allows regulators to be self-sufficient, flexible, and proactive in an ever-changing environment. 

The Bank of Ghana case study 

In the last three years, The Bank of Ghana has dramatically transformed, moving from closing failed banks to winning the Central Bank of the Year in 2020.  

Cleaning up Ghana’s banking sector was a significant challenge. The focus was on strengthening the regulatory framework, making supervisory structures more robust, and strengthening the capacity of the bank’s supervisory staff. 

The Bank of Ghana has realised significant benefits using our supervisory solution.   

  • Improved quality, consistency, reliability, and integrity of data  
  • Customised reporting applications with the Central Bank’s Online Regulatory Analytic Surveillance System.  
  • Providing supervisors with insightful surveillance reports  
  • Enhanced monitoring and supervision helping identify risks within the financial system and proactively determine actions.  
  • Significant decreases in the time and cost to implement new regulatory requirements  
  • Risk-Based Supervision  solution greatly assists the Bank of Ghana in compliance with Basel Capital Accords and other international regulatory requirements.

Contenus similaires

  • From Vision to Execution: Operationalizing EBA Reporting Simplification

    Contenu

    From Vision to Execution: Operationalizing EBA Reporting Simplification

    The EBA's supervisory reporting simplification is a major shift towards integrated data architecture. In the final part of our EBA reporting simplification series, our experts analyze key takeaways from the recent EBA workshop on how the plan will be operationalized.

    Lire
  • EBA simplification is the first step toward integrated supervision

    Contenu

    EBA simplification is the first step toward integrated supervision

    In this Q&A, Regnology experts analyze the EBA's plan to untangle the "Regulatory Web" of fragmented reporting. They explain it is the first phase of a two-step global trend toward Integrated Supervision, moving from eliminating silos within regulatory domains to the future vision of enabling data sharing between them.

    Lire
  • EU Supervisory Reporting: Why the EBA’s simplification agenda is really a data architecture story

    Contenu

    EU Supervisory Reporting: Why the EBA’s simplification agenda is really a data architecture story

    The EBA’s simplification package is not a reduction exercise; it is a structural shift. Our new discussion paper analyzes the move from fragmented reports to an integrated data architecture.

    Lire

Contactez-nous