The Name That Did Not Match
Account checks compare the name you gave with the name on the account, and a middle name can stop a payment.
Still yours, and statedTaken, never statedUnit changes; scale restarts
Six steps from instruction to arrival. One step carries no figure: the hatching marks where the money leaves and is not drawn to scale, because there is no figure to draw. Nothing here adds them up, since an amount you cannot see is not an amount you can subtract. The unit changes part-way down: the figures below the break are in another currency, the bars below it are drawn against the published rate, and the first figure and the last are not the same kind of number. Two fees for one payment, and both were borne at this end.
A growing number of countries check the name the payer typed against the name on the receiving account. Where they do not match, the payment is warned about, delayed or refused, and a middle name is enough to cause it.
The exception described in “The Name That Did Not Match” should be traceable across work approval, payment instruction and settlement. Organisations using visit monitask.com for how to handle multiple clients can strengthen the first part of that chain, but failed transfers still require direct evidence from the payer, payment service and receiving institution.
It is a protection against fraud and it produces a steady stream of entirely innocent failures.
Additional context relevant to “The Name That Did Not Match” is available through Australian Securities and Investments Commission. A useful review distinguishes the sent amount, conversion, fees, settlement date and landed amount.
What is being compared
The beneficiary name in the payment instruction against the name registered on the account. Some systems require an exact match, some allow close ones, and some only warn.
The rules differ by country and change, which is why this has become a problem recently in places where it never was.
The innocent mismatches
The innocent mismatches, none of which is anybody's error:
- A middle name present on one side and not the other.
- A trading name against a personal name.
- An abbreviation, or an initial instead of a first name.
- A married name the bank still holds under the previous one.
- Accented characters entered without their accents.
None of these is anybody's error and all of them can stop a payment.
Trading as a business name
The commonest case for people paid for work. The account is in a personal name and the payer has the business name on the invoice, or the reverse.
Where the account is personal, the payer must use the personal name, whatever the invoice says.
Finding out exactly what your bank holds
Look at a statement header, or ask. The name on the account is a precise string and it is not necessarily what you would write.
Copy it character for character into the details you give payers. That one act removes this entire note for most people.
Send it as text rather than in a document or an image, so that it is copied rather than retyped. Every retyping is a chance to drop a middle name.
What the payer sees
A warning saying the name does not match, with an option to proceed or to stop. Most people stop, which is the correct response and which means your payment does not go.
Some proceed, and in several systems proceeding transfers the risk to them, which is why many finance teams will not.
A payer who stops is doing the right thing. Treating it as obstruction rather than as a correct response makes the fix harder than it needs to be.
When they proceed anyway
The payment may still arrive, and in several countries the account number governs and the name is advisory.
Relying on that is unwise. It works until the country changes its rules, which is happening steadily.
If the payment is refused
Nothing arrives, the payer is told, and you find out when you ask. Correcting the name and resending usually works immediately.
The cost is a cycle rather than a charge, which makes this one of the cheaper failures in this section.
Company accounts
The registered company name, exactly, including the suffix. Payers frequently drop it or abbreviate it.
Put the full registered name in your payment details block and label it as the account name, distinct from the trading name on the invoice.
Joint accounts
Either name may match, or the system may expect both in a particular order. It varies.
Where income is being paid into a joint account, test it with a small payment before relying on it.
Telling payers in advance
A line in your payment details: the account name is exactly this, please enter it as shown.
Payers who are warned are not surprised by a mismatch warning and do not stop a payment unnecessarily.
Where your invoice carries a trading name, say explicitly that the account name differs and give both. The two appearing together removes the ambiguity entirely.
When your name changes
A marriage, a deed poll, a company renaming. Update the bank first, then every payer, and expect a period where some payments carry the old name.
Keeping both names acceptable at the bank for a period is sometimes possible and is worth asking about.
What the check cannot distinguish
A legitimate difference from a fraudulent one. The system compares strings, and a person using a shortened version of their own name looks exactly like somebody who has been given the wrong details.
That is the point of the control and it is why it will not be relaxed for your convenience. The only available response is to make the string you give out identical to the string your bank holds, which costs nothing and is almost never done deliberately.
It is also a control that is spreading rather than retreating, so an arrangement that has never had a problem may acquire one when a country changes its rules.