FCA Regulatory Reporting — Obligations, Deadlines and Common Errors

Why Regulatory Reporting Matters

Regulatory reporting is not merely an administrative obligation — it is one of the FCA's primary supervisory tools. The data submitted through regulatory returns allows the FCA to: - Monitor the financial health and stability of authorised firms - Identify emerging risks and trends across sectors - Detect potential conduct issues (such as rising complaint volumes or declining capital ratios) - Allocate supervisory resources based on risk indicators - Benchmark firms against their peers

Firms that submit late, incomplete or inaccurate returns immediately raise supervisory concern. The FCA has publicly stated that poor regulatory reporting is a leading indicator of broader governance and control weaknesses.

Key Regulatory Returns

The specific returns required depend on the firm's authorisation type and the activities it conducts. The most common returns include:

Financial returns: - MIFIDPRU returns (investment firms) — quarterly reports on own funds, K-factor requirements, concentration risk and liquidity. Due 30 business days after the reporting period end. - FSA returns (various firm types) — periodic financial returns including balance sheets, income statements and capital adequacy calculations. Frequency and deadlines vary by firm category. - Payment services returns — for payment institutions and EMIs, covering transaction volumes, safeguarding balances and capital adequacy.

Conduct and customer returns: - Complaints data (DISP) — all firms must submit complaints data to the FCA semi-annually. Returns must include the number of complaints received, the products and issues complained about, the proportion upheld and redress paid. - Consumer Duty reporting — while not yet a standalone return, the FCA increasingly expects firms to provide Consumer Duty outcome data through existing reporting frameworks and on request.

Transaction reporting: - MiFIR transaction reports — investment firms that execute transactions in financial instruments must report details of each transaction to the FCA by the end of the following working day (T+1). Reports must include the instrument identifier, the parties involved, the price, quantity and timestamp. - EMIR reporting — firms that enter into derivative contracts must report details to a registered trade repository.

Financial crime returns: - REP-CRIM (Annual Financial Crime Report) — all firms must submit an annual return covering their financial crime framework, including information on customers, products, geographic exposure, SAR filings and compliance staffing. - MLR annual return — registered MSBs must submit an annual return to the FCA detailing their AML/CFT compliance activities.

Client assets returns: - CASS returns — firms that hold client money or assets must submit periodic returns detailing the value of client money held, the results of reconciliations and any breaches of CASS requirements. - CMAR (Client Money and Assets Return) — monthly returns for firms holding significant client money or asset balances.

Other returns: - Controllers and close links — notifications of changes in controllers, close links or group structure. - Section 166 reporting — skilled person reports commissioned by the FCA on specific topics. - Principle 11 notifications — firms must notify the FCA of material events including significant rule breaches, fraud, IT incidents and changes to key personnel.

Filing Deadlines and Processes

Most regulatory returns are submitted through the FCA's RegData system (which replaced Gabriel). Key points:

• Deadlines are non-negotiable. The FCA publishes a regulatory reporting calendar. Firms must submit returns by the specified deadline — there is no general provision for extensions.
• Data must be accurate. Firms must have adequate systems and controls to ensure the accuracy of data submitted. The FCA expects firms to implement a "four-eyes" review process for regulatory returns — with the preparer and an independent reviewer checking submissions before filing.
• Corrections must be timely. If a firm discovers an error in a previously submitted return, it must correct the return as soon as practicable. Material errors should also be notified to the FCA via a Principle 11 notification.
• Senior management accountability. Under SM&CR, the SMF2 (Chief Finance) or another designated SMF holder is typically accountable for the accuracy and timeliness of financial regulatory returns.

Common Reporting Errors

Based on FCA supervisory feedback and thematic reviews, common errors include:

• Late submissions — missing deadlines due to inadequate planning, staff absence or system issues. The FCA publishes league tables of late reporters, creating reputational as well as regulatory risk.
• Inconsistent data — figures that do not reconcile across different returns or with the firm's audited financial statements. The FCA's analytical tools are designed to detect inconsistencies automatically.
• Misclassification — incorrectly categorising transactions, products or customer types in regulatory returns. This is particularly common in MiFIR transaction reporting, where instrument classification errors are a frequent issue.
• Incomplete fields — submitting returns with missing or placeholder data. The FCA expects all mandatory fields to be completed accurately.
• Failure to resubmit corrections — identifying errors internally but failing to correct them in the FCA's reporting system.

MiFIR Transaction Reporting

Transaction reporting under MiFIR deserves special attention due to its complexity and the frequency of errors. Key requirements:

• Reports must be submitted by T+1 (the end of the working day following the transaction)
• Reports must include 65 data fields covering the instrument, the parties, the trading conditions and the price
• Firms must use Legal Entity Identifiers (LEIs) for counterparty identification
• The FCA uses transaction reports for market surveillance — inaccurate reports can undermine the detection of market abuse

The FCA's Market Data Processor (MDP) system automatically validates reports and identifies errors. Firms with high error rates receive supervisory attention. Common transaction reporting errors include: - Incorrect or missing LEIs - Wrong instrument identifiers (ISINs) - Inaccurate price or quantity data - Failure to report cancelled or amended trades - Incorrect buyer/seller designation

Building a Reporting Framework

1. Create a reporting calendar: Maintain a comprehensive calendar of all regulatory returns, with filing deadlines, preparation timelines and responsible owners. Build in review periods before each deadline to allow for quality checks and corrections.

2. Assign clear ownership: Each return should have a named owner (typically a senior individual within finance or compliance) and a named preparer. The owner is responsible for the accuracy and timeliness of the return; the preparer is responsible for data gathering and submission.

3. Implement data quality controls: Establish systematic checks to ensure data accuracy before submission: - Reconciliation against source systems and financial statements - Trend analysis (comparing current period data with previous periods to identify anomalies) - Four-eyes review (independent review by someone other than the preparer) - Automated validation rules where possible

4. Document your processes: Maintain documented procedures for the preparation and submission of each regulatory return. Procedures should cover data sources, calculation methodologies, review processes and escalation protocols for errors or delays.

5. Plan for contingencies: Identify the risks that could prevent timely filing (key person dependency, system outages, data quality issues) and develop contingency plans. Consider cross-training to reduce key person risk and establishing relationships with third-party providers who can provide emergency support.

Consequences of Non-Compliance

The FCA's approach to late or inaccurate reporting ranges from supervisory engagement to formal enforcement:

• Supervisory correspondence — letters highlighting the failure and requesting remedial action
• Enhanced monitoring — increased supervisory scrutiny and more frequent reporting requirements
• Financial penalties — the FCA can impose fines for systematic or persistent reporting failures. Recent fines for transaction reporting failures have exceeded £1 million
• Skilled person reports — the FCA may commission a section 166 review of the firm's reporting systems and controls, at the firm's expense
• Public censure — the FCA publishes enforcement actions, creating reputational damage

Regulatory Outlook

The FCA is investing in enhanced data analytics and supervisory technology. This means regulatory returns will increasingly be used for proactive — not just reactive — supervision. Firms should expect: - More granular data requests, particularly around Consumer Duty outcomes and operational resilience - Greater use of peer comparison and outlier detection in supervisory assessments - Potential new reporting requirements related to ESG, digital assets and operational resilience - Integration of regulatory reporting with real-time supervisory monitoring in certain sectors