They miss the stage where laundering becomes hardest to see. Placement is often visible through unusual deposits, but layering can look like routine movement unless teams connect accounts, counterparties, and jurisdictions. A placement-only model leaves the main concealment mechanism unchallenged and creates confidence without real coverage.
What changes once you look past placement?
Placement tells you that illicit funds have entered the system, but it does not tell you how they are being disguised. The real break in coverage happens when teams stop at the first visible stage and fail to follow the money into layering, where the same value is fragmented, routed through intermediaries, and made to resemble ordinary activity. That is the stage that most monitoring programmes need to challenge.
Once that shift is missed, alerting becomes structurally shallow: a programme can flag unusual cash or deposit behaviour while still missing the networked movement that makes funds harder to trace. Effective AML coverage therefore has to move from isolated transactions to relationship analysis across accounts, counterparties, jurisdictions, and timing patterns.
Why layering is the stage that defeats placement-only monitoring
Layering is where concealment becomes operationally effective. The funds may no longer move in one obvious burst, but through transfers, conversions, pass-through accounts, and cross-border hops that each look plausible in isolation. A placement-only model is weak because it treats the first anomaly as the problem rather than the start of the laundering process.
That gap matters because layering is designed to break simple rules. A single account review may show nothing unusual, yet the wider sequence can reveal coordinated movement, circular flows, or counterparty relationships that are only visible when teams correlate behaviour over time and across entities. The control failure is not absence of alerts, but absence of joined-up interpretation.
For teams building detection logic, the practical question is whether the programme can connect typologies rather than only trigger on thresholds. FATF Recommendations — AML and KYC Framework remains the clearest baseline for risk-based customer due diligence, ongoing monitoring, and suspicious activity reporting expectations that go beyond a single transaction stage.
What a placement-only view causes teams to miss
A placement-only programme misses the main concealment mechanism, which means it can create false confidence. Analysts may believe they are seeing the full laundering pattern when they are only seeing the entry point. That leaves the hardest part of the chain untested: how value is dispersed, obscured, and reintegrated without obvious red flags.
The practical consequence is that higher-risk relationships are not prioritised correctly. If accounts, counterparties, and jurisdictions are not analysed together, the programme may underweight structuring, mule networks, shell entities, or repeated route patterns that are more informative than the initial deposit. This is why monitoring has to be built around behaviour patterns, not just event types.
Rules and alerts also need to reflect the local filing and supervision environment. FinCEN and EBA AML/CFT Guidance are useful reference points for how suspicious activity expectations and risk-based controls are applied in practice, especially when transaction chains span multiple jurisdictions.
How to widen coverage without drowning in false positives
The answer is not to monitor everything equally, but to widen the lens in a controlled way. Start with the flows most likely to reveal layering: repeated movement between related accounts, new counterparties that appear only once, rapid pass-through behaviour, and jurisdictional changes that do not fit the customer profile. Then use those signals to prioritise review, rather than treating every anomaly as equally meaningful.
The strongest programmes combine transaction monitoring with entity and relationship review. They ask whether the movement makes sense for the customer, the counterparties, and the destination, not just whether a deposit crossed a threshold. That reduces the chance of overfitting to placement and improves detection of laundering sequences that unfold over days or weeks.
Where monitoring is still mostly rule-driven, the main practitioner judgement is to accept that coverage quality comes from correlation, not volume. A narrow placement rule can be useful as a starting point, but it is not a complete AML model unless it is paired with layering detection and the ability to trace movement across linked records.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | DE.CM-01 — Anomalies and Events are Detected | Monitoring must detect suspicious transaction patterns beyond the first deposit. |
| ID.RA-01 — Asset Vulnerabilities Are Identified and Documented | AML programmes need risk analysis of accounts, counterparties, and jurisdictions. | |
| GV.RM-01 — Risk Management Strategy Is Established and Implemented | A placement-only model is a risk strategy gap that leaves concealment untested. | |
| Recommendation — Extend detection logic to correlate linked movement patterns, not just single-event anomalies. Assess laundering exposure by mapping linked accounts, counterparties, and route patterns. Define monitoring scope that covers the full laundering chain, not only placement. | ||
| CIS Controls v8 | CIS-8 — Audit Log Management | Cross-account and cross-jurisdiction tracing depends on usable activity records. |
| Recommendation — Retain and review transaction records that support chain reconstruction across entities. | ||
| ISO/IEC 27001:2022 | A.5.7 — Threat intelligence | AML teams should use threat and typology intelligence to detect evolving laundering patterns. |
| Recommendation — Incorporate current laundering typologies into monitoring and investigation rules. | ||
Practitioner Guidance
What to verify: Confirm that your alert logic can link accounts, counterparties, and jurisdictions across a time window, not just flag the initial deposit event. If investigators cannot reconstruct the movement path from one alert set, the programme is probably still placement-centric.
Decision rule: If the detection model only triggers on unusual entry behaviour, treat that as a coverage gap rather than a tuned filter. Escalate any programme that cannot explain how it identifies pass-through movement, circularity, or rapid redistribution after placement.
Practitioner takeaway: Placement is often the easiest stage to see, but layering is where the real concealment happens, so a serious AML programme must be built to follow relationships and movement, not just the first suspicious deposit.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 21, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org