FCA Regulatory Returns for Credit Brokers: Who Owns the Calendar?

Imagine a broker whose next return is due on Tuesday. Finance thinks compliance has it. Compliance is waiting for operations. The director with submission access is on leave. Everyone has a reasonable explanation. The firm still has a reporting problem. This is a hypothetical business, but the failure is easy to recognise: several people own parts of the job and nobody owns its completion. A calendar reminder cannot resolve that. It can only announce the approaching consequence.

For credit brokers, autumn 2026 is a sensible time to examine the whole reporting process. The FCA refreshed its consumer credit reporting overview on 1 October, while affected firms are preparing for the new complaints return in 2027. Neither development creates one convenient timetable for every broker. Firms need a defensible answer to three questions: which obligations belong to this business, who will deliver them, and what proves they were delivered properly? FCA consumer credit reporting; FCA complaints reporting.

FCA Regulatory Returns

Start with the authorised legal entity and its permissions, not the trading name on the website. Establish whether it has limited or full permission, whether it acts as a principal, what other regulated activities it can undertake, and which exceptions or reporting thresholds apply. Record the accounting reference date too. The same commercial description, “credit broker”, can conceal quite different reporting obligations.

For an ordinary limited-permission credit broker, CCR007 and CCR009 both belong in the scope assessment. Full-permission brokers generally need CCR002 and CCR009; CCR001 is relevant where the firm has only credit-related permissions, subject to the detailed exclusions. Lending permissions can bring CCR003 into scope, while relevant debt-collection permissions can bring CCR006. Introducing customers to a lender does not, by itself, make the broker a lender. The FCA’s reporting overview explains the starting positions; the application provisions and notes in SUP 16.12.29CR settle the detail. FCA reporting overview.

Look beyond the CCR labels. FIN073, the Baseline Financial Resilience Report, applies to many full-permission brokers but excludes limited-permission firms. Its default is quarterly, with specified exceptions, including an annual arrangement for certain RMAR-reporting firms. That is a useful warning against treating all financial reporting as an annual accounts exercise. Complaints, principal-firm reporting and other potentially applicable obligations also need their own assessment. A register should record why an item applies, or why a plausible candidate does not. “It has never appeared before” is not a legal analysis. Equally, copying every return mentioned in an industry article obscures the obligations that matter. SUP 16.30.

Nor has CCR009 abolished CCR002 and CCR007. The FCA provides reduced reporting instructions for specified elements, not permission to discard both returns. Any change to the calendar should follow a checked requirement or instruction, not somebody’s recollection that a new form was replacing an old one. FCA CCR009 instructions.

Different Reporting Clocks

RegData gives a firm a tailored reporting schedule. Use it alongside the relevant Handbook provisions and completion instructions. The FCA’s schedule guide distinguishes the reporting period’s start and end from the submission due date. Preserve those distinctions in the firm’s own calendar. “Annual return: February” tells a preparer almost nothing about the information required. RegData schedule guide.

The current SUP 16.12.29CR table gives CCR001, CCR002, CCR003, CCR006 and CCR007 a 30-business-day submission period, and CCR009 40 business days. Their reporting frequencies and periods still require separate checking. CCR007 follows the calendar year from 2026. CCR009 also uses calendar-based periods; where the ongoing twice-yearly requirement applies, its year-end submission covers January to December, not merely July to December. Consider a hypothetical established, full-permission broker with only credit-broking permission, a 30 September accounting reference date and annual credit-related revenue comfortably below £5 million. Its CCR001 and CCR002 reporting can follow that September year-end, while its annual CCR009 covers the calendar year. One company, different clocks. Setting every recurring task to the accounts timetable would manufacture an omission. SUP 16.12.29CR.

For each applicable item, record the entity and firm reference number, rule source, reporting basis, period, frequency, regulatory due date and the date the schedule was checked. Include the preparer, reviewer, authorised submitter and deputy. Keep the evidence location beside the entry. This is a suggested control record, not an FCA-prescribed spreadsheet. Investigate a mismatch between the rules and the displayed schedule promptly with the FCA. Do not silently delete the inconvenient entry or assume that an absent item extinguishes an obligation. Until resolved, assign the question an owner and retain the correspondence. An unresolved applicability question is work in progress, not a completed compliance decision.

Give Ownership Teeth

The calendar owner needs authority to obtain information and escalate delay. Giving the job to someone who can send reminders but cannot secure a response is an elaborate way of outsourcing worry. A named senior person should oversee the arrangement, with operational responsibility assigned clearly enough that colleagues know who decides when there is a dispute. Preparation, review and submission are different jobs. Finance can own financial source data and reconciliations. Operations can own activity records. The complaints lead can own the relevant case population. Compliance can interpret requirements and challenge the treatment. The submitter confirms that the approved version is the version being sent. These are suggested responsibilities, not mandatory job titles or a claim that every return requires a board resolution.

Small firms may combine roles. That makes a second-person check, or another proportionate challenge arrangement, more valuable, not less. The question is whether somebody has tested the important assumptions rather than merely congratulated the preparer on finishing. External accountants or consultants can help, but an engagement letter does not transfer the firm’s reporting obligations. Work backwards from each verified deadline. A firm might set its data handover fifteen working days before submission, review eight days before and final approval three days before. Those are illustrative internal buffers, not FCA deadlines. A complicated return may need much more preparation. Escalate missed internal dates while options remain.

Access belongs in this plan. Test that the intended submitter and deputy have appropriate permissions for the actual data item. The FCA specifically notes that the RegData Principal User must give other users access to view, edit or submit CCR009. A working login alone proves very little. Here, “Principal User” is a system role, not a statement that the firm is an AR principal. FCA CCR009 access guidance.

The Principal’s Calendar

An appointed representative is not simply a directly authorised broker with a lighter filing burden. For business carried on within its appointment, it operates under its principal’s responsibility. The principal must organise the information needed for its own applicable returns. An AR should supply reliable records under the agreed arrangements; it should not assume the principal can reconstruct its business from a monthly invoice. IARs have a narrower appointment scope, which the reporting arrangements must respect. FCA principal responsibilities.

REP025 illustrates the distinction. Under SUP 12.7.9DR, the principal reports annually, within 60 business days of its accounting reference date. The FCA’s REP025 FAQs explain that relevant ARs and IARs include relationships terminated during the reporting period, with information covering the period for which the firm was principal. IAR information requirements are not identical to full-AR requirements. Suppose, hypothetically, an AR leaves halfway through the principal’s reporting year. The commercial team removes it from the current partner list. If reporting preparation begins with that list, the former AR may disappear from the return altogether. The remedy is a reporting population built from relationship start and end dates, supported by an agreed final data handover. Termination should trigger that handover while people still answer the telephone. SUP 12.7.9DR; REP025 FAQs.

Set AR delivery dates early enough for the principal to investigate discrepancies. Confirm which principal is responsible where there are multiple appointments, and follow each return’s scope instructions. An internal deadline agreed with an AR is not the FCA’s submission deadline, and REP025 does not replace other applicable returns. The principal needs a coordinated collection process, not an assumption that one form covers everything.

Prepare For Challenge

Before the reporting window becomes a race, settle what the preparer will hand to the reviewer. A useful pack contains the source extracts, the period and population used, the mapping into reporting fields, reconciliations and a short record of judgement calls. It should identify missing information and unresolved exceptions. A polished final total is not a substitute for that account of how it was reached. Preserve the version of each extract used. Operational records change: transactions reverse, classifications are corrected and late information arrives. A reviewer who reruns a live report a week later may obtain a different number for a legitimate reason. Without a dated snapshot and adjustment record, the firm cannot distinguish an update from an error.

Build the challenge around the business. Has a new product, acquisition, permission change or channel altered what belongs in the return? Does a nil response reflect verified inactivity, or an empty file that nobody investigated? No activity does not automatically remove a reporting requirement. Follow the relevant nil-return instructions and retain the evidence behind the answer. Never use zero as a discreet substitute for “we have not obtained the information”. Review should end with an identifiable decision: who approved which version, what was challenged and how significant questions were resolved. If a figure changes afterwards, send the affected material back through review. Approval of version four cannot sensibly authorise version seven simply because both files contain “final” in their names.

Reconcile The Differences

Reconciliation does not mean forcing different returns to show identical figures. First establish whether they cover the same entity, activities, period and measurement basis. A financial position at a reference date is different from income earned over a period. An accounting-year total is different from a calendar-year total. Take a purely hypothetical revenue bridge, assuming the same entity, scope and revenue definition throughout. Income for the year to 30 September is £640,000. Remove £145,000 relating to the previous October to December and add £175,000 for the current October to December: the calendar-year figure is £670,000. The £30,000 difference is explained, not corrected. This arithmetic is illustrative, not an instruction to use that revenue definition in every return.

Now suppose one return includes a category of activity that another excludes. The period bridge alone is insufficient: the preparer needs a separate scope adjustment supported by records. Finance should confirm the underlying figures, compliance should challenge the regulatory treatment, and the reviewer should be able to follow both. An unexplained balancing entry only makes the spreadsheet quieter. Cross-return checks are particularly useful when different teams prepare related information. Keep a shared record of approved explanations for genuine differences, while checking that last year’s explanation still holds. Where a mismatch reveals an omission, assess every affected return and period. Correcting the workbook currently open does not establish that the reporting problem has been contained.

Prove The Submission

“Ready to submit” is a staging point, not a receipt. The FCA’s validation guide explains that a data item may be ready for submission or waiting for cross-validation after checks. Those system checks help identify specified inconsistencies. They do not establish that the underlying business records are complete or every classification is right. The authorised submitter should compare the approved pack with what is actually being submitted, complete the submission process and check the resulting status. The FCA’s submission-history guide shows how to locate submitted data items by period, status and submission date. Use that evidence rather than somebody’s recollection that the button was pressed. RegData validation guide; submission-history guide.

Retain the submitted version, submission confirmation or history record, timestamp, relevant reference and approval evidence together. Mark the calendar entry complete only when that evidence exists. Apply the firm’s relevant record-retention requirements rather than inventing one retention period for every report. This evidence bundle is a recommended operating control, making a future query answerable without reconstructing the process from inbox fragments. If access or a technical failure threatens submission, escalate promptly and use the applicable FCA reporting and support route. Do not assume a helpdesk ticket extends the deadline. For complaints reports, DISP 1.10.6 specifically requires written notification without delay where a systems failure prevents electronic submission. DISP 1.10.

Correct Without Concealment

Discovering an error after filing calls for action, not a quiet replacement of the internal spreadsheet. SUP 15.6.4R requires immediate notification where the firm becomes aware, or has information reasonably suggesting, that information supplied to the FCA was or may have been false, misleading, incomplete or inaccurate, or has or may have changed in a material particular. Do not invent a general monetary threshold below which inaccurate reporting can be ignored. The notification must explain the affected information and why it was provided, and give the correct information. Where the correction is not immediately available, SUP 15.6.5R requires it as soon as possible afterwards. Completing the investigation is not a precondition for the initial notification. SUP 15.6.

RegData has a separate process for requesting resubmission through Submission History. Follow the applicable notification requirements as well; reopening a return is not necessarily the whole response. Keep the original submission, correction, explanation and communications linked. Imagine, hypothetically, that a duplicate import inflated an activity count and the same process fed two earlier returns. The owner should identify the affected population and periods, escalate immediately, ensure required notification takes place, arrange corrected submissions and test the repaired process. The closure record needs to show what stopped the recurrence. “Human error” still leaves the question of why the process allowed it through. FCA resubmission guide.

Keep It Current

A reporting calendar needs change control as well as recurring reminders. Record permission changes, accounting-reference-date changes, acquisitions, new appointments and relevant threshold movements when they happen. Assess their reporting consequences before rolling the timetable forward. Under SUP 16.3.17R, changing the accounting reference date itself requires notification to the FCA, with timing depending on whether the accounting period is extended or shortened. SUP 16.3.

Keep forthcoming requirements separate from current submissions. COM001’s first reporting period for affected firms is 1 January to 30 June 2027. The current DISP rules also provide for the final existing reporting period to end on 31 December 2026, potentially creating a shorter final period. The limited-permission exception remains important: ordinary limited-permission brokers do not simply acquire COM001 because the FCA describes a unified complaints return. The calendar owner should oversee both the remaining existing filings and the implementation needed for future data collection. That is a handover between regimes, not permission to abandon one early. Assign the change a reviewer and a completion test. A revised policy does not demonstrate that the complaints system can produce the required information. FCA complaints reporting; current DISP rules; forthcoming DISP provisions.

At Authorised Compliance Ltd, the practical question is whether a broker can show the route from obligation to evidence without relying on one person’s memory. Reliable FCA regulatory returns need a maintained register and a credible review process, not simply a large compliance manual. Try one test at the next management meeting. Select a return at random and ask its deputy to explain why it applies, which period it covers, who reviewed it and where submission is evidenced. If the answer depends on waiting for somebody to return from holiday, the firm has found its next reporting project.