AML Staffing Benchmark

How to use the AML Staffing Benchmark

Enter four inputs that define your program's scale and complexity. Each one affects the output in a distinct way.

Number of customers drives your base program headcount. KYC onboarding, periodic review, enhanced due diligence, and governance functions all scale with your customer population. A smaller customer base does not eliminate these obligations, it just concentrates them.

Monthly monitoring alerts determines your alert-review FTE requirement. This is often the largest and most variable component of an AML team. If your transaction monitoring system generates a high volume of alerts, even a well-tuned ruleset creates significant analyst workload.

Jurisdictions operated in adds a fixed increment per jurisdiction. Each additional regulatory regime typically requires dedicated oversight: local reporting obligations, jurisdiction-specific typologies, and regulatory relationships that cannot be centralized entirely.

Inherent risk profile is the scaling factor that converts the baseline estimate into a low-high band. A higher inherent risk profile, reflecting factors like customer type, product mix, or transaction volumes, requires proportionally more capacity. The result is not a single number but a range, which reflects real-world variability in program design and operational efficiency.

Once you have your inputs, the tool returns four figures: alert-review FTEs, base program FTEs, and the resulting illustrative low and high totals. Use these as an order-of-magnitude reference, not a staffing mandate.

What the result means

The low and high figures bound a plausible staffing range given your inputs. The gap between them reflects the inherent risk multiplier and the practical reality that two organizations with identical inputs may staff very differently depending on their operating model, automation investment, and regulatory posture.

Alert-review FTEs and base program FTEs are shown separately because they respond to different levers. If your alert volume is high but your customer count is modest, the solution may be alert-tuning or automation rather than hiring across the board. Conversely, a large customer base with well-controlled alert rates still requires substantial KYC and governance capacity.

If your current headcount falls materially below the low end of the range, that is worth examining. It does not automatically mean you are non-compliant, but it does mean you should be able to articulate how your program compensates, whether through technology, risk-based scoping, or other controls. Regulators increasingly focus on whether staffing is commensurate with the risk profile, not just whether policies exist.

If your headcount is above the high end, the output may still be useful. It can support a case for maintaining or growing the team, or it may prompt a review of whether alert volumes are appropriately tuned.

Why this matters for compliance teams

AML staffing decisions are consequential in both directions. Understaffing creates regulatory exposure: missed alerts, delayed SARs, and gaps in KYC review that examiners will find. Overstaffing is rarely raised as a concern by regulators, but it creates budget pressure that can result in sudden reductions at the wrong time.

Many compliance teams arrive at their headcount organically, through incremental hiring in response to specific incidents or regulatory findings, rather than through systematic capacity planning. This benchmark gives MLROs and compliance officers a structured way to pressure-test current staffing against a transparent, input-driven model.

The tool is also useful in conversations with senior management and boards. A concrete FTE range, grounded in observable program metrics, is easier to defend than a judgment-based request. It shifts the discussion from "we need more people" to "here is what our alert volume and customer base imply, and here is how we compare."

FluxForce makes this tool available as part of a broader set of AML planning resources. The goal is to give compliance teams a factual basis for decisions that are often made under time pressure and with limited external reference points.