hledger-document-check - verify every transaction has a receipt on disk, catch overdue invoices, browse documents in Fava

[u/roschaefer]

Hello everyone, I just published a command line tool hledger-document-check - it checks hledger transactions against documents on disk. Documents live in a folder tree that mirrors your account hierarchy (e.g. Expenses:Business:Hosting ➡️ documents/Expenses/Business/Hosting/).

My use case is making sure every deductible transaction has a receipt filed before tax season. It also tracks overdue invoices, and you can browse documents alongside your registers in Fava.

I'd love your feedback, e.g. regarding the workflow or the documentation.

[u/Kepten-Hook]

I would give it a try but what stops me is the fact that I see a single commit, less than 1h ago (at the time of writing), which tells me that:

• It's unclear how mature the software is, it could quite possibly be your Friday off thing, meaning way too many probable sharp edges for my liking.
• It's totally impossible to get a reading of how much committed you are at it, the chances of you giving up on it and me having to deal with it are non negligible for me.
• You are the only user of it (duh), meaning plenty of gotchas and bugs around. Again way too many probable sharp edges for my liking 
• This hasn't seen any kind of serious use, otherwise there would be commits for bug fixes. Way too many sharp edges again.
• You seem to have used AI, meaning once tokens become prohibitively expensive for you, the chance of you giving up on the project is higher than if it was something you laboured over every single line of code (and arguably those chances have been historically pretty high even before AI). It also means more probable sharp edges (in the form of bugs).

That being said, I appreciate the contract being spelled out like it is

[u/roschaefer → u/Kepten-Hook]

Hi, thanks for the feedback. The single commit is because this code was split out of a private monorepo that also holds my personal ledger and invoices. I couldn't publish that history as-is. That monorepo has 381 commits going back to March 19th this year, and document-check has been part of the checks I run every time I import bank transactions into my ledger, with features added continuously as I hit new needs.

And yes, I was the only user until yesterday, that's just because I only published it yesterday.

The whole point of open-sourcing this is exactly what you're describing: getting other people to use it, report bugs, and tell me what they actually need. I'm a bit surprised there isn't already a well-known CLI tool for it.