GNOME Bugzilla – Bug 735907
Aging report is inconsistent in considering lots
Last modified: 2018-06-29 23:33:21 UTC
Quoting Mike Alexander from bug 734921: The Receivable Aging report is a bit undecided about how to handle lots linking payments and invoices. For the purpose of calculating the amount each customer owes it ignores lots entirely and just sums all invoices and payments whether they are linked or not. However if you tell it to ignore zero balance customers then it uses lots to determine who has a zero balance. If a payment isn't linked to an invoice it is ignored for this purpose. Since all the customers showed a zero balance and I hadn't told it to ignore zero balance customers, I didn't realize that the payments weren't linked to the invoices. I'm not sure if the report should be changed, or if so how, but it seems wrong that it mostly, but not entirely, ignores lots.
Interesting that having acted on bug 734921 my aging reports, that were previously wrong, are now showing the correct information.
This looks like a problem I have only recently noticed with Receivable Aging reports. I was gettijg the problem using version 2.6.3 and have just upgraded to 2.6.14 on Windows 10 and am getting the same problem occuring after the upgrade. I am in UK using sterling and my accounts are not complicated. If I make a report to show receivable aging for any date range, I only get a full list if I have the show zero balance box ticked. If I don't tick it, it only gives me a few of the entries. I cannoy believe I have forgotten to link as many invoices to payments as are missing from the report. If my end date for the report is the year end, then only when the zero balance box is ticked does the total sum in the report agree with what shows in a Trial Balance Report for that year. A visual look at my 'Account Receivable' account looks OK with Invoices and payments and linked payments all appearing to be there but I am no expert and wonder if there is a way to check that they do all tie up.
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=735907. Please continue processing the bug there and please update any external references or bookmarks.