On Monday, May 3, 2021 at 1:37:47 PM UTC+7 [email protected] wrote:

> Building on the example discussed, is it best to then have separate 
> accounts for each currency you operate it?  For example:
>
> Expenses:Restaurants:Canada CAN
> Expenses:Restaurants:US USD
>

In general, with beancount, the way you want to structure accounts depends 
on how you want to eventually query data from them. The bad part is that 
you often don't know that for months/years after using beancount. The good 
part is that restructuring your beancount file is (relatively) painless if 
you decide you want things another way.

Anyway, I just have Expenses:Restaurants. I have all my expenses in three 
currencies. I've never seen any need to have my US spending, my Australian 
spending, my Vietnamese spending ... oh and what about when I'm only 
holiday and spend money in Hong Kong Dollars, Singapore Dollars, Euros, and 
Thai Baht? Make separate sub-accounts for all of those?

What's your use case for separating them into per-currency sub-accounts? 
Why not just write a query of "select * where account ~ 
Expenses:Restaurants and currency = USD" if, for some reason, you only 
wanted the USD expenses?
 

> Then If you want to see total restaurant spending (say in USD) can you 
> just write the appropriate query in BQL at the node "Expenses:Restaurants"? 
> Will this automatically convert using the prices available or do you have 
> to manually do that conversion? 
>

You have to manually do the conversion. There is a convert BQL method. 

-- 
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/5248787b-b251-499e-ac68-d98404219a49n%40googlegroups.com.

Reply via email to