Resources

Explore Essential AML Tools and Resources to Support Your Estate Agency​

Welcome to Smart Compliance’s resources page, your hub for valuable AML compliance tools and information

Your March AML checklist: what to review before audit pressure builds 

Your March AML checklist: what to review before audit pressure builds 

 

In this blog:
-Why is March the right time to review your AML process? 

-How can estate agents ensure consistency across branches and negotiators in AML checks? 

-What documentation gaps cause audit problems for estate agents? 

-Why does AML exception handling break down in many agencies? 

-What does an audit-ready AML file actually look like? 

-What practical AML checks should estate agents complete this month? 

-How does adviser-led AML support reduce audit pressure and uncertainty? 

 

March is often when compliance pressure starts to rise. 

Transactions increase. Pipelines move faster. Files stack up. And AML processes that felt manageable in January begin to feel stretched. 

An HMRC visit may not be scheduled. But audit readiness is not something to leave until a letter arrives. 

This checklist is designed as a practical internal review. It focuses on the areas that most often create problems later: inconsistency, weak documentation, and unclear exception handling. 

Use it to sense-check how confident your current process really is. 

 

Why March is the right time to review 

By March, most agencies have a clear view of how the year is shaping up. 

New staff may have joined. Volume may have increased. Processes may have adapted under pressure. 

This is exactly when small gaps appear: 

  • Notes become shorter. 
  • Exceptions are handled informally. 
  • Evidence is saved in different places. 
  • Decisions rely on memory rather than documentation. 

Left unchecked, these gaps compound. They do not usually cause immediate disruption. They create audit pain later. 

A March review allows issues to be corrected early, before volume builds further and before habits become embedded. 

 

Consistency across branches and negotiators 

In many audits, the core question is not whether checks were completed. 

It is whether they were completed consistently. 

Consider: 

  • Would two negotiators handle the same higher-risk case in the same way? 
  • Would two branches record decisions using the same structure? 
  • Is the same documentation standard applied across sales and lettings? 
  • Is there a clear escalation route for unusual cases? 

Inconsistent processes increase regulatory risk. They also slow teams down, because files must be reopened, explained and corrected later. 

Consistency does not mean being rigid. It means having a simple, shared way of working that everyone follows, with clear notes and proper oversight. 

 

The documentation gaps that create audit pain later 

Audit pressure rarely comes from routine checks. It comes from missing clarity. 

Common documentation gaps include: 

  • No clear explanation of why a risk rating was assigned. 
  • No written rationale for proceeding with incomplete information. 
  • Missing source of funds narrative, even where documents are present. 
  • Evidence saved, but not clearly referenced in file notes. 
  • No record of who reviewed or approved an exception. 

 

In practice, HMRC will look for a logical story within the file. 

What was checked.
What was identified.
What was decided.
Why that decision was reasonable. 

If a third party cannot follow that story without additional explanation, the file is unlikely to feel audit-ready. 

 

 

Exception handling: where most processes break 

Straightforward cases rarely expose weaknesses. Exception cases do. 

Pressure builds when something does not fit neatly into the standard process. This might include: 

  • ID that does not match perfectly 
  • Documents provided in stages 
  • Complex ownership structures 
  • Overseas clients 
  • Higher-risk source of funds profiles 

These situations require judgement, not just completion of a check. 

In many agencies, exception cases are either pushed back to negotiators or handled differently depending on who is available at the time. Over time, that creates two consistent problems: 

  • Decisions vary from person to person 
  • The reasoning behind those decisions is not clearly documented 

When reviewed months later, it becomes difficult to explain why a particular approach was taken. 

Exception handling should be structured, not improvised. A controlled process should include: 

  • A clear escalation route 
  • Defined criteria for when additional checks are required 
  • A record of adviser or senior review 
  • Written reasoning for the final decision 

Without that structure, audit confidence depends too heavily on individual experience rather than a consistent, defensible process. 

 

What “audit-ready” looks like in real files 

An audit-ready file does not rely on memory or verbal explanation. 

It shows: 

  • Clear identity verification records. 
  • Risk assessment with written rationale. 
  • Source of funds evidence supported by narrative. 
  • Notes explaining any anomalies or clarifications. 
  • A record of who reviewed and approved the case. 
  • Evidence stored in a consistent, retrievable format. 

Most importantly, it feels controlled. 

A reviewer should be able to open the file and understand the journey from first check to final decision without needing further clarification. 

That is the difference between “checks completed” and “audit-ready”. 

 

Five practical checks you can complete this month 

This month, select five recently completed files across different branches or negotiators. 

For each file, ask: 

  • Is the risk rating clearly explained in writing? 
  • Would someone unfamiliar with the case understand the source of funds position? 
  • Are any exceptions clearly recorded, with documented reasoning? 
  • Is all supporting evidence easy to locate within two minutes? 
  • Is there a clear record of review or oversight? 

If any of these answers are uncertain, the process may rely too heavily on individuals rather than structure. 

Small refinements now prevent significant pressure later. 

 

How adviser support reduces pressure and uncertainty 

Many compliance weaknesses do not stem from lack of intent. They stem from uncertainty. 

When documentation is unclear or a case feels unusual, teams often hesitate. That hesitation leads to delay, informal workarounds, or incomplete notes. 

Structured adviser support changes that dynamic. 

With human-led oversight: 

  • Exceptions are reviewed and resolved properly. 
  • Decisions are documented consistently. 
  • Negotiators are not left to interpret risk alone. 
  • Documentation standards are maintained across volume. 
  • Accountability is clear. 

Automation can complete checks. It cannot explain judgement. 

Audit confidence comes from combining technology with experienced human review, producing documentation that stands up to scrutiny. 

 

Final sense-check 

If this checklist highlights uncertainty in your current process, it is better to address it now. 

A one hour review can clarify: 

  • Whether your files would feel defensible under scrutiny. 
  • Where documentation standards may need tightening. 
  • How exception handling is working in practice. 
  • Whether your current approach genuinely transfers risk away from the branch. 

 

Book a one hour AML consultation 

If you would like a practical sense-check of how confident your current AML process really is, you can book a one hour AML consultation.

Training Video

Training Video