Financial Crime
AML Analyst Job Description: What the Role Does, Produces, and Requires
An AML analyst reviews flagged activity against what a customer is expected to do, decides whether it has a legitimate explanation, and documents that decision so it survives a regulator. Here is what the job produces, the skills it needs, how it differs from KYC, and how to tell an alert-queue seat from a role with real judgment.
On this page 13 sections
- AML analyst vs KYC analyst
- What the duties are anchored to
- What the responsibilities section is actually telling you
- An annotated example, line by line
- What the work product looks like
- A sample task to prepare before you apply
- Required qualifications: what is actually required versus aspirational
- Seniority signals the title alone won't give you
- Red flags and green flags checklist
- How this role differs from other adjacent titles
- FAQ
- What to do with this before you apply
- Sources
An AML analyst is the person who looks at activity the monitoring system flagged and decides whether it is explainable or needs to be reported. The short version of the job:
- What they do. Work transaction-monitoring alerts, investigate the ones that do not clear, pull in the customer's KYC profile and history, and decide whether the activity fits what the institution expects from that customer. Where it does not, build the case and, depending on seniority, draft the Suspicious Activity Report (SAR).
- What they produce. An alert disposition with a written rationale, a case file that shows what was checked and why the conclusion follows, and, for reportable activity, a SAR narrative that answers who, what, when, where, and why.
- Skills needed. Reading transaction data for patterns, matching activity against a customer profile, writing a short rationale a regulator or law enforcement officer can follow, working to filing deadlines, and knowing the difference between unusual and suspicious.
- How it differs from KYC. KYC analysts build and refresh the customer profile at onboarding and review. AML analysts monitor what the customer actually does against that profile. See the comparison table below.
The same title covers very different jobs. An "AML Analyst" at a regional bank and the same title at a payments company handling millions of transactions a day can mean closing a quota of alerts against a fixed checklist with no authority beyond "escalate" or "close," or building the narrative that gets filed with FinCEN and having real input into whether a customer relationship continues. The job description is where you find out which one you are applying for.
AML analyst vs KYC analyst
AML analyst | KYC analyst | |
|---|---|---|
When the work happens | Continuously, as transactions and alerts come in | At onboarding, at periodic review, and when a trigger event changes the customer |
Starting point | A transaction-monitoring alert, a referral, or a law enforcement request | A new or existing customer relationship |
Core question | Does this activity fit what we expect from this customer, and if not, is it reportable? | Who is this customer, who owns and controls it, and what will the account be used for? |
Main output | Alert disposition with rationale, case file, and where warranted a SAR narrative | CDD file: identity verification, beneficial ownership record, purpose note, risk rating |
Regulatory anchor (US banks) | SAR rule (31 CFR 1020.320) and the ongoing monitoring element of the CDD rule (31 CFR 1020.210) | Customer Identification Program rule (31 CFR 1020.220) and the beneficial ownership rule (31 CFR 1010.230) |
Deadline pressure | Regulatory: a SAR is due no later than 30 calendar days after initial detection of facts that may support a filing, 60 at most if no suspect is identified | Program-driven: review cycles set by the institution's risk-based procedures |
What "senior" usually means | SAR drafting ownership, complex investigations, scenario tuning, QA of other analysts' dispositions | Enhanced due diligence, QA of other analysts' files, input into the risk rating model |
The two roles hand off constantly: the KYC profile is what an alert gets measured against, and an AML investigation often sends a customer back for a refreshed KYC review. Some smaller institutions combine both into one seat. For the neighbouring title read the same way, see KYC analyst job description: what the role does, produces, and requires.
What the duties are anchored to
For US banks the core AML duties sit on two rules, and knowing them tells you what the job has to deliver no matter how the posting phrases it.
- Ongoing monitoring. The AML program rule requires risk-based customer due diligence procedures that include "conducting ongoing monitoring to identify and report suspicious transactions." That is the regulatory basis for the alert queue.
- Suspicious activity reporting. The SAR rule requires a bank to file when a transaction conducted or attempted through it "involves or aggregates at least $5,000 in funds or other assets" and the bank knows, suspects, or has reason to suspect that it involves illicit funds, is designed to evade Bank Secrecy Act requirements, or "has no business or apparent lawful purpose" and "the bank knows of no reasonable explanation for the transaction after examining the available facts." The filing is due no later than 30 calendar days after the date of "initial detection by the bank of facts that may constitute a basis for filing a SAR," with up to 30 more days to identify a suspect, and "in no case shall reporting be delayed more than 60 calendar days." The clock runs from when those facts are detected, which is not automatically the date an alert fires; institutions define that point in their procedures. A copy of the SAR and its supporting documentation must be kept "for a period of five years from the date of filing the SAR." A SAR "and any information that would reveal the existence of a SAR, are confidential," with disclosure permitted only to FinCEN, authorised law enforcement and regulators, and in the other limited cases the rule lists.
- The narrative. FinCEN's SAR narrative guidance describes the narrative as the only free-text section of the form and says it should identify "the five essential elements of information" of the activity, "who? what? when? where? and why?", with the method of operation (how) also included.
The confidentiality rule matters for how you talk about the work. Do not disclose SARs, or information that would reveal one exists, in interviews or any other setting the rule does not authorise. Expect to be asked about your process, not your cases.
What the responsibilities section is actually telling you
Most AML analyst postings list some version of the same core duties: alert review, case investigation, SAR drafting, and quality assurance on existing cases. The verbs attached to each one tell you far more than the duty itself.
- "Review and disposition transaction monitoring alerts" usually means you work a queue generated by the monitoring system, decide true-positive or false-positive, and close or escalate. This is the base-level version of the job, and entry-level AML analyst postings are often built almost entirely around it.
- "Conduct enhanced due diligence on high-risk customers" signals a step up: you are not just clearing alerts, you are building a profile of a customer's expected activity and judging whether actual behavior fits it. This requires understanding the customer's business, not just the transaction data.
- "Draft Suspicious Activity Reports for regulatory filing" means the role writes the document a bank actually sends to FinCEN. This is meaningfully more senior work than alert review, because a poorly written SAR narrative is a regulatory liability, not just an internal process failure.
- "Partner with the BSA Officer on escalations and look-back reviews" tells you the role has visibility into decisions above the analyst's own authority, and may get pulled into remediation work after an exam finding, a useful pattern to learn from early in a career.
- "Maintain alert disposition logs for exam readiness" is administrative, fine at entry level, but a posting titled "Senior AML Analyst" that lists only this and alert review is over-titled for the work described.
If a posting is built almost entirely around the first and last bullet above, expect a high-volume queue job with a quota attached. If it includes enhanced due diligence and SAR drafting, expect a role with real judgment calls and more exposure to how the bank's financial crime program actually functions. For the wider arc this role sits inside, see financial crime and AML careers: entry points, progression, and what the work is really like.
An annotated example, line by line
Here is a composite written to illustrate language that recurs in postings, annotated for what each line signals. It is not taken from any one employer.
"Review daily transaction monitoring alerts generated by the AML system, applying established typology rules to determine disposition."
This is rules-based triage. "Established typology rules" means the judgment framework already exists; you are applying it, not building it. That is entirely normal for a first AML role, but if every bullet in the posting reads this way, the job has a hard ceiling on how much independent judgment you will exercise.
"Conduct customer-level investigations incorporating KYC profile data, transaction history, and adverse media, documenting findings that support an escalation or closure recommendation."
Note "recommendation." This role builds the case but does not necessarily make the final call. Compare that to:
"Determine SAR-worthiness of escalated cases and draft the narrative for QA and filing review."
This is a decision-adjacent role: the analyst's judgment directly shapes what gets filed, even if a second reviewer signs off. That is a real step up in both responsibility and the experience a hiring manager will expect.
"Participate in look-back reviews and remediation efforts following regulatory exam findings or consent order requirements."
This tells you the program has had a regulatory finding serious enough to require remediation, which is common and not automatically a red flag, but it does mean the workload may spike unpredictably and the role may involve reworking old cases under deadline pressure from a regulator, not just a manager.
Read your target posting the same way: underline every verb and ask whether it implies input (review, document, flag) or decision (determine, draft for filing, approve closure).
What the work product looks like
The core output of an AML analyst is a disposition with a rationale. The example below is a fictional illustration written for this article. The customer, the figures, and the activity are invented, and it is not based on any real alert, filing, or anyone's work history.
Fictional example: alert disposition note
Alert: Scenario "structuring, cash deposits below reporting threshold," triggered on a personal checking account. Activity: Six cash deposits over nine days, each between USD 7,000 and USD 9,500, total USD 51,200. Customer profile (from KYC file): Sole proprietor, mobile food vendor, account opened two years ago, expected monthly cash deposits of USD 15,000 to USD 25,000, risk rating medium. Checks performed: Twelve months of deposit history (prior monthly cash range USD 12,000 to USD 22,000, single deposits rarely above USD 6,000). Business registration still active. No prior alerts. No adverse media. No related accounts. Assessment: In nine days, deposits exceeded twice the upper end of the customer's stated monthly range, and the deposit sizes cluster just below USD 10,000, which fits the scenario's pattern. The customer's prior history does not explain the change, and no event in the file (new location, seasonal spike) accounts for it. Disposition: Escalate to investigations for a SAR decision. Recommend a request for information to the customer on the source of the increase, in line with the institution's procedures. Owner and date: Analyst name, date, second-level reviewer assigned.
What makes this useful is that every step a reviewer or examiner would want is visible: what fired, what the baseline was, what was checked, why the conclusion follows, and what happens next. A note that just says "activity appears suspicious, escalated" fails the same review.
A sample task to prepare before you apply
AML interviews often include a short case exercise. You can practise with a scenario like this one, which is fictional and written for this article.
An alert fires on a small import business's account for "rapid movement of funds." Over two weeks, three incoming wires totalling USD 180,000 arrive from a company in a different country, and within two days of each arrival most of the money leaves by wire to a third company. The KYC file says the customer imports kitchen equipment, expected monthly wire volume is about USD 60,000, and the account has been open for four years with no prior alerts.
Write half a page covering: what in the KYC profile could explain this and what could not; the three or four checks you would run before reaching a view; what you would conclude on the facts given and what you would need to change your mind; and whether this is a close, a request for information, or an escalation. Then check your reasoning against the rule text and the narrative guidance linked in the Sources section. Interviewers are looking for a clear chain from evidence to conclusion, not a guess at the "right" answer.
Required qualifications: what is actually required versus aspirational
Qualifications lists in AML postings tend to describe an idealised candidate rather than the minimum the role needs. A few patterns worth checking before you rule yourself out:
- Degree requirements ("Bachelor's in Finance, Criminal Justice, or related field") are often listed alongside an "or equivalent experience" clause. Backgrounds in banking operations, customer service at a financial institution, fraud, and investigative work map onto the duties directly because the core skill is pattern recognition and clear documentation under a framework.
- CAMS (Certified Anti-Money Laundering Specialist) comes up often in AML postings. Check whether a posting says "preferred" or "required"; the first is common at analyst level, the second usually indicates a senior analyst, investigator, or management-track role. For a breakdown of which credential matters when, see financial crime certifications explained: CAMS, CFCS, and CFE.
- "2-4 years of BSA/AML experience" on a mid-level posting is more likely to be flexible if the rest of the description is alert-review-heavy. It is far less likely to be flexible when the posting mentions SAR drafting ownership or exam remediation work.
- Tooling mentions (Actimize, SAS, Verafin, or a case management system built in-house) tell you what you would be working in, not how good the program is. A well-known platform and an in-house system can each be run well or badly. Ask in the interview how the platform is governed, supported, and validated, and who tunes its scenarios.
Weigh the qualifications section against the responsibilities section, not against your resume in isolation. A posting demanding CAMS plus four years of experience for a job that is entirely queue-clearing is a mismatch worth questioning in the interview, not a bar that should stop you from applying.
Seniority signals the title alone won't give you
Titles are inconsistent across institutions; an "AML Analyst II" at one bank does the work of a "Senior AML Investigator" at another. Look instead for these signals:
- Does the posting mention setting or revising alert thresholds, typologies, or scenario tuning? That is a senior or specialist-track signal. Entry-level analysts work inside the typology framework; senior analysts and financial crime data specialists help build it.
- Is there any mention of reviewing or QA-ing other analysts' case dispositions? That is a lead-level responsibility regardless of what the title says.
- Who does the role report to? Reporting to a named "BSA Officer" or "Director of Financial Crime Compliance" suggests a resourced, formally structured program. Reporting to a generic "Compliance Manager" with no BSA-specific title attached sometimes means the AML function is newer or thinner than the posting's language implies.
- Is there a stated alert volume or case load ("manage an average caseload of 25-30 open investigations")? A specific number usually means the program measures itself, which is a reasonable proxy for how predictable your own workload will be.
Red flags and green flags checklist
Green flags
- Specific responsibilities tied to real judgment (enhanced due diligence, SAR narrative drafting, escalation recommendations with rationale)
- A named, established monitoring platform and documented typology framework already in place
- Reasonable stated caseload or alert volume relative to team size
- CAMS listed as "preferred" rather than "required" for entry and mid-level titles
- Clear reporting line to a BSA Officer or equivalent named role
Red flags
- The posting is almost entirely "clear the queue" language dressed up with a "Senior" or "Lead" title
- No mention of who reviews escalations or signs off on SAR filings, which usually means accountability for a wrong call is unclear
- Vague alert-volume language implying an unsustainable caseload for a single analyst, especially at a fast-growing company scaling faster than its compliance headcount
- No mention of ongoing training on typologies or regulatory changes, which often means the analyst is left to learn the job's actual risk judgment entirely on their own
- "Fast-paced," "wears many hats," and "self-starter" substituting for any description of an actual review or escalation process
A cluster of red flags, especially unclear accountability combined with high alert volume, is the pattern worth taking seriously. One red flag in isolation rarely disqualifies a posting on its own.
How this role differs from other adjacent titles
Beyond KYC, several titles overlap with AML work under different labels:
- BSA Analyst is often used interchangeably with AML Analyst, though some institutions use "BSA" specifically for the regulatory-filing and policy side and "AML" for the transaction-monitoring side. Read the responsibilities, not the title.
- Fraud Analyst roles investigate losses to the institution itself (account takeover, card fraud, first-party fraud) and sit on a different risk lens than AML, which is concerned with illicit proceeds moving through the institution regardless of whether the institution itself loses money. For how investigative skills carry between the two, see fraud examination and investigation as a career.
- Financial Crime Investigator or Senior AML Investigator titles generally sit above standard analyst work, handling the most complex escalated cases, coordinating with law enforcement requests, and often owning SAR filing decisions directly rather than recommending them upward.
- Sanctions Analyst overlaps with AML in screening work but is a distinct specialty focused on OFAC and other restricted-party lists rather than transaction typologies; see sanctions analyst job description: how to read one before you apply.
- Compliance Analyst or GRC Analyst on a governance, risk, and compliance team is a different kind of work, built around control frameworks and policy rather than transaction review. If a posting mixes the two, see GRC analyst job description: what the role does, produces, and requires to tell which one you are really looking at.
If you are targeting the field broadly, read the responsibilities section rather than filtering by title, since labels vary across banks, fintechs, and money services businesses.
FAQ
What does an AML analyst do, in one sentence? An AML analyst reviews flagged transactions against what the institution expects from the customer, decides whether the activity is explainable or potentially suspicious, and documents that decision so it can support a filing and survive an examination.
Do I need CAMS to get hired as an AML analyst? Not usually at entry level, where postings more often list it as preferred. It carries more weight for senior analyst, investigator, and management-track roles. Read the specific posting rather than assuming.
What is the difference between an AML analyst and a KYC analyst? KYC analysts build and periodically refresh the customer risk profile at onboarding and renewal. AML analysts review ongoing transaction activity against that profile and against typology rules, deciding whether behavior looks consistent with what is expected or warrants escalation. The table above lays the two side by side.
Is this a job that requires a finance background? Not necessarily. A background in banking operations, customer service at a financial institution, paralegal work, or investigative work transfers, because the core skill is pattern recognition and clear documentation under a framework, not financial modeling.
What should I ask in the interview that the posting won't answer? Ask how the team measures alert quality (not just volume), who has final sign-off authority on a SAR filing, how large an individual caseload typically runs, and whether the program has an open regulatory finding currently driving remediation work. Those answers tell you more about day-to-day reality than any bullet point in the posting.
What to do with this before you apply
Copy the responsibilities section of the posting you are considering. Mark every line as either input (review, document, flag, recommend) or decision (determine, draft for filing, approve closure, escalate to a named owner). A posting weighted toward decision language, with a defined typology framework and a reasonable stated caseload, is worth your time. One that is entirely queue-clearing language wearing a senior title is a quota job in better packaging, and you should negotiate scope with that read in mind, or keep looking. Then write the sample task above once, so you have already practised the chain from evidence to disposition before anyone asks you to do it live.
Sources
All checked November 4, 2026. The rule text is quoted from the Code of Federal Regulations as published by the Legal Information Institute, which mirrors the official text.
- 31 CFR 1020.320, Reports by banks of suspicious transactions: law.cornell.edu/cfr/text/31/1020.320
- 31 CFR 1020.210, Anti-money laundering program requirements for banks, including the ongoing monitoring element: law.cornell.edu/cfr/text/31/1020.210
- FinCEN, Guidance on Preparing a Complete and Sufficient Suspicious Activity Report Narrative (November 2003): fincen.gov (PDF)
- FinCEN, Suggestions for Addressing Common Errors Noted in Suspicious Activity Reporting (October 10, 2007): fincen.gov
The disposition note and the sample task are fictional illustrations written for this article. This article does not provide salary estimates.