Computer Glitch Leaves Some Australians Without Cash
An anonymous reader writes "National Australia Bank payments to customers were again delayed today after a computer glitch yesterday morning due to a corrupted file in its mainframe computer. Upset consumers are now demanding compensation for any fees for late mortgage and credit card payments, overdrawn accounts or bounced direct debits charged by any institutions as a result of the mess."
Still the safest place until you house burns down
For justice, we must go to Don Corleone
Maybe some other big banks could copy this computer glitch and wipe out the billions of pounds /dollars /yen / euros / gold pieces that everyone owes each other, we could get back to some kind of normality.
It looks like consumers aren't demanding it so much as the bank is promising it, which is no surprise. Even if Australia doesn't have laws protecting consumers in that sort of event, the bank will do it anyhow because they have to.
As a practical matter all it'll likely take is phone calls/letters to creditors explaining that it was a glitch and no fault of the person involved. As a somewhat related example a friend of mine got hit because of a glitch years ago. The power company double debited his payment. That happened right about when a number of other transactions came which caused some of them to bounce, including his rent check. All the fees from the bank overdrew his account, he had other fees from the people he owed money to, and his landlord notified him he'd be evicted if he didn't pay. Well, the power company made things right and gave him back his money. They also called the relevant parties saying "Sorry, it was our fuckup." Every single one canceled all the fees. Since it wasn't his fault, they didn't fine him. Had they not, the power company said to send them the bills for the fees and they'd reimburse him.
So while this is doubtless a stressful time for those involved, in the end I have to imagine it'll all get worked out. Goes double since this is a major fuckup, and going to be well known.
"National Australia Bank payments to customers were again delayed today after a computer glitch yesterday morning due to a corrupted file in its mainframe computer. Upset consumers are now demanding compensation for any fees for late mortgage and credit card payments,
If you have a payment due on X date, you wait until day X - 1, and something goes wrong and delays you by one day, this is your fault, not your bank's fault.
Matters would be different if there was a problem at day X - 7 that lasted for 7 days, or X - 14 that lasted for 14 days.
It is not reasonable to expect there will never be any problems with electronic payment systems. 1 to 2 days is reasonable to sort this out, you are taking an unreasonable risk if you don't attempt to complete payment to a bill at least 3 days before the due date.
In other words, these consumers should get stuck with these late fees, and learn about a valuable lesson in taking reasonable steps to ensure their obligations are met, even if something goes not quite as expected with the payment.
If you take everything down to the wire to maximize interest, fine, but you are gambling the gains in interest vs the potential loss in terms of fees. If you are ok with that, fine, but then don't cry when you do get hit with fees and lose out. Personally I think the other way is smarter. I keep an amount of money in my non-interest bearing checking account since that is where all my transactions draw from. That way if there is a miscalculation there's no overdraw, no bounced payments, no fees. Likewise I pay things before the drop dead date.
Do I miss out on some interest? Sure, if I messed with funds all the time and tried to keep everything in savings till the last second I'd get a bit more interest. However it wouldn't take much in the way of a fee to negate any of that.
So I think there's some real validity to the GP's statement. Don't take things down to the wire, build in time to make sure if there's a glitch, there's no problem.
When westpac fucked up like this, they just replayed the batch the next day and it was sorted.
The fact that this wasn't fixed on day one means they're trying to put the data back together from scratch. (ie: they are so fucked)
Not Meta-modding due to apathy.
Unisys has been slogging their large scale x86 machines running Windows Datacenter Edition as mainframes for almost a decade.
Few people take that claim seriously, any more than they would believe a claim that a 32 CPU Sun or HP server was a "mainframe". Such machines are just mid range servers with a larger than usual number of CPUs.
The basic difference is that mid-range servers (system software and hardware) are more "commodity-ish" (and much less expensive) than true mainframes where companies spend on the order of ten times as much just to gain additional advantages in reliability, availability, and serviceability. If you don't spend at least $1M on a computer it probably isn't a mainframe.
Even if you do, by convention Unix is a mini-computer operating system, and Windows Server even lower down the scale, and systems running those operating systems aren't generally considered mainframes no matter how much extra RAS effort is put into them.