Due Date is Before Invoice Date on Cash Only Direct Invoices

Please check that your Cash Only is not set to Prepayment type in Setup tab, Payment Terms. It should be set to cash.

/Joe

Uhhhh....  I think I may have figured out what's happening, although I haven't a clue why it's happening or how to fix it.  It looks like for payment type "cash" it's taking the due date from the invoice date of the previous invoice.  Here's a couple of examples of what I mean:

Invoice # 109 has an invoice date of 2012/04/15, terms of "first day of next month", and a due date of 2014/05/01 (correct!).

Invoice # 110 has an invoice date of 2012/04/17, terms of "cash", and a due date of 2014/04/15 (wrong!).

Invoice # 111 has an invoice date of 2012/04/28, terms of "cash", and a due date of 2014/04/17 (wrong again!)

I haven't done that many direct invoices, but I've checked them all and it's consistent that whenever the payment terms is set to "Cash Only" (which has a payment type set to "Cash" in the setup) FA always sets the due date to the invoice date of the previous invoice not the invoice date of the current invoice.

Hope that helps you track down the solution  Thanks again for your help!

Chris

These are invoices with an invoice date before today's date, but that shouldn't matter, should it?  For any invoice where the payment terms are "Cash" the invoice and due dates should be the same.

I'm using version 2.3.13 db version 2.3rc (according to version.php).  I checked the database and it is posting the wrong date to fl_debtor_trans so the problem is in the posting routine somewhere.

Thanks, again, for your help!

Regards,

Chris

Is the server date/timezone affecting the issue?

Want to try it out in the later Mercurial build ?

Hi, apmuthu!

I have decided that I wouldn't mind trying the Mercurial build, but can you explain to me how to do it so that the Mercurial build accesses the same database so I don't have to set-up everything from scratch?  I tried uploading the files (to a separate directory, of course!) and then copying the config.php and config_db.php files  from the 2.3.13 directory to the new mercurial directory, but when I tried accessing the site that bombed big time.

Thanks!

Regards,

Chris

Apache and MySQL are both on the same server, so I'm assuming that the time zone variable for both are identical, but even if they aren't the difference would be a matter of hours, not days.

My problem is that FA is consistently grabbing the invoice date for the previous invoice, not the current one, when posting invoices that have a payment term of "cash."  If I'm entering an invoice with an invoice date of 2013/01/13 and the previous invoice has an invoice date of 2012/07/01 then the due date for my new invoice will be set to 2012/07/01 when I post it if the payment terms is set to "cash."  So, again, I doubt than error has anything to do with how Apache and SQL time zones are setup.

As for the Mercurial Build, I suppose I could do a db backup of the production server, install Mercurial, and then restore the data into Mercurial.  That would save me from having to re-enter the data again.

Thanks for the help and suggestion!

Regards,

Chris