4 ms·
Simply managing the text files with git would solve that retirement
by diegocg 6y ago
Simply managing the text files with git would solve that retirement
- mongol 6y agoNo it wouldn't. It would provide history, but it would not prevent you from changing a transaction that was booked the previous month.
- veeti 6y agoSo don't change it? The audit trail is there.
- mongol 6y agoDepends on if authorities agree with that point of view. Accounting here needs to follow what can be translated as "Generally accepted accounting principles". If you do bookkeeping with pen and paper, you cannot erase a past mistake. You need to correct it with a new transaction. Basically, an append-only system is needed.
- veeti 6y agoI don't really see how this is practically different from any other "accountant approved" software. Even if the user interface is "append only" you can modify the saved data whether it's saved in plain text, binary blob or a SQL server. On pen and paper you can copy a new falsified ledger and throw away the original. I think that's fraud, so good luck with it.
- tacostakohashi 6y agoIf you do bookkeeping with pen and paper, you can throw away the page and replace it with a new piece of paper. The security mechanism is out of band - you keep the pages secure, and you also reconcile / audit your accounts with those of your bank, suppliers, customers, etc - it's never 100% within the medium of the accounts themselves.
- zie 6y agoNot really. Git's history is 100% fungible, you can mix and match git's history like a swiss army knife. There are VCS's out there that have unfungible history. Fossil SCM is one such VCS. Git is an amazing VCS swiss army knife. That doesn't make it the best tool for a given job.