I had a desire to try to keep things as minimal as possible and work towards understanding what's actually going on before adding something like beancount_reds (it comes up basically whenever I google an import question) but taking a look at your example, it does look like it's going to save me a lot of time getting my fidelity data imported
One question -- have you considered adding support for csv files from Fidelity that have multiple accounts? Here's the scenario:
- I have many fidelity accounts
- I can export a csv for each one, which would match your example here exactly
- I can also go to "all accounts" in fidelity and export one csv for everything (columns are `Run Date,Account,Action...` instead of `Run Date,Action...`)
- Significant reduction in CSV files that need to be downloaded but some code would need to leverage the account column to dynamically update the Assets:Fidelity:<account> entry for beancount
Appreciating the guidance.