Predicate Offense: Definition and Use in Compliance

What is Predicate Offense?

A predicate offense is the criminal act that generates the proceeds being laundered. Money laundering doesn't exist in isolation. It's always downstream of something else: drug trafficking, fraud, corruption, human trafficking. The laundering is what happens to the money afterward.

The legal requirement is structural. Before a prosecutor can charge money laundering, they must establish the underlying crime. That's the predicate. Without it, there's no illicit origin, and without an illicit origin, the money isn't "dirty" in a legal sense.

This isn't merely a prosecutorial technicality. It shapes how banks think about suspicious activity. When an analyst reviews unusual cash flows, the first question isn't whether this is laundering. It's: what crime would explain this money? That question determines the typology, the investigation scope, and the SAR narrative.

The concept entered US federal law through the Money Laundering Control Act of 1986, codified at 18 U.S.C. § 1956. That statute defined "specified unlawful activities," the legal term for predicates in the US system. The list has grown considerably since 1986 and now covers over 200 offense categories across drug trafficking, financial fraud, cybercrime, and tax evasion.

The EU took a different approach. Before 2018, predicate offense lists varied substantially across member states, creating real gaps in cross-border investigations. The Sixth Anti-Money Laundering Directive (6AMLD) standardized a minimum list of 22 predicate categories across the EU, added cybercrime, and introduced criminal liability for legal entities alongside individuals. One concrete result: a financial institution in Frankfurt and one in Chicago now share a common baseline for what counts as a predicate. That matters for correspondent banking relationships and for prosecutors coordinating across jurisdictions.

A useful way to think about it: the predicate offense is the crime you're investigating, and the money laundering is the crime your bank may have been used to commit. Both matter. They require different evidence, different timelines, and often different reporting obligations.

How is Predicate Offense used in practice?

The predicate inference is the first decision in almost every AML investigation. It's not a legal conclusion, but it's a working hypothesis that drives everything else.

Consider a concrete example. A mid-size import/export company routes payments through three accounts at the same bank. Average transaction size is $95,000. Payments cluster just below the $100,000 reporting threshold. Counterparties are in jurisdictions with weak AML regimes. The probable predicate is not random: the pattern points toward trade-based money laundering or tax evasion. That hypothesis determines which documents the analyst requests, which counterparties get screened, and how the customer due diligence review is framed.

Different predicates produce different forensic signatures. Drug trafficking generates high-frequency cash deposits, often structured to stay below reporting thresholds. Bribery and corruption typically involve large lump-sum transfers to offshore accounts, often through shell companies. Payment fraud generates rapid account cycling and unusual refund patterns. Compliance teams build these patterns into their transaction monitoring rules and tag alerts with a probable predicate code.

This matters for prioritization. A team handling 2,000 monthly alerts can't treat them all equally. Probable terrorism financing predicates go to the front of the queue. Probable low-level tax evasion can wait.

It also matters for SAR filing. FinCEN's SAR form (FinCEN 111) requires filers to select a suspicious activity category. Those categories map directly to predicate types: structuring, fraud, bribery, terrorist financing. An analyst who can't articulate the probable predicate will write a weaker SAR, and regulators notice that. A SAR that reads "unusual transactions inconsistent with business profile" without specifying a probable predicate gives law enforcement very little to act on. One that says "transaction pattern consistent with proceeds of wire fraud, based on counterparty profile and transaction velocity" is a starting point for an investigation.

Predicate classification is also the triage mechanism for escalation. If the probable predicate involves a politically exposed person or a sanctioned jurisdiction, the case goes to enhanced due diligence before a SAR is filed.

Predicate Offense in regulatory context

FATF Recommendation 3 is the international baseline. It requires jurisdictions to criminalize money laundering across all serious offenses and lists 21 designated categories that must be included. The list covers drug offenses, fraud, counterfeiting, environmental crime, extortion, human trafficking, tax crime, and cybercrime. FATF's mutual evaluation process tests whether countries' predicate lists meet this standard, and deficiencies lead directly to grey list placements and reputational consequences.

Not every country adopted the full list at first. Some jurisdictions historically excluded tax evasion as a predicate, which created a real gap: a client could move proceeds from offshore tax fraud through a bank without triggering money laundering liability. FATF's 2012 revision explicitly added tax crimes to the designated categories. Switzerland, Singapore, and several other jurisdictions subsequently updated their domestic predicate lists.

The US predicate framework is broader than FATF's minimum. Under 18 U.S.C. § 1956, "specified unlawful activities" span more than 200 offense categories. The USA PATRIOT Act of 2001 added foreign corruption and terrorism financing. The Anti-Money Laundering Act of 2020 added cybercrime and intellectual property offenses.

For terrorism financing specifically, the predicate logic works differently. Terrorism financing can involve clean money: funds raised legitimately and then directed to terrorist purposes. Most jurisdictions handle this by treating terrorism financing as a standalone offense rather than requiring it to be a predicate to a laundering charge. But the funds flow through the same banking channels, which is why compliance teams treat terrorism-linked transactions as their own SAR category with tighter timelines.

The EU's 6AMLD, in force since December 2020, also strengthened aiding and abetting provisions. A bank employee who knowingly assists in laundering predicate proceeds can now face direct criminal liability, not just the institution. That raised the personal accountability stakes considerably.

Jurisdictional mismatches remain a real operational problem. A transaction involving a predicate offense in one country may not trigger any obligation in another. Organized crime networks actively exploit those gaps, routing funds through jurisdictions where the underlying activity sits outside the local predicate list.

Common challenges and how to address them

The hardest practical problem is the unknown predicate. An analyst sees suspicious transaction behavior but can't determine what crime generated the funds. This happens with complex layering schemes, where proceeds have passed through multiple jurisdictions and corporate structures before reaching the bank.

The regulatory answer in most frameworks: banks don't need to prove the predicate offense to file a SAR. They need reasonable grounds to suspect that funds may be the proceeds of crime. That's a lower threshold than criminal proof. But it still requires the analyst to articulate a credible basis for suspicion, not just flag unusual behavior.

Enhanced Due Diligence (EDD) is the primary tool for resolving predicate uncertainty. When the probable predicate is high-risk, such as bribery, terrorism financing, or sanctions evasion, the compliance team should expand source-of-funds documentation, run adverse media screening across multiple databases, and seek independent verification of the client's stated business activity. A customer who claims proceeds from a construction business but shows no verifiable contracts, employees, or physical premises gives the analyst grounds to escalate even without identifying the specific predicate.

Cross-border predicate divergence is a second challenge. Consider a correspondent banking scenario: a transaction arrives from a respondent bank in a jurisdiction where the originating activity is legal but would constitute a predicate offense in the receiving jurisdiction. Certain gambling proceeds, certain cannabis revenues, certain cash-intensive businesses fall into this category depending on the jurisdictions involved. The receiving bank applies its own jurisdiction's predicate list, not the sender's. That's the correct approach, but it requires analysts to know the predicate lists of the jurisdictions they deal with most frequently.

Sophisticated compliance programs address predicate uncertainty by building predicate profiles into customer risk ratings during onboarding. A customer in a high-corruption sector gets a higher inherent risk score from day one. A customer with identified connections to a known predicate-crime network gets escalated to a relationship manager before any transaction is processed. The goal is to move predicate assessment upstream, into onboarding and periodic review, rather than waiting for a transaction monitoring alert to surface it six months later.

Related terms and concepts

Predicate offense connects to several terms compliance professionals use daily, and the distinctions matter.

Structuring is both a predicate offense in its own right under US law (31 U.S.C. § 5324) and frequently a symptom of another predicate. A drug trafficker breaking $500,000 in cash into sub-$10,000 deposits is committing structuring and laundering drug proceeds simultaneously. Compliance teams treat structuring as a red flag pointing toward an underlying predicate crime, not as the full story.

Trade-based money laundering is a laundering method, not a predicate. The predicate in a TBML case is usually fraud, tax evasion, corruption, or drug trafficking. The trade mechanism is the layering tool: over- and under-invoicing, phantom shipments, multiple invoicing for the same goods. The distinction matters because the investigation needs to follow the predicate, not just the trade anomaly.

Placement, layering, and integration are the three stages of money laundering that follow a predicate offense. Placement introduces the illicit funds into the financial system. Layering obscures their origin. Integration makes them appear legitimate. Understanding which stage the suspicious activity represents helps analysts identify the probable predicate: structuring and cash deposits point to placement-stage laundering, often indicating proceeds from physical crime; complex wire chains suggest layering of fraud or corruption proceeds.

Typologies are predicate-linked by design. FATF's typology reports and FinCEN advisories group suspicious behavior patterns by probable predicate: human trafficking typologies look different from real estate laundering typologies, and both look different from cybercrime proceeds. A typology library organized by predicate category is one of the most operationally precise configurations for transaction monitoring rules.

Finally, "predicate crime" appears in court documents and law enforcement press releases as a direct synonym. The meaning is identical. In compliance documentation, "predicate offense" is the standard term across most AML frameworks. Using both interchangeably within a single case file or policy document adds unnecessary ambiguity: pick one and stick with it.