Wachovia Tells Man He Owes $211,010,028,257,303.00
Joe Martins of Georgia got a surprise letter from Wachovia telling him he owed $211,010,028,257,303.00 on his account with them. That's two-hundred and eleven trillion, ten billion, twenty-eight million, two-hundred and fifty-seven thousand, three-hundred and three dollars, and zero cents. The letter also said Wachovia was reporting him as a risky bank customer. When contacted by a local news station, the bank apologized and blamed it on a "word processing error."
This is a test using rich text formatting and html links. It's the generic "company" ad that should appear on all posts with the Company category if they don't have an ad attached to a specific company.
Post a comment
Comments:
@KivaWolf: In a poorly designed application it would easy to type the wrong stuff into the wrong field. Clearly this is a poorly designed application if it lets someone enter this large a number into the dollar field.
Of course Wachovia only needs ONE person to pay this kind of bill, and the subprime mess is OVER. ;)
But seriously...Quote from the article: "Since it is a closed account it is now safe to say the dollar figure in the letter matched the account number." what it doesn't say is whether he actually owed them some money (I wonder if it says it's for account number -5 or anything).
@Leiterfluid: HA! I felt so smart thinking I was the only one who noticed that.
@KivaWolf: It's amazing how quickly people want to fire people for silly, meaningless mistakes.
@swalve: I want you fired for your comment! OMG how could you not want a person who makes a stupid mistake to get fired? Okay, but seriously though, rather than fire the person who typed that up, Wachovia should HIRE a second person to read the letter to check that it makes common sense and legal sense.
@P41: Think other banks will follow suit? Doing this just might make America's economy really competitive again.
I will bet it was not the bank that screwed up but the guy that attached the database to the job he was printing.
Form letters like this are generated by attaching a database to a form. The form would read something like "Dear [first] you owe us [balance] that is due by [date]". [first], [balance] and [date] are all variables. If you enter the database for any reason it is real easy to change a field by accident. This time it just happened to be the [balance] field.
In any case, you know the poor guy had a most amusing WTF? expression when he opened the letter. Now that would have been a Kodak moment.
"That's two-hundred and eleven trillion, ten billion, twenty-eight million, two-hundred and fifty-seven thousand, three-hundred and three dollars, and zero cents."
I think you mean "That's two-hundred eleven trillion, ten billion, twenty-eight million, two-hundred fifty-seven thousand, three-hundred three dollars, AND zero cents."
When speaking writing out numbers, the word "and" represents a decimal point.
this is a but similar to this story:[news.yahoo.com], but instead of the person having to owe an insane amount, he was given a check for nearly 2 million by accident
What's this talk about firing the data entry shmuck (probably under stress from quotas or whatever) over this screwup? NO, fire the programmer, who didn't put in a test to confirm anything over, say, a million. (And if they can't put that kind of logic in, fire the 1980's era IT manager.)
On a similar vein, a while back I remember reading someone complaining that their two day guaranteed airmail was late when "sent to the wrong place". I'm told that the people at UPS who scan the tracking codes as they load your packages in the truck have to VISUALLY spot if it's going to the wrong state. It would be quite easy for the computer to check the barcode's intended destination, and buzz disapproval if that's not where the package is supposed to be going. So why are computers always programmed to not allow refunds, or require some meaningless thing, and huge obvious screwups sail right by?
This is sad. It sounds like the guy ran straight to the news before he tried to resolve it with the bank, who would have obviously seen it as a mistake...
Ive said it before, but the Consumerist is better than running these typo-stories as if they were stories of companies legitimatly trying to screw a consumer.
I can understand a data monkey putting the account in the wrong field, but there are still two thing I can't understand:
1) What kind of crazy programmer makes the "dollars owed" field/variable so damn big. Isn't that like a long unsigned int or something? (it's been a while).
2) What kind of bank needs a system capable of having more than 10 trillion account numbers? Do they expect everyone who has every lived (and everyone that will ever live) to open an account at their bank? This sort of thing bugs me alot, because if the state of Florida had a system that did not allow more than 12 billion people to get FL driver's licenses before overflowing the system, I would not have had to without my wallet and check my ID every time I filled out a financial aid form! If the SSA can get by with 9 digits, why does florida need 1 Letter + 10 digits?!?
@thirdgen: It really depends on the specific datatype. Any sane application will use at least double-precision (64-bit) values for currency although there special currency types are still available and preferred in many cases. The max value of a 64-bit double depends on the language but in C++ it's 1 followed by 37 zeros (i.e. big enough)
Please don't fault them for allowing such large values. In software you design for expandability and the unknown. I regularly beat my head against the wall working around these types of "we never thought we'd need that many" design decision. What we can fault them for, however, is not verifying the data before being entered into a letter mailed to the customer. At the very least the process that generates the letter should have a maximum value that sets off an alert or something.
@catnapped: But think of how good his score will be when they reverse the charge and it shows he paid off a two hundred eleven trillion dollar loan. :)























How many "word processing errors" actually occur? If they screw up this badly, how many other times have they screwed up? Did this guy actually owe anything at all? If he didn't, then this is more than just a "word processing error."