Regulatory reporting is the discipline where a plausible interview is easiest to give and hardest to assess. The vocabulary is learnable, the regimes are documented, and a candidate who has sat near the work can describe it convincingly. What distinguishes someone who has genuinely owned a submission is far more specific: where the data comes from, how it reconciles, what happened when it did not, and what they did the time a return went out wrong. This guide sets out the questions that reach that, what good looks like for each, the technical questions for MIFIDPRU, RegData and bank reporting, the red flags, and a way to score the answers. For the capability itself, see our guide to MIFIDPRU and IFPR reporting skills.
Establish the ground first
Regulatory reporting means different things in different firms, and the first three questions should establish which version the candidate has done.
1. Which returns have you personally prepared, and which have you reviewed? Preparation and review are different jobs. Ask for the specific returns rather than a general answer. What good looks like: named returns (MIF001, MIF002, the CMAR, COREP templates), a clear split between what they built and what they checked, and no inflation of either.
2. What was the firm’s permission and regime? MIFIDPRU investment firm, payment institution, insurance intermediary, consumer credit — the obligations differ markedly and experience is regime-specific. What good looks like: the firm’s category stated precisely, including whether it was SNI or non-SNI, and how that shaped the reporting.
3. What was the submission frequency and the team around you? Someone submitting quarterly in a firm with a dedicated reporting team has done something different from the sole finance person submitting monthly. What good looks like: a concrete picture of the calendar, who supplied data and who signed off.
Technical ownership questions
4. Walk me through your last submission, from data extraction to filing. The single most revealing question. Owners describe the awkward parts — the field that never maps cleanly, the balance that had to be split, the report that arrives late from operations — without prompting. Reviewers describe the output. What good looks like: a sequence with dates, systems and checkpoints, ending in the validation and sign-off before upload.
5. Where does the data actually come from, and how do you reconcile it? This is the question that separates people who have done this from people who have supervised it. Regulatory returns draw on operational systems finance does not own, and the reconciliation between the return and the ledger is the real work. What good looks like: named source systems, a reconciliation to the trial balance and an explanation of the recurring differences.
6. Talk me through the own funds calculation. [Where relevant.] Components, deductions, and which requirement bites for their firm. Someone who has owned it knows immediately whether the fixed overheads requirement or the K-factor requirement drives their number. What good looks like: own funds by tier after deductions such as intangibles, and the own funds requirement as the higher of the permanent minimum requirement, the fixed overheads requirement and, for non-SNI firms, the K-factor requirement.
7. What is in your fixed overheads calculation, and what did you exclude? The judgement lives in the exclusions, and the answer shows whether they made the call or inherited it. What good looks like: a quarter of relevant annual fixed expenditure, normally from the latest audited accounts, with each exclusion named and justified.
8. How do you handle a field where the guidance is ambiguous? Every return has them. Look for someone who documents the interpretation, applies it consistently, and can explain it later — rather than someone who decides afresh each quarter. What good looks like: a specific example, the written interpretation and who agreed it.
Process and control questions
9. Tell me about a resubmission or a return that went out wrong. Anyone with real submission history has one. Strong answers describe how it was found, what was corrected, whether it was notified, and what changed in the process afterwards. A claim of a perfect record over several years is either inexperience or evasion. What good looks like: candour, quantification and a process change that stuck.
10. What is your review process before submission? Look for a second pair of eyes, a comparison against prior period with explanations for movements, and a documented sign-off. Firms where one person prepares and submits with no review are common and it is a control weakness the candidate should recognise as one. What good looks like: analytical review with thresholds, a checklist and evidence retained.
11. How is the process documented? The key-person question in disguise. Regulatory reporting concentrates knowledge in one head more than almost any finance discipline, and a candidate who has written the methodology down is describing a different standard of practice. What good looks like: desk notes a competent colleague could follow, kept current after each change.
12. How do you keep current with changes to the regime? Reporting requirements change. Look for a specific recent change and what they did about it, rather than a general claim about reading updates. What good looks like: a named consultation or rule change and the impact assessment they ran.
Communication and stakeholder questions
13. Explain the firm’s capital position to me as you would to a board that is not prudentially literate. A live test, and the most useful two minutes in the interview. In-house regulatory reporting lives or dies on being understood by the people who make decisions — our guide to capital in the management accounts covers what good looks like. What good looks like: the surplus, what drives it and what would erode it, in plain English.
14. How do you get data out of teams that do not report to you? The recurring practical difficulty. Look for influence and process rather than escalation as a first move. What good looks like: agreed data deadlines, named owners and a calendar shared with operations.
15. Have you dealt with the regulator directly, and in what context? A query, a data request, a supervisory meeting. The answer establishes whether they have been the point of contact or behind it. What good looks like: a specific exchange and what they prepared for it.
Technical questions on MIFIDPRU returns
For investment firm roles, test the returns themselves. The MIFIDPRU sourcebook and the FCA’s IFPR pages are the references; our guide to regulatory capital, ICARA and the IFPR covers the framework.
16. What goes into MIF001 and MIF002, and how do they tie together? What good looks like: MIF001 as own funds, the own funds requirement and the own funds threshold requirement; MIF002 as liquidity, with core liquid assets against the basic liquid assets requirement (broadly one third of the fixed overheads requirement); both quarterly, and both consistent with the management accounts.
17. How would a large new mandate feed into K-AUM over the following year? What good looks like: an understanding that K-AUM uses a rolling average of monthly values over the previous 15 months, excluding the most recent three, so the effect phases in. A candidate who quotes only the 0.02% coefficient has probably reviewed rather than built.
18. What does MIF007 report, and what can go wrong with it? What good looks like: the annual ICARA questionnaire, with figures that must agree with the firm’s ICARA document. The FCA’s data quality work found MIF007 values differing from firms’ own ICARAs, threshold requirements below the own funds requirement, blank key fields and figures in the wrong units (returns should be in sterling thousands).
19. How do you know which data items your firm owes? What good looks like: reference to the firm’s reporting schedule rather than memory, and awareness that the schedule changes when permissions, size or SNI status change.
RegData questions
FCA returns are submitted through RegData, which replaced GABRIEL. Our guide to RegData, COREP and FINREP covers the mechanics.
20. How do you prepare and upload a return in RegData, and who has access? What good looks like: clear understanding of user roles, of who can submit as opposed to prepare, and of the evidence kept outside the system.
21. A return fails validation the day before the deadline. What do you do? What good looks like: reading the validation message, distinguishing a data error from a format error, fixing at source rather than overriding, and escalating early if the deadline is at risk.
22. How is a resubmission handled? What good looks like: correcting the data, resubmitting, considering whether the error needs explaining to the FCA, and logging the root cause.
COREP and FINREP questions for banks
For banks and building societies, prudential reporting runs under the PRA’s framework rather than MIFIDPRU, and returns go to the Bank of England; its regulatory reporting pages are the reference. The questions below are general; tailor them to the templates the role owns.
23. What is the difference between COREP and FINREP? What good looks like: COREP as capital adequacy reporting (own funds, capital requirements, and related areas such as leverage, large exposures and liquidity); FINREP as financial information on the balance sheet and income statement in prescribed detail.
24. Which templates have you owned, and how did they reconcile to each other? What good looks like: named templates and the cross-template checks, for example own funds in COREP agreeing with equity in FINREP after prudential adjustments.
25. How did you handle a change in the reporting taxonomy or rules? What good looks like: a mapped impact, test runs before go-live and documented sign-off.
Data lineage and controls questions
The FCA’s findings on reporting quality are mostly controls failures, not rule misreadings — which makes lineage and controls the most predictive area to probe. Our guide to data quality and the finance function covers the wider picture.
26. Pick one figure from a return you filed and trace it back to source. What good looks like: every step named — source system, extract, transformation or mapping, adjustment, return cell — with the control at each step.
27. What controls sit around manual adjustments and spreadsheets? What good looks like: a log of adjustments with reasons and approver, version control, locked formulas and an independent check of key calculations.
28. How would you stop last quarter’s data being rolled forward unchanged? What good looks like: movement analysis with thresholds, mandatory commentary on unchanged fields and a reviewer who challenges both.
Scenarios
Scenario 1: the deadline and the doubt. “The return is due tomorrow and one figure looks wrong, but you cannot resolve it in time. What do you do?” Strong answers distinguish between a number they can support with a documented basis and one they cannot, would rather submit on a stated basis and correct than guess, and would escalate internally before the deadline rather than after. The tell is whether they treat the deadline or the accuracy as the binding constraint.
Scenario 2: the historic error. “You discover in month two that a field has been reported incorrectly for the last two years. What is your plan?” Strong answers quantify the effect first, establish whether it is material and whether it changed any regulatory conclusion, and take it to the SMF holder and compliance promptly rather than quietly correcting forward. This tests integrity under maximum inconvenience.
Scenario 3: the source that broke. “The operational system you extract from has changed and the data no longer maps. Submission is in three weeks.” Strong answers establish what changed, build a bridge from the new structure to the old for comparability, and document the change — rather than manually forcing a number that agrees to last quarter.
Hiring for regulatory reporting? — 0204 553 8893
Our recruitment team screens on submission history, not vocabulary. Same working day response; permanent shortlists typically within one to two weeks, interim candidates within days.
Red flags
Consistent warning signs: unable to say where the underlying data comes from; no example of a resubmission or an error; describing the return as an output rather than a process; claiming regime experience while using the vocabulary of a different one; no view on what should be documented; and — the subtle one — treating the submission as the deliverable rather than the accuracy of what is in it. None disqualifies alone; together they describe someone who has been near this work rather than accountable for it.
Scoring the answers
Score each area from 1 to 4 and agree the weightings before the first interview, so every panel member assesses the same thing.
| Score | What it means |
|---|---|
| 4 — Owner | Specific, unprompted detail on data, reconciliation and errors; could run the process tomorrow |
| 3 — Capable | Sound on mechanics with minor gaps; owned parts of the process |
| 2 — Reviewer | Describes outputs and rules accurately but not the underlying data |
| 1 — Adjacent | Vocabulary without examples; regime confusion |
A sensible weighting for a hands-on role puts data lineage, reconciliation and the errors question at around half the total, regime knowledge at a quarter, and communication at a quarter. For a manager role, shift weight towards review, documentation and stakeholder questions.
Running the process
Three practical points. Give them a real return — an anonymised prior submission and twenty minutes, with the question: what would you check first, and what looks odd? It reveals more than any question set. Involve compliance or the SMF holder in one stage if finance lacks the regime expertise to assess the answers. And time the search away from the reporting calendar: recruiting in the fortnight before a submission is the hardest version of it, and an interim covering a cycle is frequently better than a rushed permanent hire.
Qualification — ICAEW, ACCA or CIMA — is the baseline and worth verifying before shortlist. Adjacent backgrounds transfer well: banking prudential reporting, or consultancy that has advised on ICARAs. A purely statutory background with no prudential exposure does not. Our guides to the regulatory reporting accountant role and hiring regulatory experience cover the specification.
On budget, our regulated-firm finance salary guide puts Senior Regulatory Reporting Accountants at typically £62k–£85k in London and Regulatory Reporting Managers at £65k–£95k, with interim regulatory reporting typically £500–£800 a day. For the wider role of finance in an investment firm, see finance in an investment firm. SMF16 and SMF17 appointments are handled by our sister firm SMF Capital, and CFO searches by FD Capital.
Regulatory reporting interviews: FAQs
How many interview stages are sensible?
Two is usually enough: a technical interview with a practical return exercise, then a stage with the CFO, compliance or the SMF holder focused on judgement and communication.
Can a bank COREP specialist move into MIFIDPRU reporting?
Usually, yes. The prudential frame and data discipline transfer; test K-factors, the fixed overheads requirement and the ICARA specifically.
Adrian Lawrence FCA — Founder, Accountancy Capital
Fellow of the ICAEW | Chartered Accountant holding an ICAEW practising certificate | Part of FD Capital Group
Adrian is a former listed-company Finance Director with a BSc from Queen Mary College, University of London. If he could keep only one regulatory reporting question, it would be where the data comes from and how it reconciles: the rules are documented and learnable, but pulling numbers out of systems never designed to produce them, and explaining the difference a year later, is not.
Related Pages and Resources
Regulatory Reporting
Prudential and regulatory reporting appointments.
→ Regulatory reporting recruitment
Other Question Sets
Employer interview guides across the function.
Need a regulatory reporting specialist? — 0204 553 8893
Permanent, interim and fractional regulatory reporting hires for FCA- and PRA-regulated firms, from our London and West Midlands offices. Fees are agreed in writing before a search starts. Email recruitment@accountancycapital.co.uk.