Recommended Posts

It was a sickening, gut-wrenching moment when, one evening in October 2012, Sally Donaldson checked her bank account and realised she had made the silliest financial mistake of her life.

Two years earlier, hairdresser Sally had organised for her monthly pay, ?1,000, to be transferred from her HSBC account to the joint account at Nationwide building society she shares with her husband. But on that October night, the mother of two discovered she had made a simple but calamitous error.

It's a mistake anyone can make. To transfer money online from one account to another, you simply tap in the recipient's name, their sort code and account number. But Sally had incorrectly typed in just one of the eight digits in the account number ? and the money was sent to the wrong person. :|

What makes her story so extraordinary, though, is that she made the mistake in May 2010. Every month since ? for more than two years ? her pay was going into someone else's Nationwide account. And now, to her horror, Sally is discovering she has almost no chance of getting back a penny of the ?26,650 transferred in error.

The recipient took the money, spent it, and is refusing to repay it. Nationwide says there is nothing it can do ? and won't tell Sally who the recipient is because of data protection rules.

The fact she correctly entered her surname as the intended recipient at Nationwide, alongside the correct sort code, counted for nothing. When banks transfer money, they use only the sort code and account number ? it turns out that account names are irrelevant.

Legally, Sally has every right to demand the money back ? no one is entitled to keep money wrongly credited to their account. But getting it back is an altogether different matter.

Many people will sympathise with her over a silly mistake. But most will also wonder how she and her husband failed to notice a missing ?1,000 every month. Indeed, Nationwide says it has never before come across a case of "mis-applied credit" that went on for so long.

The answer may lie in the widespread switch to paperless statements, where an account can only be viewed online. Sally did not see a bank statement from Nationwide for the entire period the money was going astray. She kept an eye on the balance when she took money out at the ATM, but that was about all, while her husband, who also paid his income into the account, sorted out most of the bills.

"By law, a person is not entitled to rely on another's mistake to keep money to which they were not entitled," a Nationwide spokesman says. But he adds: "The final payment transferred was recovered, but previous payments were no longer in the account. The recipient has been contacted and we have established she doesn't have the funds to repay."

more

Link to comment
https://www.neowin.net/forum/topic/1135988-the-40000-typo/
Share on other sites

I check every number a dozen times whenever I make bank transfers. The name doesn't mean anything when making transfers, my (current) bank doesn't even provide that field anymore.

Also if I was doing payments like that I'd be checking after the first one (and from time to time after that) that it was indeed ending up where it was supposed to.

  • Like 1

I don't understand how it went unnoticed for so long. You'd think a normal person would check their monthly back statements at least once in that time period.

15d9nvc.png

  • Like 2

The recipient probably justified spending the money as it was the bank's error. However, this story puts a name and story to that windfall. In the end it's not the "cold-hearted bank" that was hurt, but someone innocent who made a mistake. Although we don't know the recipient's circumstances, they shouldn't have spent money that wasn't theirs.

I don't understand how it went unnoticed for so long. You'd think a normal person would check their monthly back statements at least once in that time period.

15d9nvc.png

It is unusual. The only thing I can think is that they were so focussed on saving that they just didn't want to check their account. I don't know, it's a sad story, especially when you read on and see that their joint income is less than ?50,000.

The banks should improve the way they handle online transactions. She was asked for a surname in addition to the account and sort code and it's reasonable to expect that the surname was used to validate the account details. If not, why did the bank ask for it? Also, why don't bank accounts incorporate a check digit to avoid this sort of thing?

The recipient probably justified spending the money as it was the bank's error. However, this story puts a name and story to that windfall. In the end it's not the "cold-hearted bank" that was hurt, but someone innocent who made a mistake. Although we don't know the recipient's circumstances, they shouldn't have spent money that wasn't theirs.

As the article states, the recipient wasn't legally entitled to spend the money. They're only getting away with it because the bank isn't prepared to recoup the money from them.

I'd save the money for the first couple months... then I'd probably be like, ok this is weird and report something.

But honestly if you screw this up this many times without checking your balances in your accounts and somehow not being notified you're months and then years in debt without payment..... idk, you deserve it, I guess I'm saying. You deserve to not get that money back. But maybe that's just me.

The receiver should still return the money, but in all honesty, I don't really feel bad for the woman if they don't.

The fact she correctly entered her surname as the intended recipient at Nationwide, alongside the correct sort code, counted for nothing. When banks transfer money, they use only the sort code and account number ? it turns out that account names are irrelevant.

Why even bother with our names and sort code if they aren't going to bother to use it?

This is one of those rare situations that a person should have the ability to sue the way we do in the USA. Refusing to pay it back should be illegal. There is no way the recipient didn't know that money didn't belong to them.

Really? You wouldnt realize if an extra 1000 was being transferred into your account every month? :huh: You'd have to be rich to not realize it, and the fact that this person doesnt have the money to pay it back cancels out the rich part. Just another example where people will try and get away with as much as they can. God forbid the person called their bank to see where the money came from... nope. Ill just spend it and plead ignorance when the times comes.

Really? You wouldnt realize if an extra 1000 was being transferred into your account every month? :huh: You'd have to be rich to not realize it, and the fact that this person doesnt have the money to pay it back cancels out the rich part. Just another example where people will try and get away with as much as they can. God forbid the person called their bank to see where the money came from... nope. Ill just spend it and plead ignorance when the times comes.

You might want to re-read what you quoted. I think you misunderstood...

This never could have happened in Belgium and shouldn't happen anymore in Europe either as long as you use IBAN numbers instead of national bank account numbers. In both our Belgian account numbers and IBAN's there is a pretty good check built-in. Replacing a single character will always invalidate the account number, switching the positions of two numbers will too. All other changes are also pretty unlikely to still be valid (unless you're really unlucky).

UK bank account numbers don't have checks built in?

This topic is now closed to further replies.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!