How GF Bankas distributed DORA ICT reporting across service owners with Copla Registry

EU-regulated bank - DORA ICT Third

Party Register

Article 28 / RoI reporting

"The biggest time saving came from handing Register entries over to service owners. A useful side effect was their growing awareness of third-party risk management when signing contracts and applying contract controls."

GF Bankas compliance team

The challenge

A first-time submission, new rules, and a primitive Excel tool

GF Bankas was filing its first DORA ICT third-party report. The regulation had been published shortly before, so the team was learning the rules at the same time as filling in the data.

Their existing process ran on an Excel-based tool that the team described as quite primitive. Information went in by hand, attribute by attribute, and the same data points often needed to be repeated across multiple places.

Several people were pulled into the project to dedicate their time to the Register, and the team described the overall submission experience as exhausting.

What changed

Copla Registry: A clearer structure, distributed entry, and validated export

Each provider and contract attribute gets entered once. The structure links related values, so the same data point is reused automatically. The team described filling in Copla as intuitive and clear from the start.
The biggest gain came from a workflow change that the tool made viable: handing Register entries directly to service owners. Entry became significantly more convenient and clearer for them, and a layer of central review caught the occasional filling error.
The side effect of service owner involvement was an organization-wide lift in third-party risk awareness. Service owners began to think about risk at the point of signing contracts and applying signed-contract controls, where awareness matters most.
The xBRL-CSV export ran with a validation step before generation, which the team appreciated.
Support throughout was responsive. The team specifically called out Registry’s Product Owner for quick replies across a heavy volume of questions during their first submission.

Honest feedback

What they'd add next

The team flagged a few areas where the tool could be extended further: deeper subcontractor management features, a clean Excel export of all fields for internal analysis work, and a couple of small refinements to in-record save behavior and filter persistence. Each was raised as a constructive next step, building on a foundation that already carried them through their first submission with confidence.

Worth noting: These sit on the active roadmap. Copla continues to evolve the supplier view and data export capabilities in direct response to customer feedback like this.

Looking ahead

A team confident in year-round maintenance

Knowing a contract ID, finding and updating a record is quick. Knowing the filing rules, adding a new contract to the Register is straightforward. The team is confident that keeping providers and contracts current across the year is well within reach for them.

Org-wide

Lift in third-party risk awareness as service owners took on Register entry

GF Bankas

EU-regulated bank · Lithuania

See other success stories:

Replacing manual DORA reporting

Saving millions of dollars

Managing your ICT register in spreadsheets?

See how Copla Registry handles the structure, validation, and export — so you don't have to.