Sage moves to patch 2010 accounts bug - update
Programmers at Sage HQ in Newcastle are working to fix a bug in Sage 50 Accounts 2010, which was went on sale last week.
Sage Accountants Division managing director Greg Ford alerted AccountingWEB.co.uk on Thursday that some test users had experienced problems when creating a new Recurring entry in the 2010 edition’s Bank module.
This issue only affects people who have upgraded to Sage 50 Accounts 2010, not users who are installing the program for the first time. Amending existing recurring entries works perfectly in the new system, but when a new recurring entry is added, it can over-write the first recurring item in a list. No historical transactions are lost and of course actual direct debits or standing orders, for example, are completely unaffected by this, Ford informed readers of our Sage 50 Accounts 2010 review.
According to Ford, the flaw was discovered by a beta test site after the assessment period had closed. By the time the bug was reported, around 6,000 copies of Sage 50 Accounts 2010 had gone out the door - a relatively small number in the overall Sage 50 universe. From its activation records, Sage estimates only around 300 customers had actually installed and activated the new version. Sage immediate set about contacting those affected and turned to AccountingWEB.co.uk to help notify potential users.
“If you or your clients have received the upgrade to 2010, we would recommend that you don’t upgrade, as per a communication we’re sending out today, until you’re advised the correction is available to be applied by our auto-updates mechanism,” Ford said.