Integer Wealth Global
← All articles Regulatory Reporting Requirements for Wealth Managers Ultimate guide

Regulatory Reporting Requirements for Wealth Managers

Quick Summary

Regulatory reporting requirements for institutional wealth managers are structured submissions of financial, risk and operational data to supervisors at set intervals. The FCA sets the core expectations in the United Kingdom, and the applicable obligations depend on each firm's type, permissions and products.

  • Confirm which obligations attach to your firm by matching each activity to its permission type.
  • Reconcile the general ledger against the prudential return before each deadline, not during it.
  • Build the reporting calendar with internal preparation, review and sign-off dates, not just the external due date.
  • Maintain a field-level inventory that maps each reported field to its source system and reconciliation control.
  • Watch out: a return can be submitted on time and still be wrong, so review must precede submission.

Table of Contents

Regulatory Reporting Requirements for Wealth Managers (Source: Financial Conduct Authority's Handbook)

Last Updated: 14 November 2026

Understanding Regulatory Reporting Requirements for Institutional Wealth Managers

Regulatory reporting requirements for institutional wealth managers form the backbone of how firms demonstrate compliance, manage risk and maintain trust with supervisors and investors. Regulatory reporting duties for institutional wealth managers are broader than many teams expect.

Regulatory reporting is the structured submission of financial, risk and operational data to a supervisory authority at set intervals. Its purpose is to let regulators assess a firm's financial health, conduct and exposure to risk. The Financial Conduct Authority (FCA) sets the core expectations in the United Kingdom, and its FCA wealth management survey report 2026 focuses on discretionary portfolio management and the standards firms are expected to meet.

Reporting obligations are increasingly dependent on structured data. Current demands include structured data aggregation, standardised templates and audit traceability, which means data must be complete, consistent and traceable back to its source. NeoXam's overview of regulatory reporting requirements in financial services describes these expectations, though the underlying figures are not quantified in that source.

Mapping the Key Regulatory Frameworks That Apply to Your Firm

The applicable framework depends on the firm's type, its permissions and the products it manages. A discretionary wealth manager, a fund manager and an advisory-only firm will face different returns, so the first task is confirming which obligations attach to which activities.

Frameworks typically overlap. Prudential requirements concern capital and financial resilience, conduct requirements concern how clients are treated, and product-level requirements concern the instruments held. A single report may draw on more than one of these, so reporting teams need a clear view of which data feeds which submission.

Prudential Reporting and Own-Funds Obligations

Prudential reporting shows whether a firm holds enough capital to absorb losses. Own-funds calculations form the core of this work, comparing the firm's qualifying capital against the requirements set for its activities. Firms that are unsure of their own-funds position should review the FCA's published rules for their permission type before submitting anything.

Errors here are costly to fix after the fact, so reconciliation between the general ledger and the prudential return should happen before each deadline, not during it.

Investor and Product-Level Reporting

Investor reporting covers the information clients receive about their holdings, charges and performance. Product-level reporting covers the data on the funds or instruments the firm manages. Both must be accurate, timely and consistent with each other, since a mismatch between what an investor is told and what the product data shows is a common source of supervisory concern.

FCA Reporting Deadlines, Frequency and Responsible Teams

This section sets out a practical pattern for organising reporting obligations by return family, frequency and the team that usually owns preparation. Firms should always confirm the exact due date against the FCA's current rules for their permission type, because deadlines can shift with rule changes and individual permissions.

A workable calendar is built in four layers: the return, its frequency, its statutory or regulatory due date, and the internal dates for preparation, review and sign-off. The internal dates matter more than the external one, because a return that is prepared on the due date has no room for reconciliation.

Return family Typical frequency Typical owner Typical reviewer
Prudential returns (capital and own funds) Quarterly or half-yearly, depending on permission Finance Risk and Compliance
Financial resources and liquidity returns Monthly or quarterly Finance Risk
Transaction and order reporting Daily or transaction-by-transaction Operations Compliance
Fund and product-level reporting Monthly or quarterly Fund operations Compliance
Investor and client reporting Periodic, often quarterly or annual Client reporting Compliance
Conduct and complaints returns Half-yearly or annual Compliance Board or senior management
Change-in-particulars and notification returns Event-driven Compliance Senior management

A common pattern is to assign each return a named preparer, a named reviewer and a named sign-off approver, with the sign-off recorded in the same system that holds the submission evidence. Where a return is event-driven, the calendar should still carry a placeholder date so that the trigger is not forgotten between reporting cycles.

Finance usually owns the capital and ledger inputs, risk owns exposure and liquidity data, compliance owns conduct-related returns, and operations owns the data pipelines and transaction reporting. The board or a delegated committee should receive a reporting dashboard at each scheduled meeting, showing which returns are due, which are complete and which have open reconciliation items.

Watch out: a return can be submitted on time and still be wrong, so the calendar must include a review and reconciliation step before the submission date, not just the submission date itself.

Firms operating across more than one permission type should build the calendar from the union of all applicable returns, then mark each entry with the legal entity and permission it relates to. This prevents the common failure where a return is prepared for the main entity but missed for a subsidiary with a narrower permission.

Inventory of Report Types, Templates and Data Fields

This section sets out the inventory that institutional wealth managers typically maintain, organised by report family, with the template source and the core data fields that feed each one. The inventory should be reviewed whenever a rule changes, because it shows exactly which fields a new requirement will touch.

Report family Typical template source Core data fields
Prudential and own-funds returns FCA published return templates Qualifying capital, deductions, own-funds requirement, surplus or deficit
Financial resources and liquidity FCA published return templates Liquid assets, liabilities, cash-flow projections, stress assumptions
Transaction and order reporting Prescribed electronic format Instrument identifiers, price, quantity, venue, timestamp, client or firm capacity
Fund and product-level reporting Fund documentation and regulatory templates Net asset value, holdings, charges, leverage, liquidity profile
Investor and client reporting Firm-designed templates within regulatory expectations Holdings, performance, charges, risk indicators, costs and charges disclosure
Conduct and complaints returns FCA published return templates Complaint volumes, categories, redress, root-cause analysis
Notifications and change-in-particulars FCA notification forms Change description, effective date, impact assessment, remediation plan

Each row in the inventory should carry four additional attributes: the legal entity and permission it relates to, the submission frequency, the source system for each data field, and the evidence retained for each submission. The evidence attribute is often overlooked, yet it is the one an auditor or supervisor will ask for first.

Data lineage matters here. Each field should be traceable to its originating system, with reconciliation checks and retained evidence showing how the figure was produced. Where data is aggregated from several systems, the transformation logic should be documented so an auditor can follow it. A common pattern is to maintain a field-level mapping document that links each reported field to its source system, its transformation rule and its reconciliation control.

A practical inventory also distinguishes between fields that are sourced directly, fields that are calculated, and fields that are manually entered. Manually entered fields carry the highest risk of error and should attract the strongest review controls. Fields that are calculated should have their formulae version-controlled, so that a change in methodology is visible and can be explained to a supervisor.

Watch out: an inventory that lists report names but not data fields will not support regulatory change management, because it cannot show which fields a new rule will affect.

Firms should test the inventory against a recent rule change to confirm it is fit for purpose. If the inventory cannot identify the fields affected by a change within a reasonable time, it needs to be rebuilt at field level rather than report level.

Regulatory Reporting Controls and Governance Within Your Firm

Strong governance turns reporting from a periodic scramble into a controlled process. Effective controls include documented procedures, segregation of duties between preparers and reviewers, automated validation checks and a clear escalation route when figures do not reconcile.

Flowchart detailing internal governance and regulatory reporting requirements for compliance teams.
Flowchart detailing internal governance and regulatory reporting requirements for compliance teams.

Firms can demonstrate this through their published wider governance and risk context for wealth management and through internal policies that set out who approves what. Integer Wealth Global maintains a [page:3] that shows how it approaches transparency, and reviews its own standards through its [page:4], which may help teams building a comparable framework.

Internal reporting to senior management and the board should also be scheduled, so that material reporting risks reach decision-makers before they become regulatory issues.

Choosing Regulatory Reporting Software for Wealth Management

Reporting software can automate data collection, validation and submission, but no tool removes the need for governance. When evaluating options, firms should check whether a system supports the relevant templates, maintains audit trails, handles data lineage, and can be updated when rules change.

Other providers vary considerably in scope, so teams should test any platform against their own inventory of report types before committing. Ask how the system handles regulatory change and what evidence it retains for each submission.

Booking a Regulatory Reporting Review With Integer Wealth Global

Reviewing reporting obligations against your current controls can help identify gaps before a supervisor does. Firms seeking support can contact Integer Wealth Global via its website.


BUTTON: Arrange a reporting review CARD_TITLE: Is your reporting framework audit-ready? CARD_TEXT: Integer Wealth Global helps wealth managers assess governance and reporting controls.

Frequently Asked Questions

What regulatory reports do institutional wealth managers need to submit?

The reports depend on the firm's permissions, size and business model. Institutional wealth managers commonly submit prudential returns, own-funds calculations and investor or product-level disclosures to the Financial Conduct Authority. The exact set, templates and submission routes are set out in the FCA Handbook and its reporting guidance, which should be checked against your current permissions before any filing. Firms should maintain a register of every return they are required to make and the responsible team for each.

Which UK regulators oversee institutional wealth managers?

The Financial Conduct Authority is the primary conduct regulator for wealth and asset management firms authorised in the UK, and it sets most of the reporting rules these firms follow. The Prudential Regulation Authority supervises prudential matters for firms it regulates, including certain capital and reporting requirements. Firms should confirm which regulator applies to their specific permissions, as the division of responsibility depends on the firm's authorisation type.

How can wealth managers identify which reporting requirements apply to their business?

Start by reviewing your firm's FCA permissions and its classification under the relevant prudential rules, since these determine the applicable obligations. Map each permission and business activity to the reporting requirements in the FCA Handbook, then record the frequency, deadline and responsible team for each. A periodic applicability review, repeated whenever the business model or permissions change, keeps the register accurate. Compliance advisers can help, but the firm remains responsible for the final judgement.

What controls help ensure regulatory reports are accurate and submitted on time?

Effective controls include a documented reporting calendar, named owners for each return, and a four-eyes review before submission. Reconciliation between source data and reported figures, retention of audit trails and evidence of sign-off are also important. Firms should test these controls periodically and record any errors and remediation actions. Clear escalation routes for late or incomplete data help prevent missed deadlines.

What are the consequences of inaccurate or late regulatory reporting?

Inaccurate or late reporting can lead to supervisory enquiries, requirements to remediate, and enforcement action by the FCA, including public censure or financial penalties. Repeated failures may also raise questions about the firm's governance and systems and controls. The precise consequences depend on the nature and severity of the breach, and firms should refer to the FCA's enforcement guidance for the current approach.

GoogleAdd integerwealth.global as a preferred source on Google →