Where it earns its keep is when the single-stream "money in / money out" view starts lying to you — several accounts, some debt, reimbursements, an asset or two — because a spending pie chart can't tell you where you actually stand. Double-entry forces the books to balance, which catches errors and gives you a real net-worth position instead of a vibe
There still isn't, but I did recently find simplefin(https://beta-bridge.simplefin.org/). Its not great (e.g. quota of only ~25 requests per day), but its good enough and the price was cheap enough that I just bit the bullet. It also paired well with Actual budget, and now I have a personal accounting system that I am reasonably happy with.
I also found teller.io, which is frankly a better dev experience (and good free tier!), but they don't support all the banks I'm on and somehow simplefin does.
Would be nice/interesting to see something like that come about, but It's a bit frustrating. A delegated read-only api key against a specific account shouldn't be that hard to do.
Things Gnucash does.
and plain text accounting in general
I somehow fell out of the habit but I really need to get back to it.
They leave you with lots of options though, which could be a problem if you're starting into accounting
Ugh. Just write your own damn post already
So I built a local-first double-entry desktop app — a plain local database file on your own machine, no telemetry, no aggregator. Happy to talk about the local-first trade-offs (no auto bank sync is the price), or why I went one-time-purchase instead of subscription. Not here to pitch — genuinely interested in how others in this crowd handle their own books.
I've been using hledger and I usually just plug in purchases as I make them, but I do that on purpose because it's like a self-balancing checkbook so I'm always aware of what's going where.
> It's also the work of one accountant who happens to be the daily user, built with a lot of AI assistance.
The UI you're showing now looks more like a bag of controls thrown on a page by a backend engineer in 2006 and less like a B2C product in 2026. Various boxes all over the place, weird colors, misalignment, inconsistent spacing, confusing what does what, a random calculator(?) in the middle of the screen, unclear abbreviated labels. It needs so much work that a full rethink might be in order.