Queensland Health Payroll Debacle Hits Six Month Mark

Some 50 staff members will again not be paid this month

1 min read
Queensland Health Payroll Debacle Hits Six Month Mark

A few months ago, I wrote a long blog about the on-going problems of paying staff working for the Queensland Health service in the Australian State of Queensland. Well, the problems are still on-going, six months later.

The health service installed a late, over-budget and under-tested payroll system on the 24th of March of this year. Immediately, technical deficiencies surfaced, which resulted in many Queensland Health staff not getting paid; some getting paid incorrectly; some employees who had quit a year ago (or died) still getting paid; some getting paid but with blank payroll slips to tell them what was taken out of their pay; and some staff even quitting over the problem.

The problems caused a major political row to erupt, with promises that the payroll problems would be fixed in the "near future."

Well, the near future is now, and according to this story in the Courier Mail, Queensland Health admits that at least 50 of its staff won't be paid again this pay period, and that it still hasn't processed 11,500 pay corrections that are needed. Queensland Health administrators did try to put a positive spin on the news, however, saying that 11,500 pay corrections is way down from the 35,000 that once existed.

Tell that to the staff who haven't been paid - or paid correctly - for the past six months. I am sure they will rejoice at the progress being made.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less