SimpleFIN Bridge uses MX, a Plaid-like service, to access your accounts. On Saturday, January 11, 2025 at 8:04:30 PM UTC-6 mtb...@gmail.com wrote:
> > How does SimpleFin connect to accounts ? Does it "know" your passwords ? > On Saturday, January 11, 2025 at 1:33:13 PM UTC-5 ch...@hasenpflug.net > wrote: > >> Hi all, I have published my initial work on a SimpleFIN python library >> with command line interface. It is available on pypi ( >> https://pypi.org/project/simplefin/) and Github ( >> https://github.com/chrishas35/simplefin-python/). >> >> This initial release has commands to convert a SimpleFIN setup token into >> an access token (which you must securely store for future use). Subsequent >> commands look for the access token as an environment variable (personally I >> use direnv with .env files). You can use the CLI to get your SimpleFIN >> Account IDs and then run the transactions command to get a table or json >> output of that account's transactions. I plan to build and release a >> generic beangulp importer based on the json output in the future. >> >> As this library is not beancount specific, feel free to open discussion >> or issues on the github repo. >> >> -C >> >> On Friday, January 10, 2025 at 7:37:53 AM UTC-6 Chris Hasenpflug wrote: >> >>> Timely topic! I've been playing around with SimpleFIN a bit as well and >>> trying to get it integrated into my workflow. I have the start of a python >>> library and CLI that I'd like to share. Perhaps the snow day will give me >>> an opportunity to polish it for publishing. >>> >>> On Thursday, January 9, 2025 at 9:28:16 AM UTC-6 wpa...@gmail.com 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 beancount+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/beancount/a7fd3305-2639-4535-be6e-f556c758427en%40googlegroups.com.
