AML for lawyers: privilege, scope and the Bar-filter route
A practical guide to lawyer AML workflows that respect legal privilege while still documenting regulated transactional work.
Executive summary
Lawyer AML needs mandate scoping before ordinary CDD routing.Privileged legal analysis should be separated from AML evidence.Reporting paths must respect the profession’s protected route.Lawyer AML is different because the compliance workflow must respect professional secrecy, legal privilege and the Bar’s filtering role. A generic AML file is not enough where privileged legal analysis and regulated transactional assistance may sit close together.
The key is scoping. A lawyer needs to decide whether the mandate falls inside AML obligations, whether privilege affects the reporting path, and whether records should be partitioned from the ordinary case file.
A defensible lawyer workflow does not weaken AML. It makes the route explicit: scope the mandate, protect privileged content, document non-privileged AML evidence, escalate through the correct internal and Bar-sensitive route, and keep accountable sign-off.
Who this applies to
This guide is for lawyers and law firms whose work sometimes falls inside AML scope, especially transactional mandates involving companies, real estate, funds or tax structuring.
- Law firms with mixed litigation and transactional practices
- Lawyers assisting company formation or transfer
- Real-estate and client-money mandates
- Tax-structuring or cross-border advisory work
- AMLCOs designing privilege-aware workflows
Legal and supervisory context
The hard part for lawyers is not whether AML matters. It is how to apply AML duties without flattening professional secrecy, privilege and Bar-filter obligations into an ordinary corporate workflow.
A lawyer-specific workflow begins with scope and route: what is the mandate, which parts are privileged, which AML records are separate, and how would a reporting decision be escalated.
What the office must actually do
The office should convert the legal requirement into a repeatable workflow with named owners, dated records and a clear review route.
- Classify the mandate.
- Identify privileged content and protected communications.
- Capture AML evidence separately from legal advice notes.
- Define who can view reporting records.
- Escalate potential reports through the correct lawyer route.
- Keep sign-off and rationale.
What good evidence looks like
The evidence should show that the firm did not ignore AML, but also did not expose privileged legal analysis unnecessarily.
Common mistakes supervisors find
- Using the same file space for legal advice and AML reporting notes.
- Treating every lawyer matter as out of scope.
- Treating every lawyer matter as ordinary AML without privilege review.
- Letting junior staff decide scope without sign-off.
Practical checklist
- Scope the mandate.
- Mark privilege-sensitive material.
- Open separate AML record.
- Screen parties where in scope.
- Document UBO and source-of-funds evidence.
- Escalate reporting concerns through the correct route.
- Keep signed scope and privilege rationale.
- Routes lawyer files through privilege-aware scoping.
- Partitions AML evidence from case-file records.
- Supports Bar-filter reporting preparation.
- Requires senior sign-off for scope and reporting decisions.
- Keeps inspection evidence without exposing unnecessary privileged content.
FAQ
Are all lawyer services inside AML scope?
No. Scope depends on the mandate and regulated activity. That is why file-level scoping matters.
Can privilege remove every AML duty?
No. It affects route, access and reporting treatment; it should not become an undocumented blanket exemption.
What should a supervisor see?
A clear scope decision, AML evidence where applicable, protected handling of privileged content and accountable sign-off.
Official references
From knowledge to compliance
Reading is a start. Sceau turns these obligations into a workflow that runs itself and proves itself.
Book a demo