Skip to main content
Category: Customer Due Diligence

Purpose and Intended Nature

Also known as: Purpose and Intended Nature of the Business Relationship, Purpose and Intended Nature of the Business Relationship or Occasional Transaction
Simply put

"Purpose and intended nature" refers to understanding why a customer is establishing a relationship or carrying out a transaction with a financial institution or other regulated business, and what that relationship or transaction is expected to look like in practice. For example, a firm seeks to understand the reason a customer is opening an account and the type and pattern of activity it can expect to see. This information helps the firm build a picture of the customer so it can better assess and manage money laundering and terrorist financing risk.

Formal definition

"Purpose and intended nature" is a customer due diligence (CDD) element under which obliged entities identify, assess, and where appropriate obtain information on the reason for, and the expected characteristics of, a business relationship or occasional transaction. UK guidance frames "purpose" as the reason something is done, created, or exists, and "intended nature" as its expected characteristics. This element is typically used to inform the customer risk profile and to establish an expected baseline of activity against which ongoing monitoring can be conducted; it is a component of CDD rather than a standalone control, and it should not be conflated with identity verification or with enhanced due diligence measures. The specific obligation and its documentation requirements vary by regime: for example, it appears in FFIEC BSA/AML guidance in the United States in connection with developing a customer risk profile, in FINTRAC business relationship record-keeping requirements in Canada, and under Article 25 of the EU AML Regulation (AMLR), which requires obliged entities to identify and document it for business relationships and occasional transactions. Exact scope, thresholds for occasional transactions, and record-keeping specifics should be confirmed against the applicable regulation.

Why it matters

Understanding the purpose and intended nature of a business relationship is foundational to a risk-based approach to customer due diligence. Without a clear picture of why a customer is establishing a relationship and what activity can reasonably be expected, an obliged entity has no baseline against which to judge whether later activity is consistent or anomalous. This element feeds directly into the customer risk profile, which in turn shapes decisions about the intensity of ongoing monitoring and whether enhanced measures may be warranted. It is a component of CDD rather than a standalone control, and it does not by itself verify identity or determine that any activity is illicit.

The practical significance is most visible in ongoing monitoring. Where a firm has documented an expected pattern of activity at onboarding, subsequent transactions that diverge sharply from that baseline can be identified and reviewed. A relationship described as, for example, a personal savings account would raise different expectations than one described as a high-volume international trading operation. Establishing this expectation early helps a firm detect, deter, and manage money laundering and terrorist financing risk, though it should be understood as a measure to manage risk rather than a guarantee against it.

The obligation is reflected across multiple regimes, though the specific requirements and documentation standards differ. It appears in FFIEC BSA/AML guidance in the United States in connection with developing a customer risk profile, in FINTRAC business relationship record-keeping requirements in Canada, and under Article 25 of the EU AML Regulation, which requires obliged entities to identify and document it for business relationships and occasional transactions. Because scope, thresholds for occasional transactions, and record-keeping specifics vary, firms should confirm exact obligations against the regulation applicable to them.

Who it's relevant to

Compliance officers and CDD teams
Those responsible for onboarding and customer risk assessment use this element to build the customer risk profile and to establish an expected baseline of activity. They must ensure that the information gathered and documented meets the standards of the applicable regime, whether that is FFIEC BSA/AML guidance, FINTRAC record-keeping requirements, Article 25 of the EU AML Regulation, or another framework.
Transaction monitoring and financial intelligence analysts
Analysts rely on the documented purpose and expected activity as the reference point against which actual transactions are assessed. Divergence from the expected baseline can prompt review, though it establishes only a basis for investigation and does not, by itself, indicate wrongdoing.
Obliged entities across regulated sectors
Financial institutions and other regulated businesses subject to CDD obligations must identify, and where appropriate obtain information on, the purpose and intended nature of business relationships and occasional transactions. The precise scope, thresholds for occasional transactions, and documentation requirements differ by jurisdiction and should be confirmed against the applicable regulation.
Legal, risk, and audit functions
These functions review whether the firm's approach to capturing purpose and intended nature is adequate, proportionate to risk, and consistent with the record-keeping obligations of the relevant regime. They help ensure the element is applied as part of a broader CDD framework rather than treated as a substitute for identity verification or enhanced due diligence.

Inside Purpose and Intended Nature

Purpose of the Business Relationship
Information capturing why the customer is establishing the relationship with the obliged entity, such as the type of account or service sought and the underlying reason for it. This forms part of Customer Due Diligence (CDD) obligations and typically feeds the customer risk assessment.
Intended Nature of the Business Relationship
Information describing how the customer is expected to use the relationship, including anticipated activity, transaction types, expected volumes and values, counterparties, and geographies. This establishes a baseline of expected behaviour against which actual activity can later be compared.
Baseline for Ongoing Monitoring
The purpose and intended nature information provides the reference point that enables ongoing monitoring, helping the obliged entity assess whether transactions are consistent with what is known about the customer and their risk profile. Deviations may warrant further review but do not, on their own, establish wrongdoing.
Regulatory Source and Scope
Understanding the purpose and intended nature of a business relationship is generally an element of CDD required of obliged entities. The obligation is reflected in the FATF Recommendations as international standards and is transposed into binding law through instruments such as the EU AML framework, the US Bank Secrecy Act and FinCEN rules, and the UK Money Laundering Regulations, with details and thresholds varying by jurisdiction.
Risk-Based Application
The depth and formality of information gathered on purpose and intended nature is typically calibrated to the assessed risk. Lower-risk relationships may be understood in more general terms, while higher-risk situations may prompt Enhanced Due Diligence (EDD) with more detailed inquiry.

Common questions

Answers to the questions practitioners most commonly ask about Purpose and Intended Nature.

Is collecting information on the purpose and intended nature of a business relationship the same as verifying a customer's identity?
No. Verifying identity is a distinct element of customer due diligence, whereas understanding the purpose and intended nature of the relationship is a separate CDD component that focuses on why the customer is establishing the relationship and how they expect to use the account or service. In many jurisdictions, obtaining information on the purpose and intended nature of the relationship is listed as its own CDD measure alongside identification, verification, and beneficial ownership identification. Identity verification confirms who the customer is; understanding purpose and intended nature establishes the expected pattern of activity against which ongoing monitoring can later be assessed. The exact wording of each obligation should be confirmed against the applicable regulation.
Does documenting the purpose and intended nature of the relationship guarantee that later transactions are legitimate?
No. Establishing the purpose and intended nature of a relationship is a measure to help detect, deter, and manage financial crime risk, not a guarantee of legitimacy. Its function is typically to create an expected baseline of activity that supports ongoing monitoring, so that deviations can be identified and assessed. A customer's stated purpose may be accurate, incomplete, or deliberately misleading, and activity consistent with a stated purpose is not proof of legitimacy any more than a deviation is proof of wrongdoing. No single control eliminates financial crime risk.
How much detail should be captured about the purpose and intended nature of a relationship?
The level of detail generally reflects a risk-based approach. For lower-risk relationships, a broad understanding of the anticipated purpose and expected use may be sufficient, while higher-risk relationships, such as those involving certain customer types, products, or jurisdictions, may warrant more granular information about expected transaction types, volumes, values, counterparties, and geographies. The aim is typically to capture enough to establish a meaningful baseline for ongoing monitoring. Specific documentation expectations vary by regime and by obliged entity type and should be confirmed against the applicable regulation and internal policy.
When should the purpose and intended nature of the relationship be established?
In many jurisdictions this is expected to be understood as part of onboarding, before or during the establishment of the business relationship, as one of the CDD measures applied at the outset. It is generally not a one-off exercise: the recorded understanding is typically revisited and updated as part of ongoing monitoring and periodic or trigger-based reviews, particularly where activity diverges from expectations or where the customer's risk profile changes. The precise timing requirements depend on the applicable regime and should be confirmed against the relevant rules.
How does the purpose and intended nature of a relationship feed into ongoing monitoring?
The information typically serves as the expected baseline against which actual activity is compared during ongoing monitoring. Where transactions are broadly consistent with the anticipated purpose and expected patterns, they may attract less scrutiny; where activity is materially inconsistent with what was recorded, this can prompt further review, requests for information, or escalation. A material and unexplained deviation may contribute to a decision to consider a suspicious activity or transaction report, but it is a trigger for assessment rather than a determination of wrongdoing, and terminology and filing obligations differ by jurisdiction.
What should happen if a customer cannot or will not explain the purpose of the relationship?
An inability or refusal to provide a plausible account of the intended purpose is often treated as a risk factor that may warrant enhanced scrutiny, further enquiry, or escalation, and in some circumstances may affect whether the relationship can be established or continued consistent with the entity's risk appetite and CDD obligations. Depending on the facts and the applicable regime, it may also feed into a suspicion assessment. The specific consequences, including any obligations where CDD cannot be completed, depend on the relevant regulations and internal policy and should be confirmed against those sources.

Common misconceptions

Understanding the purpose and intended nature is the same as identity verification (KYC).
Identity verification confirms who the customer is, whereas establishing purpose and intended nature addresses why the relationship is being formed and how it is expected to be used. Both are components of CDD, but they are distinct elements and are not interchangeable.
A single, uniform standard for what must be recorded applies across all jurisdictions and all customers.
While understanding purpose and intended nature is a common CDD element internationally, the specific requirements, documentation expectations, and thresholds differ across regimes such as the EU AML framework, the US BSA/FinCEN rules, and the UK Money Laundering Regulations, and are applied on a risk-sensitive basis rather than identically for every customer.
Activity that departs from the stated intended nature proves that money laundering is occurring.
A deviation from expected activity is a signal that may warrant further review or escalation; it is an operational indicator, not proof of criminal conduct. Purpose and intended nature information supports the detection and management of risk, but does not by itself establish wrongdoing.

Best practices

Gather and record the purpose and intended nature of the relationship at onboarding as a distinct element of CDD, separate from identity verification, so the baseline for expected activity is documented from the outset.
Calibrate the depth of inquiry to assessed risk, seeking more detailed information on expected activity, counterparties, volumes, and geographies where higher risk or Enhanced Due Diligence is indicated.
Use the documented purpose and intended nature as the reference point for ongoing monitoring, comparing actual activity against expectations to identify deviations that may warrant review.
Treat departures from expected activity as prompts for further inquiry or escalation, not as conclusions of wrongdoing, and document the rationale for how any deviation is assessed.
Review and refresh purpose and intended nature information over the life of the relationship, particularly when triggering events, material changes in behaviour, or risk-level changes occur.
Confirm the specific documentation, threshold, and record-keeping requirements against the applicable regulation in each relevant jurisdiction rather than assuming a single global standard applies.