Lots of ways to do your accounting today with LLMs, but for some reason there is this expectation you are suppose to keep the old accounting software around? And it sort of makes sense, they vouch for the ledger integrity and keep the audit trail.

It reminded me of how things where like before git. You trusted the host not just to keep the data but to vouch for the versioning, and what git really did was move that last part into the data itself.

Accounting ledgers need integrity, in fact it is mandated by law in most places. Git buys integrity by publishing, because if you do not share your repo with anyone, you can always force push and rewrite the commit history and no-one would know. But your books are sensitive and cannot be published.

So I made git-style versioning for double-entry accounting. Entries gets hashed and timestamped, service checks for debit equals credit, and it ends up as json files you keep in your own S3 bucket. Not in a vendor database. For the hosted version the access keys to the buckets are encrypted with the user passkey / assistant OAuth, so the service cannot read anything at-rest.

For user convenience there is a hosted version where you do the books through MCP on whatever LLM you already use. The whole thing is so cheap to run, because the service does not store any sensitive data, so it is free, although you need an AI client with MCP support and an S3 bucket.

Hosted version: https://bobalice.com Code walkthrough: https://bobalice.com/docs/alice


Comments URL: https://news.ycombinator.com/item?id=50589229

Points: 1

# Comments: 0