We fielded a question from a client about their having a problem with Simply 2012.
When they did a cheque run they put in a Period End Date of 12/08/2011.
When they did the cheque run the actual printed cheques had a Period End Date: 12/13/2011!
We verified that the custom Crystal Reports forms had the correct fields in them which they did.
After a few tests we came to realize that Simply 2012 was dropping in the date chosen when the Simply company file was first opened. Most folks open with today’s date so that’s the date that would show up on the cheques.
We called into Simply support and sure enough they knew about the problem. They also knew about two ways to work around the problem until an update fixes it:
- When opening the company file set the date to Period End Date for a payroll cheque run only.
- Once done the payroll run log off and back on again with the correct day’s date.
The Simply technician indicated that an update is forthcoming to address this problem.
In the mean time our client has run through hundreds of pre-printed cheques with the wrong period end date at a _huge_ cost to them. What do they do? In this case they could let folks know that there was a glitch . . . maybe.
How is it that a software vendor will refuse to publish a bug about this kind of problem? It is not a simple little problem that has very little impact! What about those companies that are doing payroll cheque runs into the thousands?!?
This bug can have a big impact on a company that uses the Sage Simply 2012 accounting product.
We challenged the Simply tech support person on Sage’s not publishing the problem anywhere on their site and they indicated that our suggestion to publish high impact bugs on their Support Site would be brought up at a meeting of some sort.
This situation is very disappointing and really undermines our trust level with Sage. We already take Intuit’s QuickBooks with a first version grain of salt. Now it looks like we will be lumping Simply Accounting into that camp as well. :(
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book