Anti-money laundering, customer due diligence and sanctions rule changes for banks and payment firms, with the opportunity each one opens up.
Updated monthly · Last updated: · Items leave the tracker once their month has passed.
Who sets AML and sanctions rules
| Region | Rules | Payments angle | Who it applies to |
|---|---|---|---|
| United States | FinCEN (Bank Secrecy Act rules), OFAC (sanctions) | AML programs, due diligence, suspicious activity, screening | Banks, money transmitters, card and payment firms |
| European Union | AML Regulation, AML Directive 6, AMLA | One EU rulebook and EU-level supervision | Banks, payment and e-money firms, crypto firms |
| Global | FATF standards | Country risk lists and the travel rule | All regulated firms |
What changed this month
A short log of new and changed items, updated every month.
Week of Nov 16, 2026
- Tracker launched with 5 AML and sanctions changes in the US and EU.
- Next deadline: EU Anti-Money Laundering Regulation, Jul 10, 2027.
- Moved here from the Payment Rules and US Regulators trackers so each item appears once.
Sanctions and AML tracker
Soonest first. Tap a region or a status to filter; tap again to clear.
FILTER BY REGION
FILTER BY STATUS
| Region | Rule or change | What it means | Opportunity | Key date |
|---|---|---|---|---|
| European Union | Anti-Money Laundering Regulation (AMLR) Our guide → · Source: Forvis Mazars (summary) | One EU-wide AML rulebook replaces national rules. | One AML product for 27 countries; AI monitoring demand. | Jul 10, 2027 Upcoming |
| European Union | AMLA starts selecting firms for direct supervision Anti-Money Laundering Authority (AMLA) Our guide → · Source: Jones Day | About 40 high-risk cross-border firms will be chosen; AMLA supervises them from Jan 1, 2028. | Readiness reviews for firms likely to fall under EU-level supervision. | Jul 1, 2027 Upcoming |
| United States | AML rule for investment advisers starts FinCEN Our guide → · Source: FinCEN | Registered and exempt reporting advisers need AML programs and suspicious activity reports. | AML program build-outs for advisers and their payment providers. | Jan 1, 2028 Upcoming |
| United States | FinCEN customer due diligence (proposed) FinCEN Our guide → · Source: FinCEN | New rules for checking who owns and controls company customers. | Simpler, risk-based KYC and onboarding; comment to shape the rule. | Comments early 2027 Proposed |
| United States | FinCEN AML/CFT program rule (proposed) FinCEN Our guide → · Source: BDO | AML programs must be effective, risk-based and reasonably designed. About 12 months to comply once final. | Risk assessments, transaction-monitoring tuning and program evidence. | Final rule date not set Proposed |
WHO OWNS THIS
Sanctions and AML: roles and sign-off
Each rule needs a named owner. The BSA/AML officer owns the program; sanctions compliance owns screening; financial crime operations runs cases; analytics owns monitoring rules; the Chief Risk Officer signs off.
1. Roles and responsibilities
- Writes the impact assessment
- Updates policies and the risk assessment
- Owns regulator contact
- Reports to the board
- Keeps lists and rules current
- Tests screening
- Handles true matches
- Certifies screening
- Updates procedures
- Trains investigators
- Files suspicious activity reports
- Confirms operations are ready
- Tunes rules and models
- Validates models
- Measures false positives
- Certifies monitoring
- Builds data and screening changes
- Plans releases
- Supports testing
- Reports status
- Interprets new rules
- Drafts comment letters
- Advises on reporting duties
- Signs the legal reading
- Sets risk appetite
- Accepts remaining risk
- Gives final sign-off
- Reports to the board
2. Who is accountable for what (RACI)
| Activity | BSA/AML officer | Sanctions lead | FinCrime ops | Analytics | Payments PM | Legal | CRO |
|---|---|---|---|---|---|---|---|
| Log a rule and name an owner | A | C | I | I | I | R | I |
| Impact assessment | A | C | C | C | R | C | I |
| Screening lists and rules | C | A | R | C | I | I | I |
| Monitoring rules and models | C | C | C | A | I | I | I |
| Customer due diligence changes | A | I | R | I | C | C | I |
| Regulator reporting | A | C | R | C | I | C | I |
| Program sign-off | R | R | R | R | R | C | A |
A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed.
3. From review to sign-off
4. Sign-off record
One line per rule. No signed line, no go-live.
| Item | Prepared by | Reviewed by | Signed off by | When | Evidence |
|---|---|---|---|---|---|
| EU AML Regulation readiness | BSA/AML officer | Legal counsel | Chief Risk Officer | Before Jul 10, 2027 | Gap assessment, policy updates |
| FinCEN program rule (proposed) | BSA/AML officer | Legal counsel | Chief Risk Officer | Plan once final | Gap assessment |
Titles differ by firm; small teams may combine roles, but the person who builds should not be the only one who signs off. General guidance, not legal advice.
Runbook: from an AML or sanctions rule to sign-off
How to handle an AML, due diligence or sanctions rule from this tracker. Use one runbook per rule. Each phase says when, why, what, who and how, and the evidence to keep.
▸1. Plan · Decide if the item applies to you, how big the change is, and who owns it.
When: As soon as an item appears on the tracker. Target: at least 90 days before the key date (T-90). For proposed rules, inside the comment window.
Why: Late discovery is the main reason teams miss deadlines, pay fines or ship rushed changes. Early planning turns a rule into a normal roadmap item.
What: Decide if the item applies to you, how big the change is, and who owns it.
Who: Owner: BSA/AML officer. With: Legal counsel (reads the rule), Sanctions compliance lead, Payments product manager (system impact).
Example: a new AML rule. Confirm which customers, products and payments are in scope.
How
- Open the official source linked in the tracker and read the actual text, not only the summary.
- Map it to your products, rails, systems, vendors and customers in scope.
- Run a short gap analysis: what we do today versus what the rule needs.
- Size the work (small, medium, large) and add it to the roadmap with a target date.
- Log risks, assumptions, issues and dependencies in the RAID log.
Evidence to keep
- Impact assessment (applies / does not apply, with reason)
- Gap analysis
- Epic or change request with owner and target date
- RAID log entry
▸2. Prepare · Turn the rule into requirements, a design, a test plan and a rollout plan.
When: T-90 to T-60 days.
Why: Clear requirements and a test plan stop rework and give auditors a straight line from the rule to the change.
What: Turn the rule into requirements, a design, a test plan and a rollout plan.
Who: Owner: BSA/AML officer. With: Financial crime analytics lead (monitoring), Financial crime operations lead (procedures), Payments product manager.
Example: map each rule clause to a policy, procedure, rule or report.
How
- Write requirements that quote the rule clause they come from.
- Agree the design and any vendor or partner changes, with dates.
- Build a traceability matrix: rule clause, requirement, test case, evidence.
- Plan test data, environments and a rollback.
- Book change windows and tell support and operations teams.
Evidence to keep
- Requirements with rule references
- Design or configuration decision
- Traceability matrix (draft)
- Test plan and rollback plan
▸3. Execute · Build or configure, test, and release the change safely.
When: T-60 days to go-live.
Why: This is where the change is built and proven. Testing against the rule, not just the feature, is what protects you.
What: Build or configure, test, and release the change safely.
Who: Owner: Financial crime operations lead. With: Financial crime analytics lead, Payments product manager, screening vendor.
Example: update due diligence steps and monitoring rules.
How
- Build or configure the change behind a flag where possible.
- Run unit, system, regression and negative tests, plus UAT with the business.
- Fix defects and re-test; keep the defect log current.
- Hold a go/no-go meeting with clear criteria.
- Release, watch live metrics and keep the rollback ready.
Evidence to keep
- Test results and defect log
- UAT sign-off
- Go/no-go record
- Change ticket and release notes
▸4. Evidence · One evidence pack that shows the rule was understood, built, tested and approved.
When: Collected all the way through; packaged by T-7 days.
Why: If it is not written down, it did not happen. Good evidence makes audits short and calm.
What: One evidence pack that shows the rule was understood, built, tested and approved.
Who: Owner: Financial crime operations lead. With: Financial crime analytics lead (model tests), Sanctions compliance lead (list tests).
Example: keep model tests, list tests and procedure versions.
How
- Create one folder per tracker item with a simple index.
- Store each document with date, version and owner.
- Complete the traceability matrix with links to every test and approval.
- Add screenshots or exports of live configuration where relevant.
- Record training or communications sent to staff and customers.
Evidence to keep
- Evidence index
- Final traceability matrix
- Configuration proof
- Training and communication records
▸5. Audit · Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
When: From T-7 days to 30 days after go-live.
Why: An independent check finds gaps before a regulator, scheme or customer does.
What: Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
Who: Owner: BSA/AML officer (control check). Independent check: Internal audit.
Example: sample alerts and cases for quality.
How
- Walk through the evidence pack against the rule text.
- Re-perform a sample of key tests or checks.
- Raise findings with a rating, owner and due date.
- Track findings to closure and re-test the fix.
Evidence to keep
- Control test results
- Findings log with owners and dates
- Closure evidence for each finding
▸6. Review · Post-implementation review: did it work, what broke, what we learned.
When: About 30 days after go-live.
Why: A short look back confirms the change works in real life and makes the next rule easier.
What: Post-implementation review: did it work, what broke, what we learned.
Who: Owner: BSA/AML officer. With: Financial crime analytics lead, Sanctions compliance lead (post-live review of alerts and false positives).
Example: review alert volumes and false positives.
How
- Check live metrics: errors, rejects, exceptions, complaints, incidents.
- Confirm all findings and defects are closed or accepted.
- Note lessons learned and update this runbook if needed.
- Update the tracker status and any related guides.
Evidence to keep
- Post-implementation review notes
- Metrics snapshot
- Lessons learned
▸7. Sign-off · Named people confirm the item is done and the evidence is complete.
When: After the review, and before closing the item.
Why: Formal sign-off shows clear ownership and closes the loop for auditors.
What: Named people confirm the item is done and the evidence is complete.
Who: Owner: the Chief Risk Officer (approves). Signers in order: BSA/AML officer, Legal counsel, Payments product manager, Financial crime analytics lead, Sanctions compliance lead, Financial crime operations lead.
Example: close the item when every signer has signed.
How
- Share the evidence pack and review notes with the approvers.
- Each approver confirms their part in writing, with date.
- Archive the pack in your GRC tool or records system.
- Close the epic and the RAID entries.
Evidence to keep
- Signed approvals (name, role, date)
- Archived evidence pack
- Closed epic and RAID items
Sign-off
Sign in this order: Prepared, then Reviewed, then Certified, then Approved. Each signer checks the evidence of the lines above. Close the item only when every line has a name, date and evidence link. The person who prepares cannot approve.
| # | Role | Stage | Confirms | Evidence | Name and date |
|---|---|---|---|---|---|
| 1 | BSA/AML officer | Prepared | Impact assessment done; program changes planned | Impact assessment | ________________ |
| 2 | Legal counsel | Reviewed | Reading of the rule is correct | Legal memo | ________________ |
| 3 | Payments product manager | Reviewed | System changes built and stable | Change ticket | ________________ |
| 4 | Financial crime analytics lead | Certified | Rules and models tested | Model test results | ________________ |
| 5 | Sanctions compliance lead | Certified | Screening lists and rules work | List test results | ________________ |
| 6 | Financial crime operations lead | Certified | Procedures updated; staff trained | Procedures, training records | ________________ |
| 7 | Chief Risk Officer | Approved | Accepts remaining risk and closes the item | Signed approval | ________________ |
Tip: copy this runbook into your own tracker or GRC tool, one copy per rule. Dates are relative to the key date shown in the tracker (T-90 means 90 days before).
Risk and control self-assessment (RCSA): Sanctions and AML
The main risks for this area, the controls that reduce them, and the risk left after those controls. 4 risks are specific to this area and 6 are shared by every tracker (C1 to C6). Owners match the roles in the Who owns this section above. Reviewed every quarter and checked by the second line. Preventive controls lower likelihood; detective and corrective controls lower impact. Read more in our RCSA guide.
10 risks assessed for this area. Controls bring every high inherent risk down to medium or low.
How to read the heat map: each dot is a risk. It starts at its inherent rating (no controls) and moves to its residual rating (after controls). Score = likelihood x impact: 1 to 6 Low, 8 to 12 Medium, 15 to 25 High. Mid-blue dots are this area; navy dots are shared risks.
QUARTERLY RCSA CYCLE
RISK AND CONTROL REGISTER
| ID | Type | Risk and cause | Control | Owner | Inherent | Residual |
|---|---|---|---|---|---|---|
| AML-R1 | This area | A sanctioned party is paid Cause: Lists updated late; fuzzy matching weak | Daily list updates, screening tests and match review Preventive · Daily | Sanctions compliance lead | High 15 L3 x I5 | Low 5 L1 x I5 Control: Effective |
| AML-R2 | This area | Suspicious activity is missed Cause: Monitoring rules out of date | Rule tuning and model validation each year Preventive and detective · Yearly | Financial crime analytics lead | High 15 L3 x I5 | Medium 8 L2 x I4 Control: Partly effective |
| AML-R3 | This area | Customer due diligence is incomplete Cause: Owners and controllers not checked | Due diligence checklist and periodic reviews Preventive and detective · Per customer | Financial crime operations lead | Medium 12 L3 x I4 | Low 6 L2 x I3 Control: Effective |
| AML-R4 | This area | Too many false alerts slow investigations Cause: Rules tuned too wide | False-positive tracking and quarterly tuning Preventive and detective · Quarterly | Financial crime analytics lead | Medium 12 L4 x I3 | Low 6 L2 x I3 Control: Effective |
| C1 | Shared | A rule change is missed Cause: No owner watches the sources; news arrives late | Weekly tracker review; every new item gets a named owner within 5 days Preventive and detective · Weekly | Legal counsel | High 20 L4 x I5 | Medium 8 L2 x I4 Control: Effective |
| C2 | Shared | A rule is read the wrong way Cause: Summaries used instead of the rule text; no expert review | The impact assessment is signed against the source text Preventive · Per item | Legal counsel | High 15 L3 x I5 | Medium 10 L2 x I5 Control: Effective |
| C3 | Shared | A deadline is missed Cause: Work starts too late; dependencies not tracked | Planning starts at T-90; RAID log and go/no-go before release Preventive and detective · Per item | BSA/AML officer | High 16 L4 x I4 | Low 6 L2 x I3 Control: Effective |
| C4 | Shared | Testing does not cover the rule Cause: Tests check features, not rule clauses | Traceability from each rule clause to a test, with sign-off Preventive · Per release | Financial crime analytics lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| C5 | Shared | Evidence is missing at audit time Cause: Documents spread across tools; no index | Evidence pack with an index, checked at T-7 Preventive · Per item | BSA/AML officer | Medium 9 L3 x I3 | Low 3 L1 x I3 Control: Effective |
| C6 | Shared | Audit findings stay open Cause: No due dates or follow-up | Findings log with owner and due date; monthly review Preventive and detective · Monthly | BSA/AML officer | Medium 9 L3 x I3 | Low 4 L2 x I2 Control: Partly effective |
Open actions
- AML-R2: validate monitoring models against the EU AML Regulation. Owner: Financial crime analytics lead.
- AML-R1: test screening for name variants in new scripts. Owner: Sanctions compliance lead.
- Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Risk and internal audit.
Quarterly attestation
BSA/AML officer and Financial crime operations lead (first line): confirm risks, controls and ratings are current. ________________
Risk and internal audit (second line review): confirms the review and challenge. ________________
Chief Risk Officer: accepts residual risk. ________________
This is a sample RCSA for planning and training. Adjust risks, ratings and owners to your own organisation before use. The full cross-area register is in the monthly portfolio status report.
This tracker is a summary for planning, not legal advice. Dates can change, so always check the official source before acting. The Opportunity column is our own view. Summaries are written in our own words; linked pages remain the property of their publishers. Corrections: sp@paymentconsultant.top.
© 2026 SP Sankar · paymentconsultant.top. This tracker, its summaries, diagrams and layout are original work and are protected. Please do not copy, republish or scrape this page without written permission. You are welcome to link to it. See also Payment Rules Tracker and Payment Tech News.