bean-report error messages

[jkepler]

Hello beancount users,

I'm running bean-check against my ledger and its giving me "No position 
matches" errors for entries purchasing a commodity. I don't understand what 
that error could mean on a purchase transaction - if I were reducing lots, 
it would make perfect sense, but when augmenting lots?

Does beancount have a command to anonymize input files to make it easier to 
share them for debugging?

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 post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/0243d101-d59a-4762-b95e-dfa407e9f7cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: can one reduce FIFO lots purchased in one currency and sold in another?

[jkepler]

Thanks for your thorough and helpful response. I think I'd seen Selinger's 
currency trading accounts post referenced before, but hadn't taken time to 
read and understand it. Wow. His method does resolve the problem 
"elegantly," as you say.

Unfortunately for me, I believe that the IRS requires using FIFO to 
calculate capital gains and losses with bitcoin. So as much as I would like 
to simply treat it like another currency and use Selinger's "trading 
account(s)" method, I don't think I'm free to do that.

So, I'm currently trying (A.) to wrap my mind around how to write a plugin 
as you suggested or (B.) to re-work my source data converting the EUR 
amounts to USD equivalents, thereby avoiding the problem of trying to 
reduce lots in a different currency from that which I used to purchase them.



Le samedi 19 août 2017 23:52:55 UTC+2, Martin Blais a écrit :
>
> On Sat, Aug 19, 2017 at 7:54 AM,  wrote:
>
>> One clarification: over lunch I was thinking about this, and realized 
>> that beancount does FIFO booking reductions correctly for securities like 
>> stocks under the usually valid assumption  a security is sold/ reduced in 
>> the same currency it was purchased in, since each security is denominated 
>> in the currency of its exchange.  
>>
>
> That is correct.
> The main issue is that there are two processes going on, and it's not 
> clear which one could come first:
> - Interpolation of missing values
> - Booking against existing inventories of lots
> Resolving this is hard - one can come up with useful cases where one would 
> be preferred to run before the other - and part of it involves inferring 
> the currency of a lot.
> Once the currencies are resolved, then the booking takes place.
> So the currency is fixed.
>
>  
>
>> This is reasonable: if one buys shares in Nokia (NOK) listed on the New 
>> York Stock Exchange, they're always listed in USD. Shares listed in EUR are 
>> available on the Helsinki Stock Exchange, but their symbol is NOKIA, hence 
>> a different security. 
>>
>> Where thinks currently seem not to work is if one is tracking a real 
>> commodity -- apples, bitcoin, or coffee -- anything that doesn't have an 
>> intrinsic currency for valuing it. 
>>
>
> What you call a "real commodity" here is generally a currency. Beancount 
> differs from Ledger in this regard, you can treat currency as they are.
>  
>
>>
>> Does that make sense, or have I misunderstood something? 
>>
>
> No, I think you get it.
>
> However, I think there may be a better resolution here.
> I think you may be able to treat Bitcoin as a currency, disregard its cost 
> basis, yet still be able to account for gain/loss for it.
> Let me explain.
>
> When a currency conversion is accepted by Beancount, no cost basis is 
> stored.
> However, if the exchange rate takes place, a gain or loss will be incurred.
> In other words, the sum of all postings will not be an empty inventory.
> In order to deal with this, Beancount inserts an ugly conversion 
> transaction which makes us for exactly this. 
> This transaction is inserted by this code:
> http://www.mscs.dal.ca/~selinger/accounting/tutorial.html
> Its purpose is to exactly counterbalance this difference, across all 
> currencies.
> One problem is that its contents must depend on the set of transactions 
> being summarized.
> That's why it's inserted when you open or close on the set of directives, 
> e.g.., before producing a report.
>
> Now, please take a few minutes to dive in and go read this:
> http://www.mscs.dal.ca/~selinger/accounting/tutorial.html
>
> This method resolves the problem elegantly.
> Each of the transactions posts the currency differences to a dedicated set 
> of currency accounts.
> Unfortunately, it would be a pain to enter your transactions in this way.
>
> However, it would be simple to do this automatically with Beancount, even 
> as a plugin.
> I plan to do this eventually.
> (You're welcome to get ahead about that, I'm working on other things these 
> days.)
>
> Now, how does this relate to your question?
> Well, with this "trading accounts" method, you could later (in time) 
> unwind some of these currency account at their current rate, and post the 
> difference as a gain/loss.
>
> I know I've said previously it would be easier to use the cost basis. 
> What you get from that is specific lot reduction methods, e.g. FIFO, LIFO.
> On the other hand, if you'd like not to have a particular cost currency, 
> really you are dealing with currencies.
> In this case, you won't have any booking, but you could still have total 
> gain/loss.
>
> (I hope this makes sense.)
>
>  
>
>>
>> Thanks for all you work on beancount. It's a great tool! 
>>
>
> Thanks, and please keep on finding problems, that's the way software gets 
> stronger.
>
>  
>
>>
>> Joel 
>>
>> Le samedi 19 août 2017 11:38:11 UTC+2, Joel a écrit :
>>>
>>> Thanks for your response.
>>>
>>>
> 2. If I explicitly put "USD" in all my empty {}, how does 

Re: can one reduce FIFO lots purchased in one currency and sold in another?

[jkepler]

Thanks for your response.


>> 2. If I explicitly put "USD" in all my empty {}, how does will FIFO 
>> booking option handle the occasional cases where I've purchased bitcoin 
>> with euros? 
>>
>
> I don't understand the question. If you try to reduce and provide USD in 
> the description, it will only match against lots in USD. Can you provide an 
> example pair of transactions?
>
>
>  
>
>> Will it always reduce the oldest bitcoin lots first, regardless of the 
>> currency I'm reducing with, or will explicitly specifying the reducing 
>> currency mean I have to manually check the order lots are cleared to make 
>> sure that the total of the two currencies reduces correctly per FIFO?
>>
>
> I'm still not sure I understand, it will never convert currencies when 
> reducing.
>
>
 Here's an example, from a fictitious episode in which I rode Amtrak back 
and forth a few times between New York City and Montreal to sell apples:

 
option "title" "My Personal Ledger"
option "operating_currency" "USD"
option "operating_currency" "CAD"
option "booking_method" "FIFO"

2016-01-01 open Equity:Opening-Balances
2016-01-01 open Assets:US:CashUSD
2016-01-01 open Assets:CA:CashCAD
2016-01-01 open Assets:MyBackpack:StuffAPPLES
2016-01-01 open Income:CapitalGains

2016-05-26  price  CAD   0.77046 USD
2016-05-28  price  CAD   0.76761 USD

2016-05-24 * "Opening Balances"
  Assets:US:Cash40.00 USD
  Assets:CA:Cash 0.00 CAD
  Equity:Opening-Balances

2016-05-25 * "Bought some apples in New York"
  Assets:MyBackpack:Stuff   10 APPLES {1.00 USD}
  Assets:US:Cash

2016-05-26 * "Convert USD to CAD"
  Assets:CA:Cash 
  Assets:US:Cash   -15.03 USD @ 1.29792 CAD

2016-05-26 * "Bought some more apples in Montreal"
  Assets:MyBackpack:Stuff   13 APPLES {1.50 CAD}
  Assets:CA:Cash

2016-05-27 * "Bought some apples in New York"
  Assets:MyBackpack:Stuff   11 APPLES {1.20 USD}
  Assets:US:Cash

2016-05-28 * "Sold some more apples in Montreal"
  Assets:MyBackpack:Stuff  -14 APPLES {USD} @ 1.70 CAD   ; should sell 10 
APPLES {1.00 USD} & 4 APPLES {1.50 CAD}, a cost basis of 14.605 USD
  Assets:CA:Cash23.80 CAD; converts to 
18.269 USD
  Income:CapitalGains; revenue (18.269 
USD) - cost basis (14.605 USD) = 3.665 USD

; CapitalGains = 3.47 USD per beancount when the {1.50 CAD} lot doesn't get 
reduced.

I don't think beancount is reducing my apples by FIFO correctly, because 
when I run the *bean-report *sample *holdings* when selling 14 apples, its 
reducing from my {1.00 USD, 2016-05-25} and {1.20 USD, 2016-05-27} lots, 
but not reducing any apples from my {1.50 CAD, 2016-05-26} lot. Since 
apples are apples, shouldn't it reduce the lots by date order?

If I replace the {USD} with an empty {} beancount tries to reduce all 14 
sold apples form the {1.50 CAD, 2016-05-26} lot, but fails because there's 
only 13 apples in that lot. The only was I can find to have beancount 
reduce my apple inventory selling the oldest lots first is manually, like 
this:
2016-05-28 * "Sold some more apples in Montreal"
  Assets:MyBackpack:Stuff  -10 APPLES {USD} @ 1.70 CAD
  Assets:MyBackpack:Stuff   -4 APPLES {CAD} @ 1.70 CAD
  Assets:CA:Cash23.80 CAD
  Income:CapitalGains

So, I'm not sure FIFO is reducing the oldest lots first. It depends on the 
lot currency.


-- 
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 post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/579301c3-c02b-4209-aacf-0b119b893951%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

can one reduce FIFO lots purchased in one currency and sold in another?

[jkepler]

Hello fellow beancount users,

I've got a bunch of bitcoin purchases in USD that I then sold for EUR, and 
beancount isn't matching the EUR sales with the USD purchases of bitcoin. 
Running *bean-check* against the transactions results in a "No position 
matches" and a list of the current non-reduced lots--all denominated in 
USD. I have daily EUR - USD and BTC - USD price histories per beancount's 
syntax in my ledger file. All my sales of bitcoin to USD reduced just 
fine... its just the sales to EUR that aren't working out.

Originally I had my reducing legs of the transactions with empty curly 
braces {} but then I tried the following:

option "title" "My Personal Ledger"
option "operating_currency" "USD"
option "booking_method" "FIFO"

2013-01-01 open Equity:Opening-Balances
2013-01-01 open Assets:Crypto:Bitcoin   BTC
2013-01-01 open Assets:Checking:CapitalOne  USD
2013-01-01 open Expenses:Crypto:Fees:Coinbase   USD
2013-01-01 open Assets:Checking:BNP EUR
2013-01-01 open Income:CapitalGains

2016-05-25  price  BTC449.24 USD
2016-05-25  price  EUR1.12 USD
2016-05-27  price  BTC474.38 USD
2016-05-27  price  EUR1.11 USD

2016-05-25 * "Coinbase" "Bitcoin purchase"
Expenses:Crypto:Fees:Coinbase4.60 USD
Assets:Crypto:Bitcoin1.0214 BTC {450.07 USD}
Assets:Checking:CapitalOne-464.30 USD

2016-05-27 * "(s9d8fukf0)" "Sell BTC via bitsquare"
Assets:Crypto:Bitcoin   -0.5000 BTC {USD} @ 416.75 EUR
Assets:Checking:BNP208.38 EUR
Income:CapitalGains

2016-05-27 * "(l2l3jfp5d)" "Sell BTC via bitsquare"
Assets:Crypto:Bitcoin   -0.5000 BTC {USD} @ 412.00 EUR
Assets:Checking:BNP206.00 EUR
Income:CapitalGains

That seems to work, except that that *bean-report* balances now shows me 
EUR and USD on separate capital gains lines:
Income:CapitalGains -414.38   EUR
Income:CapitalGains  450.07   USD

So, I've got two questions:

1. Since my file includes prices, is there a way I can have beancount know 
the USD equivalent for reducing lots in EUR that were purchased with USD?

2. If I explicitly put "USD" in all my empty {}, how does will FIFO booking 
option handle the occasional cases where I've purchased bitcoin with euros? 
Will it always reduce the oldest bitcoin lots first, regardless of the 
currency I'm reducing with, or will explicitly specifying the reducing 
currency mean I have to manually check the order lots are cleared to make 
sure that the total of the two currencies reduces correctly per FIFO?

I guess I'm looking to understand more specifically what the FIFO booking 
is doing or not doing when a commodity (BTC) is purchased in one currency 
(USD) and sold in another (EUR).


-- 
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 post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/77653225-48df-4b1d-8e36-939a4ae6b138%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: balanced ledger transaction(s) imported to beancount won't balance... help!

[jkepler]

Thanks for pointing me in the direction of the commands and document 
resources I can use to debug my file. I'll re-read your trading 
documentation, as well as the docs on beancount's many tools. I had no idea 
the book_conversions plugin is ancient.

Regarding my Bitcoin use, my primary use is to buy it with USD in the US 
(where I get paid) and sell it for EUR here in Europe (where I live and 
work). Its significantly cheaper and faster than using traditional 
international wires or a service like Transferwise. Plus by using bisq.io I 
don't have to trust a third-party company with my money, other than my 
banks---which I already have to trust. I also occasionally use it to buy 
stuff our family needs on Amazon at a discount using purse.io. However, due 
to a super-busy work and family period the past two years, I've neglected 
keeping my journal file current, and that's created a ton of work for me 
(and its forcing me to dig in to learn interesting things and revive my 
programming skills).

About those Ethereum transactions - last year I did some trading between 
Bitcoin and Ethereum, but then I stopped, due to the time-consuming nature 
of accounting for those transactions... I've more important things to spend 
my time on.

Thanks again for your response.





Le dimanche 13 août 2017 05:41:16 UTC+2, Martin Blais a écrit :
>
> Ouf... you're opening a number of cans of worms here.
>
>
> (1)
> The error you see happens because your 0.84429 reducing transaction has 
> nothing to match against. You didn't add anything at a cost basis to reduce 
> against. Check out the "bean-doctor context" command to help you debug 
> what's going on, and "bean-query print".
>
> But mainly, you should not be using the book_conversions plugin. This is 
> ancient and if I recall it was created to answer a question on the 
> mailing-list (search for it for context) before FIFO support was 
> implemented. Since then, Beancount has had proper support for FIFO, LIFO 
> booking.
>
>
> (2)
> Now, the other can of worms you're opening is that you're using Bitcoin. 
> Is Bitcoin to be used as a currency or as an investment? If it's to be used 
> as a currency, you need not care about its cost basis and such. But more 
> likely, if you're using Bitcoin like most of the other people - to 
> speculate - surely you want to handle it like an investment, that is, 
> tracking cost basis. Beancount can do this, though when you use your 
> Bitcoins to buy things, you'll have to book reductions like sales. It's not 
> difficult, but you'll have to use syntax that hints the expense is to be 
> reduces with a cost basis (e.g., {}). There's no great intermediate 
> solution here.
>
> So assuming you're happy doing that (that is, treating Bitcoins like 
> investments) you'll have to be cognizant of writing appropriate syntax 
> every time you add new bitcoins: supplying the cost basis when you add 
> Bitcoins to an account, and making sure to let Beancount know reductions of 
> Bitcoins from an account are to be carried out with the cost basis (using 
> as little as {} should be possible, since FIFO should kick in).
>
> I would suggest you should become intimately familiar with this doc: 
> http://furius.ca/beancount/doc/trading, and the FIFO and LIFO, etc. 
> booking method bits of the language syntax documentation, and start 
> treating all deposits and withdrawals of Bitcoins from accounts like you 
> would shares of a company.
>
>
> (3) 
> Thirdly, you're attempting to use both Bitcoin and Ethereum, both of which 
> surely you'll be wanting to track cost basis for. It's not impossible, but 
> you're making your life miserable if you're going to use this for any real 
> world expenses. The analogy is like if you were going to buy shares of 
> AAPL, and every time you go to the coffee shop you'll pay coffee with some 
> fractions of shares of AAPL and always have to choose which lot to choose 
> from every single time (yes, Beancount can figure out which lot to use, but 
> still, you have to indicate as such). I don't think there's any system that 
> is designed with that use case as the common case, neither Ledger, 
> Beancount or any other, though Beancount comes the closest to having the 
> features you need to do that.
>
> I think if you have the time you can probably come up with a clever system 
> of accounts where you set aside some amount of Bitcoins to a separate 
> account stripping away the cost basis and when you spend you always book 
> against this account. This would segregate all the cost basis tracking and 
> trading activities to another set of accounts. I think that would be a 
> practical and probably nicely workable compromise. I haven't tried (and 
> cannot afford to right now) but I think there's everything there to support 
> that use case already. 
>
>
>
>
>
> On Sat, Aug 12, 2017 at 5:02 PM,  wrote:
>
>> Hello,
>>
>> So, since I got the plugin for dealing with lots and capital gains 
>> 

balanced ledger transaction(s) imported to beancount won't balance... help!

[jkepler]

Hello,

So, since I got the plugin for dealing with lots and capital gains running, 
I'm attempting to import my balanced ledger journal files into beancount so 
I can have the plugin deal with reducing my lots rather than doing it 
manually. But I've a significant number of transactions that beancount says 
aren't balanced, in spite of their balancing in ledger. Here's one example 
(including my header incase I missed something there):

; -*- mode: org; mode: beancount; coding: utf-8; fill-column: 400; -*-

option "title" "My Personal Ledger"
option "operating_currency" "BTC"
option "operating_currency" "ETH"


  plugin "beancount.plugins.book_conversions" 
"Assets:Crypto:Ethereum,Income:Capital-gains"

* Equity
2015-01-01 open Equity:Opening-Balances

* Account declarations
2015-01-01 open Assets:Crypto:Bitcoin  BTC
2015-01-01 open Assets:Crypto:Ethereum ETH
2015-01-01 open Expenses:Crypto:NetworkFees   BTC

* Income
2015-01-01 open Income:Capital-gains

* Expenses
2015-01-01 open Expenses

* Transactions
2015-01-01 * ""Opening Bank balance""
Assets:Crypto:Bitcoin0.0500 BTC
Assets:Crypto:Ethereum   1. ETH
Equity:Opening-Balances

2016-08-13 * "Ethereum sale "
 Assets:Crypto:Ethereum  -0.84429 ETH {0.02055 BTC, 2016-08-09} @ 
0.01995 BTC
   trades: "trade-570f1d77bece"
 Income:Capital-gains
 Assets:Crypto:Bitcoin 0.01684358 BTC


bean-check complains about a half a satoshi (which can't exist in the real 
world, only in spreadsheets) not balancing:

/home/joel/beancount/temp2.bc:1333:Transaction does not balance: (-
0.55 BTC)

   2016-08-13 * "Ethereum sale "
 Assets:Crypto:Ethereum  -0.84429 ETH {0.02055 BTC, 2016-08-09} @ 
0.01995 BTC
   trades: "trade-570f1d77bece"
 Income:Capital-gains0.0005065740 BTC   
 
 Assets:Crypto:Bitcoin 0.01684358 BTC  

However, all the transaction in that file were balancing in ledger, before 
I converted them to beancount format. I checked this one by running it 
through ledger after commenting out the "trades" line

2016-08-13 * "Ethereum sale "
 Assets:Crypto:Ethereum  -0.84429 ETH {0.02055 BTC, 2016-08-09} @ 
0.01995 BTC
   ;trades: "trade-570f1d77bece"
 Income:Capital-gains
 Assets:Crypto:Bitcoin 0.01684358 BTC

and got the following result:

joel@bregalad:~/beancount$ ledger -f temp3.dat bal
  0.01684358 BTC
-0.84429 ETH  Assets:Crypto
  0.01684358 BTCBitcoin
-0.84429 ETHEthereum
  0.00050658 BTC  Income:Capital-gains

  0.01735016 BTC
-0.84429 ETH
joel@bregalad:~/beancount$ nano temp3.dat
joel@bregalad:~/beancount$ ledger -f temp3.dat bal
  0.01684358 BTC
-0.84429 ETH  Assets:Crypto
  0.01684358 BTCBitcoin
-0.84429 ETHEthereum
  0.00050658 BTC  Income:Capital-gains

  0.01735016 BTC
-0.84429 ETH

Any ideas what I'm missing in beancount? Or is there a way I can tell it to 
force anything less than a satoshi(0.0001 BTC) to balance?

And another issue I don't understand:

In the same file, I had four transactions that resulted in the following 
output from bean-check:
Could not match position Posting(account='Assets:Crypto:Ethereum', units=-
44.08 ETH, cost=None, price=0.02439024 BTC, flag=None, meta={'filename': 
'/home/joel/beancount/temp2.bc', 'lineno': 99})

The offending transaction here (same header as above, as its the in the 
same beancount file) is:

2016-06-05 * "Sell ETH"
Assets:Crypto:Bitcoin 1.0751 BTC
Assets:Crypto:Ethereum   -44.08 ETH @ 0.02439024 BTC
; CSV: 06-05-2016,10:45:13 AM,Sell ETH via Bitsquare,a4453750,,,1.0751 
BTC,0.02439024 BTC,44.08 ETH,Completed
; Imported: 2017-07-15
; Price per coin: 0.02439024 BTC
; Time: 10:45:13 AM
; Trade Status: Completed
; UUID: 7d96c7ac8441d01fbfa81c64628b5b963180c3f7

Here again the transaction balances when I ran it through ledger, unchanged 
from above. I don't understand why it could not match the position posting. 
Does that mean that there's not enough ETH in the lots inventory and I'm 
missing a transaction?

Thanks,

Joel

-- 
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 post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/23f40716-a471-4bac-8c24-d33a7ee8f6aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to I run a beancount plugin? beancount.plugins.book_conversions

[jkepler]

Duh! I found it in the documentation, 
https://docs.google.com/document/d/1QftxNvQPdH-MikMBHupftU6F4IsNZP5FlFh1LCbVgk8/edit:
 
a plugin is added to the input file via the optional syntax.

In my case, that was simply adding this line:

  plugin "beancount.plugins.book_conversions" 
"Assets:Bitcoin,Income:Capital-gains"

and the sample data works.



Le samedi 12 août 2017 15:58:02 UTC+2, jke...@gmail.com a écrit :
>
> Hi there,
>
> I'm a beginning beancount user, if I can get the 
> beancount.plugins.book_conversions to run on my journal for calculating my 
> capital gains/losses.
>
> I found that the source for that plugin is in the plugins directory on my 
> beancount install, but I'm at a loss for how to use it.
>
> Can someone point me to the appropriate documentation?
>
> Thanks,
>
> Joel
>

-- 
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 post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/30257e38-52c3-4551-9753-ba6cc1ca106e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: syntax error, unexpected ACCOUNT

[jkepler]

Yup. Beginners error here.

Thanks for clarifying that so quickly for me.

Joel

Le samedi 5 août 2017 18:28:40 UTC+2, Martin Blais a écrit :
>
> You cannot insert comment syntax between the postings.
> (This limitation is mainly due to the special treatment indentation has 
> and some limitations of the lexer implementation. In theory it would be 
> fixable, but falls under the "we need to rewrite the lexer" rubric.)
>
>
> On Sat, Aug 5, 2017 at 11:41 AM,  wrote:
>
>> Hello,
>>
>> I'm a Ledger user thinking of switching to Beancount based on what I 
>> understand from the documentation on how it handles lots. While trying to 
>> import my data from Ledger to Beancount using *bean-check* I'm getting a 
>> syntax error. Here's a small sample from my data:
>>
>> 2013-01-01 open Expenses:Crypto:NetworkFees BTC
>>
>> ; lots of other transactions were here
>>
>> 2017-06-27 * "Bitcoin network fee"
>> ; Account: Pocket money
>> Expenses:Crypto:NetworkFees   0.00082487 BTC
>> Assets:Crypto:Bitcoin
>>
>> When I run *bean-check* on that file, I receive the following error 
>> message:
>>
>> joel@bregalad:~/beancount$ bean-check ledger.bc
>>
>> /home/joel/beancount/ledger.bc:3308:*syntax error, unexpected 
>> ACCOUNT*
>>
>> Any ideas what's going on with my directives? Maybe this is an obvious 
>> beginners mistake, but I can't see it.
>>
>> Joel
>>
>> -- 
>> 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 post to this group, send email to bean...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beancount/ea767f56-d10f-4417-90d8-096578b286fe%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 post to this group, send email to beancount@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/3da300b9-af76-419e-ba8c-45dfeb1c49b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.