Auditing AML Transactions
Screens transaction data for suspicious patterns using red flag typologies and structures SAR narrative elements for BSA/AML compliance.
When To Use
- Transaction monitoring system generates an alert requiring human review
- BSA officer receives a referral (internal, law enforcement, or examiner finding)
- Periodic look-back or enhanced due diligence review of high-risk accounts
- Continuation SAR is due on the 90-day cycle
- Independent audit requires sample transaction review
- 314(b) information-sharing request received from another institution
Inputs To Gather
Collect all items below before starting review. If transaction records are unavailable, STOP — document the gap and escalate.
Institution & Scope
- Institution type (bank, MSB, broker-dealer, credit union, insurance, casino, other) [VERIFY]
- Charter/license jurisdiction and primary regulator [VERIFY]
- BSA/AML program status (established / recently remediated / under consent order)
- Review period (start and end dates)
- Alert source and alert/case ID
Subject Information
- Subject name(s) — individuals and/or entities
- Account number(s), account type(s), and open date
- Customer risk rating (Low / Medium / High / Unrated)
- KYC profile: stated occupation, income, expected activity, source of funds
- Prior SAR history on this subject
Data Sources
Confirm availability of each: transaction records (debits/credits), wire transfer details (originator/beneficiary), cash activity and CTR history, check images and deposit slips, account statements, CDD/EDD documentation, OFAC/sanctions screening results, negative news and adverse media, law enforcement subpoenas or 314(b) requests.
Workflow
Step 1 — Transaction Profiling
Summarize account activity for the review period:
| Metric |
Value |
| Total credits (count / dollar) |
|
| Total debits (count / dollar) |
|
| Cash-in / Cash-out (count / dollar) |
|
| Wire-in / Wire-out (count / dollar) |
|
| ACH/EFT and check activity (count / dollar) |
|
| Average and largest single transaction |
|
| CTRs filed during period |
|
| Jurisdictions involved |
|
Compare observed activity against three baselines:
- KYC expected activity — Does volume/type match customer declarations?
- Peer group — Consistent with similarly situated customers?
- Historical baseline — Has pattern shifted from prior periods?
Flag material deviations with [DEVIATION] and quantify the variance.
Step 2 — Red Flag Identification
Screen activity against recognized typologies. For each red flag identified, document:
- Red flag typology — Name from reference taxonomy
- Category — Structuring / Rapid Movement / Geographic / Shell-Layering / Trade-Based / Behavioral / Other
- Transactions implicated — Date, amount, type, counterparty
- Severity — High / Medium / Low
- Explanation — Why this pattern is suspicious in context
Key thresholds:
- CTR: $10,000 cash (single or aggregate same-business-day). Transactions just below are a structuring indicator. [VERIFY current threshold]
- SAR dollar minimum: $5,000+ with known suspect; $25,000+ with no identified suspect (banks). No dollar minimum for MSBs. [VERIFY by institution type]
- Rapid movement: Funds deposited and withdrawn/transferred within 48 hours with no apparent business purpose.
- Round-dollar transfers: Unusual frequency of round-amount wires inconsistent with commercial invoicing.
Step 3 — OFAC & Sanctions Screening
Confirm whether any party to flagged transactions appears on:
- OFAC SDN List and Consolidated Sanctions List
- FinCEN 311 Special Measures (jurisdictions/institutions)
- EU/UN sanctions lists (if applicable) [VERIFY applicability]
- FATF High-Risk and Non-Cooperative Jurisdictions list
Record each counterparty/jurisdiction screened, the result, list version, and date. If a potential OFAC match is identified, escalate immediately — OFAC obligations are strict liability with a shorter timeline than SAR filing.
Step 4 — Disposition
Reach one of four dispositions:
| Disposition |
Criteria |
Action |
| File SAR |
Suspicious, unexplained, meets dollar thresholds |
Proceed to Step 5 |
| Close — Below Threshold |
Concerning but below SAR dollar minimums |
Document rationale; retain 5 years; consider enhanced monitoring |
| Close — Explained |
Legitimate purpose confirmed with documentation |
Document rationale and evidence; retain 5 years |
| Escalate |
OFAC match, law enforcement nexus, or insider involvement |
Immediate escalation per institution policy |
Document rationale for every disposition. Examiners review closed cases as closely as filed SARs.
Step 5 — SAR Narrative Drafting
The narrative must answer who, what, when, where, why, and how.
Structure:
- Subject Information — Full legal name(s), DOB, SSN/TIN (if available), address, account relationship, risk rating and basis.
- Suspicious Activity Description — Nature of activity (use FinCEN characterization codes), identify all subjects and roles, specific transactions and patterns, date range, branches/jurisdictions, why activity is suspicious, method/mechanism used.
- Transaction Detail — Chronological summary of key transactions, total dollar amount, instruments/channels (cash, wire, ACH, check, crypto).
- Investigation Summary — Detection method, investigation steps, CDD/EDD reviewed, third-party information (314(b), public records, adverse media).
- Supporting Documentation — Exhibit list, reference to prior SARs if continuation filing.
Narrative rules:
- Factual, not conclusory — state what happened; never assert a crime was committed
- Chronological presentation
- Specific — dates, amounts, account numbers, counterparty names
- Self-contained — reader with no prior knowledge should understand the case
- Quantified — total suspicious amounts and transaction counts
- No SAR-tipping language — never indicate the customer was or will be notified (31 USC 5318(g)(2)) [VERIFY current statutory cite]
Filing deadlines [VERIFY current FinCEN guidance]:
| Scenario |
Deadline |
| Standard SAR |
30 calendar days from initial detection |
| No suspect identified |
30 days; may extend to 60 days to identify suspect |
| Ongoing activity |
Continuing SARs every 90 days |
| Criminal referral |
Notify law enforcement immediately; SAR still due within 30 days |
Output
Deliverables for each review:
- Transaction summary table with profiling metrics and baseline comparisons
- Red flag log — each flag with typology, category, severity, implicated transactions, and explanation
- OFAC/sanctions screening record with list versions and dates
- Disposition memo — selected outcome with written rationale
- SAR narrative (if filing) — structured per the template above, ready for BSA officer review
- Filing deadline tracker — calculated deadline with calendar entry
Quality Checks
Completeness
Accuracy
Regulatory Compliance
Professional Standards
Reference Files
| File |
Description |
references/AML-RED-FLAGS.md |
Categorized AML red flag typologies with indicators and activity patterns for transaction screening |
1---2name: auditing-aml-transactions3description: Screens transaction data for suspicious patterns using red flag typologies and structures SAR narrative elements. Use when reviewing transactions for AML, identifying suspicious activity, or drafting SAR narratives.4tags:5 - compliance6 - financial-compliance7 - aml8metadata:9 author: casemark10 practice_areas:11 - Regulatory Compliance12 - Financial Regulation13 - Compliance14 document_types:15 - Compliance Report16 skill_modes:17 - Audit18 - Review19---2021# Auditing AML Transactions2223Screens transaction data for suspicious patterns using red flag typologies and structures SAR narrative elements for BSA/AML compliance.2425## When To Use2627- Transaction monitoring system generates an alert requiring human review28- BSA officer receives a referral (internal, law enforcement, or examiner finding)29- Periodic look-back or enhanced due diligence review of high-risk accounts30- Continuation SAR is due on the 90-day cycle31- Independent audit requires sample transaction review32- 314(b) information-sharing request received from another institution3334## Inputs To Gather3536Collect all items below before starting review. If transaction records are unavailable, STOP — document the gap and escalate.3738### Institution & Scope3940- Institution type (bank, MSB, broker-dealer, credit union, insurance, casino, other) [VERIFY]41- Charter/license jurisdiction and primary regulator [VERIFY]42- BSA/AML program status (established / recently remediated / under consent order)43- Review period (start and end dates)44- Alert source and alert/case ID4546### Subject Information4748- Subject name(s) — individuals and/or entities49- Account number(s), account type(s), and open date50- Customer risk rating (Low / Medium / High / Unrated)51- KYC profile: stated occupation, income, expected activity, source of funds52- Prior SAR history on this subject5354### Data Sources5556Confirm availability of each: transaction records (debits/credits), wire transfer details (originator/beneficiary), cash activity and CTR history, check images and deposit slips, account statements, CDD/EDD documentation, OFAC/sanctions screening results, negative news and adverse media, law enforcement subpoenas or 314(b) requests.5758## Workflow5960### Step 1 — Transaction Profiling6162Summarize account activity for the review period:6364| Metric | Value |65|---|---|66| Total credits (count / dollar) | |67| Total debits (count / dollar) | |68| Cash-in / Cash-out (count / dollar) | |69| Wire-in / Wire-out (count / dollar) | |70| ACH/EFT and check activity (count / dollar) | |71| Average and largest single transaction | |72| CTRs filed during period | |73| Jurisdictions involved | |7475Compare observed activity against three baselines:76- **KYC expected activity** — Does volume/type match customer declarations?77- **Peer group** — Consistent with similarly situated customers?78- **Historical baseline** — Has pattern shifted from prior periods?7980Flag material deviations with `[DEVIATION]` and quantify the variance.8182### Step 2 — Red Flag Identification8384Screen activity against recognized typologies. For each red flag identified, document:8586- **Red flag typology** — Name from reference taxonomy87- **Category** — Structuring / Rapid Movement / Geographic / Shell-Layering / Trade-Based / Behavioral / Other88- **Transactions implicated** — Date, amount, type, counterparty89- **Severity** — High / Medium / Low90- **Explanation** — Why this pattern is suspicious in context9192Key thresholds:93- **CTR**: $10,000 cash (single or aggregate same-business-day). Transactions just below are a structuring indicator. [VERIFY current threshold]94- **SAR dollar minimum**: $5,000+ with known suspect; $25,000+ with no identified suspect (banks). No dollar minimum for MSBs. [VERIFY by institution type]95- **Rapid movement**: Funds deposited and withdrawn/transferred within 48 hours with no apparent business purpose.96- **Round-dollar transfers**: Unusual frequency of round-amount wires inconsistent with commercial invoicing.9798### Step 3 — OFAC & Sanctions Screening99100Confirm whether any party to flagged transactions appears on:101- OFAC SDN List and Consolidated Sanctions List102- FinCEN 311 Special Measures (jurisdictions/institutions)103- EU/UN sanctions lists (if applicable) [VERIFY applicability]104- FATF High-Risk and Non-Cooperative Jurisdictions list105106Record each counterparty/jurisdiction screened, the result, list version, and date. If a potential OFAC match is identified, **escalate immediately** — OFAC obligations are strict liability with a shorter timeline than SAR filing.107108### Step 4 — Disposition109110Reach one of four dispositions:111112| Disposition | Criteria | Action |113|---|---|---|114| **File SAR** | Suspicious, unexplained, meets dollar thresholds | Proceed to Step 5 |115| **Close — Below Threshold** | Concerning but below SAR dollar minimums | Document rationale; retain 5 years; consider enhanced monitoring |116| **Close — Explained** | Legitimate purpose confirmed with documentation | Document rationale and evidence; retain 5 years |117| **Escalate** | OFAC match, law enforcement nexus, or insider involvement | Immediate escalation per institution policy |118119**Document rationale for every disposition.** Examiners review closed cases as closely as filed SARs.120121### Step 5 — SAR Narrative Drafting122123The narrative must answer **who, what, when, where, why, and how**.124125**Structure:**1261271. **Subject Information** — Full legal name(s), DOB, SSN/TIN (if available), address, account relationship, risk rating and basis.1282. **Suspicious Activity Description** — Nature of activity (use FinCEN characterization codes), identify all subjects and roles, specific transactions and patterns, date range, branches/jurisdictions, why activity is suspicious, method/mechanism used.1293. **Transaction Detail** — Chronological summary of key transactions, total dollar amount, instruments/channels (cash, wire, ACH, check, crypto).1304. **Investigation Summary** — Detection method, investigation steps, CDD/EDD reviewed, third-party information (314(b), public records, adverse media).1315. **Supporting Documentation** — Exhibit list, reference to prior SARs if continuation filing.132133**Narrative rules:**134- Factual, not conclusory — state what happened; never assert a crime was committed135- Chronological presentation136- Specific — dates, amounts, account numbers, counterparty names137- Self-contained — reader with no prior knowledge should understand the case138- Quantified — total suspicious amounts and transaction counts139- **No SAR-tipping language** — never indicate the customer was or will be notified (31 USC 5318(g)(2)) [VERIFY current statutory cite]140141**Filing deadlines** [VERIFY current FinCEN guidance]:142143| Scenario | Deadline |144|---|---|145| Standard SAR | 30 calendar days from initial detection |146| No suspect identified | 30 days; may extend to 60 days to identify suspect |147| Ongoing activity | Continuing SARs every 90 days |148| Criminal referral | Notify law enforcement immediately; SAR still due within 30 days |149150## Output151152Deliverables for each review:1531541. **Transaction summary table** with profiling metrics and baseline comparisons1552. **Red flag log** — each flag with typology, category, severity, implicated transactions, and explanation1563. **OFAC/sanctions screening record** with list versions and dates1574. **Disposition memo** — selected outcome with written rationale1585. **SAR narrative** (if filing) — structured per the template above, ready for BSA officer review1596. **Filing deadline tracker** — calculated deadline with calendar entry160161## Quality Checks162163### Completeness164- [ ] Intake items fully populated or gaps explicitly documented165- [ ] Transaction profiling covers all activity types in the review period166- [ ] Every red flag has severity rating and supporting transactions167- [ ] Disposition is one of the four defined outcomes with written rationale168169### Accuracy170- [ ] Dollar amounts cross-referenced to source transaction data171- [ ] Dates confirmed against bank records (not estimated)172- [ ] Counterparty names verified against wire details / account records173- [ ] OFAC screening uses current list version174175### Regulatory Compliance176- [ ] SAR narrative answers all six questions (who/what/when/where/why/how)177- [ ] No SAR-tipping or customer-notification language anywhere in output178- [ ] Filing deadline documented and within regulatory window [VERIFY]179- [ ] CTR analysis included for cash-intensive accounts180- [ ] 5-year record retention requirement noted181182### Professional Standards183- [ ] Findings distinguish confirmed facts from inferences184- [ ] All inferences and assumptions marked with `[VERIFY]`185- [ ] Terminology consistent throughout186- [ ] Output actionable for BSA officer / compliance committee187- [ ] Escalation triggers clearly identified188189## Reference Files190191| File | Description |192|---|---|193| `references/AML-RED-FLAGS.md` | Categorized AML red flag typologies with indicators and activity patterns for transaction screening |