Last updated:

Why FCA PS25/19 marks a turning point for complaint MI and what firms need to do next

Blog author
Emma Scott
Complaint Regulatory Compliance
Complaint Governance and Oversight
A photo of the corner of a grey stoned castle wall with a moat around it on a sunny winter day. There are grass banks either side of the moat. There are 2 trees without leaves, a ciuple of houses and a church in the background.

In this article, we're going to discuss:

Author’s note

This article was originally published on 22 December 2025 and updated on 29 October 2026. It covers the implications of FCA PS25/19 for complaint MI and oversight, with links to our practical COM001 preparation guide.

Introduction

The FCA has finalised significant reforms to the complaint reporting process under FCA PS25/19. From 1 January 2027, FCA COM001 will replace five existing complaints returns, with affected firms reporting every six months at individual legal entity level. The changes also include a modernised complaints taxonomy and clearer requirements for recording and reporting customer vulnerability.

In the FCA’s PS25/19 policy statement, the FCA says complaints data plays a vital role in understanding market trends, spotting current or emerging consumer harm, and improving its understanding of consumer outcomes after complaints. This puts greater emphasis on the quality of complaint MI and its use in identifying emerging harm.

For firms, complaint data is no longer just a regulatory obligation. Used well, it becomes a protective moat around the firm, helping leaders evidence what customers are experiencing. This gives firms earlier visibility of emerging harm and evidence of the action taken to improve outcomes.

1. What changes does FCA PS25/19 make to complaints reporting?

A single six-monthly return at legal entity level

Affected firms will need to collect data for FCA COM001 from 1 January 2027. Each legal entity will report separately every six months. Group-level reporting will no longer be permitted, which means inconsistencies and gaps previously hidden inside consolidated returns may become much more visible.

This change needs to be noted because the FCA expects greater accountability at individual firm level. If one entity has weaker data quality, different vulnerability capture, inconsistent categorisation or unexplained complaint patterns, this will be harder to hide behind the group view.

A refreshed complaints taxonomy

The FCA has updated the complaints taxonomy so the categories better reflect modern financial products and services. The aim is to reduce reliance on broad categories such as “Other”, which can dilute insight and make it harder to understand what customers are really complaining about.

This is a practical issue, not just a reporting one. If too many complaints end up in broad or unclear categories, leaders may struggle to spot repeat themes, root causes and emerging harm quickly enough.

Firms looking to improve the quality and visibility of their complaint MI can explore how Complyr supports data and analytics for regulated teams.

Mandatory reporting on vulnerability and harm

Under FCA COM001, firms will report complaints from consumers identified as vulnerable, regardless of how this was identified. They will separately report complaints relating to or caused by the firm’s failure to consider or respond appropriately to a consumer’s vulnerability.

This directly connects complaint reporting with Consumer Duty. The data should help firms identify gaps in vulnerability recognition and support, so they can act on potential harm.

For practical preparation steps, read our COM001 complaints reporting guide. It covers the changes complaint teams can make to their case records and reporting.

2. How does FCA PS25/19 impact complaint MI and oversight?

FCA PS25/19 impacts complaint MI because more consistent categories and reporting at legal entity level should make differences between firms easier to identify. Leaders will need to understand what these differences mean in practice. For example, is there enough data being collected to monitor and evidence the outcomes of remedial action across all groups?

The FCA is raising the bar on MI quality

This means firms need to trust how the data is captured, categorised and reported.

If a firm cannot explain its complaint categorisation, the MI becomes harder to rely on. The case record also needs to evidence vulnerability recognition and the support provided to the customer.

This is where manual workarounds create problems. Spreadsheets, manual notes and inconsistent categorisation can make it harder to explain the story behind the data. We’ve covered this in more detail in our blog on spreadsheet reporting blind spots in complaint handling.

The point for this article is this: if the data behind the report is weak, the report itself becomes weak, or simply put: rubbish in, rubbish out.

Vulnerability may not be declared by customers when they make a complaint

Customers seldom say 'I am vulnerable'. More often, vulnerability shows up through behaviour, context, communication, life events, health, resilience or capability.

This is why complaint teams need more than a checkbox. They need time, training, clear workflows and enough visibility to spot when a customer may need additional support.

For leaders, the bigger challenge is making vulnerability recognition consistent across the complaint journey, not leaving it to individual judgement. We’ve covered this in more detail in helping leaders embed vulnerability into regulated complaint handling.

If firms don’t have these foundations in place, vulnerability is likely to be under-reported, recorded inconsistently, or missed completely. This weakens the MI leaders rely on to assess customer support.

Atypical vulnerability ratios may raise questions

An unusually high or low proportion of complaints from consumers identified as vulnerable may lead the FCA to ask further questions.

Low ratios may indicate gaps in vulnerability identification or recording.

High ratios may suggest unmet needs, process failure, poor customer support or ongoing harm.

Neither number tells the full story on its own, but both should prompt firms to look more closely at what is happening behind the data.

This becomes even more important with legal entity-level reporting. Once each entity reports separately, differences in vulnerability capture, complaint outcomes and customer support will be harder to hide inside a group-level view.

3. How does FCA PS25/19 support the FCA’s 2025–2030 strategy?

The direction of the FCA’s 2025 to 2030 strategy is pretty clear. The regulator wants to make better use of data, identify harm earlier, and focus more closely on whether firms are delivering good consumer outcomes.

The changes under FCA PS25/19 are intended to support this direction through clearer complaints categories, more consistent vulnerability reporting and individual legal entity reporting. This should help the FCA compare firms more accurately.

This is why complaint reporting can no longer be treated as a backward-looking exercise. Used properly, complaint MI should act as an early warning system for customer friction and emerging harm. This gives firms an opportunity to act before problems become harder to control.

Automating reports can make the process more efficient. Firms also need to use complaint data to identify emerging problems and take action before more customers are affected.

4. What should leaders expect from their complaint MI?

Complaint MI shouldn’t just show movement in the numbers. Leaders need reliable evidence to act on emerging harm and monitor the outcomes of remedial action.

Firms should review current MI patterns, including vulnerability ratios, complaint themes, uphold rates, repeat issues and entity-level differences. If one entity, product, journey or customer group looks different from the rest, leaders need to investigate this. Poor capture or inconsistent categorisation can distort the picture.

Manual reporting is not automatically a problem, but it becomes risky when it creates delay, inconsistency or uncertainty around the numbers. Leaders need to be able to trace the MI back to the case evidence.

For practical preparation steps, read our COM001 complaints reporting guide. It covers mapping reporting requirements to complaint records, recording the vulnerability measures, preparing carry-over cases and testing January’s data.

5. What does FCA PS25/19 mean for complaint teams and consumers?

The FCA wants customers in vulnerable circumstances to receive fair treatment and outcomes as good as those of other consumers. For complaint teams, this means there is even more pressure on how vulnerability is recognised, recorded, supported and evidenced throughout the complaint journey.

This is where FCA PS25/19 moves beyond reporting. If a customer needs additional support, the firm needs evidence of this need and the support considered and provided. The case record should also support a review of the fairness of the outcome.

For complaint teams, this means clearer visibility of the decisions they make and better evidence around the support provided. For consumers, it should mean fewer missed indicators and fewer avoidable barriers. The complaint process should reflect their circumstances rather than forcing them through a standard route.

Reliable complaint data gives firms earlier insight into issues, stronger evidence for decisions and a clearer understanding of customer needs.

Missed vulnerability indicators and unreliable complaint data can make it harder for leaders to show whether customers are receiving fair and consistent outcomes.

6. How can Complyr support complaint MI and FCA PS25/19 preparation?

Complaint teams using Complyr can build vulnerability guidance into workflows, flag important customer information so it stays visible throughout the case, and capture root cause analysis consistently as the complaint moves forward.

This has a positive impact because FCA PS25/19 puts more weight on the quality of complaint data, not just the final report. Firms need reliable records of complaint categorisation, vulnerability recognition and support. This gives leaders a stronger basis for reviewing customer outcomes.

Complyr helps by keeping case handling, evidence, actions, vulnerability indicators, root cause and reporting connected in one complaint management system. This makes evidence easier to produce, helps leaders trust the MI, and gives teams a clearer way to manage complaints in line with the expectations set out in FCA PS25/19.

You can explore the product overview to see how Complyr supports regulated firms with structured complaint handling, clearer reporting and better oversight.

FCA PS25/19: frequently asked questions

These FAQs explain FCA PS25/19 and its implications for complaint MI, with links to practical COM001 preparation guidance.