Basel IV in the US, UK and GCC will not look like the Basel text. It will look like what CRR3 implementation actually produced inside European G-SIBs.
CRR3 was not merely a European exercise. It was the first full-scale implementation of the Basel IV framework in a complex, multi-supervisor jurisdiction. Every bank outside the EU that is approaching Basel IV will face the same structural challenges — and can shortcut them with these five lessons.
The 72.5% output floor is not a single number you feed into a spreadsheet. In practice, it creates a parallel capital calculation that touches every risk type, every business line, and every reporting chain. Banks that treated it as a parameter change missed 6–12 months of programme work. It requires its own governance, its own data feeds, and a standing working group between risk, finance and the business lines.
The largest sustained cost in every CRR3 programme we worked on was not model redevelopment — it was data lineage. Tracing every input to every risk parameter back through staging layers, golden sources and manual overrides. The banks that solved lineage early freed their teams to focus on optimisation. Those that deferred it are still burning through budget two years later.
Under Basel IV, SA-CR, SA-CCR and the Fundamental Review of the Trading Book — SA all gain structural importance. The output floor makes the standardised result the binding constraint for many portfolios. Banks that under-invested in SA data quality, SA mapping accuracy and SA reporting infrastructure found their IRB optimisation work partially stranded.
The CRR3 text is a single regulation, but its implementation varies meaningfully across the SSM, PRA, BaFin and every NCA that retains discretion. The same portfolio can attract 15–40 basis points more or less CET1 depending on the supervisory interpretation of discretionary items. Banks operating across jurisdictions need a divergence matrix from day one.
CRR3 did not merely require model recalibration — it changed the economics of model maintenance. With the output floor reducing the marginal capital benefit of internal models, the cost-benefit analysis of running a large IRB model estate has shifted. The winning banks re-engineered their model lifecycle: retiring models that no longer pay for themselves, consolidating validation functions, and investing in model monitoring automation.
Where the €40–80m actually went — data lineage dominated run-rate spend.
The Basel IV framework is being implemented differently in every major jurisdiction. The CRR3 experience provides the ground truth that makes this comparison actionable rather than theoretical.
| Dimension | EU (CRR3) | US (Endgame) | UK (Basel 3.1) | GCC |
|---|---|---|---|---|
| Timeline | 1 Jan 2025 (live) | H2 2026 (est. re-proposal) | 1 Jul 2026 (confirmed) | 2027–2028 (varied) |
| Output Floor Equivalent | 72.5% phased to 2030 | Dual-stack (expanded SA + models) | 72.5% with PRA recalibration | 72.5% Basel text; local discretion |
| Supervisor Landscape | ECB SSM + 21 NCAs | Fed / OCC / FDIC trifecta | PRA single supervisor | CBUAE, SAMA, CBB, QCB (fragmented) |
| Data Lineage Maturity | Advanced | Moderate | Advanced | Early Stage |
| Key Risk | Transitional arbitrage | Political re-scoping | IRB cliff effects | Capability gap |
US banks that map their Endgame implementation to the CRR3 ground truth can compress their programme timeline by 12–18 months. The structural lessons around output floor governance, data lineage architecture and standardised approach investment are directly transferable. The political uncertainty around the Endgame re-proposal is no reason to delay — the implementation architecture is the same regardless of where the final thresholds land.
How leading banks are navigating supervisory differences across borders.
GCC banks are approaching Basel IV from a fundamentally different starting position than European or US peers. Three structural challenges define the implementation landscape.
European IRB models were calibrated on decades of through-the-cycle loss data. GCC portfolios — dominated by sovereign-adjacent corporates, real estate and construction — have different risk dynamics. Attempting to transplant EU-developed IRB approaches without re-calibration to local loss histories will produce models that supervisors will challenge and that capital planning cannot rely on. The output floor makes this less punishing but does not eliminate the problem.
The data infrastructure in most GCC banks is 5–8 years behind the European G-SIB standard for regulatory risk data. But the advantage is a smaller, more concentrated balance sheet. A GCC Tier-1 bank can build a compliant data lineage in 18–24 months with the right architecture. European banks took 4–5 years because they were working across 15+ legal entities and dozens of legacy systems. The GCC path is shorter if it starts now.
GCC central banks operate with closer, more relationship-driven supervisory models than the ECB’s industrialised inspection framework. This creates both opportunity and risk. Banks that engage proactively — presenting implementation plans, requesting early guidance on interpretation — can shape the regulatory outcome. Those that wait for prescriptive instructions will find Basel IV arrives as a surprise, with less time to respond.
Maturity assessment across key Basel IV data dimensions.
GCC banks targeting 2027–2028 implementation have 18–24 months of effective build time remaining. Data lineage alone requires 12–18 months of sustained effort. Banks that have not started their data foundations by Q3 2026 will face a binary choice: accelerate with external support or accept a compliance-minimum implementation that leaves 30–60 bps of CET1 on the table.
Six phases, derived from the CRR3 ground truth, that form the architecture of a successful Basel IV implementation — regardless of jurisdiction.
The four levers that separated successful CRR3 programmes from compliance-minimum outcomes.
Building IRB and SA reporting infrastructure in parallel from programme inception, rather than retrofitting SA capability when the floor became binding.
Treating data lineage as the first deliverable, not a parallel workstream. Every downstream activity — model development, reporting, optimisation — depends on it.
Standing working groups with Risk, Finance and Business representation that met at minimum monthly. Programmes without this structure lost 3–6 months to coordination failures.
Proactive retirement of IRB models where the output floor eliminated their capital benefit. The best programmes reduced model estate by 15–25% while maintaining regulatory compliance.
When the output floor is fully phased in and Basel IV is operational across the G20, the banks that performed well will not be those that read the regulation most carefully. They will be the ones that imported the ground truth from CRR3 and compressed their learning curve.
“CRR3 is not the final destination. It is the dress rehearsal. Every bank outside the EU that is approaching Basel IV has the opportunity to learn from 3.5 years of European ground truth — and arrive at implementation having already made the mistakes that cost European G-SIBs hundreds of millions of euros.”— Hannan Mohammad, Founder & Managing Partner, Ezelman
Across every CRR3 programme we have delivered, the difference between a well-executed implementation and a compliance-minimum implementation is 30–60 basis points of CET1. That is not a rounding error — it is the difference between a bank that can grow and one that is capital-constrained. The same gap will emerge in the US Endgame, in UK Basel 3.1, and in every GCC implementation. The question is whether your bank will be on the right side of that gap.