AML Policy: What to Include, Section by Section

What an AML policy must say section by section, how it differs from procedures, who approves it, and the exam findings a weak policy draws.
Alexandre Berkovic

TL;DR: An AML policy is the governing document that states what an institution commits to do about money laundering, who owns each commitment, and how the board oversees it. A usable policy has about 15 sections, stays short enough to be followed, and leaves step-by-step instructions to procedures. Weak documents have consequences: Crowe counted 42 BSA/AML enforcement actions in 2024, up from 29 in 2023, and federal agencies treat a program that departs from its written policies as a failure to implement.

What an AML Policy Actually Is

An AML policy, also called an anti-money laundering policy or BSA/AML policy, is the top-level written statement of an institution's AML commitments. The regulations ask for something slightly different. Neither 31 CFR 1020.210 nor the OCC's 12 CFR 21.21 uses the word "policy." They require a written compliance program, approved by the board and reflected in the minutes. A common structure makes the policy the core of that written program, supported by procedures, a risk assessment and a training plan.

The FFIEC Manual's internal controls section defines internal controls as the bank's "policies, procedures, and processes", and a policy is one layer of that set. Sphinx's overview of the five pillars of an AML compliance program covers the required components themselves. This article covers how to write them down.

Policy, Procedure, Process

The policy states what the institution will do and who is accountable. Procedures state how staff do it. Processes are the work as it actually runs in systems and teams. The FFIEC program sections use the three terms together without separately defining them, so the split below is drafting practice. Each institution should state its own version on the policy's first page.

LayerAnswersExampleTypical approverChanges when
PolicyWhat and whoThe BSA officer decides whether a SAR is filedBoardRisk, law or accountability changes
ProcedureHow, in what order, by whenSteps from L1 alert review to SAR committee packetBSA officerA workflow or system changes
ProcessWhat actually happensQueue rules and case fields in the monitoring toolOperations owner under procedureConfiguration or staffing changes

A frequent drafting error is placing procedure in the policy. Each system name and form number written into a board document becomes a promise that needs board action to change.

An AML Policy Template, Section by Section

The outline below works as an AML policy template for a U.S. bank, and fintechs and MSBs can adapt it. Adjust depth to the institution's risk profile, and have counsel review the final text.

SectionWhat it must say
1. Purpose and legal basisThe rules the program implements, including 31 CFR 1020.210 and the regulator's rule
2. ScopeEntities, branches, business lines and agents covered, with any exclusions stated
3. Board and senior managementBoard approval, oversight, resourcing and the reports the board receives, including notice of SARs filed
4. BSA officerDesignation, authority, independence, access to resources, reporting line and named backup role
5. Risk assessmentMethodology owner, categories covered, review cycle and events that force an update
6. Customer identificationCommitment to a risk-based CIP that forms a reasonable belief of each customer's identity
7. Due diligence and beneficial ownershipCustomer risk profiles, risk rating ownership, enhanced due diligence triggers and refresh approach
8. Monitoring and alertsWhich activity is monitored, who owns scenarios and thresholds, and who approves changes
9. Suspicious activity reportingReferral channels, decision authority, the 30 and 60 day deadlines, confidentiality and continuing activity
10. Currency reporting and recordsCTR filing above $10,000, exemptions if used, and retention periods including five years for SARs
11. Information sharing and law enforcementOwnership of 314(a) responses, whether the institution participates in 314(b), and subpoena handling
12. SanctionsCross-reference to the OFAC program, which is separate from the BSA
13. Third partiesWhich BSA functions third parties perform, oversight, data access and retained responsibility
14. Training and testingRole-based training, board training, attendance records, independent testing and its reporting line
15. Maintenance and exceptionsPolicy owner, review cycle, update triggers, version history, exception approval and issue tracking

Four sections that deserve extra drafting time

Section 4 sets the officer's authority in writing, so it needs real language on stopping or escalating a product launch. BSA officer responsibilities covers what examiners look for in the role. Refer to the officer by title in the policy and name the person in the board resolution, so a departure does not reopen the whole document.

Section 5 should explain how results reach the rest of the program. The FFIEC Manual expects controls to incorporate the risk assessment and any changes in risk. The policy needs only the owner, the cycle and the triggers. The method belongs in the BSA/AML risk assessment.

Section 9 is where the separation of duties has to be explicit. The FFIEC Manual says employees who complete SARs and CTRs generally should not also decide whether to file them or grant exemptions. Sample language:

The decision to file or not file a SAR rests with the BSA Officer or the SAR Committee chaired by the BSA Officer. No business line employee may approve, delay or veto that decision. Any attempt to do so must be reported to the Board Risk Committee.

Section 15 keeps the policy current. Sample language:

The BSA Officer reviews this Policy at least annually and within 30 days of any new product launch, material change in customer base, change in applicable regulation, or examination or audit finding that affects its content. Each revision is recorded with its date, author, summary of change and approval.

Thirty days is an example. Whatever period goes in, the institution has to be able to meet it every time.

Approval and Ownership

Federally supervised banks must have the board approve the written program and note the approval in the minutes. The BSA officer typically owns drafting and maintenance, with counsel reviewing and the board or a designated committee approving. Keep the approval traceable: the minutes should identify the document version approved, so an examiner can match the two.

31 CFR 1022.210 requires an MSB's program to be in writing and available to Treasury on request, and it charges the designated compliance person with keeping the program updated. Under the April 2026 proposal, the board, an equivalent governing body or appropriate senior management could approve the written program. The current bank rule still names the board, and the proposal had not been finalized as of early November 2026.

Independence limits who can hold the pen. The FFIEC Manual says outside auditors or consultants performing BSA testing should not be involved in functions such as developing policies and procedures. A consultant who wrote the policy should not test it.

The bank program rules set no review interval. The FFIEC Manual expects timely updates in response to regulatory changes and changes in risk, so an annual review plus defined triggers is a sensible default.

Keeping the Policy Matched to the Work

A policy is only as defensible as the institution's ability to show it being followed. The federal banking agencies' 2020 joint statement on BSA/AML enforcement says institution-issued policy statements alone are not sufficient, and that the program as implemented must be consistent with written policies, procedures and processes. Five habits keep the two aligned:

  • Write only what the team does today or has funded and dated.
  • Keep a commitments register. List each "must" in the policy with its procedure, control owner and the evidence that proves it happened.
  • Gate change. New products, vendors and threshold changes should not go live until someone has checked the register.
  • Test on a schedule. Each quarter, pick several commitments and pull a small sample of files to see whether the evidence exists.
  • Communicate revisions. Train affected staff on each change and retain the record, since the FFIEC Manual lists poor communication of policy changes among the causes of violations.

Common Exam Findings

Policy findings tend to appear as the root cause of a monitoring, due diligence or staffing issue. Crowe's review of 2024 actions found suspicious activity monitoring deficiencies in 28 of 42 actions and described one bank whose outdated policies and procedures led to inconsistent application across its operations. Of the actions against banks, 54% involved institutions under $1 billion in assets.

The FFIEC Manual's list of root causes translates directly into what to look for in a policy review:

  • A product, customer type or geography operating without coverage in the policy or risk assessment
  • Staff who cannot describe the policy, or who follow an informal version of it
  • Commitments to reviews, refreshes or reports that the file evidence does not support
  • Revisions never communicated to the people doing the work
  • Board approval missing from the minutes, or minutes that do not identify the version approved

Severity depends on pattern. The FFIEC Manual says minor weaknesses and technical violations alone do not make a program inadequate, while the joint statement requires a cease and desist order when an institution fails to correct a previously reported program problem. Treat any policy commitment made in response to a finding as a tracked deliverable. Sphinx's guide to community bank BSA exam preparation covers the wider exam file.

Should a Rewrite Wait for the Final Rule?

A BSA officer with a stale policy should rewrite it now and build the document so it can absorb the final rule. FinCEN's April 2026 proposal would place risk assessment processes within internal policies, procedures and controls, require a U.S.-based AML/CFT officer, and require review and appropriate incorporation of the AML/CFT Priorities. FinCEN proposes 12 months for implementation after a final rule. In the template above, those changes mostly touch sections 4, 5 and 7. Keep current terminology and the current approval standard until the final text issues.

Where Sphinx Fits

Sphinx is an investigation layer inside the tools a team already uses, so the quality of its output depends on written SOPs that reflect the policy. Its AI agents prepare evidence, apply those SOPs and produce a traceable recommendation, and the team keeps final approval. Sphinx reports 94-98% agreement with analysts. Sphinx does not write the policy, set risk appetite, score transactions or block payments in real time.

Frequently Asked Questions

What should an AML policy include?

An AML policy should cover scope, board oversight, the BSA officer, risk assessment, customer identification, due diligence, monitoring, SAR and CTR reporting, recordkeeping, information sharing, sanctions linkage, third parties, training, independent testing and policy maintenance. Each section should state the commitment and name an owner.

What is the difference between an AML policy and AML procedures?

The policy states what the institution will do and who is accountable, and the board normally approves it. Procedures state how staff carry out each commitment and can change without board action if the policy allows. The FFIEC BSA/AML Manual groups the two together, so each institution should define the split in its own document.

Who must approve an AML policy?

Federally supervised banks must have the board of directors approve the written BSA/AML compliance program and note that approval in the minutes. FinCEN's April 2026 proposal would allow approval by the board, an equivalent governing body or appropriate senior management. That proposal had not been finalized as of early November 2026.

How often should an AML policy be updated?

The bank rules set no fixed interval, and the FFIEC Manual expects timely updates when regulations or risks change. An annual review with triggers for new products, regulatory changes and exam findings is a common approach. The policy should state its own cycle, because examiners can test against it.

Can a company use an AML policy template?

A template works as a starting structure. The FFIEC Manual expects policies to align with the institution's own risk profile, so generic language that does not match actual products, customers and workflows creates findings.