Compliance

What should our compliance records show if a supervisor asks to see them?

By Paul Meakin8 min read

Close up view of red office binders neatly organized on a shelf
Photo: Zulfugar Karimov on Pexels

What does a compliance folder actually prove?

Less than people hope. Open a typical one and you find a scanned passport from when the customer first signed up, a risk assessment last saved by someone who has since left, and a policy document that was signed once and never opened again. Everything is there. None of it says whether anyone has looked at that customer since the day they arrived.

That is the gap. A folder proves a document existed at some point. It does not prove that a check was done, who did it, what they found or what they decided. And it says nothing at all about the checks that should have happened since.

A compliance folder is not a compliance system. It is where a system would keep its paperwork, if there were one.

What does the guidance say you must be able to show?

This section uses HMRC's guidance, written for the businesses HMRC supervises under the Money Laundering Regulations. If a professional body or another regulator supervises you, follow their guidance instead. The shape is similar. The detail is theirs.

HMRC's page on your responsibilities under money laundering supervision says you need to keep a record of all customer due diligence measures that you carry out, and lists what that includes: identification documents, risk assessments, your policies, controls and procedures, and training records. It says you must keep your records for 5 years, beginning from the date a business relationship ends or the date a transaction is completed. Scanned, computerised and electronic records are all on its list of acceptable formats.

HMRC's record keeping guidance explains why. The records are evidence of the work you have done to comply, and evidence for use in any investigation HMRC carries out. For transactions, it asks for enough supporting records to enable the transaction to be reconstructed. It also lists records of your risk assessment, your policies and any changes to them, the steps taken to communicate them, and the training you have provided.

Then comes the line that matters most. HMRC's guidance on policies, controls and procedures says the obligation is central to ensuring that PCPs are not only documented but actively implemented and enforced across the business. It expects policies to be reviewed at least annually, even if no changes seem necessary, with the review date recorded. If nothing changes, you should still keep a record of the review.

So the question a supervisor is really asking is not whether you have a policy. It is whether you can show the policy being followed.

Why is ongoing monitoring the part that slips?

Because onboarding has a moment and monitoring does not. A new customer arrives, someone runs the checks, the file is saved. After that there is no natural point at which anyone looks again.

The guidance does not allow for that. HMRC's page on ongoing monitoring says you must continue to monitor a business relationship after it is established and for its duration. That includes reviewing customer due diligence information and records to keep them up to date, including replacing expired documents with valid copies, and reviewing beneficial ownership for corporate clients so it remains accurate. It also expects action when something changes, such as a change in the customer's circumstances that could affect their risk assessment, or transactions that look unusual against what you expected.

In a folder, none of that has a date attached. Passports expire quietly. A company changes hands and nobody notices. The review that was meant to happen sits in one person's memory, and memory is a poor scheduler.

What does an audit trail look like when someone does ask?

It answers questions quickly, without anyone rebuilding the story from inboxes. Here is the difference in practice.

The question Answered from a folder Answered from a logged system
When was this customer last reviewed? Nobody is sure A dated entry with the reviewer's name
Is their ID still valid? Someone opens the scan and checks The expiry date is recorded and flagged before it passes
Who approved this higher risk customer? Buried in an email thread Recorded against the customer, with the reason
When was the policy last reviewed? The file's last saved date, maybe Each review logged, including the ones with no changes
Has everyone been trained on the current version? A spreadsheet someone used to update Training records tied to each version of the policy

The policies guidance also expects you to respond quickly and fully when HMRC, the police or other named authorities ask whether you have had a business relationship with a person in the past five years, and to explain the nature of that relationship. With a folder, that is an afternoon of searching. With a register of customers and dated checks, it is a filtered list.

Where do people get this wrong?

The first mistake is storing the document and not the check. A passport scan with no note of who verified it, when, against what, and what they concluded is a picture of a passport. The check is the thing a supervisor wants to see.

The second is keeping everything for ever. The record keeping guidance says that when the retention period expires, you must delete any personal data unless one of a small set of exceptions applies, such as a legal requirement to keep it or reasonable grounds to believe it is needed for legal proceedings. A folder nobody prunes turns a compliance duty into a data protection problem.

The third is the annual review that lives in someone's calendar. When that person is on holiday, or leaves, the review simply does not happen, and there is no record that it was ever due.

The fourth is treating software as the compliance. A system can schedule, remind, record and report. It cannot decide your risk appetite, and it does not take on your obligations. HMRC's guidance makes the same point about delegating record keeping to a third party: it is ultimately your responsibility to comply.

Can the checks run on a schedule rather than on memory?

Yes. This is where the remembering stops being anyone's job. The idea is simple. Every customer has a record, and every record carries dates: when they were onboarded, when their ID expires, when they were last reviewed, and when the next review is due based on the risk level your policy sets.

A scheduled job reads those dates and does the remembering. When a review falls due or a document is close to expiry, it opens a task for a named person and tells them. That person does the review, records what they looked at and what they decided, and the next due date is set. If a task sits untouched, it goes to whoever your policy says should know.

The same approach works for the business level records. The policy review comes round each year and gets logged whether or not anything changed. Each new version of the policy goes out to staff, and the system records who received it. Training is tied to the version people were trained on, so the question of who has seen the current one has an answer.

None of this needs to be elaborate. For a small firm it might be a structured register in Google Sheets with a script that runs on a timer. For a larger one it might be a web application with access controls and a log of every change. Either way, the decisions stay with people. The system makes sure the questions get asked on time and the answers get written down. We build this as process automation, around the policy you already have.

When is this not the answer?

If you have a small number of customers and very little changes. A dated register with a review column, kept honestly, may be all you need. Do not build a system to look after a list you can read in one sitting.

When the question is about the rules themselves. Whether you are in scope, which customers count as higher risk and how often each should be reviewed are matters for your supervisor's guidance and, if you need it, a compliance adviser. We build the systems that carry out and record your process. We are not regulated advisers, and we do not tell you what your obligations are.

When the problem is a missing policy rather than a missing system. Automating the reminders for a process nobody has written down only produces tidy reminders for the wrong things. Write the policy first.

A supervisor visit already booked with records out of order is a job for proper advice now, not a build that finishes after the visit.

Where do you start?

Pick a handful of customer files at random and try to answer the questions in the table above from what is in them, without asking anyone. Note which answers you can find, which take a search, and which nobody can give. That list is your gap, and it often comes down to a small number of dates and decisions nobody is recording.

If the list is longer than you would like, tell us what's stuck and we'll map the quickest fix. We will tell you straight whether it needs a register and a reminder, a fuller system, or nothing more than an afternoon of tidying. Time to talk yet?

Common questions

How long do money laundering records have to be kept?

HMRC's guidance for the businesses it supervises says records must be kept for 5 years, beginning from the date a business relationship ends or the date a transaction is completed. Other supervisors publish their own guidance.

Do we still need a record if the annual policy review changed nothing?

Yes. HMRC's guidance on policies, controls and procedures says that if no changes are made, you should still keep a record of the review, and that the review date should be recorded.

Can our compliance records be kept digitally?

HMRC's page on your responsibilities lists scanned, computerised and electronic records among the acceptable formats. What matters is that the records are complete and can be produced when asked.

If a third party keeps our records, are we covered?

No. HMRC's record keeping guidance says that if you delegate record keeping to a third party, it is ultimately your responsibility to comply, so you need to know the third party is keeping them properly.

Sources

  1. Your responsibilities under money laundering supervision, GOV.UK
  2. AMLG11700, Record Keeping, HMRC internal manual, GOV.UK
  3. AMLG1900, Policies, Controls and Procedures (PCPs), HMRC internal manual, GOV.UK
  4. AMLG11411, Ongoing monitoring of business relationships, HMRC internal manual, GOV.UK

Paul Meakin, Founder

Twenty years of fixing businesses from the inside, eighteen of them in recruitment from consultant to national operations, before building the automation, web applications and compliance systems Staxxd runs today.

More about Paul

Time to talk yet?

Tell us what's stuck and we'll map the quickest fix. Fifteen minutes, no obligation.

Time to talk yet?