On Friday, January 10, 2025 at 4:31:42 AM UTC-5 [email protected] wrote:
- multiple importers matching the same source file, each extracting
transactions pertinent to one account. The transactions are grouped
per-account in the ledger and the source statement can be copied in
multiple locations in the archival folder
This makes a lot of sense! Must be a newer feature; not working for me but
it's also been a minute since I've updated
* .../Downloads/simplefin.json ERROR
beancount_utils.importers.simplefin.Importer
beancount_utils.importers.simplefin.Importer
Document identified by more than one importer.
I don't use archive, but if archive as *copy* implies an additional
"destroy" command to do actual cleanup, I would use that. I think 1:1
importer *instance* per account makes sense. Too, especially, for
brokerage-type accounts where you may want more flexibility in
PnL/income/fee postings (e.g. between retirement and non-retirement taxable
accounts).
Though for fun, I'm working on a truly single-file multiple-account
imports: Medical Claims. It's a mess/work in progress, but it imports the
aggregate claims from my insurance and outputs transactions to per-provider
payable accounts. This is much easier to reconcile than one big
Liabilities:Medical:MyInsurance bucket without having to scrape every
single MyChart (those in the US may know). Basically just provider -> payee
and provider+patient -> account with simple re-match+dict mappings.
2024-10-12 * "Labcorp" "Paul"
claim: "123456"
patient: "PAUL"
provider: "LABCORP HOLDINGS"
Liabilities:Medical:Labcorp:Paul -1.23 USD
^isn't at all 1:1 instance:account, but still works well with beangulp's
deduplication and other paradigms.
Paul
--
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/beancount/4b2762e2-8219-4d96-839d-4eb2525b779cn%40googlegroups.com.
