Skip to main content
FinCrime Institute
Category: Customer Due Diligence

Occasional Transaction Threshold

Also known as: Occasional Transaction CDD Threshold, Occasional Transaction Trigger
Simply put

An occasional transaction threshold is a monetary limit that, when a one-off transaction reaches or exceeds it, requires a business to carry out customer due diligence checks even though the customer does not have an ongoing business relationship with that business. The exact amount and the type of transaction it applies to vary depending on the country and the type of business involved. Because thresholds differ between regimes, the applicable figure should always be confirmed against the relevant local regulation.

Formal definition

The occasional transaction threshold is the monetary value at or above which an obliged entity must apply customer due diligence (CDD) measures to a transaction, or a linked series of transactions, that is carried out otherwise than as part of an established business relationship. An 'occasional transaction' is generally understood as a transaction (or provision of services connected to a transaction) that is not conducted within an ongoing business relationship. Thresholds and their scope are set by the applicable regime and are not uniform: for example, under the UK regime, high-value dealers must apply CDD to an occasional transaction in cash of £10,000 or more, whether executed in a single operation or in linked operations; the ADGM AML rules require CDD where an occasional transaction is USD 15,000 or more; and in the EU the concept is addressed within the AML framework, including work on regulatory technical standards under Article 19(9) referenced in AMLA consultation material. Practitioners should note that threshold-based triggers apply only to specified transaction types, entity categories, and jurisdictions, that certain regimes may aggregate linked transactions, and that some approaches to threshold-based monitoring may be unsuitable in particular contexts, requiring other methods of scrutiny. Exact monetary values, aggregation rules, and in-scope entities must be verified against the applicable regulation.

Why it matters

The occasional transaction threshold addresses a structural gap in customer due diligence obligations: without it, a business could serve one-off customers who never form an ongoing relationship and therefore fall outside the CDD measures that typically attach to established business relationships. By setting a monetary trigger, regimes ensure that higher-value transactions receive scrutiny even where no continuing relationship exists, so that individuals cannot rely on transactional anonymity simply by avoiding an account or ongoing engagement. This matters because occasional transactions, particularly in cash or through certain dealers, can present money laundering and terrorist financing risk that would otherwise go unexamined.

The threshold also creates a specific compliance risk that practitioners must manage: aggregation. Because certain regimes require linked transactions to be treated together, a customer who splits a payment into several smaller amounts to stay beneath the trigger, a pattern sometimes described as structuring, may still bring the aggregate within scope. Under the UK regime, for instance, high-value dealers must apply CDD to an occasional cash transaction of £10,000 or more whether executed in a single operation or in linked operations, which means the obligation cannot be evaded by simple fragmentation. Firms that monitor only individual transaction values, rather than linked series, may fail to identify transactions that the applicable regulation treats as reaching the threshold.

It is important to recognise the limits of threshold-based triggers. Regulatory guidance acknowledges that threshold-based transaction monitoring approaches are sometimes used in situations where they are not suitable, and that other methods of scrutiny may be required. Reaching or exceeding a threshold triggers a CDD obligation; it does not establish that a transaction is suspicious or unlawful. Conversely, transactions below the threshold are not automatically low risk and may still warrant scrutiny under other provisions of the applicable regime.

Who it's relevant to

High-value dealers
Businesses dealing in high-value goods are among the entity categories to which occasional transaction thresholds most directly apply. Under the UK regime, high-value dealers must apply CDD to an occasional cash transaction of £10,000 or more, whether executed in a single operation or in linked operations. Such firms need processes to identify when a one-off transaction reaches the applicable trigger and to detect linked operations that may reach it in aggregate. The exact threshold and aggregation rules should be confirmed against the applicable regulation.
Compliance officers and MLROs at obliged entities
Those responsible for designing and operating CDD programmes must ensure their procedures correctly identify occasional transactions, transactions not carried out as part of an established business relationship, and apply due diligence at the point the applicable threshold is reached. They should be alert to the risk that threshold-based transaction monitoring may be used in situations where it is not suitable, and may need to build in other methods of scrutiny rather than relying on the trigger value alone.
Financial intelligence analysts and transaction monitoring teams
Analysts responsible for monitoring transactions need to account for aggregation, since certain regimes require linked transactions to be treated together for the purposes of the threshold. Monitoring that assesses only individual transaction values may miss a linked series that collectively reaches the trigger. Reaching a threshold prompts CDD; it does not by itself indicate wrongdoing or suspicion.
Firms operating across multiple jurisdictions
Because thresholds and their scope differ between regimes, for example £10,000 for cash occasional transactions under the UK regime for high-value dealers, and USD 15,000 under the ADGM AML rules, firms with cross-border operations cannot apply a single global figure. They must map the applicable threshold, in-scope transaction types, covered entity categories, and aggregation rules to each jurisdiction in which they operate, and confirm exact values against the relevant local regulation, such as Article 35, § 1 of the Belgian AML legislation or the EU AML framework.

Inside Occasional Transaction Threshold

Occasional Transaction
A transaction carried out for a customer with whom the obliged entity does not have an established business relationship. It is treated differently from ongoing relationships because there is no continuing account or engagement through which risk is monitored over time.
Monetary Threshold Trigger
A defined value at or above which customer due diligence (CDD) obligations are triggered for an occasional transaction. The specific amount varies by jurisdiction and instrument, and exact values should be confirmed against the applicable regulation.
Aggregation / Linked Transactions
Rules that require multiple transactions that appear to be linked to be added together for the purpose of assessing whether the threshold is met, to prevent structuring below the limit. The treatment of linked transactions differs across regimes.
Wire Transfer and Fund Transfer Considerations
In many jurisdictions, certain transfers of funds may be subject to lower thresholds or specific information requirements distinct from the general occasional transaction threshold, reflecting travel-rule-type obligations.
Source Instruments
The threshold and its scope derive from the applicable AML framework rather than a single global rule. Examples include the FATF Recommendations (standards, not binding law), the EU AML Directives/Regulation, the US Bank Secrecy Act and FinCEN rules, and the UK Money Laundering Regulations. Requirements and figures diverge between these regimes.
CDD Obligation Consequence
Where the threshold is met or exceeded, the obliged entity generally must apply customer due diligence measures, such as identifying and verifying the customer, before or during the transaction, subject to the applicable regime.

Common questions

Answers to the questions practitioners most commonly ask about Occasional Transaction Threshold.

Does the occasional transaction threshold mean I never have to conduct due diligence below that amount?
No. The threshold identifies one trigger for customer due diligence on transactions carried out outside an established business relationship, but it is not the only trigger. In many jurisdictions, CDD is generally required regardless of value where there is a suspicion of money laundering or terrorist financing, or where there is doubt about the veracity or adequacy of previously obtained identification data. Certain transaction types, such as some wire transfers, may also be subject to information requirements at lower or no thresholds. The threshold should therefore be treated as a floor for a specific scenario, not a universal exemption below which no obligations apply. Confirm the applicable triggers against the regulation governing your entity.
Is the occasional transaction threshold the same figure everywhere?
No. Threshold amounts, the currencies in which they are expressed, and the transaction categories to which they apply vary by regime. The concept appears in the FATF Recommendations as a standard, but FATF Recommendations are standards rather than binding law, and individual jurisdictions transpose them differently through their own instruments, such as the EU AML framework, the US Bank Secrecy Act and FinCEN rules, or the UK Money Laundering Regulations. Some regimes also set distinct thresholds for particular activities. You should not assume a single global figure; verify the exact value, currency, and scope in the regulation applicable to your business.
How should I handle transactions that appear to be deliberately structured to stay below the threshold?
Transactions that appear to be broken into smaller amounts to avoid triggering CDD are commonly treated as a red flag, and many regimes address linked or connected transactions so that amounts may be aggregated where they appear to be related. Aggregation rules and the treatment of linked transactions are set by the applicable regulation and should be confirmed there. Where the pattern gives rise to a suspicion of money laundering or terrorist financing, that suspicion is itself an independent trigger for due diligence and, potentially, for reporting. Note that an apparent structuring pattern is an indicator that warrants review and is not by itself proof of wrongdoing.
What is the difference between applying the threshold to a single transaction and to linked transactions?
A single transaction is assessed on its own value against the threshold, while linked or connected transactions may be assessed on their combined value where the regime provides for aggregation. The purpose of aggregation provisions is generally to prevent a single occasional transaction from being split to fall below the threshold. The precise definition of what counts as linked, and any time window over which transactions are aggregated, is set by the applicable regulation and varies between regimes, so the exact aggregation methodology should be confirmed against the instrument governing your entity rather than assumed.
Does exceeding the threshold change whether I apply standard, simplified, or enhanced due diligence?
Crossing the threshold generally triggers a requirement to carry out customer due diligence on an occasional transaction, but the intensity of that due diligence is typically determined separately on a risk-sensitive basis. Standard CDD applies in ordinary-risk situations, simplified measures may be available in lower-risk situations where the regime permits, and enhanced due diligence is generally required in higher-risk scenarios, such as those involving certain higher-risk jurisdictions or, in the case of PEP screening, politically exposed persons. The threshold determines when the CDD obligation is engaged for an occasional transaction; the applicable risk assessment then informs which level of measures is appropriate.
How should the occasional transaction threshold be reflected in transaction monitoring and system configuration?
Systems are typically configured to identify when a transaction outside an established business relationship reaches or exceeds the relevant threshold so that CDD is applied at the correct point, and, where the regime requires it, to support aggregation of linked transactions rather than assessing each in isolation. Configuration should reflect the exact threshold value, currency, and transaction scope set by the applicable regulation, and should not rely solely on the threshold, since suspicion and other triggers can require action independently of value. Monitoring is a measure to help detect and manage risk; it should be periodically reviewed and does not by itself guarantee that all relevant transactions are captured. Confirm parameters against the governing regulation and your entity's risk assessment.

Common misconceptions

There is a single, universal monetary threshold for occasional transactions that applies everywhere.
Thresholds are set by individual regimes and instruments and can differ in amount, scope, and how they treat linked transactions. FATF issues standards rather than binding law, and jurisdictions such as the EU, US, and UK implement their own figures and rules. Exact values should be confirmed against the applicable regulation.
Staying below the threshold means no AML obligations apply to the transaction.
Aggregation and linked-transaction rules can bring related transactions above the threshold in combination, and separate obligations, such as those for certain fund transfers or suspicion-based requirements, may apply regardless of the value. Falling below the threshold does not remove all obligations.
The occasional transaction threshold and the requirement to report suspicion are the same trigger.
The threshold governs when CDD is generally required for a one-off transaction; it is distinct from suspicion-based obligations. In many jurisdictions, a reasonable suspicion can require action irrespective of whether the monetary threshold is reached, and neither an alert nor a filing establishes wrongdoing.

Best practices

Confirm the specific threshold amount, currency, and scope against the AML instrument applicable to your jurisdiction and business line rather than relying on a single assumed figure.
Implement aggregation logic that identifies and combines transactions that appear to be linked, so that structuring below the threshold is detected and appropriate CDD is triggered.
Distinguish occasional transactions from established business relationships in your onboarding and transaction workflows, since the two attract different monitoring and due diligence expectations.
Apply any lower or specific requirements that may attach to certain fund or wire transfers separately from the general occasional transaction threshold, and document which rule set was applied.
Treat the monetary threshold as one trigger among several; ensure suspicion-based obligations are actioned independently of whether the threshold is met.
Maintain clear records of how the threshold assessment was made, including any aggregation decisions and the CDD measures applied, to support auditability and regulatory review.