If you run complaints, compliance or operations at an insurer or broker, the clock is ticking. From 1 January 2027, the FCA complaints return changes to a single, unified return called COM001, and you’ll need to be capturing the new data points from that day.
That’s about six weeks away. And for most of the insurance teams we speak to, the hard part isn’t filling in a new form. It’s whether the complaints data behind it is joined up, consistent and trustworthy enough to report on with confidence.
In this article I’ll walk through what’s changing, where we see data gaps most often, and how you can use Dynamics 365 Customer Service and the wider Power Platform to get your complaints data ready. It’s a practical, data-readiness view rather than compliance advice, so do check the detail with your compliance team.
The FCA confirmed the new return in its Policy Statement PS25/19, published in December 2025. COM001 replaces five existing complaints returns, including DISP 1 Annex 1, and applies to FCA-authorised firms subject to the DISP rules, including life and general insurers.
The changes that matter most for your data are:
The FCA has also said it will publish individual firm data only where a firm reports 500 or more complaints, and that the vulnerability data itself won’t be published.
On 13 November 2026 the FCA updated its complaints reporting page. It confirmed it has removed the Data Reference Guides it previously published for COM001, because the technical schema and validation rules are still subject to change, and it says firms shouldn’t rely on those earlier guides when developing reporting systems. Updated guides will follow once COM001 is finalised.
Importantly, the FCA is clear that this doesn’t change the policy or reporting requirements in PS25/19 or the future DISP rules. You should still be collecting the individual data points from 1 January 2027.
So here’s our view: don’t wait for the final file format before you act. The format of the return may still move, but the information you’ll need to capture is already known. If your complaints data is well structured at source, mapping it to the final schema later becomes a much smaller job.

In our experience, complaints reporting problems rarely start in the reporting team. They start much earlier, wherever a complaint first lands. The common patterns we see are:
None of this is unusual, and none of it is fixed by a reporting tool on its own. The answer is a single, structured place where every complaint is recorded consistently from the start, which is what a CRM built for financial services gives you.
Here’s how we’d approach it in Dynamics 365 Customer Service, using out-of-the-box capabilities wherever possible.
Structure the complaint record. Add choice columns to your complaint or case records for the things you’ll report on, such as product category, complaint type, root cause and legal entity. Choice columns give people a fixed list of values, so data stays consistent. A global choice can be shared by several choice columns, which helps when the FCA publishes its final taxonomy and you need to update values in one place.
Guide people through the same steps. A business process flow leads your team through the stages of handling a complaint and makes sure the same information is captured every time. It’s a simple way to make “record the vulnerability flags” a normal step, not an afterthought.
Catch complaints as they arrive. Email classification in Dynamics 365 Customer Service uses AI to sort incoming emails into categories you define, so a complaint doesn’t sit in a general inbox. You can test your categories against historical emails in a simulation before switching it on. It needs pay-as-you-go billing enabled, so check your licensing first. We wrote more about this in our article on Consumer Duty claims handling.
Give handlers the full picture quickly. Copilot case summaries pull together the key details of a case, including the customer, subject, product, priority and description, along with related emails and notes. That helps a handler see the history before they categorise or respond. Your administrator chooses which case fields Copilot uses, and you stay in control of what’s recorded.

The two vulnerability data points are where we’d take the most care. The FCA expects firms to have regard to its vulnerability guidance and the four drivers of vulnerability: health, life events, resilience and capability. It also makes clear that you need to decide the appropriate lawful basis for recording vulnerability information, and you only report on information you hold legally. That’s a conversation for your data protection and compliance colleagues.
On the system side, two Dataverse capabilities help:
Keep the flags simple and close to the complaint: was a vulnerability identified, and did the complaint relate to it? Two clear yes/no style fields, reviewed when the complaint is closed, are much easier to report accurately than a long free-text note.
The return is a twice-yearly obligation, but the data is useful every day. In PS25/19 the FCA agrees that contextualised data drives complaint trend analysis and root cause reviews, and that’s exactly where we’d encourage you to aim.
Because Dynamics 365 Customer Service stores data in Microsoft Dataverse, you can connect Power BI to it and build a complaints dashboard by legal entity, product category, complaint type and vulnerability flag. Run it monthly, not just at the end of June, and you’ll spot problems while you can still fix them. Power Automate can then handle routine follow-ups, such as reminders when a complaint is missing a category before closure.

If I were starting today, here’s where I’d begin:
Our Inspirational Clarity approach is built around this kind of step-by-step progress. You can see how we’ve helped insurance businesses in our Direct Commercial case study and our Acquis Insurance Management case study, or watch our 10-minute Dynamics 365 for Financial Services demo.
The FCA complaints return will look different from 2027, and some technical details are still being finalised. But the direction is clear: more granular, legal-entity-level complaints data, with a sharper focus on customers in vulnerable circumstances. If you structure your data well now, the final format becomes a mapping exercise, not a scramble.
If you’d like to talk through your complaints data and how Dynamics 365 Customer Service could support it, contact Cloud9. Or, if you’re already considering Dynamics 365 Customer Service, get a quote with our Clarity Tool.