Skip to main content
Curvestone AI
Definition

CRM compliance checks: what a separate file check still adds

Updated

Why the question is coming up now

CRM vendors are adding compliance features to new versions, and firms are being migrated onto them. An operations lead at a UK mortgage brokerage described it on a call with us: "version two that they're migrating us onto has a little bit more of a compliance checking feature in it."

The same lead wanted to understand "if there are any gaps". It is the right question. A firm that pays for a separate file check and gets a compliance feature in its CRM upgrade should test the overlap, not assume it.

Completeness checks and content checks

Compliance checking inside a case system can mean two different things.

  • Completeness checks confirm that the case is in order: a required field is filled, a document is attached, a stage was signed off before the next one opened. They stop a case moving with something missing.
  • Content checks read what the documents say and test it against a standard: does the income in the fact-find match the payslips, does the suitability letter explain the recommendation the client actually received, is the reason for adding a fee to the loan recorded.

Both are useful. They answer different questions. A case can pass every completeness check and still fail a file review, because the letter is there but its reasoning does not match the rest of the file. That is why a vendor's description of "compliance checking" needs a closer look.

Six tests for your CRM's compliance feature

Ask the CRM vendor, or test it yourself:

  1. Does it read documents or fields? If the check confirms a document exists but never reads it, it cannot find a contradiction between two documents.
  2. Whose rules does it run? A fixed rule set from the vendor, or your own checklist? When you change a question, is the change versioned with an author and a date?
  3. Which cases does it see? Only the cases keyed into that CRM. A network with appointed representatives on other systems, or cases that arrive by another route, will have gaps in coverage.
  4. When does it run? At submission, before the offer, or only when someone opens the case? A check that runs after completion finds problems too late to fix for that customer.
  5. What record does it leave? For each failure you need the question, the answer, the evidence it relied on, who overrode it and why. Without that record you cannot group failures by adviser or root cause.
  6. Who sees the failures? If the adviser can click past a warning with no review, the check is a prompt, not a control.

Where a separate file check fills the gap

A dedicated file check earns its place where the CRM feature fails one of those tests. The usual gaps are:

  • Content across documents. Reading the fact-find, payslips, illustration and suitability letter together, and flagging where they disagree.
  • Your own standard. Running your firm's checklist, question by question, rather than a generic set, with a version history when it changes.
  • One standard across systems. Applying the same checks to every case whichever CRM or route it came through.
  • An evidence trail. A result for each question with the source cited, so compliance can review the failures and the board report can draw on the results.

Where the CRM feature passes all six tests for your cases, a second tool may add little. Where it passes only the first, it is a completeness check, and your file review still carries the monitoring.

A practical test: take the files that failed your last quarter's reviews and ask whether the CRM feature would have flagged each one. That shows the overlap in your own cases, not in a demo.

What the rules ask, and what they leave to you

The Consumer Duty does not specify how files are checked. PRIN 2A.9.8R requires a firm to "regularly monitor the outcomes retail customers receive", and PRIN 2A.9.11R requires "processes to identify the root causes" of failures. Under PRIN 2A.8.3R, the board report sets out "the results of its monitoring under PRIN 2A.9 and any actions required".

FCA guidance in FG22/5 accepts that file reviews "will be based on a risk-based sample". The size of that sample is a choice, and the effort of checking each file shapes it. A check that runs on every submitted case gives the board report more to stand on than one that runs on the cases someone had time to open.

If your CRM is changing, our guide to how compliance checks connect to a mortgage CRM covers the integration routes, and running your own checklist in an automated check covers how firm rules and versions fit together.

Curvestone works alongside the CRM rather than replacing it. With adapters for OMS and Finova, a submitted case goes to the check and the result comes back to the case record, with every document checked against your own checklist, question by question, and the evidence cited.

Questions

Frequently asked questions

Does the FCA require a separate compliance file-checking tool?
No. The FCA describes itself as technology-agnostic and does not prescribe a tool. The Consumer Duty requires firms to regularly monitor customer outcomes, identify root causes of failures and report the results to the governing body. Whether a CRM feature, a separate check or a manual review does that is the firm's decision.
Can a CRM compliance feature and a separate file check run on the same case?
Yes. With a CRM integration, a submitted case goes to the separate check automatically and the result comes back to the case record. The CRM feature can stop a case moving with a missing document, and the file check can then read what the documents say against your own checklist, with the evidence for each answer.
How do we test whether our CRM's compliance checking is enough?
Take the files that failed your last quarter's file reviews and ask whether the CRM feature would have flagged each failure. Then ask the vendor the six questions in this guide: what it reads, whose rules it runs, which cases it sees, when it runs, what record it leaves and who reviews failures.
Sources
  1. 01FCA Handbook: PRIN 2A.9 Monitoring of consumer outcomes
  2. 02FCA Handbook: PRIN 2A.8 Governance and culture
  3. 03FG22/5 Final non-Handbook guidance for firms on the Consumer Duty (FCA)
  4. 04FCA: AI Update
Related reading
Dawid Kotur
Written by

Dawid Kotur

CEO and co-founder, Curvestone

Dawid co-founded Curvestone in 2024 after a decade working at the intersection of financial services and applied machine learning. He writes about the strategic direction of regulated-industry AI, the FCA's evolving approach to model risk, and the operational changes UK lenders are making in response to Consumer Duty. He sits on the FCA Smart Data Accelerator advisory cohort.

LinkedIn

Compliance that thinksahead. Automatically.

Join mortgage networks, lenders, and legal firms using Curvestone to review cases at scale.