Confirmation of Payee

Confirmation of Payee (CoP) is an account name-checking service that verifies whether the name on a payment instruction matches the name registered to the destination bank account before the payment is sent. It is a pre-execution control designed to prevent misdirected payments and authorised push payment (APP) fraud.

In private fund administration, CoP is particularly significant because capital calls and distributions involve large, infrequent wire transfers to account details that may have been provided weeks or months earlier, creating a window in which fraudulent substitution of payment instructions can occur.

How it works

When a payer's bank submits a payment instruction, it queries the payee's bank via a shared API and returns one of four responses: match (the name is an exact or close match), close match (the name is similar but not identical), no match (the name does not correspond to the account), or unable to check (the payee bank does not participate in the scheme or the account type is not covered).

The payer's bank presents this result to the payment initiator before authorising the transaction. In consumer and business banking, this is surfaced as a warning in the payment interface. In fund administration workflows, it must be integrated at the point of payment instruction processing, typically within a payment operations system or treasury management platform.

In the UK, CoP is mandated for all Faster Payments and CHAPS transactions above a threshold, administered under Pay.UK rules. Participation is required for all major UK banks and building societies. Across the EU, similar name-checking requirements are being embedded in SEPA Instant Credit Transfer regulations under amendments to the EU Instant Payments Regulation, which require payment service providers to offer payee verification services.

CoP operates at the bank-to-bank infrastructure level. It does not verify that the payee is the correct counterparty in a commercial relationship; it verifies only that the account name matches. Fund administrators and GPs therefore cannot rely on CoP alone to confirm that a distribution is reaching the correct LP entity. CoP is one control within a layered verification framework, not a standalone solution.

Worked example

Meridian Private Credit Fund III is processing a EUR 4.2 million capital call drawdown. The fund administrator's payment operations team loads a batch of LP wire instructions. Before submission, the payment system queries CoP for each instruction.

For LP A (Windermere Pension Trustees Limited), the query returns a match against the registered account name at the receiving bank.

For LP B (Calloway Family Office), the query returns a close match: the account is registered to "Calloway Family Office Limited" rather than "Calloway Family Office." The fund administrator's operations team contacts LP B to confirm the correct legal entity name before releasing the payment.

For LP C (Northgate Endowment Fund), the query returns no match. Investigation reveals that the LP updated its banking details three weeks earlier by email, and the new account details were entered without completing the administrator's standard verification process. The payment is held pending re-verification through a secure channel.

In this example, CoP functions as the last-line check before payment execution. The near-miss for LP C illustrates why CoP is necessary even when administrators believe their onboarding controls are robust.

Frequently asked questions

Does Confirmation of Payee apply to international payments? CoP applies to domestic UK payments within the Faster Payments and CHAPS schemes. For international wire transfers (SWIFT), there is no equivalent mandatory scheme, though some banks offer voluntary SWIFT GPI-based checks. This gap is significant for fund administrators processing cross-border capital calls and distributions.

What is the difference between a "close match" and a "no match" result? A close match indicates that the account name registered at the receiving bank is similar but not identical to the name on the instruction, typically due to abbreviations, punctuation, or missing legal suffixes such as "Ltd" or "Limited." A no match means there is no recognisable correspondence between the instruction name and the registered account name. Both results require investigation before payment release; neither should be auto-cleared.

Is CoP mandatory for fund administrators in the UK? CoP is a requirement for payment service providers (banks and payment institutions), not for fund administrators directly. However, fund administrators using UK bank accounts for capital call and distribution payments benefit from CoP checks when their payment bank participates in the scheme. Fund administrators should confirm with their banking provider whether CoP queries are executed as part of their payment processing workflow.

Does CoP prevent all payment fraud in fund administration? No. CoP verifies account name matching at the point of payment execution. It does not prevent fraud that originates in the onboarding process, where a fraudulent account is registered under a legitimate-sounding name. It also cannot detect compromised legitimate accounts. CoP is most effective as part of a layered security approach that includes secure onboarding, payment instruction controls, and regular account detail re-verification.

What happens when a payee bank does not participate in CoP? When a query returns "unable to check," the payer bank cannot provide a name match result. In private fund administration, an "unable to check" result for a large payment instruction should trigger a manual verification step rather than being treated as a default approval. Administrators should maintain documented procedures for handling non-participating payee banks.

Related terms

APP fraud (authorised push payment fraud), Business email compromise (BEC) in capital calls, IBAN verification in private fund payments, Maker-checker in fund administration, Straight-through processing (STP) in fund payments

Related pages

How fund administrators should protect capital call payments from wire fraud, Swelv for fund administrators