FrontAccounting forum — Bug in customer aging

Re: Bug in customer aging

null@example.com (MarkAndrew) — Thu, 19 Feb 2015 18:39:01 +0000

Thanks Joe
Appreciated as always.
Reports that are generated with wrong info is serious as we make decisions based on reports from Front.
Glad it's fixed after 8 yrs!
Mark

Re: Bug in customer aging

null@example.com (joe) — Thu, 19 Feb 2015 16:42:53 +0000

Yes, there were a 1 day failure in the aging routines. These errors have been here for 8 years .

Well, not a serious bug perhaps, but as you say Mark, quite annoying.

The HG repo for 2.3.23 will be updated asap. If you can't wait you can download:

/reporting/rep.102.php1 and /reporting/rep202.php1. Rename the files to .php.

/sales/includes/db/customers_db.inc and /purchasing/includes/db/suppliers_db.inc.

And replace the files.

/Joe

Bug in customer aging

null@example.com (MarkAndrew) — Thu, 19 Feb 2015 12:40:02 +0000

I noticed the following:

When I process a customer payment with today's date it appears in the customer aged analysis in the 30 day column and not the current column.

Tried several times with same result.

Then I processed a customer payment with last month's date. Instead of showing in the 30 day column in the customer aged analysis it showed in the 60 day column.

Did same test with a payment to supplier with same results as above.

Conclusion: it looks like customer / supplier payments are shown on the customer/supplier aged analysis one aging column too old which means customer/supplier aged analysis report is not always reliable. A fix is needed.