On Wednesday, August 28, 2024 at 9:06:04 AM UTC+2 DK wrote:
I recently switch to beancount, and I'm trying to set it up for both my
personal finances, and for my business.
Consider the following transaction:
```
2024-08-01 txn "Some Service" ""
invoice: "xxx"
Assets:Wise:EUR -9.32 EUR @@ 10 USD
Expenses:MyComp:Operating:Software 10 USD
Expenses:Misc:USD
```
I purchased some service from a US company for 10 USD, but my Wise bank
account was charged with 9.32 EUR (The Expenses:Misc:USD is there because
apparently this transaction, as is, does not balance and is missing
0.00000000000001 USD, or close to that, but that's a different issue).
I think Martin considers this to be a bug, but you can work around it by
putting 10.00 instead of 10
2024-08-01 txn "Some Service" ""
invoice: "xxx"
Assets:Wise:EUR -9.32 EUR @@ 10.00 USD
Expenses:MyComp:Operating:Software 10.00 USD
check:
https://colab.research.google.com/drive/1laDSOEdxMC2b9yo3zX8e-gxyomM5Zuqm?usp=sharing
```
Ideally, if I run the report now, I should get the same value, but I
don't! Instead, I get 10 USD as the value for the position, but the
converted cost of the position is now *8.46 EUR*, and even though it has a
price of 0.93 EUR attached to it.
This is because the beanquery *convert *function is not using the implicit
convertion rate of the transaction (10 USD @@ 9.32 EUR), but the price,
derived from the latest price directive, which you have staying elsewhere.
It kind of makes sense, because when converting from one currency to
another you want to use an official rate, not the one used by a
specific merchant for a specific purchase.
you can use the implicit_prices
<https://github.com/beancount/beancount/blob/master/beancount/plugins/implicit_prices.py>plugin
though.
"""This plugin synthesizes Price directives for all Postings with a price or
directive or if it is an augmenting posting, has a cost directive.
"""
Even with the implicit_prices
<https://github.com/beancount/beancount/blob/master/beancount/plugins/implicit_prices.py>plugin
however,
you still can get a situation, that on a specific date you may have
different prices, but the convert function will use only one of it per day.
To hunt such problems, there is a unique_prices.py
<https://github.com/beancount/beancount/blob/master/beancount/plugins/unique_prices.py>
plugin
In addition all of them are combined in the pedantic.py
<https://github.com/beancount/beancount/blob/master/beancount/plugins/pedantic.py>
plugin
I tried to play with all kinds of parameters in the query, like with date
or without date, etc, but I still get 8.46 EUR for that transaction as
converted amount, hence the converted balance is also incorrect.
I don't mind recording the transaction as in the first example, but what
I'm worried about is that the reports might turn out to be incorrect. I
randomly caught this transaction, but who knows how many there are/will be.
Am I misunderstanding something?
--
You received this message because you are subscribed to the Google Groups
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/af47b125-642b-42c2-99fe-7005f83fbdfan%40googlegroups.com.
