Member log in

Banking glitch stops salary payments

Payments NZ, which manages overnight payments between banks through its Swift network, says a computer glitch hit its system at 2am this morning.

The problem - caused by a single faulty jumper cable - affected all New Zealand banks, and meant payments - including thousands of wages and salaries - did not go through.

Payments NZ CEO Steve Nichols said that the fault was fixed, but it would take time to sort out all payments.

“Experts from all banks have been working throughout the night to clear the backlog of payments. Some payments have been processed already and we expect that everything will be back to normal soon.”

Most payments had been put through by around 1.30pm.

Although tens of thousands were affected, a recent move from single overnight payments to banks exchanging payments five times a day limited the scope of the problem.

Comments and questions
6

wasn't another accidental test of the internet "off" switch was it?

Something new here. The NZ bulk payments interchange and bank settlement system never used to use SWIFT. Seems banks have not tested these newly introduced SWIFT interfaces or maybe the SWIFT network had an overload (originally designed for Forex payments). Maybe NZ should not have its payment system dependant on an offshore host/supplier.

all part of global integration.

5 times a day i got nothing still

a salient example of the downfall awaiting NZ due to this national party government's quest to centralise/cheapen 'back office functions' to a single supplier 9who, usually will find NZ's business such a small % that often little notice will be taken). This is part of John key's idiot & dishonest economic strategy for NZ to fatten the pockets of middlemen who happen to be NP members. Hopefully, there will be some journalists/newspapers who will begin to expose this soon.

As much as I dislike John Key, this has nothing to do with him. SWIFT is the most reliable financial messaging system on the planet and as someone who worked on the SBI project I must say I'm surprised and sceptical to hear that this was a SWIFT issue. I think you should be pointing your fingers at AT&T. Enough said