I'll add a simple case that maybe does not happen often in real accounting but happens to me all the time.
When traveling and exchanging cash at various small shops, the exchange rate varies wildly. This, however, should not have the precedence compared to the official central bank's rate. Also, what happens when the currency is exchanged a few times per day? These are the negative side-effects of your proposal. It is, however a very valid question if the reports are using only one rate. In that case, I would prefer to be in control of the rate used. Another important item is that the Australian Tax Office, for example, publishes the official exchange rates for the tax year and I would really need to be able to use that rate for all my tax reports, irrespective of what the other entered prices may be. > Sent: Sunday, May 13, 2018 at 12:34 PM > From: "Christopher Lam" <christopher....@gmail.com> > To: gnucash-devel@gnucash.org > Subject: [GNC-dev] pricedb policy > > My concerns relate to (1) above. I believe these transactional prices are > always more accurate than online quotes, because they describe the exact > prices achieved. > > But it's buggy, e.g. if there are 2 transactions involving GBP/USD on the > same day, the second entered price will overwrite the first. (<- according > to my last test) > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
