- some transactions go through without a text
- some transactions generate two identical texts
- for Forex transactions, the amount in the text and the amount on your statement will not match
- some texts are ambiguous in that they could have been generated by two different kinds of transaction; especially true of deposits & credit card payments
In the end I gave up, accepted that accounting will never be smooth & simple, and now just generate a CSV every month by hand.
I am working on a plugin to pull categories and transactions from the Hibiscus DB (H2 or PG) to Beancount [2]. It is not there yet, but the process overall looks promising.
[2]: https://github.com/Sieboldianus/beancount-hibiscus-importer
I'm pretty sure FinTS/HBCI is a mostly only used here in Germany sadly. Which is a shame because all this "OpenBanking" stuff requires registering/paying/certificates etc.
>Developer Information (in german)
Which sends to a Javadoc which is actually a 404.
To be honest, I wouldn't work on/with a project that uses not-English as primary language (even if it was my own). Maybe a bit of cleanup and documentation would help make it more accessible.
Actually, a client is migrating their system and needs to redo their bank synchronization. Shall I try with Google Translate, or is there someone who would also work on updating some of the resources to English?
We originally used Quickbooks Online and I'm glad we decided to switch to ERPNext a few years ago.
If you are okay with Plaid[1], many of their bank connections are now using OAuth-style authentication instead of password sharing. I actually added a new feature called Direct Connect[2] a while back to allow any plaintext accounting book users to pull CSV directly via Plaid API through BeanHub. We don't train AI models with our customers' transactions, and if we want to, we will ask for explicit consent (not just ToS) and anonymize customers' data.
If you're okay with the above, the key to achieving a high automation level is the ability to pull CSV transaction files directly from the bank in a standard format. Maybe you can give it a try. We have 30 days free trial period.
I am not so familiar with the CMMC requirements, as you mentioned, but for us to access transactions from some banks, such as Chase, Plaid requires us to pass an auditing process about our security measurements. Is the CMMC compliance your company needs to meet to take a third-party software vendor into considerations?
[1]: https://plaid.com
[2]: https://beanhub.io/blog/2025/01/16/direct-connect-repository...
In 2024, CFPB had mandated all U.S. banks to open up data history to SaaS/fintech vendors, if the customer gives permission.
The banks having to do it if we want them to, doesn't not mean we have to want them to.
> if the customer gives permission
Of course once permission has been given, it is part of that dataset (whether or not that is made clear by the app) and numerous other datasets (unless the law requires companies not share that data, and companies all fully obey that law, and they don't have any little data accidents).
...not always, they don't. Some financial institutes provide this, some do not. I know very specifically that some FIs do not have any way to grant read-only access, and that aggregators like Plaid, Flinks, Quicken, etc. will simply fallback on good-old-fashioned "give us your username/password and we'll screen scrape your account info".
I can personally attest to this being true in 2025 in Canada, at least.
I'm evaluating whether self hosting accounting software is at all feasible to meet CMMC requirements and so far have my sights set on ERPNext. I configured my bank to send me an email alert for every transaction and intend to parse that and appene it to my ledger, but the API to do so is fairly annoying, so hearing that beancount is meant to be automatable is intriguing indeed
BTW the other thing that shocks me about quicken classic is lack of version control - the database can become corrupt and your only recourse is restoring from backup or sending the file to support and having them manually fix it!