Blog
-
What a receipt reveals
A receipt carries a card fragment, a location, a time and a purchase history. That has handling consequences whichever way you store the thing.
-
Records you don't actually hold
An order history is not your archive. Access ends with the account, the subscription or the relationship, and it takes the documents with it.
-
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.
-
Which date a record belongs to
A single purchase can carry five defensible dates. Pick one for filing, record the rest, and never let the file's own timestamp be the answer.
-
How long to keep things
This site won't tell you the number, because it isn't one number. What it can give you is a scheme that works whatever the number turns out to be.
-
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.
-
Paper, digital, or both
A scan is a photograph of the information, not the information. Knowing what each format preserves and silently drops decides which one you need.
-
Test your filing by trying to break it
You find out whether a records system works when someone asks for something. Ask yourself first, on a random month, and time how long it takes.
-
Recurring charges leave the thinnest trail
Subscriptions produce no paper, no capture moment, and no memory. The record has to be built from the arrangement rather than the transaction.
-
Why thermal receipts fade
There is no ink. The image is a chemical reaction in a coating, and it can be undone by heat, light, friction, solvents and ordinary plastic.
-
Receipts you keep for reasons other than tax
Warranty, insurance, returns and proof of ownership run on their own clocks. Some of them outlast every other reason you keep a record.
-
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.
-
Records two people share
Two people filing into one system produces gaps neither can see. The fix is an owner per class, one destination, and a habit of saying what you did.
-
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.
-
The cost of keeping everything
Keeping everything feels free and isn't. Volume is paid for in retrieval time, in noise, and in holding data about other people you didn't need.
-
Running a disposal review
A retention scheme that never disposes of anything is just an accumulation. Here's the periodic pass that makes it a scheme, without stating any period.
-
What happens to metadata
The date attached to a file is not the date on the receipt, and it changes when you copy things. Put what matters where copying can't touch it.
-
A synced folder is not a backup
Sync propagates deletions and corruption as faithfully as it propagates files. Two copies of one live folder is one copy with extra steps.
-
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.
-
The expense claim as a records problem
A claim sends your records into somebody else's system. Keep your own copy of both the receipt and the claim, because they establish different things.
-
An inbox and an archive
Most filing systems fail because one container has to be both a landing zone and a permanent home. Split them and the hesitation at capture disappears.
-
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.
-
Where paper survives
Paper doesn't decay at one rate. It decays at the rate its surroundings dictate, and a drawer indoors beats a wallet by a margin nothing else can close.