FRTB Reporting Compliance Framework

With the CRR III implementation, FRTB reporting requirements for market risk are being fundamentally expanded. Financial institutions will need to submit COREP templates for the alternative standardised approach (ASA) and the alternative internal model approach (AIMA). The EBA-ITS define new reporting templates for sensitivity calculations (Delta, Vega, Curvature), Default Risk Charge (DRC), and Residual Risk Add-on (RRAO). Own funds requirements under ASA must be calculated at least monthly, while AIMA calculations must be performed more frequently. Supervisory reporting continues quarterly on the reference dates of

31 March,

30 June,

30 September, and

31 December. Institutions exceeding the thresholds under Art. 325a CRR must mandatorily apply the ASA.

The standardised approach (SA/ASA) and internal model approach (IMA/AIMA) impose different requirements on FRTB reporting. For SA reporting, institutions must calculate sensitivity measures across seven risk classes and report them in the COREP MKR templates — including general interest rate risk (GIRR), credit spread risk (CSR), foreign exchange risk (FX), and commodity risk. Additionally, DRC and RRAO calculations are required. For IMA reporting, Expected Shortfall calculations, Stressed Capital Add-ons, and Non-Modellable Risk Factor (NMRF) identification must be reported. Critically, each trading desk must regularly pass the P&L Attribution Test and backtesting to retain IMA approval. If a desk fails, it reverts to the standardised approach. An integrated framework processing both approaches in parallel reduces data management effort by up to 40%.

Data quality is the most critical success factor in FRTB reporting. Erroneous or incomplete market and position data lead to incorrect own funds calculations and can result in supervisory sanctions. Our framework implements multi-level data quality management: at the data capture level, automated completeness and plausibility checks for all market, position, and reference data. At the calculation level, cross-validations between SA and IMA results are performed. At the reporting level, an automated validation engine checks all COREP templates against current EBA validation rules and taxonomies. Additionally, end-to-end data lineage tracking ensures full traceability of all data flows — from source data capture to the final reporting template. Institutions deploying this framework reduce data quality issues by an average of 85% within the first three months.

FRTB reporting must not be viewed in isolation but needs to be embedded in the entire regulatory reporting landscape. The COREP market risk templates form part of the comprehensive supervisory reporting framework that also covers credit risk, liquidity (LCR/NSFR), and own funds ratios. An integrated approach leverages shared data sources, harmonised taxonomies, and consolidated validation processes across all regulatory frameworks — including BCBS 239, IRRBB, and stress testing. Cross-regulatory data mapping reduces data redundancies by 40–60%. Integration into a unified regulatory reporting fabric enables consistent submissions to supervisory authorities and reduces total regulatory reporting costs by 25–35%.

The EU Commission has postponed the FRTB application date to

1 January

2027 (delegated act under Art. 461a CRR). This means institutions must have their FRTB reporting systems in parallel operation by Q

3 2026 at the latest to ensure sufficient testing cycles before go-live. The recommended implementation timeline includes: gap analysis and architecture planning (

6 months), implementation of data infrastructure and calculation logic (9–12 months), parallel operation and validation (

6 months), and fine-tuning and supervisory dialogue (

3 months). Institutions starting implementation now still have adequate buffer for unforeseen complexities. Those starting only in late

2026 risk regulatory non-compliance with corresponding capital surcharges.

Effective FRTB reporting requires clear governance structures that define responsibilities, escalation paths, and control mechanisms. Central is the integration into the Three Lines of Defence model: the first line (trading, market risk) is responsible for data provision and initial calculation, the second line (risk controlling, compliance) handles independent validation and quality assurance, and the third line (internal audit) reviews the effectiveness of the overall process. We additionally recommend an FRTB Data Governance Council for data quality oversight, an Integrated Reporting Committee for consistency across different reporting frameworks, and Model Risk Governance for managing the entire model lifecycle — from development through validation to ongoing monitoring and recalibration.

FRTB reporting implementations are resource-intensive but can be made significantly more cost-efficient through a strategic approach. Our approach combines four levers: First, a differentiated sourcing strategy that develops strategic components internally and sources standardised modules externally — cost advantage of 20–30% versus a pure build approach. Second, phased implementation prioritising regulatory minimum requirements and spreading investments over time. Third, leveraging shared services and reusable components across business lines — scale effects of 35–45%. Fourth, cloud-native architecture concepts for compute-intensive calculations (Expected Shortfall, Stressed ES), reducing infrastructure costs by 30–50%. Overall, institutions using this approach achieve a reduction in ongoing operating costs of 20–30% while simultaneously improving reporting quality.