IBAN–Name Mismatch: Bank Liability, İzmir Appeal Court 2026

A customer who wants to send a private pension or life insurance premium writes the insurance company as the recipient name, but the IBAN supplied actually belongs to an individual. When the money reaches the receiving bank, the system notices that the name and the account number do not match and drops the transfer into the branch pool. What happens next, meaning on whose instruction and after which checks the money in the pool is released, becomes the real question that decides the bank's liability. The case examined by the 11th Civil Chamber of the İzmir Regional Court of Appeal discusses the answer together with the bank's defence that "IBAN validation is only a format check".
By its decision dated 12.06.2026, Docket No. E.2026/249, Decision No. K.2026/1031, the 11th Civil Chamber of the İzmir Regional Court of Appeal dismissed on the merits the bank's appeal against a first-instance judgment. That judgment held the bank liable for the loss after it moved TRY 360,000.00, which had dropped into the branch pool because the recipient name and IBAN did not match, to an individual's account on the strength of a forged instruction received by fax, with a signature that did not match the one on record, and without a confirmation call.
💸 Where Did the Money Go?
According to the statement of claim, the claimant sent TRY 360,000.00 from a deposit account at their own bank to an account at the defendant bank, reported to be in the name of the "Hayat ve Emeklilik" company. When the expected policy did not arrive, the claimant looked into what had happened to the EFT and learned that the IBAN belonged to the spouse of one of the defendant bank's branch employees. The claimant argued that the bank should have checked the IBAN against the recipient name and obtained confirmation by telephone, that it had failed in its objective duty of care, and asked for the amount to be recovered with statutory interest from the transaction date.
The bank's own account of events also clarifies how things unfolded. Under the bank's procedure, when an EFT arrives by IBAN for an individual's account, the amount is credited automatically up to a certain limit if the first three characters of the beneficiary's name and surname match; if they do not match, the transfer falls into the branch pool regardless of the amount. In the EFT at issue the beneficiary name and IBAN did not match, so the transfer fell into the pool. The account holder told the branch a day in advance that he would withdraw TRY 200,000.00, withdrew that amount in cash the next day and moved the balance to his account at another branch.
🧭 From the Consumer Court to the Commercial Court
Before any result on the merits, the case went through a dispute over which court had jurisdiction:
- By its decision of 03/12/2019, the İzmir 3rd Consumer Court upheld the claim, stating that the bank had made the payment without a matching confirmation despite the mismatch between the recipient and the IBAN.
- By its decision of 20/01/2023, No. 2020/703 E., 2023/89 K., the 11th Civil Chamber of the İzmir Regional Court of Appeal set that judgment aside under Article 353/1-a-3 of the Code of Civil Procedure (HMK), stating that the dispute arose from a banking transaction treated as a commercial case and that a commercial court of first instance should hear it.
- By its decision of 05/11/2025, No. 2023/701 E., 2025/949 K., the İzmir 6th Commercial Court of First Instance found that the money in the pool had been transferred on a fax instruction with a forged signature, without a signature check or confirmation, and ordered TRY 360,000.00 to be paid with statutory interest from 29/09/2016.
Only the defendant bank appealed this last judgment. For a different aspect of the jurisdiction question in cases against banks, see the article on jurisdiction in a case against a bankTR.
⚖️ The Bank's Line of Defence
Both in its response to the claim and at the appeal stage, the bank relied on the following arguments:
- The validation duty in the TCMB's Communiqué No. 2008/6 on the International Bank Account Number covers only whether the IBAN conforms to the format; it does not include checking that the name and IBAN match.
- The Banks Association of Türkiye's 2009 letter on IBAN practice likewise did not interpret validation as confirmation that an IBAN belongs to a particular person.
- The claimant had obtained the IBAN from the insurance agent and had previously had private pension policies issued through this person in their own name and their daughter's. Since there was a relationship of trust between the parties, the error was the claimant's.
- Because the earlier insurance relationship was known, the amount in the pool was transferred to the account holder; the expert reports did not take this relationship into account.
- The bank was without fault; even if the opposite were accepted, a reduction for contributory negligence should be applied.
🏦 The Chamber's Assessment
The Chamber characterised the dispute as a claim for compensation for loss suffered through a breach of the duty of care during banking transactions. The starting point of its reasoning was the merchant's duty to act as a prudent businessperson under Article 18/2 of the Turkish Commercial Code (formerly Article 20/2 of Code No. 6762). According to the Chamber, the standard of prudence expected of banks is higher than that of any other merchant; banks are institutions of trust that must keep the funds entrusted to them safe and pay the person entitled, and they are therefore liable even for slight fault.
Applying this to the case, the Chamber made the following findings: although "Hayat ve Emeklilik" had been written as the recipient name, the IBAN entered belonged to an individual's account, so the transfer dropped into the pool. To release the money in the pool, a duly confirmed written instruction that had passed a signature check should have been obtained from the sender. Instead, the bank relied on a forged instruction that arrived by fax from a stationery shop and did not match the claimant's signature on record in the system, and it moved the money to the individual's account without even a confirmation call. The Chamber characterised this conduct as a gross service fault and dismissed the appeal on the merits under Article 353/1-b-1 of the Code of Civil Procedure. The decision was unanimous, and the route of appeal to the Court of Cassation was left open.
🧾 The Difference Between a Format Check and a Name Check
The most instructive sentence of the decision is this: the format validation duty in the TCMB's Communiqué No. 2008/6 does not remove the banks' general duty of care to check that the name and IBAN match and not to act on a forged instruction. This approach separates the minimum technical obligation found in the legislation from the duty of care that arises from the contract and from the bank's status as a merchant.
An interesting aspect of the case is that the bank's own system had already caught the mismatch. Because the name did not match, the transfer was not credited automatically and dropped into the pool. The debate therefore focused not on whether the bank noticed the mismatch, but on how it behaved after noticing it. In the Chamber's view, the pool is a security stage; releasing the money without testing the authenticity of the instruction needed to pass that stage rendered the protection offered by the system ineffective.
In this respect the decision also reflects an expectation that the bank compares the signature on record with the signature on the instruction and confirms an unusual instruction with the customer. For the Court of Cassation's approach to a bank's liability for payments based on a forged signature, the article on a forged-signature transfer instructionTR can be read together with this one, and for another aspect of the receiving bank's duty of care, the article on a transfer to a closed accountTR.
🔐 Why the Wrong IBAN Entry Was Not Treated as Fault
The bank's alternative defence was that the compensation should be reduced because the claimant had entered the wrong IBAN. The Chamber did not accept this request either. According to the reasoning, the claimant's entering of wrong IBAN details cannot be treated as contributory negligence in the face of the bank's service fault of paying on a forged fax instruction without a signature check or a confirmation call.
Two points appear decisive in this assessment:
- The chain of causation: The wrong IBAN did not cause the money to pass automatically to the individual's account; on the contrary, it stopped the transfer. The last link that caused the loss was the release of the money in the pool on a forged instruction.
- The gravity of the fault: The Chamber saw the bank's conduct not as ordinary negligence but as a gross service fault. A fault of this degree on the part of an institution under an aggravated duty of care pushed the sender's error of information into the background.
The bank's defence based on the earlier relationship between the claimant and the insurance agent was likewise not seen as affecting the outcome. The fact that the parties had done business in the past did not justify carrying out a forged instruction issued in the sender's name without verifying it.
📌 What This Means in Practice
The decision clearly shows the position of the bank in disputes where payments for insurance and private pension products are directed through intermediaries. What was discussed was the liability not of the sending bank but of the bank that received the money in its account; how the receiving bank handled a mismatch caught by its own security mechanism was decisive.
In the first-instance judgment, interest was set as statutory interest from the transaction date, 29/09/2016; because the bank did not raise a separate appeal objection on this point, the Chamber's reasoning does not discuss interest separately. The period of the dispute, running from 2016 to 2026, also shows how far the setting-aside decision on jurisdiction can prolong proceedings.
❓ Frequently Asked Questions
Are banks required to check the recipient name in an EFT?
What does "branch pool" mean?
Did it change the outcome that the claimant got the IBAN from the agent?
Why was the case first heard in a consumer court and then moved?
For detailed information and legal support, you can contact Savun Law & Consultancy. Contact details are on the contact page, and the other decisions in the series are in the Precedent DecisionsTR archive.
This article is for general information only; the summary is compiled from the decision of the 11th Civil Chamber of the İzmir Regional Court of Appeal published in the Bedesten system. The assessment is based on a specific case in which the recipient name and IBAN did not match, the transfer fell into the branch pool and was released on a forged fax instruction; the outcome may differ in cases where the form of the instruction, the checks carried out by the bank and the relationship between the parties are different. Regional court of appeal decisions do not have the status of Court of Cassation case law, and an appeal to the Court of Cassation is open against this decision. Savun Law & Consultancy cannot be held responsible for any application, lawsuit or defence made on the basis of this article.

Questions & answers · Istanbul Bar Association 75235
Have a question about this topic? Ask our lawyer.
Write your question and Attorney Veli Savun will answer it on this page. You do not need to give your name.
Example questions — tap one and adapt it to your situation:
Answers are general information only; they do not create a lawyer–client relationship and are not legal advice on your specific case. All questions & answers →
This page is an English adaptation of our Turkish article IBAN–İsim Uyumsuzluğunda Banka – İzmir BAM 11. HD 2026/1031.
More from Investment Fraud & Crypto Law in Türkiye
- Bank Liable for Employee's High-Return Promise: Court of Cassation
- Stock Tips Site Fundraising: Court of Cassation 2024/3604
- Crypto Gains and Legality in Tax: Council of State 2024/7487
- Fake Investment Ads: Platform Liability, Germany and Türkiye
- Bank Liability for Forex Pool Account: Court of Cassation Ruling
- Lawsuit Against a Dissolved Company: Istanbul Appeal Court 2025/513