The Destination Audit: Why a New Settlement Bank Restarts the Underwriter's Clock

The field that carries the most weight

Of all the data points an offshore acquirer holds on a UK merchant, none is more sensitive than the account into which money is paid. Pricing can be renegotiated and descriptors can be amended, but the settlement destination is the acquirer's final point of control. Once funds leave the acquiring chain, recovery options narrow sharply. That is why a routine-sounding instruction — please pay us somewhere else — is read in the risk department before it is read in the operations department.

Three concerns converge on the same field. First, change-of-beneficiary fraud: business email compromise remains one of the most common ways for funds to be diverted, and payment companies know that a spoofed instruction is far cheaper to attempt than a genuine attack on their infrastructure. Second, anti-money-laundering obligations: a new beneficiary is a new counterparty to screen, in a new jurisdiction, potentially with a different ownership chain behind it. Third, continuity of control: if the account holder changes, so too does the question of who genuinely directs the business.

What counts as a change

Merchants often underestimate the scope. A review is likely to be triggered by any of the following:

• a new IBAN or account number, even at the same bank;
• a move to a different bank or a different country;
• a change to the name on the account, including from a trading style to a legal entity name or the reverse;
• a shift from a bank to an electronic money institution, or the reverse;
• a change of settlement currency;
• the addition of a second account for split payouts.

A change of account holder name should be treated as a new application in all but name. It alters the legal identity receiving funds, and the acquirer will ordinarily want the onboarding evidence refreshed rather than merely amended.

The evidence file, assembled in a sensible order

Acquirers differ in detail but converge on substance. A complete pack, sent unprompted, shortens the review considerably.

Board or member resolution. Dated, quorate, naming the individuals authorised to instruct the change, and quoting the new account details in full. A resolution that says "the new account notified to the board" invites a follow-up question; one that reproduces the IBAN does not.

Dual authorisation. Two signatories, typically one director and one finance officer, with evidence that both are authorised signatories on the company mandate. Where the same person holds both roles, say so in the covering note rather than letting the acquirer discover it.

A bank attestation letter. Issued on the bank's letterhead, confirming the account name, IBAN, currency and — critically — that the merchant entity is the account holder rather than a client, trust or pooled beneficiary. A merchant-authored PDF describing the account carries very little evidential weight.

Confirmation of Payee evidence. Where the receiving institution supports it, run a check from the merchant's existing account and record the outcome, including a mismatch where one occurs. Many offshore accounts sit outside the scheme; in that case, record that the check was attempted and unsupported, and rely on the bank letter instead. An acquirer is more comfortable with a documented limitation than with silence.

Ownership and identity refresh. The same core pack used at onboarding: certificate of incorporation, register of members, persons with significant control, director identification, and proof of the entity's address. If the ownership chain has moved since the original file was built, this is the moment it surfaces.

Account confirmation. A statement or opening confirmation showing the entity name and IBAN, matching the resolution exactly.

An internal audit trail. Who requested the change, who approved it, when, under which ticket reference, and which version of which document was sent. This is the part merchants most often omit and the part that most reliably accelerates subsequent queries.

The delays that recur

Name mismatches account for a large share of friction. Acquirers reconcile the settlement account name against the merchant legal entity and the descriptor on the cardholder statement; a trading style that appears in one place and not the other requires explanation.

Client-money and third-party accounts are generally unacceptable. A settlement account must belong to the contracting entity, not to an agent, a parent, or a payment facilitator acting on its behalf.

Institutional type matters too. Some acquirers accept electronic money institutions subject to safeguards confirmation; others do not, or will only do so for certain jurisdictions. A change that moves the relationship from a bank to an institution of a different type is a change of risk category, not a change of address.

Sequencing around the payout calendar

Read the contract before setting a date. Notice periods for bank detail changes commonly run between ten and thirty business days, and some agreements reserve the right to suspend payouts while verification is completed.

Aim for the change to take effect at the start of a settlement cycle rather than mid-cycle, when a part-processed batch creates reconciliation ambiguity. Assume a payout pause of one to two cycles and fund working capital accordingly; a three to four week liquidity buffer is a reasonable planning assumption for a first change with a new institution.

Ask directly, and in writing, whether the change affects reserve or holdback terms. A new beneficiary can prompt a rollover reserve review even where the merchant's risk profile is unchanged. If the existing terms are to be preserved, obtain confirmation rather than inference.

Keep the outgoing account open and monitored for at least two further cycles. Dual confirmation of the first successful payout to the new destination is a small administrative cost against the alternative.

Handling the conversation

Use one thread, one named contact and written correspondence throughout. Request the acquirer's own checklist at the outset — processes vary, and improvising around them wastes time. Confirm the effective date, the anticipated pause, the status of the merchant identifier and any reserve implications in a single confirmation email.

If the change is driven by circumstances rather than preference — a bank withdrawing from a sector, a jurisdiction or a currency — say so plainly. It reframes the request from a discretionary amendment to an operational necessity, and acquirers price those two situations differently.

What to avoid

Never transmit new bank details without a call-back verification to a number already on file. Do not split one change across several tickets, which fragments the audit trail. Resist bundling a bank change with a currency change and a corporate restructure in the same month; sequential changes are reviewed sequentially, and the file stays legible.

After the money lands

Reconcile the first payout against expectation and record the result. Update standing data everywhere it appears: contracts, invoices, insurance, VAT records and internal mandates. Retain the full file for six years, in line with the record-keeping habits expected of UK companies.

The settlement destination is not an administrative field. It is the point at which the acquirer's exposure becomes irreversible, and it deserves to be treated with the same preparation as the original application.