Banking and financial services architecture: top trends 2026

Capgemini publishes its top-trends series for banking, insurance and financial services each year. BCG runs its AI Radar. PwC publishes its UK financial services regulatory commentary. McKinsey publishes its banking agentic AI work. The set of pieces is consistent and broadly agrees on the strategic agenda.

The architecture function's read of the same operating environment is different. The advisor writes for the chief executive, the chief risk officer, the chief financial officer. The architect writes for the people who have to deliver the systems that will make any of this real.

This piece is the architect's view of the 2026 agenda.

Trend 1: regulatory engagement shifts upstream

The FCA, PRA and EBA have moved noticeably faster on AI, operational resilience and outsourcing in the last eighteen months. The architecture function's involvement in regulatory engagement is moving from "after-the-fact review" to "design-phase consultation". Firms that have not made this shift are paying for it through extended implementation timelines.

What to do: embed the regulatory function into the architecture review process, not the other way around.

Trend 2: agentic AI moves from pilot to production

The pilot programmes of 2024 and 2025 are now production in 2026. The production environment surfaces problems the pilot environment did not: scaling cost, audit trail discipline, vendor lock-in, change control. The architecture function carries more of this load than the 2024 sales pitch implied.

What to do: budget for steady-state operating cost of agent infrastructure (registry, policy engine, audit trail, override interface) before scaling beyond the pilot footprint.

Trend 3: the core banking and policy admin platform

modernisation cycle is accelerating

The legacy mainframe estate that survived the last modernisation cycle (2010s) is now under genuine pressure. The agentic shift has changed the integration demands; the regulatory shift has changed the data-residency demands; the cost-base pressure has changed the executive appetite for the modernisation programme.

What to do: separate the modernisation business case from the AI investment business case. Treat them as sequenced rather than combined. The combined business case is too brittle to defend through the inevitable re-baselining cycles.

Trend 4: the architecture function shifts from

"reviewer" to "delivery owner" on agent capabilities

In 2024, the architecture function reviewed the agent deployments after the AI function had built them. In 2026, the architecture function in well-run firms owns the agent platform: registry, policy engine, tool gateway. The AI function owns the use cases on top.

What to do: clarify the ownership boundary explicitly. If the architecture function does not own the platform, the firm will have multiple bespoke implementations within twelve months.

Trend 5: MCP and equivalent standards become

material to vendor selection

Foundation model providers, vertical AI tools and SaaS platforms with embedded AI are being assessed against their interoperability with MCP and equivalent standards. The firms that get this right preserve optionality; the firms that do not are committing to vendor-specific integration that becomes expensive to unwind.

What to do: include interoperability standards compliance in the vendor assessment criteria. See MCP is the most important enterprise standard nobody is implementing.

Trend 6: data residency and sovereignty become

architecture decisions, not just policy decisions

The data residency requirements for financial services have firmed up in both the UK and EU. The architecture function has to design for residency, not just declare it in policy. The implications cascade through model hosting, vector database location, audit trail storage and recovery infrastructure.

What to do: model the residency requirements at the data-flow level, not just at the data-class level.

Trend 7: model risk management becomes a

steady-state discipline

SS1/23 and the equivalent EBA guidance now apply to AI models in production. Model risk management is no longer a project-phase concern; it is a steady-state operating discipline. The architecture function carries significant weight in maintaining the model inventory, the validation evidence and the performance monitoring.

What to do: fund the model risk management function properly. The model inventory needs ongoing engineering support, not just policy support.

Where this leaves the firm

The 2026 agenda is more operationally weighty than the 2024 agenda. The pieces that worked as pilots have to work as production. The pieces that worked at the strategic narrative layer have to work at the systems layer.

The firms that will land 2026 well are the ones whose architecture function has the seniority, the funding and the authority to carry this. The firms where the architecture function is a service provider to other functions will struggle.