Re:Books: an immutable double-entry accounting database service
by jen_h on Thursday October 17, 2019 @09:58AM
(#21282084)
Yeah, people have been using things like Mint for ages, too, and it's not like professional accountants hosting Quickbooks on their ancient Windows boxen is any less terrifying from a security perspective than a ledger SaaS startup...
Personally, I'm likely to stick with Gnucash until or unless it becomes completely unsupported, but Intuit needs some real competition and it would be great to have more choice available.
gledger looks like a neat project, will check it out!
Re:Books: an immutable double-entry accounting database service
by painted on Thursday October 17, 2019 @09:34AM
(#21281858)
do you also have some kind of frontend for it? how do you see what's the flow of money and reporting? does it work with kibana out of the box?
Re:Books: an immutable double-entry accounting database service
by sudhirj on Thursday October 17, 2019 @11:36PM
(#21288438)
Each reporting system / products does its own reporting, and no plans of adding ELK integration right now, although we are moving to the ELK stack so it might happen.
We think of it more as a database++ with financial primitives baked in, so we want to keep it very simple and dumb. It’s not a complete solution - it’s a book to write in, and you need another service that decides what and how to write and writes it (we call it the bank or teller service, and it’s all business logic for our business). Each product has its own bank to teller service, but they all use the same ledger underneath.
Can still make a case for licensing, though, depending on the features.
We built this for our internal accounting, it's a ledger service that enforced immutable double entry rules and can run as a container with a Postgres DB configured. https://github.com/realimage/qledger