*Apologies, meant to start a new thread:*
Awesome, thanks for sharing beanbuff. March seems to be the #ingest month
:).
I'm curious though: what is the fundamental concern around representing
thousands of temporary positions in Beancount? Is it performance, and if
so, won't v3 solve this? Is
Awesome, thanks for sharing beanbuff. March seems to be the #ingest month
:).
I'm curious though: what is the fundamental concern around representing
thousands of temporary positions in Beancount? Is it performance, and if
so, won't v3 solve this? Is it to not pollute your ledger with
Great stuff Luciano, thank you for sharing, I'll definitely have a good
look at it when I find a bit of time.
Red: Related to investments, I'm in the process of cleaning up and
building common data structures specifically for trading accounts, in a new
repo called "beanbuff". Find related codes
It's does a pretty good job for something you just tried :). Agree, custom,
per-importer dedup solves all the problems here. Thanks!
On Tuesday, March 30, 2021 at 5:01:22 AM UTC-7 bl...@furius.ca wrote:
> Dedup detection is definitely far from perfect and was just something I
> tried at the
Nice to see others writing importers. And great, comprehensive
documentation too! Thanks for sharing this.
I'm wondering if your import scripts can be used for building investment
transactions? How do you handle balance assertions? How do you handle
institutions that include multiple tables in
You may want to take a look at my project, Beanborg:
https://github.com/luciano-fiandesio/beanborg
I have used it for over a year to automatically import several types of
external CSV files from different financial institutions. It doesn't take
long to setup and once is configured, assuming you
