35+ template changes, new Output Floor disclosures, FRTB reporting requirements, and a fixed January 2027 go-live. This is the reporting infrastructure transformation guide for banks that cannot afford to miss the first submission deadline.
Not all template changes are equal. Some require minor data mapping adjustments; others demand new data sources, calculation engines, and multi-month IT projects. This inventory maps the real implementation effort.
| COREP Area | # Changes | Complexity | Data Sourcing | IT Effort | Severity |
|---|---|---|---|---|---|
| Credit Risk — SA (C 07.00–C 08.07) | 12 | VERY HIGH | MAJOR GAPS | 4–6 months | CRITICAL |
| Credit Risk — IRB (C 08.01–C 08.07) | 8 | HIGH | MODERATE GAPS | 3–5 months | HIGH |
| Output Floor (C 06.02 — NEW) | 4 | VERY HIGH | NEW SOURCE | 3–4 months | CRITICAL |
| Market Risk — FRTB (C 18–C 24 — NEW) | 7 | VERY HIGH | NEW SOURCE | 5–7 months | CRITICAL |
| CVA Risk (C 25 — REVISED) | 3 | HIGH | MODERATE GAPS | 2–3 months | HIGH |
| Operational Risk (C 16 — REVISED) | 2 | MEDIUM | MINOR GAPS | 1–2 months | MEDIUM |
| Large Exposures (C 26–C 29) | 2 | MEDIUM | AVAILABLE | 1–2 months | MEDIUM |
| Leverage Ratio (C 40–C 43) | 1 | LOW | AVAILABLE | 2–4 weeks | LOW |
Credit Risk SA, Output Floor, and FRTB templates are the three critical reporting workstreams. They account for 23 of the 35+ template changes and require entirely new data sourcing pipelines. If your reporting team has not begun implementation on these three areas, the January 2027 deadline is at serious risk.
The Output Floor is not a one-time implementation. It introduces a multi-year reporting obligation that changes each year as the floor percentage increases. Your reporting infrastructure must support dynamic floor calculations through 2029.
Reports the higher of IRB RWA and Floor% × SA RWA for each risk type. Banks must disclose which risk types are floor-binding and the magnitude of the floor add-on. This template requires parallel calculation of both IRB and SA RWA — meaning dual-engine production infrastructure.
The ECB expects granular disclosure showing: Credit Risk floor binding (typically the largest), Market Risk floor binding, OpRisk floor binding, and CVA floor binding. Each risk type must report both the IRB number and the SA floor number. The delta is the capital add-on driven by the floor.
Banks must report the current phase-in percentage and the projected impact at each future phase-in step. This means modelling forward-looking capital impact under 85% (2028) and 100% (2029) scenarios. The ECB uses this data for supervisory capital planning and SREP assessment.
Output Floor data reported in COREP must reconcile to Pillar 3 public disclosures. Any material discrepancy triggers supervisory inquiry. Banks must align internal reporting, COREP, and Pillar 3 templates during the parallel reporting phase to ensure consistency before go-live.
Every new template data point must trace to a source system. This matrix identifies the most common data sourcing gaps we see across European banks.
| Template Area | Required Data Field | Typical Source | Availability | Gap Remediation |
|---|---|---|---|---|
| SA-CR (C 07) | Granular exposure classification by CRR3 categories | Core banking / loan system | RED | Reclassification project: 3–4 months |
| SA-CR (C 07) | External credit rating mapping (ECAI) | Rating vendor feed | AMBER | Mapping table update: 4–6 weeks |
| Output Floor (C 06.02) | SA RWA by risk type (parallel to IRB) | Risk engine (dual calc) | RED | Dual engine build: 4–6 months |
| FRTB (C 18–24) | Risk factor sensitivities (delta, vega, curvature) | Front office / pricing engine | RED | New data pipeline: 5–7 months |
| FRTB (C 18–24) | Non-modellable risk factor (NMRF) identification | Market data vendor | RED | NMRF assessment framework: 3–4 months |
| FRTB (C 18–24) | Default Risk Charge (DRC) components | Credit risk engine | AMBER | Engine extension: 2–3 months |
| CVA (C 25) | SA-CVA sensitivities by counterparty | CVA desk / XVA engine | AMBER | XVA engine upgrade: 2–4 months |
| IRB (C 08) | CCF parameter estimates with CRR3 floors | IRB model / risk engine | GREEN | Parameter update: 4–6 weeks |
FRTB introduces entirely new reporting templates that have no predecessor in legacy COREP. Four components drive the reporting complexity.
Reports delta, vega, and curvature sensitivities across seven risk classes: GIRR, CSR Non-Sec, CSR Sec Non-CTP, CSR Sec CTP, Equity, Commodity, FX. Each risk class requires granular bucket-level sensitivity reporting. This is the most data-intensive FRTB component.
For banks with approved internal models: Expected Shortfall (ES) calculations, stress testing results, and backtesting outcomes. P&L attribution test (PLAT) results must be reported by trading desk. Failed PLATs force desk-level fallback to SbM — creating hybrid reporting complexity.
Standalone default risk capital for positions where issuer default is a material risk. Separate DRC calculations for IMA and SbM approaches. Requires credit spread and jump-to-default sensitivity data that most banks do not currently capture at the required granularity.
Capital add-on for exotic instruments with risks not captured by SbM or IMA (e.g., correlation products, longevity swaps, weather derivatives). Requires product-level identification and categorisation. The notional-based calculation is simple; the product classification challenge is not.
FRTB templates require daily granular risk factor data that most banks have never reported to supervisors. The data pipeline from front office pricing engines to regulatory reporting systems typically does not exist and must be built from scratch. Banks that begin FRTB reporting infrastructure in Q3 2026 will not be ready for January 2027.
CRR3 reporting changes cascade through every layer of the technology stack. Understanding which systems are impacted and to what degree is essential for accurate IT budgeting and resource planning.
Exposure reclassification under CRR3 categories requires changes to counterparty and facility master data. New attributes (e.g., CRR3 exposure sub-class, SME supporting factor eligibility) must be added. Typical change lead time: 4–6 months including UAT. This is the upstream dependency everything else waits for.
Must produce both IRB and SA RWA in parallel for Output Floor. New FRTB calculations (SbM, DRC, RRAO) must be integrated. CVA engine must support SA-CVA and BA-CVA methodologies. Most engines require version upgrades or module additions. Vendor dependency is a material risk.
New data points, revised data models, and additional data quality rules. ETL logic must accommodate new template structures. Data lineage documentation must be extended. Reconciliation checkpoints between source systems, warehouse, and reporting output must be established for every new data flow.
New XBRL taxonomy, revised validation rules, new template structures. Most vendors (Axiom, Wolters Kluwer, Vermeg) provide CRR3 updates, but release timing varies. Banks must validate vendor releases against EBA specifications independently. Do not assume vendor releases are error-free.
Most European banks rely on third-party vendors for at least one critical component of their reporting chain. Understanding vendor risk is not optional — it is a programme management necessity.
| Vendor Category | CRR3 Impact | Expected Release | Risk Rating | Mitigation |
|---|---|---|---|---|
| Risk Calculation Engine | FRTB module, SA-CVA, Output Floor | Q2–Q3 2026 | CRITICAL | Contractual delivery milestones; manual calculation fallback |
| Regulatory Reporting Platform | New templates, XBRL taxonomy, validations | Q3 2026 | HIGH | Early access to beta releases; parallel vendor/in-house testing |
| Market Data Provider | NMRF assessment, risk factor classification | Q2 2026 | HIGH | Multi-vendor strategy; internal NMRF assessment capability |
| Credit Rating Agency Feed | CRR3 ECAI mapping tables | Q1 2026 (available) | LOW | Standard mapping update — low complexity |
| Data Quality / Governance Tool | New data quality rules, lineage extensions | Q2–Q3 2026 | MEDIUM | Manual data quality processes as interim bridge |
For every critical vendor: What is your contractual CRR3 delivery date? What happens if you miss it? Do we have a manual workaround for the first submission cycle? Have you validated your release against the final EBA taxonomy? If your vendor cannot answer all four questions with specificity, escalate to procurement immediately.
Parallel reporting is not optional — it is how you validate that your CRR3 reporting infrastructure produces accurate, reconcilable output before the first live submission.
Generate new CRR3 templates using Q2 2026 data. Run full EBA validation rule set. Identify hard errors and soft warnings. Reconcile to legacy COREP where comparable data points exist. Target: <5% variance on comparable metrics. This run will surface the majority of data sourcing and mapping issues.
Full production run with Q3 2026 data. All hard validation errors resolved. Soft warnings documented with justification. Complete reconciliation between COREP, Pillar 3, and internal management reporting. This is your dress rehearsal — if it does not work cleanly, January 2027 is at risk.
Total RWA: <1% variance between COREP and internal reporting. Output Floor add-on: exact match (no tolerance). FRTB capital charge: <2% variance between risk engine and reporting output. CVA: <3% variance (higher tolerance due to calculation complexity). Any metric outside tolerance requires root cause analysis before go-live.
Target: complete CRR3 COREP generation within 15 business days of reference date (consistent with current remittance deadlines). If your parallel run takes >20 business days, your production process is too slow. Identify bottlenecks in data sourcing, validation resolution, or sign-off chain and remediate before go-live.
A phased action plan for reporting infrastructure transformation. Each phase has hard dependencies on the previous. Compression is possible but increases defect risk exponentially.