What Mandatory FCA Credit Information Sharing Means for UK Lenders

The FCA has opened consultation (CP26/7) on a proposed approach for credit information sharing (closing 1 May 2026) and is signaling a 12-month implementation runway after the policy finalization, meaning budgeting, operating model decisions, and technology choices need to start before the final rulebook lands.

The FCA’s CP26/7 proposals aim to close gaps in borrowers’ credit files by requiring more consistent sharing of consumer credit information across designated credit reference agencies. For UK lenders, the headline change is simple: share once, share with all. But the operational reality is bigger. Accuracy testing, dispute handling timelines, and cross bureau corrections become auditable expectations.

If your furnishing process is effectively a monthly batch that “mostly works,” CP26/7 raises the bar. Because “mostly” isn’t a defensible position once timeliness, systemic error detection, and cross‑CRA corrections become auditable expectations. The FCA is signaling that incomplete coverage, slow corrections, and inconsistent files drive real consumer harm and can distort affordability decisions. The consultation closes 1 May 2026, and the FCA proposes a go live 12 months after the Policy Statement, which makes this a near-term operating model decision, not a future compliance footnote.

What the FCA Credit Sharing is and What Changes for Lenders

At a headline level, the FCA is consulting on designating certain credit reference agencies and requiring consistent sharing across them. If a firm shares consumer credit information with one designated consumer CRA, it would be required to share it with all designated agencies.

That sounds straightforward until you translate it into day-to-day execution requiring consistent data scope, consistent data quality, and consistent correction behavior. The consistency is expected across every designated CRA relationship you have (or will have).

Consumer Credit Information: What Must Be Shared (and how often)

The FCA proposals introduce consumer credit information, a defined term that clarifies the data categories lenders must share. In practical terms, it covers identification information, account information, credit obligations (including balances), full repayment history (positive and negative), default information, and forbearance information.

The proposed baseline cadence is at least monthly. Many lenders already operate on a monthly reporting rhythm, but CP26/7 raises the bar on completeness and consistency across designated CRAs.

The Real Shift: From “Reporting” To A Governed Data Product

For many institutions, credit reporting sits in an awkward middle ground. It’s critical to decisions, but operationally treated as a feed. CP26/7 pushes it into a different category, which is a regulated control that must be testable, explainable, and defensible.

The FCA’s proposals emphasize systems and processes to ensure information shared is “as accurate as possible,” tested prior to submission, monitored for systemic issues, and corrected promptly. These actions should occur across all designated CRAs. That becomes a greater obligation from a governance point of view, not just reporting.

Disputes and Corrections: The 14-Day Clock and Cross CRA Consistency

The proposals tighten expectations around disputes and corrections in two ways:

• A response SLA: where firms are informed by a CRA of a dispute under s159, firms would be required to investigate and respond to the CRA within 14 days (with limited allowance for exceptional “holding responses”).
• Cross CRA correction: if an inaccuracy is confirmed, the expectation is correction across all CRAs with whom the inaccurate information was shared, plus identifying and addressing systemic root causes.

This is where operational design matters. A 14-day SLA is a workflow, queue, ownership model, evidence trail, and escalation path.

CCJs/decrees: Shifting the Satisfied Burden to Firms

The FCA also addresses a long-standing friction point: satisfied County Court Judgments (CCJs) and Scottish decrees are not always updated, and consumers may not know how or when to push the process forward. The FCA proposes placing an obligation on firms to report satisfied CCJs/decrees to the courts/Registry Trust when they become aware they have been paid in full. By doing so, the burden is shifted away from consumers.

The proposal centres on improving accuracy and timeliness of public judgment status as it feeds into credit lines. And, CCJ/decree status updates should help because they materially affect credit access and risk assessment.

The Format Gap: Why “Not Prescribing a Schema” is a Real Risk

One practical tension stands out: the FCA is deliberately avoiding a prescribed technical format, preferring high-level expectations so industry practices can evolve.

From an implementation lens, that creates a familiar risk. Firms can invest in one approach today, only to discover that emerging “common format” expectations drive rework tomorrow. Leaving the market to converge may reach the right outcome, but not always quickly or efficiently.

I don’t think that’s wrong because it’s a reasonable regulatory posture. But it does mean your safest build choices are modular mappings, traceable controls, and validation you can rerun as expectations evolve. This isn’t once and done; you’re building something you’ll need to operate and tune.

A Practical Readiness Framework for CP26/7

Below is a lender ready checklist you can run as an internal program plan while the consultation is still open and before final rules land.

FCA Credit Sharing Readiness Checklist

1. Coverage mapping for Share Once, Share with All

• Inventory which portfolios share to which CRA(s) today
• Identify one-CRA or two-CRA reporting gaps and why they exist

2. Data scope alignment (“consumer credit information”)

• Confirm your furnishing extracts cover: identity, account, obligations/balances, full repayment history, defaults, forbearance
• Validate positive + negative completeness per portfolio

3. Pre-submission accuracy controls

• Define accuracy tests you can evidence (not just “we reviewed it”)
• Develop recurring monitoring for systemic errors/root causes

4. Dispute operations redesign (14-day response)

• Set clear ownership (Ops vs Risk vs Data vs Legal)
• Implement a trackable workflow to investigate, respond, and document outcomes within 14 days

5. Correction mechanics (cross-CRA + timeliness)

• Ensure confirmed corrections propagate to all relevant CRAs
• Define material adverse impact escalation paths for faster corrections

6. CCJ/decree “satisfied” reporting process

• Identify where you become aware of satisfaction events
• Build a consistent notification process to courts/Registry Trust

7. Governance + evidence (Consumer Duty alignment)

• Create an auditable control narrative: tests performed, defects found, root causes fixed, corrections made
• Align reporting oversight to existing governance (SYSC-style expectations)

What To Do Now Within the Consultation Window

If you’re a UK lender or credit provider, there are three practical actions worth taking now:

1. Map coverage and gaps. Confirm which portfolios report to which CRA(s) today and document why any portfolio is single-CRA.
2. Stress test your dispute workflow against a 14-day response obligation, including cross CRA correction steps.
3. Build for change. Make your mappings and validation modular so you can adapt quickly if a common format (or additional designation detail) emerges post-Policy Statement.

Turning FCA Credit Sharing Into a Working Operating Model

Bridgeforce works with US lenders on the practical side of credit reporting discipline: tracing data lineage from system-of-record through furnishing outputs, designing accuracy controls that are easy to evidence, and building dispute workflows that can hit tight SLAs without creating operational chaos.

Our point of view is shaped by lived experience across US credit reporting rigor and UK lender realities. We’re especially adept at the messy middle of legacy systems, fragmented portfolios, and BAU processes that suddenly become mandatory priorities. If CP26/7 is on your 2026 agenda, we can help you translate the “share once, share with all” headline into an operating model and control set you can run repeatably. Contact us.