GnuCash
Contact   Instructions
Bug 796498 - Incorrect Starting Balance in TFX Report Calculations
Summary: Incorrect Starting Balance in TFX Report Calculations
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: TXF Export (show other bugs)
Version: 2.6.x
Hardware: Other Mac OS
: Normal normal
Target Milestone: future
Assignee: import
QA Contact: import
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-05 08:13 EDT by Clint Redwood
Modified: 2020-06-01 15:26 EDT (History)
4 users (show)

See Also:


Attachments

Description Clint Redwood 2018-06-05 08:13:11 EDT
When calculating the transactions on an asset account, it appears to take the opening balance as at the opening of Report-Start-Date minus 1 day, and then process all the transactions during the reporting period, thus giving the final balance on the closing date. 

However, if there are any transactions on RSD-1, these are ignored, so the opening balance is prior to these transactions (which is what I think is wrong) and then the correct transactions are processed, and you are left with the ending balance being out by the value of the RSD-1 transactions.

So if you have transactions in an account:

Date		Desc			Value	Balance
31/08/2016	Pay Someone		1000	9000
01/09/2016	Pay Someone Else	500	8500
31/08/2017	Pay Another Person	300	8200

and run the report for 01/09/2016 to 31/08/2017, the result is:

opening balance (31/08/2016) 10000
Pay Someone Else 500
Pay Another Person 300
closing balance (31/08/2017) 9200

whereas it should open at 9000 and close at 8200.

I'm using "Start of Accounting Period" and "End of accounting Period" as my selection dates, but it does exactly the same if I specify the dates directly.

(Interestingly, this didn't appear to be happening in v2.4)
Comment 1 Alex Aycinena 2019-01-18 23:27:46 EST
Thank you for taking the time to report the bug. I have been able to reproduce the problem and it has been fixed in commit 08704127.

Note You need to log in before you can comment on or make changes to this bug.