Now if there is an exchange rate entry for 12-19 and 12-16 but not for 12-18 or 12-17-2017 and the report is using nearest in time, that could cause what you are seeing.
On Sat, Feb 9, 2019 at 7:04 AM D via gnucash-devel < gnucash-devel@gnucash.org> wrote: > That sounds to me like it's using a different exchange rate from one day > to another, and I'd agree with your assessment in that case. I would have > thought that the exchange rate in the transaction would be used. > > Mind you, I can't wrap my head around the subtleties that seem to apply on > this report. > > David > > On February 9, 2019, at 5:56 PM, Wm via gnucash-devel < > gnucash-devel@gnucash.org> wrote: > > On 09/02/2019 07:00, Wm via gnucash-devel wrote: > > Background: My gnc TB has been wrong for years. This hasn't been a > > problem for me because I can do my own TB in sql and satisfy myself all > > is relatively well with my accounts. Over the last week or so I decided > > to try again and I think the gnc TB report is b0rked. > > OK, have a think about this. > > Having deleted the tx previously mentioned. > > If I run a TB report to 2017-12-17 it balances. > > If I run a TB report to 2017-12-18 it is out by .01 > > Problem? There are no tx on 2017-12-18 > > The ordinary use of a TB is to help find accounting errors. If the > report introduces errors I say it is not fit to be used. > > https://bugs.gnucash.org/show_bug.cgi?id=797097 > > -- > Wm > > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
