Welcome to the PlusCommunity forums! PlusCommunity is a gathering place for companies running Simply Accounting, ACCPAC Plus, Sage Accpac ERP(ACCPAC Advantage/ACCPAC for Windows), and Adagio Accounting. New visitors, please click here!
Hi, I have problems with the payment option in Simply Accounting. Since a few weeks ago, the cheque number keeps on popping back to 5565 even though that cheque number has already been used, and I'm now using cheque number 5647. Every time I go to the Payment option, I have to manually key in the next cheque number because it keeps on coming back to 5565. Is there a way to tell Simply Accounting to use the current (next) cheque number? Please advise, thanks.
Registered: 05/08/12
Posts: 1
Loc: British Columbia, Canada
When you manually change the cheque number and post a transaction, system ask you to use the next cheque number for the next payment, at that time you should select "YES". This will resolve your problem.
Problem is you tried to change cheque number manually thats why you are facing this issue. If you are still facing this issue then contact from your bank manager.
These steps might help you out: 1 Make sure you are logged in as Sysadmin and in Single User Mode 2 From the Home screen in Sage 50, click Setup, Reports & Forms 3 Click Cheques, then select the bank account for which you want to change the cheque number 4 Update the Next Cheque No field under Payment Cheque Settings and/or Payroll Cheque Settings NOTE: If you do that and there already is a cheque with that existing number, you may find some errors in future. 5 If you have selected the option to Use the same cheques for payment and payroll cheques, you need only update the Next Cheque No field at the bottom, under Cheque Settings. _____________________________________ Chris | fence company florida
You can also use Sage. That is how I troubleshoot the same exact issue I had the past few days. Also, make sure you are logged in as Sysadmin and in Single User Modes so everything would be smooth. Hope you resolve this issue already.
Hey! This has been happening to me lately. I tried fixing it alone by following all the troubleshooting steps but it led me to nowhere. I decided to get hold of tech support from sage and they did help me.
