IBAN verification in private fund payments

IBAN verification in private fund payments is the process of confirming that an International Bank Account Number (IBAN) provided by a fund counterparty is structurally valid, belongs to a real bank account at the claimed institution, and matches the name of the intended payee before a capital call or distribution payment is submitted. It is a pre-execution control that reduces both misdirected payment risk and the risk of fraudulent account substitution.

Structural IBAN validation confirms the format is correct; full IBAN verification confirms the account exists and the payee name matches, which requires integration with bank-level data or a verification service.

How it works

An IBAN consists of a two-letter country code, a two-digit check digit, and a bank-specific Basic Bank Account Number (BBAN). The check digit is calculated using the MOD-97 algorithm, which means any IBAN can be validated structurally without contacting the bank: if the check digit calculation fails, the IBAN is invalid.

Structural validation is necessary but not sufficient. A structurally valid IBAN may be valid in format but belong to a different account than the one claimed, or the account may be closed or controlled by a fraudster. Full IBAN verification requires one of three approaches:

First, account validation via a bank or payment service provider API. Some banks and payment infrastructure providers offer APIs that confirm whether an IBAN is active and the registered account holder name matches the payee name provided. This is the fund administration equivalent of UK Confirmation of Payee, applied to IBAN-based (SEPA) accounts.

Second, the EU Instant Payments Regulation (which entered force in stages from 2024 and extends through 2025 and 2026) requires payment service providers in the EU to offer IBAN verification to payers before sending SEPA Credit Transfers. PSPs must check whether the IBAN and the payee name match, and must warn the payer if they do not. This creates a regulatory mandate for IBAN name-matching across the SEPA zone, analogous to the UK's Confirmation of Payee requirement.

Third, some fund administrators implement their own counterparty verification protocols: requiring LPs and GPs to provide IBAN details through a controlled portal, with confirmation to a pre-registered contact, rather than accepting IBANs delivered by email. This approach treats IBAN verification as an onboarding and re-verification control rather than a point-of-payment check.

In the context of fund lifecycle payments, IBAN verification is relevant for both capital call collections (where the fund collects from LP accounts or where LPs wire to a fund account using an IBAN) and distributions (where the fund administrator must verify the receiving IBAN for each LP payment). The distribution verification case is higher risk for fraud, because distribution payments are typically the largest single amounts and LP banking details change over time as LPs restructure or redomicile.

The EU Instant Payments Regulation's IBAN/name matching requirement represents a significant shift in the operating environment for European fund administrators: from a world where IBAN matching was a voluntary best practice to one where PSPs are required to provide it, and where administrators whose payment banks offer the service should be configuring their workflows to use it.

Worked example

Ardent Fund Services manages distributions for a Luxembourg-domiciled SICAV with 41 LP commitments, predominantly from European institutional investors. All LPs provide payment details in IBAN format.

Before the quarterly distribution cycle, the payments team runs a verification step across all LP IBANs on the distribution list:

Structural validation confirms all 41 IBANs are correctly formatted. Three IBANs are flagged for manual review:

IBAN 1 belongs to an LP that provided updated banking details six weeks earlier via email. The verification step checks the new IBAN against the registered payee name through the fund's bank API and returns a name mismatch: the account is registered to a name that does not match the LP's legal entity name. The payment is held and the LP is contacted through a verified channel. The LP confirms their correct banking details, which differ from those provided in the email. A fraudulent substitution is identified and prevented.

IBAN 2 returns as inactive (the account has been closed). The fund administrator contacts the LP for updated details.

IBAN 3 passes all checks.

For the remaining 38 LPs, verification confirms name matches and active accounts. Distributions are processed.

Frequently asked questions

What is the difference between IBAN validation and IBAN verification? IBAN validation is structural: it checks that the IBAN conforms to the correct format for its country and that the check digit is mathematically correct. This can be done without any bank connectivity. IBAN verification goes further: it confirms that the account actually exists, is active, and that the registered account holder name matches the payee name provided. Validation catches formatting errors; verification catches fraud, substituted accounts, and closed accounts.

Is IBAN name matching mandatory in Europe? The EU Instant Payments Regulation, which applies to payment service providers within the EU, requires PSPs to offer an IBAN/name verification service to payers before processing SEPA Instant Credit Transfers, with a phased implementation timeline. This creates a mandatory verification layer at the PSP level. Fund administrators should confirm with their payment banks whether the service is available and how to integrate it into their payment workflows.

What should a fund administrator do if an IBAN verification returns a mismatch? A mismatch between the payee name in the payment instruction and the registered account holder name should trigger a payment hold and a re-verification process through an independent channel: a direct call to the pre-registered contact at the LP or GP, not a reply to the email that delivered the original banking details. The mismatch should be documented and the outcome recorded in the counterparty file regardless of resolution.

Does IBAN verification apply to non-European fund payments? IBAN is the standard account format for SEPA (eurozone and wider European) payments. For non-European payments (such as US wire transfers using ABA routing numbers and account numbers, or UK BACS payments), the equivalent pre-payment control is Confirmation of Payee (UK) or the payment PSP's own account validation service. The principle of verifying that the account belongs to the intended payee applies universally; the specific mechanism varies by payment system.

Can IBAN verification be automated as part of a payment workflow? Yes. Fund administrators using payment systems with API integration to a verification service can trigger IBAN name checks automatically as part of the payment creation or approval workflow. The verification result can be surfaced to the checker as part of the maker-checker review step, or it can be configured as a blocking control that prevents payment creation for unverified accounts.

Related terms

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

Related pages

IBAN verification for European fund payments: what administrators need to know, Swelv for fund administrators