stormy Posted January 1, 2012 Share Posted January 1, 2012 The particular combination of factors in my account has caused invoice numbering to be messed up with the year change. My sequential format is {YEAR}-{NUMBER} Yesterday's invoices which were due today and paid yesterday have the correct year in them, but the number, which was supposed to be reset this year, was reset as well. So I got invoices with numbers: 2011-1, etc. These are duplicate invoice numbers now. I will have to manually correct them and resend them. Today's invoices have the correct year, but the numbering was reset yesterday, so the first invoice of 2012 doesn't start with number 1. Time to manually correct and resend them. I'm posting here because I'm sure I'm not the only one bitten by this bug. If you use this, take a look at your invoices. 0 Quote Link to comment Share on other sites More sharing options...
mjwebhosting Posted January 2, 2012 Share Posted January 2, 2012 Hello Stormy, I have no problems. But when run your cronjobs? I have run the cronjob about 00:01 Greetz, Michaël Jonkers 0 Quote Link to comment Share on other sites More sharing options...
stormy Posted January 2, 2012 Author Share Posted January 2, 2012 My cron runs at midday, maybe it had something to do with it. 0 Quote Link to comment Share on other sites More sharing options...
com2 Posted January 26, 2012 Share Posted January 26, 2012 As far as I understood it, there is no automatic change of the number format, because how can you tell the machine there is a year in it? You have to change that manually after the last cron job of the year and before the first cronjob of the new year. Now the suggestion is given here that the sequential {number} part is reset yearly automatically. Is there a reference to this in the documentation? Or is there a setting for this? Where? If we want it to start from 1 again, then I always thought we need to set it manually too in Next Paid Invoice Number. Or am I wrong? 0 Quote Link to comment Share on other sites More sharing options...
stormy Posted January 26, 2012 Author Share Posted January 26, 2012 You can use {YEAR} as well. 0 Quote Link to comment Share on other sites More sharing options...
com2 Posted January 27, 2012 Share Posted January 27, 2012 Oh, nice! I will try that and see if it works next year 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.