GnuCash
Contact   Instructions
Bug 797852 - Error in Accounts Payable Aging re cut off dates
Summary: Error in Accounts Payable Aging re cut off dates
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Reports (show other bugs)
Version: 4.0
Hardware: PC Windows
: Normal major
Target Milestone: ---
Assignee: reports
QA Contact: reports
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-08 11:39 EDT by Alex Straun
Modified: 2020-09-27 12:45 EDT (History)
4 users (show)

See Also:

Attachments
Accounts Payable Aging as at31 October 2019 and inconsistent individual vendor reports (355.67 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-07-08 11:39 EDT, Alex Straun 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alex Straun 2020-07-08 11:39:06 EDT 
Created attachment 373785 [details]
Accounts Payable Aging as at31 October 2019 and inconsistent individual vendor reports

Balances and details are not reflective of the individual vendor reports for the cut off dates specified.  AP Aging shows zero when there were actual bills outstanding as at the cut off date.  Please see attached.
Comment 1 Christopher Lam 2020-07-09 09:27:02 EDT 
Did you change your Vendor Report dates to end on 31 October 2019?
Comment 2 Christopher Lam 2020-07-11 01:19:33 EDT 
This issue could be fixed by ensuring the aging report -> owner report also copies the report-date.

Unfortunately ownerreportCB in business-urls.c must be refactored to accept another field in the owner url, and is beyond my capabilities.
Comment 3 Christopher Lam 2020-08-18 19:29:10 EDT 
this bug fixed in maint, may be tested using build after 15-august on https://code.gnucash.org/builds/win32/maint/
Comment 4 Christopher Lam 2020-09-26 09:24:33 EDT 
Would be nice if this bug was confirm fixed. I'll mark as fixed myself.
Comment 5 Alex Straun 2020-09-27 12:45:21 EDT 
Sorry - just catching up.  Was competing.  Will also run additional test and advise.
Note You need to log in before you can comment on or make changes to this bug.