Understanding the purpose and intended nature of a business relationship is part of customer due diligence. In practice it means recording what the customer intends to do, at what scale, with whom and from where, in a form specific enough that later activity can be compared against it.
On this page
What it means
Purpose answers why the customer wants the relationship. Intended nature answers how it is expected to operate. Together they create the reference point against which later activity is judged. Without them, transaction monitoring can only compare a customer to a peer group and the firm has no documented basis for calling anything unexpected.
Regulatory basis, stated carefully
HMRC's guidance for supervised businesses describes customer due diligence as including customer and beneficial owner checks where applicable, understanding ownership and control, understanding the purpose and intended nature of the relationship, ongoing monitoring, record keeping and updating information on change. The FCA Financial Crime Guide sets out corresponding expectations for firms it supervises.
The FCA's April 2026 findings on customer due diligence processes and controls listed failure to record the purpose and intended nature of the relationship among the weaknesses it observed. That is an observation about the firms reviewed, not a statement that every firm in every sector must record the same fields in the same way, and the applicable requirements vary by sector and supervisor. This page is general information, not legal or compliance advice.
What to capture
| Field | Why it earns its place |
|---|---|
| Products and services expected | Defines the scope of the relationship and the monitoring scenarios that apply |
| Reason for the relationship | Explains why this firm and this product, which is what an unusual pattern is tested against |
| Expected volumes and values | Gives monitoring a baseline instead of a purely peer-derived threshold |
| Expected frequency and seasonality | Prevents legitimate cyclical activity generating repeated alerts |
| Expected counterparty types | Supports assessment of unexpected third-party involvement |
| Expected jurisdictions | Links the relationship to the country risk methodology |
| Expected source of funds | Allows inflows inconsistent with the stated origin to be identified |
| Channels to be used | Informs delivery channel risk and the verification approach |
Depth should scale with risk. A standard low-risk relationship can be captured with selections from defined option sets. A complex or higher-risk relationship warrants ranges, named counterparty types and a short narrative explaining the commercial rationale, which also feeds enhanced due diligence.
Structuring the record
- Use structured fields with controlled values wherever the data will drive a downstream control.
- Keep a short free-text rationale alongside the structured fields, not instead of them.
- Record ranges rather than single points for values and volumes, so normal variation does not look like divergence.
- Timestamp and version the record, so the expectation in force at any past date can be reproduced.
- Record who supplied the information and how it was corroborated, if it was.
Agora practitioner interpretation
A simple test we apply: could a monitoring analyst, without speaking to anyone, decide whether a given transaction is consistent with the recorded expectation? If not, the record is documentation rather than a control, and it will not survive independent testing however neatly it is written.
Connecting it to monitoring and risk
The recorded expectation should feed three things: the customer risk assessment, through product, geography and channel factors; transaction monitoring, through thresholds and expected counterparties; and the trigger set, through divergence between expected and actual activity. Where divergence is explained, the explanation should update the record rather than sit only in an alert disposition.
Common pitfalls
- Single-word or boilerplate purpose statements repeated across thousands of files.
- Expected activity collected at onboarding and never compared to actual activity.
- Divergence explained in an alert note that never reaches the customer record.
- Purpose held in a document rather than in data, so no control can read it.
- No versioning, so the firm cannot show what was expected at the time of a past decision.
- Remediation programmes that refresh identity data but leave purpose fields untouched. See KYC remediation.
Where technology helps
Structured capture, validation at entry, comparison against actual activity and divergence reporting are straightforward to automate and materially improve consistency. The judgement about whether a stated rationale is credible remains with a person. The Agora Due Diligence Platform captures nature of business and expected activity as structured data that feeds risk assessment, monitoring and the case report.
Primary sources
- HMRC AMLG11300, customer due diligence (updated 16 July 2026)
- FCA, Firms' customer due diligence processes and controls: our findings (8 April 2026)
- FCA Financial Crime Guide, chapter 3
- The Money Laundering, Terrorist Financing and Transfer of Funds Regulations 2017
Frequently asked questions
What does purpose and intended nature of the business relationship mean?
It is the firm's understanding of what the customer intends to use the relationship for and how it is expected to operate: the products and services to be used, the reason for using them, the anticipated activity, the counterparties and jurisdictions involved, and the source of the funds expected to flow through it.
Is recording purpose and intended nature part of CDD?
Yes. HMRC guidance describes customer due diligence as including understanding the purpose and intended nature of the business relationship alongside customer and beneficial owner checks, ongoing monitoring, records and updating on change. The FCA's April 2026 review observed firms failing to record it adequately.
What level of detail is appropriate?
Enough detail for monitoring to be able to tell expected activity from unexpected activity. For a low-risk retail relationship that may be brief and standardised. For a complex corporate or higher-risk relationship it should include expected values, frequency, counterparty types and jurisdictions.
Why do free-text purpose statements fail review?
Because they are not usable downstream. A sentence such as business banking cannot be compared against actual activity, cannot drive a monitoring threshold, and gives a reviewer nothing to test. Structured fields with a short narrative explanation are far stronger.
How often should the recorded purpose be revisited?
Whenever activity diverges materially from what was recorded, when the customer takes new products or enters new markets, at review points set by the risk rating, and whenever another trigger event prompts a review of the file.
Related resources
Regulatory answer
Do firms need to record the purpose and intended nature of a business relationship?
CDD and onboarding
Customer Risk Assessment: A Practical CDD Framework
CDD and onboarding
Enhanced Due Diligence (EDD): Triggers, Evidence and Controls
Governance and assurance
Building a Regulator-Defensible CDD Audit Trail
Where the technology fits
Agora is a technology provider: the platform supports the control described above, and your own teams operate it and hold the accountable decisions.
Next step
Turning purpose into a usable control
See structured purpose capture feeding risk assessment and monitoring in the Agora platform.