Adviserflow DirectEnterprise Wealth Tech
Implementation Guide

Replacing a Core Banking System in Germany: BaFin Outsourcing Rules, Costs and Timeline

A core banking replacement in Germany is a regulatory project as much as an IT project. Here is what BaFin, MaRisk AT 9 and DORA expect, who realistically makes the shortlist, and what 24-36 months typically costs.

By the Adviserflow Direct editorial team · November 2026 · 7 min read

Why the regulatory file starts before vendor selection

If you're a German bank replacing its core platform, the vendor decision and the supervisory file are the same project. Most buyers of core banking software Germany-wide learn late that BaFin cares less about which product they pick than about whether they can show a documented risk analysis, a correct notification, enforceable contract clauses and a workable exit plan, all before go-live.

Two regimes apply at once. Under MaRisk AT 9, which builds on Section 25b of the German Banking Act (KWG), a vendor-operated or SaaS core is almost always a material outsourcing. Under the EU Digital Operational Resilience Act (DORA), applicable since January 2025, the same arrangement is an ICT third-party service that may support critical or important functions. A purely licensed, self-hosted core may fall outside MaRisk's definition of outsourcing, because buying software generally isn't outsourcing. Vendor support, hosting and managed operations still count as ICT services under DORA. Assume both sets of obligations apply.

Advertisement

Significant institutions supervised directly by the ECB also deal with their Joint Supervisory Team. Less significant institutions deal with BaFin and the Deutsche Bundesbank.

How MaRisk AT 9 and DORA third-party risk rules stack

DORA governs ICT third-party risk for in-scope institutions, and MaRisk AT 9 still covers outsourcing more broadly. For DORA entities, the older BAIT requirements on this topic have been superseded. A core banking contract usually triggers both regimes, so build one control set that maps to each.

  • Risk analysis before contracting. MaRisk requires a documented assessment of materiality, concentration risk and the vendor's suitability. DORA adds pre-contract due diligence and an ICT concentration-risk assessment.
  • Notifications. The KWG requires you to notify BaFin and the Bundesbank of an intended material outsourcing. DORA requires you to inform the competent authority about planned contracts for ICT services supporting critical or important functions. Confirm current forms, timing and the submission channel with your supervisor contact, because procedures have shifted since DORA took effect.
  • Register of information. DORA requires a register of every ICT third-party arrangement, including the subcontracting chain, available to the supervisor on request and in regular reporting.
  • Ongoing monitoring. You need a named outsourcing management function, regular performance reviews against SLAs, and incident reporting that fits DORA's major-incident timelines.

Start the notification early. Supervisors don't approve outsourcing in advance, but a late or thin notification invites follow-up questions just as you're trying to fix migration dates.

Contract clauses BaFin outsourcing requirements make non-negotiable

DORA Article 30 and MaRisk AT 9 make several clauses mandatory. Vendors that sell into Germany regularly will accept them. Vendors that don't will try to water them down, and you shouldn't let them.

  • Unrestricted audit and access rights for the bank, its auditors, BaFin and the Bundesbank, including on-site inspection. Pooled audits are acceptable, but a vendor-chosen SOC report alone doesn't satisfy this.
  • Subcontracting controls. Require prior notice of material subcontractors, a right to object, and the same obligations passed down. This matters most for SaaS cores running on a hyperscaler.
  • Data location and access, covering GDPR, the BDSG, banking secrecy, and where support staff can reach production data from.
  • Termination rights and transition periods. These include termination on supervisory instruction, plus a contractual exit-assistance period at pre-agreed rates. Periods of 12-24 months are common asks for a core.
  • Exit plan. Both regimes expect a documented exit strategy for material and critical arrangements, and DORA expects it to be tested. That means data export formats, a realistic alternative provider, and an estimate of how long re-migration would take.

A common red flag is exit assistance priced only as "time and materials at then-current rates." You can't budget for that, and auditors notice.

Core banking vendors DACH banks realistically shortlist

For most German banks, your banking group decides the shortlist before any product comparison starts.

Bank typeRealistic optionsWhat drives the choice
Savings banks (Sparkassen)Finanz Informatik (OSPlus)Group IT provider; you're managing an outsourcing to your own group, not choosing a core
Cooperative banks (Volksbanken, Raiffeisenbanken)Atruvia (agree21)Same logic; your leverage is collective, through the association
Private and wealth banksAvaloq, Temenos, SAP Fioneer, FinastraGerman tax certificates, securities processing (often via dwpbank), reporting integration
Digital banks, BaaS, specialist lendersMambu, Thought Machine, Temenos SaaSCloud-native product configuration, API-first design, speed to market

Group membership doesn't lighten the outsourcing obligation. Each savings or cooperative bank is still the outsourcing institution and needs its own risk analysis, monitoring and exit thinking, even if the group provider supplies standard documentation. The exit plan will be modest in practice, but it has to exist.

Open-market buyers should test German localization hard: withholding tax (Abgeltungsteuer) and annual tax certificates, deposit-guarantee reporting, SEPA and instant payments, and integration with reporting tools such as Regnology. A vendor with strong references in Switzerland or the Nordics may still need substantial work to cover German retail tax.

Typical 2026 cost ranges for a German core replacement

The figures below are indicative 2026 market ranges in USD. They vary widely by contract, scope and negotiating leverage, so confirm them with vendors and integrators. Euro-denominated German contracts won't convert one-to-one.

Bank profileAnnual license or SaaSImplementation and migrationInternal team cost
Digital bank or specialist lender, under 100k accounts$0.4m-2m$3m-12m$2m-6m
Private or wealth bank, $3bn-15bn balance sheet$1.5m-6m$15m-60m$8m-25m
Large universal or regional bank$6m-20m+$80m-300m+$30m-100m+

The main cost drivers are the number of products and legacy variants you migrate, how much German tax and reporting localization the vendor still has to build, how many parallel runs your auditors expect, and the regulatory work itself. Budget roughly 5-10% of the program for outsourcing documentation, audit-rights negotiation, exit planning and supervisory interaction. Teams that omit this line tend to overrun.

Take a hypothetical private bank with a $6bn balance sheet and 60,000 clients. It might plan for a five-year total cost of ownership somewhere around $45m-90m, with migration and internal staffing making up more than half.

A phased 24-36 month timeline

Under 24 months is realistic mainly for greenfield digital banks. For an established bank migrating live customer books, 30 months is a sensible planning baseline.

PhaseDurationRegulatory milestones
Strategy, RFP and due diligence4-6 monthsMateriality and criticality assessment, concentration risk analysis
Contract negotiation2-4 monthsDORA Article 30 clauses agreed, KWG and DORA notifications filed, register updated
Design, build and localization9-14 monthsDraft exit plan, information security and business continuity integration
Data migration and dress rehearsals4-8 monthsInternal audit review, several trial migrations, reconciliation sign-off
Cutover and hypercare3-4 monthsCompletion notification, incident reporting live, first SLA reviews
Legacy decommissioningUp to 6 months, partly overlappingData retention under HGB and GoBD, archive access confirmed

Fix the cutover window early. Year-end, tax-certificate season and quarterly reporting dates are poor choices.

Red flags and a decision rule before you sign

Walk away from, or escalate, any vendor that does the following:

  • Limits audit rights to reports it selects, or excludes supervisors from on-site access.
  • Won't name its material subcontractors or hosting regions.
  • Has no German retail tax reference customers and prices localization as a later change request.
  • Offers exit assistance with no fixed duration or rate card.
  • Expects you to accept its standard DORA addendum without negotiation.

Involve German regulatory counsel and your auditors early on contract wording and on how supervisors classify your arrangement. This article explains how the rules generally work, not how they apply to your institution.

Here's the rule we'd use. Don't sign until your outsourcing officer can show the board a completed risk analysis, a draft exit plan with a named alternative provider, and a contract that grants BaFin and Bundesbank audit access in writing. If one of those is missing, the contract isn't ready, however good the demo was.

Quick answers

Does BaFin have to approve our core banking vendor before we sign?

No. German outsourcing rules work on notification, not prior approval. You notify BaFin and the Bundesbank of an intended material outsourcing, and under DORA you inform the competent authority about planned contracts for critical or important ICT services. Supervisors can still raise objections or ask for changes, so file early and thoroughly.

Can a savings or cooperative bank switch away from Finanz Informatik or Atruvia?

In theory, yes. In practice it's very rare, because the group IT provider is tied into shared products, reporting, payments and association governance. Most of these banks focus on monitoring the group outsourcing well and documenting a proportionate exit strategy, rather than running an open-market selection.

Is a SaaS core banking platform harder to get past BaFin than an on-premise one?

It isn't necessarily harder, but it needs more evidence. SaaS cores raise hyperscaler subcontracting, data-location and concentration-risk questions that the contract and the register of information must cover. Vendors with existing German regulated clients usually have tested contract templates that shorten this work.

Written by the Adviserflow Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.