How to Structure a RegData Resubmission Narrative That Avoids Past Business Review

A RegData resubmission is one of the few moments where a firm voluntarily hands the FCA a written record of its own error. How you frame it determines whether the supervisor closes the file, asks three follow-up questions, or opens a Section 166 or past business review. Most firms underestimate how much of that outcome is controlled by the narrative attached to the correction, not the correction itself.

Key Executive Takeaways

• The trigger for supervisory escalation is rarely the error itself; it is ambiguity about scope, root cause, and whether the firm knows what it does not yet know.
• A well-structured resubmission narrative closes off the three questions a supervisor must otherwise ask: is this isolated, is customer harm possible, and are controls now demonstrably fixed.
• Silence, over-disclosure, and speculative root cause statements are the three failure modes that convert a routine correction into a review.

Understand what the supervisor is actually reading for

When a resubmission lands, the supervisor is not assessing the arithmetic. They are testing three things: whether the firm understands the error, whether the error could plausibly indicate wider issues (conduct, prudential, or governance), and whether the firm has the self-awareness to have already scoped those adjacencies. If any of the three is unresolved on the face of the narrative, the default is to ask. Asking is what leads to reviews.

Your narrative must answer all three before they are asked, without appearing to protest too much.

Sequence the narrative deliberately

The order matters. A resubmission cover note that opens with root cause invites a root cause debate. One that opens with scope and materiality frames the correction as bounded before the reader forms a view.

Use this sequence:

1. The specific return, reference period, and data fields affected.
2. Quantitative impact, both absolute and as a percentage of the reported figure, with the corrected number.
3. How the error was identified (self-identified through control X, or via reconciliation Y, matters far more than firms realise).
4. Scope of review conducted to confirm the error is isolated, including adjacent returns and prior periods examined.
5. Root cause, stated factually and narrowly.
6. Remediation completed and controls now in place.
7. Confirmation of no customer impact, or if there is, the separate workstream addressing it.

Calibrate the root cause statement

This is where firms damage themselves. "Human error" reads as absence of control. "Control failure" reads as systemic. "Process gap" invites the question of what else is gapped.

Good root cause statements are specific, mechanical, and contained: "The mapping logic for field 12A did not reflect the November 2023 taxonomy update; the exception was not caught because the reconciliation between source system and RegData submission was performed at aggregate rather than field level." That sentence tells the supervisor exactly what went wrong, why it was missed, and implies the fix, without opening any adjacent doors.

Avoid speculative language. "We believe" and "it appears" are read as "we have not finished investigating."

Demonstrate scoping without inviting scope creep

The most important paragraph is the one confirming what else you looked at. State clearly which other returns, periods, and legal entities were reviewed, and on what basis. If you reviewed the prior four quarters and two adjacent returns, say so. If you concluded the error could not affect a particular return because of a structural feature of the data flow, explain that feature in one sentence.

This paragraph is what allows the supervisor to close the file. Without it, they must ask.

Handle customer impact explicitly

Even where the return is purely prudential, address customer impact in one line. "The affected data fields relate to regulatory capital calculation and do not feed customer-facing pricing, disclosure, or eligibility decisions." This single sentence removes the Consumer Duty and past business review vector before it forms.

If there is potential customer impact, do not bury it. Reference the separate remediation workstream, its governance, and the expected reporting cadence. Supervisors escalate when they suspect concealment, not when they see structured handling.

What good looks like

A two-to-three page cover note. Factual. No adjectives. Clear ownership signed off by the SMF16 or SMF17 as appropriate. Attachments limited to the corrected return and a one-page control remediation summary. No board minutes, no external advisor reports unless requested.

The test: can the supervisor forward your note to their team lead with a one-line recommendation to close? If yes, you have written it correctly.

Your next decision

Before submitting, ask whether your narrative would survive being read in isolation by a supervisor who has never spoken to your firm. If it would not, rewrite it. The resubmission is the record.

Frequently Asked Questions

Should we notify the supervisor before submitting the correction?

For material corrections, yes, by a short call or email flagging that a resubmission is coming and summarising the three points above. This prevents the correction being discovered cold and read defensively. For immaterial corrections, submit and let the return speak.

What counts as material for this purpose?

Materiality here is not just quantitative. A small numerical error in a field that feeds capital ratios, liquidity metrics, or conduct reporting is material regardless of size. If in doubt, treat it as material for notification purposes but not necessarily for Principle 11 escalation.

Should legal review the narrative?

Yes, but late in the process. Legal review at draft stage tends to strip the specificity that protects you. Have the first draft written by the person who understands the data, then have legal check for admissions, characterisations, and Principle 11 triggers.

How do we handle a pattern of small errors across multiple returns?

Do not resubmit them piecemeal. Consolidate into a single narrative that presents the pattern, the common root cause, and the structural remediation. Piecemeal resubmissions across weeks are the single most reliable way to trigger a thematic review.

When does a resubmission require a Principle 11 notification?

When the underlying issue is significant in its own right, not merely because the return was wrong. Ask whether you would notify if the return had been correct but the underlying control weakness had been identified through internal audit. If yes, notify. If no, the resubmission alone is usually sufficient.