Hi Devs
I wish to enquire about policy on pricedb.
As far as I can understand, pricedb receives entries from 3 different
sources:
1. from entering transactions into the register, if the transaction
involves a foreign currency conversion or stock. e.g. originating account
is GBP, target currency
Christopher,
I’ll add a complication for you.
Suppose one enters a transaction and later realizes the price source was not
correct.
Does editing the originally generated user:price affect the transactions in the
register? Are they in-sync or now unrelated?
If editing user:price does not chang
I'm sorry there's no complication.
There's no such thing as "price source was not correct" while entering a
transaction.
Let's say I transfer 100 GBP to 150 USD, currently generating a pricedb
entry of GBP/USD=1.5, later "realize" the price source was incorrect and
should have been GBP/USD=1
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
> On May 13, 2018, at 3:34 AM, Christopher Lam
> wrote:
>
> Hi Devs
>
> I wish to enquire about policy on pricedb.
>
> As far as I can understand, pricedb receives entries from 3 different
> sources:
>
> 1. from entering transactions into the register, if the transaction
> involves a foreig
On the contrary, there is such a thing.
Certainly, in near real-time, as you describe, no there isn’t.
But when booking an existing asset at current market prices when starting a
book, there is. There might be various reasons for this approach, not the least
of which is that the original actual
I didn’t think of that one. Pondering that accounting nightmare makes me glad I
wasn’t concerned with accounting last time I was out of country and shopping in
just such a fashion. Most of the time even receipts weren’t available. I
probably paid a different exchange rate at each vendor. (It’s h
There are two use cases that will be more common. One is the general
end-of-period valuation that is usually driven by publicly reported prices.
The other would be a book value which could be a cost basis. That might
be driven by transactions or average costs.
There needs to be a way for user
Just get local currency at a bank or from a bank’s (preferably indoor)
ATM--don’t forget to check it for a skimmer, even if it is in the bank’s lobby.
Make a “cash in wallet” account in the local currency. That will get you better
rates and only a few exchange transactions.
Regards,
John Ralls
The ONLY way to change the value in a transaction is to change it in the
transaction itself—either by changing the number of shares, the actual price
per share, or the total amount in the transaction (and note that the UI will
ask you about this if you change one without changing the others). Th
Finally got the bisect done and it's
https://gitlab.gnome.org/GNOME/glib/commit/53bd6a359f2c48e7729f89902097c892c8aa6fea,
W32: Add a stat() implementation for private use. Next is figuring out if the
implementation has a problem or if GtkFileChooser should be using the new
functions.
Regards,
Thank you.
Hence my RFC about whether "user:price" entries in pricedb should be
considered as a lookup-table to the actual prices achieved in transactions,
and should be subject to Check&Repair fixing. I'm sure the reports will
then fix themselves if they can rely on pricedb being accurate.
IMHO
The hierarchy is user:price/user:xfer-dialog<-F::Q<-user:price-editor for the
reason I explained.
One more time: No, the user:price entries in the pricedb should ***NOT*** be
considered a lookup table to the actual prices in transactions. If you want the
actual prices in transactions (actually
13 matches
Mail list logo
