I’m interested in this, as well; I’ve signed up for a SimpleFIN account but 
haven’t actually used it in anger, yet. 

Do you have a sample config showing how your importer’s used? I’d like to copy 
some of your work. :-)

What’s your workflow? A separate script that downloads from SimpleFIN and dumps 
the JSON into an imports directory?

I also wish beangulp weren’t so tied to individual files; it makes writing an 
importer that works with non-file sources awkward, at best, and I think that’s 
reflected in the singular account restriction, as well…

— 
Brian Lalor (he/him)
[email protected]

> On Jan 9, 2025, at 10:28 AM, Paul Walker <[email protected]> wrote:
> 
> Hey all,
> 
> I'm curious what importer tricks anyone has for statements with multiple 
> accounts. Aggregators like SimpleFIN <https://beta-bridge.simplefin.org/> 
> (recently discovered, a great stand-in for banks dropping ofx~ofxtools/ofxget 
> <https://ofxtools.readthedocs.io/en/latest/> support) pull many unrelated 
> accounts into one export file. The beangulp-required account function makes 
> this seem antipattern ("which account?"). This also applies to some PDFs 
> (like Fidelity which groups all retirement/non-retirement into a pair of 
> PDFs), but I imagine many of those at least share a common base/parent 
> account.
> 
> My current solution is to input a dict of all expected accounts 
> <https://github.com/pwalkr/beancount-utils/blob/54c118f4a4d6a706691fa3442db523b5253e3287/beancount_utils/importers/simplefin.py#L37>,
>  but again is awkward for the self.account 
> <https://github.com/pwalkr/beancount-utils/blob/54c118f4a4d6a706691fa3442db523b5253e3287/beancount_utils/importers/simplefin.py#L28>
>  function (I don't actually use "archive" workflow) and is making me update 
> my out_of_place deduplicator 
> <https://github.com/pwalkr/beancount-utils/blob/54c118f4a4d6a706691fa3442db523b5253e3287/beancount_utils/deduplicate.py#L6>
>  which catches manually-created expenses on the wrong credit/debit card. It 
> just doesn't isolate context and messes with the overall extract.
> 
> The alternative I've considered is to avoid multiple-account statements. 
> SimpleFIN can get individual accounts 
> <https://www.simplefin.org/protocol.html#get-accounts>, I believe that's in 
> the ofx spec too. So then I'd just get account-specific extracts and 
> initialize an importer for each. But then I remembered the likely more common 
> but more difficult to split multi-account PDFs and thought to share and see 
> if the community had other ideas.
> 
> 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] 
> <mailto:[email protected]>.
> To view this discussion visit 
> https://groups.google.com/d/msgid/beancount/cd8f42de-dc67-446b-985b-cdcdc79b25f0n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/beancount/cd8f42de-dc67-446b-985b-cdcdc79b25f0n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
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/9C9B03F0-3CD4-4BB0-8600-4E0F0DB24A09%40bravo5.org.

Reply via email to