Re: importers and get going

[Red S]

FYI, I have importers for banks and credit cards that support ofx, based on 
my beancount_reds_importers library. I'm happy to add that to my python 
package that you're using if there's interest. I wrap it with smart 
importer, which is very well designed and written, and gets it right well 
over 90% of the time.

You're right: I've found that building dependable automation around my 
import/ingest made took that part from a 3 hour task to a 3min task, and 
was a key piece in making my beancount/fava experience fruitful.

This is why I get my imports to extract balances and prices and convert 
them to balance check and price entries. Taking automation a step further, 
I also have some scripts to auto-download my statements for a few 
banks/cards/brokerages that support quicken direct connect. This automates 
the downloading step as well, and stores your passwords securely (encrypted 
with a master password).


On Thursday, June 25, 2020 at 10:21:58 PM UTC-7, Jonathan Goldman wrote:
>
> Thanks this is very helpful. I was not aware of the smart importer and 
> will try it out. And I’ll check out beancounttools. Thanks!
>
> On Thu, 25 Jun 2020 at 5:41 PM, 'Patrick Ruckstuhl' via Beancount <
> bean...@googlegroups.com > wrote:
>
>> Hi Jonathan,
>>
>> Q1
>>
>> I would say whenever you have both (or more) sides of a transactions then 
>> it's the best to import all legs. The thing is that in most cases you don't 
>> have them. On thing that I also do quite often is, that if I can import 
>> both sides of a transaction form two different sources (e.g. two different 
>> banks), then I use the transaction ids of each bank to add them to the same 
>> transaction, so I know that I have it imported from both sides.
>>
>>
>> Q2
>>
>> Not sure if you've come across smart importer 
>> https://github.com/beancount/smart_importer, this is a wrapper around 
>> your importer that uses existing transactions to guess what the missing 
>> other leg could be. For me this works extremely well.
>>
>> I use it together with the web ui fava https://github.com/beancount/fava
>>
>> when you then run an importer you get basically the list of all your 
>> transactions and you can still modify if the smart importer guess wrong.
>>
>> What I also started doing more and more (and also works quite nicely), is 
>> to actually not even have a file to import but instead directly use an 
>> available api (e.g. truelayer, revolut, transferwise, interactive brokers, 
>> ...), you can see some examples in my beancounttools 
>> https://github.com/tarioch/beancounttools
>>
>>
>> Q3
>>
>> There were some enhancements done for hooks: 
>> https://github.com/beancount/beancount/issues/458
>>
>>
>> Regards,
>>
>> Patrick
>>
>>
>>
>> On 25.06.2020 07:15, Jonathan Goldman wrote:
>>
>> Hi, 
>>
>> I have done a bunch of exploration of beancount over the last few months 
>> and really like its capabilities and now ready to get serious about getting 
>> it working for me. So far this is what I have done:
>>
>>
>>- Used the sample files to familiarize myself with the commands and 
>>beancount's capabilities. 
>>- Created accounts and manually entered some real data for my 
>>personal finances. 
>>- Tried this  
>>sem-auto-categorization web-based import tool. It's good but I think I'll 
>>mostly go the manual route. 
>>- Tried various import methods 
>>   - Tried importing a quicken file...have had some trouble with this. 
>>   - Tried a csv2ofx  tool 
>>   - Used reds_importers 
>>   
>> 
>>  
>>   for Vanguard. This has worked successfully. This generates output that 
>> has 
>>   two-sided. 
>>   - Wrote my own csv importer for my bank that is based on this csv 
>>   
>> 
>>  
>>   importer.. (I'm not a software engineer by training so this took me 
>> some 
>>   time but I'm very happy with this now and understand the code much 
>> more). 
>>   This generates output that is only one-sided.  
>>
>> My own conclusion is that I want go the route suggested by Martin and 
>> effectively have my own importers for each source and with text-based 
>> editor with auto-completion do the categorization. For the brokerages there 
>> are a limited number of accounts/categories you can have so doing the 
>> two-sided entry can be done here so it is auto-categorization if you will. 
>> (e.g. dividends from account xyz always go to this income account, etc). 
>> For credit cards and banks it rarely helps as there are so many expense 
>> categories. Perhaps a subset (e.g. interest income from the bank can be 
>> autocategorized or mortgage payment of specific amount) can be automated. 
>>
>> *Q1. Is doing two-side entry for brokerages and single-side fo

Re: No position matches - how to fix it?

[redst...@gmail.com]

In brief: ' 1. EUR {{100. HUF}} ' is incorrect syntax for what you're 
trying to do. Read the documentation (it's awesome) and it should be 
obvious.

On Sunday, June 21, 2020 at 11:14:07 PM UTC-7 Máté Farkas wrote:

> Hi,
>
> I tried to import to beancount my 11k transactions of 15 years.
>
> It works pretty well, except with the account with different currency. (I 
> was able to eliminate the No Position Matches errors using "NONE" booking 
> method, but fava has a bug , 
> so I cannot hide the account which was closed years ago.)
>
> Here is a minimalistic example, how can I make it working (without setting 
> booking method to "NONE"):
>
> option "title" "Currency account test"
> option "operating_currency" "HUF"
>
> 2020-01-01 open Income:Test
> 2020-01-01 open Expenses:Test
> 2020-01-01 open Assets:Test EUR "AVERAGE"
>
> 2020-01-02 price EUR 100. HUF
> 2020-01-02 *
>   Assets:Test   1. EUR {{100. HUF}}
>   Income:Test-100. HUF
>
> 2020-01-03 price EUR 200. HUF
> 2020-01-03 *
>   Assets:Test   1. EUR {{200. HUF}}
>   Income:Test-200. HUF
>
> 2020-01-04 price EUR 150. HUF
> 2020-01-04 *
>   Assets:Test  -2. EUR {{300. HUF}}
>   Expenses:Test   300. HUF
>
> Versions:
>
>- fava, version 1.15
>- Beancount 2.3.0
>
> Thank you in advance,
> Máté.
>

-- 
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/e15ac71a-e01a-44f0-aa73-12486a0a3ff2n%40googlegroups.com.