Virtual IBANs and Named Accounts: What They Are and When Your Company Needs Them

A virtual IBAN routes incoming payments to an underlying account and helps identify the customer or payment flow. A named account provides payment details associated with the company’s verified legal name, which can make beneficiary checks and procurement approval easier. They can be combined, but neither label alone explains who legally holds the funds, which currencies and rails are supported, or whether the same details can be used for outgoing payments.

What is a virtual IBAN?

A virtual IBAN, or vIBAN, is a unique International Bank Account Number used to route and identify payments. It usually points to an underlying collection, payment or operating account rather than representing a separate bank account with its own balance.

A provider may issue one vIBAN to a company or multiple vIBANs for specific customers, subsidiaries, regions or payment flows. When a transfer arrives, the destination vIBAN becomes a structured reconciliation field. This is often more dependable than asking a payer to enter an invoice number in a free-text payment reference.

For example, a company might use separate vIBANs for:

• European customer receipts;
• capital contributions and treasury funding;
• individual enterprise customers;
• different subsidiaries, where the provider’s account structure permits it; or
• fiat funds intended for conversion into USDC or USDT.

A vIBAN should not automatically be described as a standalone bank account. Finance teams need to identify the institution providing the underlying account, the legal account holder, the entity entitled to the funds and the way customer money is safeguarded or otherwise held. They should also confirm whether the vIBAN is receive-only or can be used to originate payments.

What is a named account?

A named account provides payment details associated with the company’s verified legal name instead of displaying only the name of a payment provider or the holder of a pooled account. This matters when a customer, investor or vendor compares the beneficiary name with the name on a contract or invoice.

Some procurement and accounts-payable teams will not release funds when payment instructions show an unrelated provider name. Named details can reduce those exceptions, but the term does not necessarily mean the company has opened a conventional bank account directly with a bank. The structure could be a dedicated account, a virtual account or an account delivered through a banking or payments partner.

Name presentation also depends on the payment rail and the sending institution. A provider may register the company’s legal name but cannot necessarily control how every bank displays or validates it. Before publishing details on invoices, request the exact account-holder wording and test how it appears to a sender using the relevant rail.

Virtual IBAN versus named account

The features are not mutually exclusive. A company may receive a vIBAN that is also registered or presented in its legal name. Conversely, named details may lead to an account that still relies on pooled infrastructure. Evaluate the operating and legal attributes rather than selecting a product based on its label.

How collection accounts fit into the structure

A collection account is designed to receive money from customers or counterparties. One underlying collection account can be connected to many virtual account numbers, allowing a business to centralise liquidity while preserving customer-level identification.

If each enterprise customer receives a dedicated vIBAN, the finance system can use the destination account number to assign an incoming transfer to that customer’s ledger. This remains useful when the payer omits an invoice number. Exceptions still require review—for example, when a parent company pays on behalf of a subsidiary or one transfer settles several invoices—but the initial attribution becomes more reliable.

Before issuing virtual accounts at customer level, confirm the issuance process, available quantity, transaction data, lifecycle controls and any applicable charges. Establish whether a closed vIBAN remains reserved or can be reassigned. Reassignment creates a reconciliation risk if a former customer sends a late or duplicate payment.

A virtual IBAN is not a multi-currency account

A multi-currency account lets a company hold and manage balances in more than one currency. A virtual IBAN is an identifier used to route payments. A product may include both, but one feature does not imply the other.

An IBAN might accept only EUR, accept several supported currencies into separate balances, or automatically convert receipts into a base currency. If a payer sends an unsupported currency, the transfer may be rejected, returned or converted by an intermediary or receiving provider.

Finance should document the following for every set of payment details:

• currencies that can be received;
• whether funds remain in the received currency;
• how any automatic conversion rate and fee are determined;
• whether local and cross-border transfers require different instructions;
• how intermediary and correspondent charges are allocated; and
• which transaction fields appear in statements, exports or APIs.

Payment rails determine speed and reach

The presence of an IBAN does not determine settlement speed. Timing depends on the payment scheme, sending and receiving institutions, cut-off times, business calendars, transaction eligibility and compliance review.

First-time payments, incomplete originator information, unusual transaction patterns and sanctions or compliance reviews can delay any rail. Treasury policies should therefore distinguish a payment scheme’s normal processing model from a provider’s estimated arrival time.

When does a company need each setup?

Choose virtual IBANs when reconciliation is the main problem

Virtual IBANs are useful when the company receives many bank transfers, payers regularly omit references or finance staff spend substantial time matching cash to invoices. The benefit is greatest when the provider exposes the destination vIBAN in transaction exports, webhooks or an API and preserves it after funds are swept or converted.

Choose named details when beneficiary identity is the blocker

A named account is more important when enterprise customers, investors or vendors refuse to transact with pooled details under a provider’s name. It can also reduce support requests caused by invoice instructions that appear inconsistent with the contracting entity.

Choose collection accounts to segment payment flows

Collection structures are appropriate when the company wants separate details by customer, subsidiary, region or product while centralising liquidity. Confirm that the accounting export retains enough information to post receipts to the correct legal entity and ledger account.

Choose multi-currency capability when conversion timing matters

If the company receives EUR, USD and GBP and wants to control when each balance is converted, currency-holding functionality matters more than the availability of an IBAN alone. Review conversion spreads, explicit fees, cut-offs and the source used for quotes.

Using fiat account details with stablecoin treasury

For companies moving between fiat and USDC or USDT, the fiat account is only one part of the workflow. Treasury must also confirm the conversion quote, supported stablecoin and blockchain network, transaction minimums or maximums, destination-address requirements and the evidence available for both sides of the conversion.

Controls should cover who can request a conversion, who approves it and who authorises the blockchain transfer. The records should connect the incoming bank payment, conversion confirmation, network transaction and accounting entry. Stablerail, for example, combines fiat off-ramp and global payouts with USDC/USDT treasury controls including approvals, signing quorum, pre-send sanctions and address screening, and exportable audit evidence.

Jurisdiction, KYB and payment restrictions

Availability depends on the company’s jurisdiction of incorporation, operating locations, ownership, industry, expected activity and the provider’s banking or payments partners. Eligibility for a stablecoin account does not automatically imply eligibility for every fiat account type or local payment rail.

Know-your-business review commonly covers incorporation records, directors and beneficial owners, registered and operating addresses, business activities, expected transaction patterns and source of funds. Providers may request contracts, invoices, financial information or licences where relevant to the business model.

Confirm eligibility for the specific legal entity that will own or use the details. Also ask which payer countries are supported, whether third-party payments are permitted, how related-party transfers are treated and what happens when a payment falls outside the declared activity.

Finance-team evaluation checklist

1. Map the flow: identify the payer, receiving entity, currency, payment rail and intended use of funds.
2. Verify identity: obtain the exact beneficiary name and test how it appears through the required rail.
3. Document the structure: record whether the details are virtual, dedicated or pooled and identify the underlying account provider.
4. Test reconciliation: confirm that statements and exports include the destination vIBAN, payer identity, reference, value date, fees and returns.
5. Review currency handling: establish whether receipts are held, rejected or converted and who bears intermediary charges.
6. Set controls: separate setup, approval, payment and reconciliation responsibilities, and retain evidence for audit.
7. Run a pilot: send representative payments over each required rail before replacing invoice instructions or moving material treasury balances.

The correct choice is often not virtual IBAN or named account. It is a structure that combines reliable payer identification, acceptable beneficiary presentation, suitable currency and rail coverage, clear legal treatment of funds and transaction data that finance can reconcile and audit.