Tagged “capture”
-
Finding it again
Storage is solved and retrieval isn't. Filenames, dates and one flat folder will beat any hierarchy you design, because you won't maintain the hierarchy.
-
Refunds, deposits and part-payments
One purchase can produce four documents and three amounts. The record has to describe the sequence, because no single artefact in it does.
-
What makes a receipt useful later
Six fields decide whether a record is worth anything in two years. Five are printed for you. The one that matters most is never on the paper.
-
When one receipt covers two things
A single total hiding two different purposes is the hardest record to reconstruct. Note the split at the till; the paper will never do it for you.
-
Writing it down at the time
A note made at the moment is a different kind of thing from one made later. Not more honest — just made when the fact was still available to you.
-
When the receipt is already digital
An emailed receipt feels safe because it arrived. It isn't filed, it isn't yours, and search only finds it if you remember words you never wrote.
-
Reconstructing a year you didn't record
You can rebuild most of what money did from statements, portals and a calendar. What you can't rebuild is why — and inference must never be filed as fact.
-
Why batch entry fails
The pile isn't a discipline problem. Batching a per-transaction task makes it grow, get harder, and cost the one thing paper never had: your memory.