Appropriate method to work Inventories

[Toby]

Hi,
I am trying to use Beancount to track inventories and I am a little 
confused on how to do this correctly. I understand that there is costs and 
pricing and that @@ is used to denote price (which can change) and {{}} 
which the cost and can't change. 

Let me explain here :-

2021-01-01 * "Purchase Some Supplies"
Assets:Inventory:Banana10 PCS  {{30 USD}}
Assets:Inventory:Apple   2 PCS {{50 USD}}
Assets:inventory:Orange3 PCS  {{20 USD}}
Assets:Cash 100.00 USD
  
Or :-

2021-01-01 * "Purchase Some Supplies"
Assets:Inventory:Banana10 PCS  @@ 30 USD
Assets:Inventory:Apple   2 PCS   @@ 50 USD
Assets:inventory:Orange3 PCS@@ 20 USD
Assets:Cash 100.00 USD
 

I often get weird output when working with commodities (they are always 
getting revalued) and the numbers don't add up. I have tried multiple 
things such as :-

2021-01-01 * "Purchase Some Supplies"
Assets:Inventory:Banana30 USD  {{10 PCS}}
Assets:Inventory:Apple   50 USD {{2 PCS}}
Assets:inventory:Orange20 USD  {{3 PCS }}
Assets:Cash 100.00 USD


The above seems to fix the valuation problem (commodities don't get 
revalued) but its a little complicated. Is there any guides on how to work 
with commodities?

Thanks

-- 
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/74e08658-2420-4627-9871-4ce691975511n%40googlegroups.com.

Re: newbie question around getting going on smart_importer

[Bman Q]

just put correct "2nd legs" of transaction for smart_importer to learn from

basically
2020-02-14 * "CHECK 213"
  Assets:Personal:Checking   -2100.00 USD

becomes
2020-02-14 * "CHECK 213 "
  Assets:Personal:Checking   -2100.00 USD
  Expenses:Personal:CostOfLiving:Rent
On Saturday, August 7, 2021 at 8:55:52 AM UTC-4 rus...@gmail.com wrote:

> How do you manually label data to be used by the smart_importer?
>
> On Wednesday, 28 April 2021 at 08:55:24 UTC+1 pat...@ch.tario.org wrote:
>
>> Hi Jonathan,
>>
>> Yes the way you describe makes a lot of sense. That way it limits the 
>> amount of config you have to manually train.
>>
>>
>> Regards,
>>
>> Patrick
>>
>>
>> On 28.04.2021 08:27, jrgo...@gmail.com wrote:
>>
>> Hi, 
>>
>> I've finally gotten (a) account structure I want for now (b) importers 
>> working for my 3 core accounts. I now want to get smart_importer working 
>> and want to understand the best strategy to bring this into the process.
>>
>> My understanding from the smart_importer data is that I can covert all my 
>> importers to be "smart importers" using the hooks that smart_importer 
>> provides as noted in the readme file. I think that is straightforward. I 
>> can use this on any importer type bank, cc, etc.
>>
>> *So my core question *then, is it best to only manually label 1-2 months 
>> of data and then use that labelled data to train the smart_importer and 
>> then run the smart_importer version on the rest of my data? For example, I 
>> have 1.5 years of OFX data from my bank in one OFX file. I can run the 
>> current non-smart importer on the entire file but then I have to manually 
>> label the entire thing. There isn't a totally different way to dynamically 
>> do this as I edit in emacs or use smart_importer in a different way? If I 
>> understand I should split into 1.3 years and 0.2 years for example. 
>> Manually label the 0.2 years and then take the remaining 1.3 years and run 
>> through the smart_importer version of the importer? Or is there some other 
>> way I should go about this?
>>
>> Also want to say, I really appreciate the beancount tool, so many amazing 
>> contributions (e.g. Reds importers), and the new smart_importer tool  and 
>> everyone helping answer questions.
>>
>> thanks,
>> Jonathan
>>
>> -- 
>> 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 beancount+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beancount/f21fac7a-5119-4ada-a1ae-01244768b2a6n%40googlegroups.com
>>  
>> 
>> .
>>
>>

-- 
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/51e4008d-2618-471d-834d-9d87b62303b1n%40googlegroups.com.

Re: Calculating Portfolio Returns

[Bman Q]

thank you, it worked.

On Sunday, September 12, 2021 at 8:46:06 PM UTC-4 wbe...@gmail.com wrote:

> You need to define commodities for everything you're using beangrow for, 
> in your case I imagine this is RDFN and SQ. You don't need to define the 
> metadata in your bullet item 3.
>
> On Sun, Sep 12, 2021, 8:40 PM Bman Q  wrote:
>
>> Guys hi
>>
>> First of all i want to thank Martin for superb work! I have been using 
>> beancount for 2 years and flexibility / functionality beancount provides 
>> are simply amazing. I always recommend beancount on plain text accounting 
>> sub and now have 1 extra reason to suggest it :)
>>
>> Secondly i have several questions / issues with installation and will 
>> appreciate your help:
>> 1. should i use "v2 master + beangrow repo" OR "beancount 2.3.3" ?
>>
>> 2. when i run configure.py, it generates empty file, what can be the 
>> reason for this?
>> i run:
>> "python scripts/configure.py -v b.beancount > conf-returns"
>> screen output:
>> INFO: Reading ledger: b.beancount
>> INFO: Inferring configuration.
>> INFO: Done.
>> but file is empty
>>
>> My accounts structure seems fine:
>> Assets:Business:...
>> Assets:Cash
>> Assets:Investing:CSchwab:Cash  USD
>> Income:Investing:CSchwab:Interest USD
>> Income:Investing:CSchwab:GainsUSD
>> Income:Investing:CSchwab:MiscCredits USD
>> Expenses:Investing:CSchwab:Fees  USD
>> Assets:Investing:CSchwab:RDFN RDFN
>> Assets:Investing:CSchwab:SQ  SQ
>> ...
>> Assets:Personal:... 
>>
>> (i never received dividends so don't have accounts for them yet)
>>
>> 3. Do i understand it right that the only change we need to do in main 
>> beancount file is add signature handlers?
>> Basically 
>> 2019-09-03 * "Buy; REDFIN CORP 00500"
>>   Assets:Investing:CSchwab:RDFN 326 RDFN {15.55 USD, 
>> 2019-09-03}
>>   Expenses:Investing:CSchwab:Fees  4.95 USD
>>   Assets:Investing:CSchwab:Cash-5074.25 USD
>>
>> will become
>> 2019-09-03 * "Buy; REDFIN CORP 00500"
>>   Assets:Investing:CSchwab:RDFN 326 RDFN {15.55 USD, 
>> 2019-09-03}
>>  flow: ASSET 
>>   Expenses:Investing:CSchwab:Fees  4.95 USD
>>  flow: EXPENSES 
>>   Assets:Investing:CSchwab:Cash-5074.25 USD
>>   flow: CASH
>>
>> 4. I tried creating simple config file myself
>> investments {
>>   # Accounts at Schwab.   
>>   investment {
>> currency: "RDFN"
>> asset_account: "Assets:Investing:CSchwab:RDFN"
>> cash_accounts: "Assets:Investing:CSchwab:Cash"
>>   }
>>   investment {
>> currency: "SQ"
>> asset_account: "Assets:Investing:CSchwab:SQ"
>> cash_accounts: "Assets:Investing:CSchwab:Cash"
>>   }
>> }
>>
>> groups {
>>   group {
>> name: "stocks"
>> investment: "Assets:Investing:CSchwab:RDFN"
>> investment: "Assets:Investing:CSchwab:SQ"
>>   }
>>   group {
>> name: "all"
>> investment: "Assets:Investing:*"
>> currency: "USD"
>>   }
>> }
>>
>> but it resulted in error:
>> (using beancount master and beangrow repo)
>> python beangrow/compute_returns.py b.beancount conf-returns out
>> R:\b\b-office>python beangrow/compute_returns.py b.beancount conf-returns 
>> out
>> Traceback (most recent call last):
>>   File "beangrow/compute_returns.py", line 105, in 
>> main()
>>   File "beangrow/compute_returns.py", line 80, in main
>> account_data_map = investments.extract(
>>   File "R:\b\b-office\beangrow\investments.py", line 553, in extract
>> account_data = [process_account_entries(pruned_entries, 
>> config.investments, aconfig,
>>   File "R:\b\b-office\beangrow\investments.py", line 553, in 
>> account_data = [process_account_entries(pruned_entries, 
>> config.investments, aconfig,
>>   File "R:\b\b-office\beangrow\investments.py", line 399, in 
>> process_account_entries
>> comm = commodity_map[currency] if currency else None
>> KeyError: 'RDFN'
>>
>> (using beancount 2.3.2)
>> R:\b\b-office>python returns/compute_returns.py b.beancount conf-returns 
>> out
>> Traceback (most recent call last):
>>   File "returns/compute_returns.py", line 97, in 
>> main()
>>   File "returns/compute_returns.py", line 73, in main
>> config = configlib.read_config(args.config, args.filter_reports, 
>> accounts)
>>   File "R:\b\b-office\returns\config.py", line 44, in read_config
>> text_format.Merge(infile.read(), config)
>>   File 
>> "C:\Users\Btycoon\AppData\Local\Programs\Python\Python38\lib\site-packages\google\protobuf\text_format.py",
>>  
>> line 696, in Merge
>> return MergeLines(
>>   File 
>> "C:\Users\Btycoon\AppData\Local\Programs\Python\Python38\lib\site-packages\google\protobuf\text_format.py",
>>  
>> line 770, in MergeLines
>> return parser.MergeLines(lines, message)
>>   File 
>> "C:\

Re: Calculating Portfolio Returns

[Bman Q]

thank you for your reply,

i understand that beangrow is experimental, and i really appreciate what it 
can do even in this form, hopefully we (i see some users on github) will 
contribute to work too. Your work is really helpful to lots of people, one 
more time thank you.

I managed to make bean grow work, i needed to add "commodity" declarations. 
(surprisingly beancount / fava worked without them just fine) Plus couple 
windows related bugs for which i opened issues on beangrow's github 
providing temp fixes.

I have couple of additional questions on bean grow set-up:
1. configure.py seems to ignore closed accounts, is it how it supposed to 
work? 
(usually for strictness i was closing accounts after i exited/sold 
position, example: "2020-10-06 close Assets:Investing:CSchwab:RDFN")

2. "Including Uninvested Cash"
Do i understand it right that the easiest way to account for uninvested 
cash is to create 
-commodity "IDDLEUSD"
-account Assets:Investing:IDDLEUSD
buy IDDLEUSD for all cash (USD) that i can invest at rate 1:1, 
and then at each interval i do reports "price IDDLEUSD 1 USD",
and when i want to buy smng sell IDDLEUSD for USD, and buy what i want.
?

OR is there a way to make my investment cash accounts 
"Assets:Investing:CSchwab:Cash", etc to be counted as investment (with 0 
return) ?

3. Is there recommended time frame for "price" quotes?
Usually i open positions for 3-5 years, so not interested in daily or even 
monthly fluctuations.
Do i understand it right that if i use
-"plugin "beancount.plugins.implicit_prices"" (to get price from buy/sell 
transactions)
-price my investments on 1st of each Quarter
-run compute_returns.py with -e DATE = 1st of each Quarter (basically same 
cut off as date of last price quote)
then i will be fine and won't need any more price quotes
?


On Sunday, September 12, 2021 at 9:59:55 PM UTC-4 bl...@furius.ca wrote:

> On Sun, Sep 12, 2021 at 8:40 PM Bman Q  wrote:
>
>> Guys hi
>>
>> First of all i want to thank Martin for superb work! I have been using 
>> beancount for 2 years and flexibility / functionality beancount provides 
>> are simply amazing. I always recommend beancount on plain text accounting 
>> sub and now have 1 extra reason to suggest it :)
>>
>
> Thanks!
>  
>
>>
>> Secondly i have several questions / issues with installation and will 
>> appreciate your help:
>> 1. should i use "v2 master + beangrow repo" OR "beancount 2.3.3" ?
>>
>
> v2 if you like stability
> beangrow should work with it
> master if you want the bleeding edge, but frankly right now it's ~ the 
> same. New code is being written in there but it's not being run through the 
> main pass (there are two parsers in there, the new one is still undergoing 
> development).
>
>  
>
>> 2. when i run configure.py, it generates empty file, what can be the 
>> reason for this?
>>
> [...]
>
> beangrow has been written a good long time ago and it did work great at 
> the time.
> I haven't run it in about a year myself, since I've switch a much more 
> active trading style, so there may have been drift and breakage.
> (FWIW I've been developing a completely different trade reporting system 
> to accommodate active trading (https://github.com/beancount/johnny) but 
> it's much more complicated and doesn't integrate well into beancount yet.)
>
> Unlike beancount, beangrow is a bit more experimental and much less mature 
> than beancount, you'll have to insert debugging code and figure out why 
> somehow the inferred configuration isn't working.  It's not something I 
> have ongoing tests for, and I have more than 10 active projects + a full 
> time job, not enough cycles to keep all of those in tip-top shape.
>
>  
>
>> 3. Do i understand it right that the only change we need to do in main 
>> beancount file is add signature handlers?
>>
>
> No you shouldn't have to do that.
> You should be able to create an input configuration that works on your 
> regular Beancount file.
>
>
> 4. I tried creating simple config file myself
>> investments {
>>   # Accounts at Schwab.   
>>   investment {
>> currency: "RDFN"
>> asset_account: "Assets:Investing:CSchwab:RDFN"
>> cash_accounts: "Assets:Investing:CSchwab:Cash"
>>   }
>>   investment {
>> currency: "SQ"
>> asset_account: "Assets:Investing:CSchwab:SQ"
>> cash_accounts: "Assets:Investing:CSchwab:Cash"
>>   }
>> }
>>
>> groups {
>>   group {
>> name: "stocks"
>> investment: "Assets:Investing:CSchwab:RDFN"
>> investment: "Assets:Investing:CSchwab:SQ"
>>   }
>>   group {
>> name: "all"
>> investment: "Assets:Investing:*"
>> currency: "USD"
>>   }
>> }
>>
>> but it resulted in error:
>> (using beancount master and beangrow repo)
>> python beangrow/compute_returns.py b.beancount conf-returns out
>> R:\b\b-office>python beangrow/compute_returns.py b.beancount conf-returns 
>> out
>> Traceback (most recent call last):
>>   File "beangrow/compute_returns.py", line 105, in 

Re: Calculating Portfolio Returns

[Martin Blais]

On Mon, Sep 13, 2021 at 8:12 PM Bman Q  wrote:

> thank you for your reply,
>
> i understand that beangrow is experimental, and i really appreciate what
> it can do even in this form, hopefully we (i see some users on github) will
> contribute to work too. Your work is really helpful to lots of people, one
> more time thank you.
>
> I managed to make bean grow work, i needed to add "commodity"
> declarations. (surprisingly beancount / fava worked without them just fine)
> Plus couple windows related bugs for which i opened issues on beangrow's
> github providing temp fixes.
>

Ah I see. I may have assumed you use the "check_commodity" plugin, which
ensures all commodities have a corresponding declarations.
(This will be default in v3.)


>
> I have couple of additional questions on bean grow set-up:
> 1. configure.py seems to ignore closed accounts, is it how it supposed to
> work?
> (usually for strictness i was closing accounts after i exited/sold
> position, example: "2020-10-06 close Assets:Investing:CSchwab:RDFN")
>

I don't remember, but I'm pretty sure I calculated returns on closed
accounts.


>
> 2. "Including Uninvested Cash"
> Do i understand it right that the easiest way to account for uninvested
> cash is to create
> -commodity "IDDLEUSD"
> -account Assets:Investing:IDDLEUSD
> buy IDDLEUSD for all cash (USD) that i can invest at rate 1:1,
> and then at each interval i do reports "price IDDLEUSD 1 USD",
> and when i want to buy smng sell IDDLEUSD for USD, and buy what i want.
> ?
>
> OR is there a way to make my investment cash accounts
> "Assets:Investing:CSchwab:Cash", etc to be counted as investment (with 0
> return) ?
>

I don't remember, honestly, but this is a really important aspect.
Uninvested cash has to count. I doubt I ignored it.



>
> 3. Is there recommended time frame for "price" quotes?
> Usually i open positions for 3-5 years, so not interested in daily or even
> monthly fluctuations.
> Do i understand it right that if i use
> -"plugin "beancount.plugins.implicit_prices"" (to get price from buy/sell
> transactions)
> -price my investments on 1st of each Quarter
> -run compute_returns.py with -e DATE = 1st of each Quarter (basically same
> cut off as date of last price quote)
> then i will be fine and won't need any more price quotes
> ?
>

Yes, that's good enough.
IIRC I was using a weekly or monthly interval.
Just depends how smooth you want the curve to be.


On Sunday, September 12, 2021 at 9:59:55 PM UTC-4 bl...@furius.ca wrote:
>
>> On Sun, Sep 12, 2021 at 8:40 PM Bman Q  wrote:
>>
>>> Guys hi
>>>
>>> First of all i want to thank Martin for superb work! I have been using
>>> beancount for 2 years and flexibility / functionality beancount provides
>>> are simply amazing. I always recommend beancount on plain text accounting
>>> sub and now have 1 extra reason to suggest it :)
>>>
>>
>> Thanks!
>>
>>
>>>
>>> Secondly i have several questions / issues with installation and will
>>> appreciate your help:
>>> 1. should i use "v2 master + beangrow repo" OR "beancount 2.3.3" ?
>>>
>>
>> v2 if you like stability
>> beangrow should work with it
>> master if you want the bleeding edge, but frankly right now it's ~ the
>> same. New code is being written in there but it's not being run through the
>> main pass (there are two parsers in there, the new one is still undergoing
>> development).
>>
>>
>>
>>> 2. when i run configure.py, it generates empty file, what can be the
>>> reason for this?
>>>
>> [...]
>>
>> beangrow has been written a good long time ago and it did work great at
>> the time.
>> I haven't run it in about a year myself, since I've switch a much more
>> active trading style, so there may have been drift and breakage.
>> (FWIW I've been developing a completely different trade reporting system
>> to accommodate active trading (https://github.com/beancount/johnny) but
>> it's much more complicated and doesn't integrate well into beancount yet.)
>>
>> Unlike beancount, beangrow is a bit more experimental and much less
>> mature than beancount, you'll have to insert debugging code and figure out
>> why somehow the inferred configuration isn't working.  It's not something I
>> have ongoing tests for, and I have more than 10 active projects + a full
>> time job, not enough cycles to keep all of those in tip-top shape.
>>
>>
>>
>>> 3. Do i understand it right that the only change we need to do in main
>>> beancount file is add signature handlers?
>>>
>>
>> No you shouldn't have to do that.
>> You should be able to create an input configuration that works on your
>> regular Beancount file.
>>
>>
>> 4. I tried creating simple config file myself
>>> investments {
>>>   # Accounts at Schwab.
>>>   investment {
>>> currency: "RDFN"
>>> asset_account: "Assets:Investing:CSchwab:RDFN"
>>> cash_accounts: "Assets:Investing:CSchwab:Cash"
>>>   }
>>>   investment {
>>> currency: "SQ"
>>> asset_account: "Assets:Investing:CSchwab:SQ"
>>> cash_accounts: "Assets:Invest

Re: Calculating Portfolio Returns

[redst...@gmail.com]

On Monday, September 13, 2021 at 5:12:30 PM UTC-7 Bman Q wrote:

> I have couple of additional questions on bean grow set-up:
> 1. configure.py seems to ignore closed accounts, is it how it supposed to 
> work? 
> (usually for strictness i was closing accounts after i exited/sold 
> position, example: "2020-10-06 close Assets:Investing:CSchwab:RDFN")
>

Hmm, it shouldn't: see this line and comment 
and
 
its code:

"""Return a list of account names from the balance sheet which either aren't 
closed or are closed now but were still open at the given start date. """

If you're seeing a problem case, would you mind opening a bug in the repo 
with a demo example? 


2. "Including Uninvested Cash"
> Do i understand it right that the easiest way to account for uninvested 
> cash is to create 
> -commodity "IDDLEUSD"
> -account Assets:Investing:IDDLEUSD
> buy IDDLEUSD for all cash (USD) that i can invest at rate 1:1, 
> and then at each interval i do reports "price IDDLEUSD 1 USD",
> and when i want to buy smng sell IDDLEUSD for USD, and buy what i want.
> ?
>
> OR is there a way to make my investment cash accounts 
> "Assets:Investing:CSchwab:Cash", etc to be counted as investment (with 0 
> return) ?
>

The latter is exactly what I do for now: simply include 
"Assets:Investing:CSchwab:Cash" as a commodity, and it'll show up with very 
low returns.

However, for me, this means that cash in other parts of the hierarchy 
(example: banks, paypal, etc.) are not counted. AFAIK, beangrow does not 
offer a global solution for this. See "Including Uninvested Cash" in Martin's 
doc 

.

Not really an analysis solution, but as a strategy, I personally use 
fava_investor  to monitor 
uninvested cash.
 

3. Is there recommended time frame for "price" quotes?
> Usually i open positions for 3-5 years, so not interested in daily or even 
> monthly fluctuations.
> Do i understand it right that if i use
> -"plugin "beancount.plugins.implicit_prices"" (to get price from buy/sell 
> transactions)
> -price my investments on 1st of each Quarter
> -run compute_returns.py with -e DATE = 1st of each Quarter (basically same 
> cut off as date of last price quote)
> then i will be fine and won't need any more price quotes
> ?
>

After including the implicit_prices plugin, and running beangrow once, you 
will want to run: 
beangrow/beangrow/download_prices_from_file.py 
/prices/prices.beancount 

and include the resulting price database in your source, and re-reun 
beangrow. Without that, beangrow uses the price values on the closest dates 
it can find, which in your case could be weeks or months off, which means 
your returns numbers will be off.

The file generated above provides the only dates on which the prices matter 
to beangrow for your configuration. These are the start and end dates of 
your cashflow. Meaning, period opening and closing dates, and dates on 
which you bought/sold, IIRC. More detail here 
.

Enjoy!
 

-- 
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/80364a2f-5e9a-4038-bb0d-f21a553e5dc4n%40googlegroups.com.

Re: Appropriate method to work Inventories

[redst...@gmail.com]

Yes, there's extensive documentation:

https://beancount.github.io/docs/how_inventories_work.html
https://beancount.github.io/docs/trading_with_beancount.html

I suggest reading and understanding those, and avoiding the @@ and {{ 
notations, at least at the beginning. Use @ and {} instead.

If you have specific problems, send us an output of your query, what you 
expect, and what you get.

Hope that helps!

On Monday, September 13, 2021 at 2:37:53 AM UTC-7 Toby wrote:

> Hi,
> I am trying to use Beancount to track inventories and I am a little 
> confused on how to do this correctly. I understand that there is costs and 
> pricing and that @@ is used to denote price (which can change) and {{}} 
> which the cost and can't change. 
>
> Let me explain here :-
>
> 2021-01-01 * "Purchase Some Supplies"
> Assets:Inventory:Banana10 PCS  {{30 USD}}
> Assets:Inventory:Apple   2 PCS {{50 USD}}
> Assets:inventory:Orange3 PCS  {{20 USD}}
> Assets:Cash 100.00 USD
>   
> Or :-
>
> 2021-01-01 * "Purchase Some Supplies"
> Assets:Inventory:Banana10 PCS  @@ 30 USD
> Assets:Inventory:Apple   2 PCS   @@ 50 USD
> Assets:inventory:Orange3 PCS@@ 20 USD
> Assets:Cash 100.00 USD
>  
>
> I often get weird output when working with commodities (they are always 
> getting revalued) and the numbers don't add up. I have tried multiple 
> things such as :-
>
> 2021-01-01 * "Purchase Some Supplies"
> Assets:Inventory:Banana30 USD  {{10 PCS}}
> Assets:Inventory:Apple   50 USD {{2 PCS}}
> Assets:inventory:Orange20 USD  {{3 PCS }}
> Assets:Cash 100.00 USD
>
>
> The above seems to fix the valuation problem (commodities don't get 
> revalued) but its a little complicated. Is there any guides on how to work 
> with commodities?
>
> Thanks
>

-- 
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/264352ff-9a6b-4511-a685-d0ba7cacd6b7n%40googlegroups.com.