The difference between customer screening and counterparty screening is not always the list being searched or the software being used. The practical difference is usually why the party enters the control, which relationship or event creates the exposure, and what decision follows the result.
A company may be a continuing customer, a supplier under a procurement contract, a payee in one transaction or several of these at once. Those labels help organise controls, but they do not by themselves determine which sanctions restriction applies or whether PEP screening is relevant.
This guide helps compliance teams classify populations and route them to the right control. It does not replace the legal-perimeter, matching, ownership-and-control or alert-investigation work covered in the practical sanctions screening guide.
Customer screening and counterparty screening are not mutually exclusive
Customer screening usually begins with a continuing business relationship. The organisation identifies the customer, collects relevant identity or company information and decides which connected parties and later changes belong in its control.
Counterparty screening is broader and more context-dependent. A counterparty may be a supplier, merchant, distributor, intermediary, beneficiary, payee, financing party or another participant in a commercial or financial activity. In FCA guidance for firms within its scope, sanctions-screening considerations expressly include new customers, counterparties to transactions and payments.1
That wording matters because “counterparty” is not synonymous with an export-control party. Nor is it always separate from “customer.” A corporate customer receiving a payout may be both the customer relationship and a party to the transaction. A marketplace seller may be a platform customer, a payment recipient and a commercial counterparty.
The useful question is therefore not:
Is this a customer or a counterparty?
It is:
In which roles does this party appear, what exposure does each role create, and which screening trigger and decision path should apply?
Customer-relationship screening versus transaction-event screening
A continuing customer relationship creates opportunities to screen at onboarding and again when relevant facts or source data change. The organisation normally has a persistent customer record, internal identifier and some history of prior reviews.
A transaction counterparty may enter the control only when a payment, payout, shipment, order or other defined event occurs. The screening input and decision may therefore need to travel with that event rather than with a continuing customer record.
The distinction affects operations:
| Control dimension | Customer relationship | Transaction or counterparty event |
|---|---|---|
| Typical record | Persistent customer or client profile | Party attached to a payment, order, shipment or other event |
| Possible trigger | Onboarding, material customer change, source change or policy-defined review | The defined transaction or business event |
| Available context | Customer identity, ownership, relationship history and prior decisions | Event data, party identity, role and available relationship context |
| Review question | Does the relationship present relevant sanctions or PEP exposure? | Does this party or activity introduce a relevant sanctions concern at this event? |
| Evidence link | Customer record and continuing review history | Specific transaction or event and its operational outcome |
These are screening controls, not behavioural transaction monitoring. Screening compares identified parties with relevant sanctions or PEP data. Transaction monitoring evaluates activity patterns according to a different control purpose.
One organisation may need both relationship-level and event-level screening. Another may not. The design should follow its applicable perimeter, products, exposure and approved policy rather than a global template.
Customer, counterparty, supplier, payee and owner: a decision matrix
The matrix below is a routing aid, not a global statement that every listed population must always be screened.
OFAC includes customers, supply chains, intermediaries, counterparties and transactions among possible inputs to an organisation-specific sanctions risk assessment.2 The EU Sanctions Helpdesk likewise advises EU SMEs to consider ownership, control and relevant transaction-chain participants.3 Neither source creates one identical screening population for every organisation.
| Population | Typical relationship | Screening question | Possible trigger examples | Deeper guidance |
|---|---|---|---|---|
| Customer or client | Continuing business relationship | Is there relevant sanctions exposure involving the customer or connected parties, and is PEP assessment required under the applicable framework? | Onboarding, material change, source change or policy-defined review | Practical sanctions screening guide and PEP screening guide |
| Supplier or vendor | Procurement relationship | Does relevant sanctions exposure arise from the supplier, ownership context or associated payment and transaction parties? | Approval, renewal or a material ownership or payment change | Supplier and third-party screening |
| Commercial counterparty | Contract, trade, financing or another business interaction | What restriction could apply to this party or activity under the relevant regime? | Relationship establishment or a relevant transaction event | Practical guide or the relevant industry page |
| Payee, beneficiary or payment party | Transaction-specific or recurring | Does the event introduce a party subject to a relevant restriction? | A payment or payout event where required by the approved control | Practical guide and the relevant screening solution |
| Beneficial owner or controller | Connected to a customer or counterparty entity | Could applicable ownership-and-control rules affect treatment of the entity? | Onboarding, ownership change or sanctions-source change | Sanctions ownership and control |
| PEP or related person | Customer or related-party risk context | Does applicable AML/CFT law or policy require PEP-specific measures? | Relationship establishment or status change under the applicable framework | PEP screening guide |
The same organisation can appear in multiple rows. Preserve stable identifiers and relationship context so reviewers can understand whether two screening events concern the same party and why each occurred.
Keep sanctions, PEP and transaction monitoring separate
Sanctions screening can extend beyond the contracting customer when ownership, control or transaction-chain parties are relevant under the applicable regime and facts. FCA guidance for firms in its scope refers to customers, counterparties to transactions and payments, while its 2026 findings discuss risk across customer and counterparty relationships and transactions.14 These are scoped UK examples, not a global population rule. Use the supplier and third-party sanctions screening guide for procurement populations and the sanctions ownership and control guide for entity analysis.
PEP screening answers a different question. FATF describes PEP measures as preventive and states that PEP status does not imply criminal activity.5 Its standards are implemented through jurisdiction-specific frameworks.6 Do not automatically extend PEP screening to every sanctions counterparty or treat PEP status as a sanctions designation. The PEP screening guide owns that process.
Behavioural transaction monitoring is also a separate control: it evaluates activity patterns rather than comparing an identified party with sanctions or PEP data. See transaction screening versus transaction monitoring for that distinction.
Before adding a population to screening, answer these questions
Use a short control-design review:
- Which legal entity, jurisdiction, activity or product creates the potential exposure?
- What role does the party play in the relationship or transaction?
- Which sanctions or PEP question is the control intended to address?
- What identity, ownership and relationship information is available at the decision point?
- Which business event should initiate screening or re-screening?
- Who reviews the result, and what evidence must connect it to the decision and outcome?
Do not add a population merely because a vendor interface supports it. Equally, do not assume that customer onboarding covers parties introduced later by procurement, ownership changes, payments or other relevant events.
One screening service can support different populations, but that does not make them one policy. Screening also identifies a candidate for review; it does not determine identity, ownership or the legal response. The practical sanctions screening guide covers those decisions in depth.
Checklynx supports sanctions-screening workflows for customers, companies, UBOs, counterparties, suppliers, agents and payment parties through portal, CSV batch, API and ongoing monitoring. The organisation remains responsible for its screening perimeter, policy and legal decisions.
Frequently asked questions
What is the difference between customer screening and counterparty screening?
Customer screening generally begins with a continuing customer relationship. Counterparty screening concerns other parties to a commercial, financial or transaction event. The categories can overlap, and neither label alone determines which legal rule or workflow applies.
Does customer screening cover every counterparty?
Not automatically. Customer screening may include connected parties defined by the organisation's control, but suppliers, payees, intermediaries or other transaction parties can enter through different relationships and events. Map each relevant population explicitly.
Does counterparty screening mean export-control screening?
Not necessarily. Counterparties appear in trade and export-control settings, but the term is also used for parties to financial transactions, payments, contracts and other commercial activity. State the sanctions or restricted-party context rather than relying on the label alone.
Should every supplier, payee and beneficial owner be screened?
There is no defensible global rule that every organisation must screen every category identically. The population and triggers should follow the applicable sanctions perimeter, activity, sector, exposure and approved control design.
Is counterparty screening the same as transaction monitoring?
No. Counterparty sanctions screening compares an identified party with relevant sanctions data. Transaction monitoring evaluates activity patterns and is a separate control, even when both operate around the same payment or event.
Should every counterparty receive PEP screening?
Not as a universal rule. PEP measures relate to business relationships and customer-risk controls under applicable AML/CFT frameworks. Determine whether the particular person and relationship fall within the relevant framework or approved policy.
Can one platform screen customers and counterparties?
Yes. One technical service can support several populations and delivery modes. The organisation should still govern each population's scope, trigger, source selection, review route and evidence separately.
Official sources
Footnotes
-
Financial Conduct Authority, Financial Crime Guide, chapter 7: Sanctions, asset freezes and proliferation financing, UK supervisory guidance referring to customers, counterparties to transactions and payments and proportionate screening controls for firms in scope, version shown from 29 November 2024, accessed 9 September 2026. ↩ ↩2
-
US Department of the Treasury, Office of Foreign Assets Control, A Framework for OFAC Compliance Commitments, organisation-specific risk-assessment guidance covering customers, supply chains, intermediaries, counterparties, transactions and geographies, published May 2019, accessed 9 September 2026. ↩
-
European Union Sanctions Helpdesk, How to get sanctions compliant: who are you dealing with?, guidance for EU SMEs on ownership, control and transaction-chain participants, accessed 9 September 2026. ↩
-
Financial Conduct Authority, Sanctions systems and controls in our firms: our findings, supervisory findings on sanctions risks across customer and counterparty relationships and transactions, published 28 May 2026, accessed 9 September 2026. ↩
-
Financial Action Task Force, Politically Exposed Persons (Recommendations 12 and 22), official guidance describing PEP measures as preventive and addressing business relationships involving PEPs, accessed 9 September 2026. ↩
-
Financial Action Task Force, The FATF Recommendations, international AML/CFT/CPF standards for implementation through measures adapted to national circumstances, amended June 2026, accessed 9 September 2026. ↩