Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Industries

The challenges of a bank's digital transformation show in where its information system lags behind

In brief

The challenges of a bank's digital transformation come down, for its information system, to five workstreams: legacy systems, regulatory requirements, risk data, customer journeys and dependency on providers. Management Square proposes a diagnosis here: the signs that may point to the lagging workstream, the document that confirms it and the response each one calls for.

Page contents

In this article, a bank’s digital transformation means all the workstreams that put its information system in a position to serve new uses (online journeys, usable data, services open to partners) without ceasing to keep the accounts or to answer the supervisor. This is a reading convention: the expression belongs to common usage, and others also include the product offering, the organisation or the business lines. Understood in this way, the challenges of a bank’s digital transformation come down to five workstreams: legacy systems, regulatory requirements, risk data, customer journeys and dependency on providers.

These workstreams do not necessarily progress at the same pace, and the one that has fallen behind can hold back the others. The diagnosis consists of spotting it by its signs, then giving it the response it calls for. This reading grid is ours: it is open to discussion and is adjusted to each institution.

The challenges of a bank’s digital transformation, read through their signs of delay

A sign is read as a clue: it may have a cause other than the one in the table. The last column indicates the document that confirms or rules out the hypothesis.

Workstream Observable signs Document to request
Legacy systems A simple change waits for the next production release window; the same people are called on by every project By domain, the out-of-support components and the people able to explain the rules
Regulatory requirements The risk analysis arrives the day before go-live; evidence is reconstructed before an inspection The list of ongoing projects, with the critical or important functions they affect
Risk data An exposure is recalculated in a spreadsheet; two departments present two values for the same indicator The path of an indicator, from its sources to the report
Customer journeys An application started online ends on paper; the adviser re-enters what the customer entered For one journey, the steps where a person re-enters data or passes it on by hand
Dependency on providers Nobody can say which functions rely on a given supplier; a contract has no exit clause The register of IT service contracts, with the functions supported

The core system, where business rules have accumulated

Account keeping, loans, payment means: legacy systems here means the core applications that new services need in order to read data or record a transaction. The diagnosis notes three facts per domain: the people who can still explain their rules, the components that their vendor no longer maintains, the number of projects waiting for the same team. Our article on application obsolescence describes the signs layer by layer.

The workstream calls for a decision per functional domain rather than a single all-at-once redesign: keep, open up through interfaces, rewrite in stages or replace. Our page on application modernisation compares these strategies and the non-regression evidence that accompanies each cutover; our article on mainframe migration covers the case of the mainframe.

Regulation (EU) 2022/2554, known as DORA, also addresses this. Its Article 8, paragraph 7, requires financial entities, other than microenterprises, regularly and at least once a year, to carry out a specific ICT risk assessment on all legacy ICT systems. We read it in the consolidated version published by the Publications Office, consulted on 12 November 2026.

Regulatory requirements examined too late

The sign is a calendar: the opinion of the risk and compliance functions arrives when the project can no longer change. The response is organisational, and our page on banking and insurance describes it: these functions come in at the framing stage, and each piece of evidence becomes a deliverable in the schedule.

Several texts intersect on a single project. Our entry on the DORA regulation presents its five pillars, and our article DORA for banks what it requires at each stage of a project. The GDPR, Regulation (EU) 2016/679, applies to customer data. The European AI regulation is added as soon as an AI system comes into scope, the subject of our guide to AI in banking. The remedy is checked on an ongoing project: the date on which the compliance function was brought in is compared with that of the commitment decision.

Risk data that the group struggles to aggregate

Risk data passes through the applications that the transformation modifies: a change in a source application can distort an indicator downstream without the project knowing. When an exposure can only be obtained by hand, the delay may lie in the master data rather than in the reporting tool: a customer known under two identifiers depending on the entity, a notion defined in two ways.

The Basel Committee document known as BCBS 239 sets out expectations in this area: integrated taxonomies, data ownership roles, reconciliation with sources. Its scope for a given institution is assessed with the legal and compliance functions. The response falls under data governance, which names owners and arbitrates definitions, and data lineage, which documents the path of a figure.

A customer journey held up by what happens behind the screen

An online journey only shows what the core system can expose. If the status of a file is only updated by an overnight batch, the mobile application will display it a day late, however good the screen. The delay of a journey can therefore point to another workstream: the core system, or customer master data that each channel keeps in its own way.

The response begins with measuring the journey end to end, from the customer’s request to the recorded transaction. Next comes opening up the core’s functions by means of interfaces. This opening does not reduce the core’s debt, but it allows the journey to progress without waiting for the redesign.

A dependency on providers to be inventoried before the next contract

Hosting providers, vendors, managed service providers: Article 28 of DORA requires a register of information on contractual arrangements for ICT services and, for services supporting critical or important functions, exit strategies. The sign of a delay is the inability to say, for a given supplier, which functions would stop with it.

The workstream calls for an inventory kept by function, clauses reviewed before signature and a tested exit, work described in our page on cyber resilience. It connects with the others: a modernisation that moves an application to an online service may replace technical debt with a contractual dependency, to be entered in the same register.

These workstreams share teams, deployment windows and master data: this is why, according to our banking and insurance page, major transformations are managed as a programme, on a schedule built backwards from the production release windows. The diagnosis is repeated at each portfolio review, because a workstream that has caught up reveals the delay of another.

FAQ

Frequently asked questions

Another question? Ask us

Which workstream should a bank's digital transformation start with?

With the one holding back the others, and it differs from one institution to another. A customer journey that is no longer progressing may depend on a core system that is hard to open up; risk data recalculated by hand may depend on counterparty master data. The diagnosis therefore starts from the signs observed, asks for the document that confirms the hypothesis, then traces back to the workstream on which the others depend.

What is meant by a legacy system in a bank?

The expression refers here to an old core application, for example account keeping, loan management or payment means, which new services need in order to read data or record a transaction. The diagnosis concerns its age less than three facts: the people who can still explain its rules, the components that their vendor no longer maintains, the number of projects waiting for the same team.

Why is risk data part of a bank's digital transformation?

Because it passes through the applications that the transformation modifies, from management systems to the reports submitted to the risk committee. The Basel Committee document known as BCBS 239 expects in particular integrated taxonomies, data ownership roles and reconciliation with sources. A project that changes a source application without knowing the path of its data can distort an indicator downstream.

What does the DORA regulation require of a bank regarding its IT providers?

Regulation (EU) 2022/2554 requires, in its Article 28, a register of information on all contractual arrangements for ICT services provided by third-party providers. For services supporting critical or important functions, the same article requires exit strategies. The application of these provisions to a given contract is checked with the legal and compliance functions.

Should the core system be modernised before customer journeys are redesigned?

Not necessarily. Exposing the core system's functions through interfaces allows a journey to progress while the core stays in place. The limit is well known: the journey inherits the core system's cycles, for example a status update that only happens overnight. The choice is made domain by domain, according to what the journey requires and what the system can expose.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.