Use Case Design · Clief Notes

Use Case Design

I built a simple receipt logging system that reads incoming files, renames them consistently, moves them into organized archive folders, and logs each purchase into a clean CSV ledger.

Existing options fall short because off-the-shelf expense apps lock your data behind monthly subscriptions, force everything into proprietary cloud dashboards, and don't organize the actual files on your own computer the way you want them.

To match my actual workflow, I made two simple design choices:

Keep everything in local files and folders: Receipts get automatically renamed with the date, vendor, and amount, then filed into year and month folders next to a single CSV ledger. Everything stays on my drive, fully searchable and independent of any third-party app.
Flag missing details instead of guessing: When a receipt is blurry or cut off, the system routes it to a review folder and asks for the confirmed total before touching the ledger. That keeps the expense log completely accurate without risking bad data.

0 comments

Use Case Design