I was sorting scanned receipts into a calendar — every document dropped into the folder for the day it was dated. It's the obvious move, and for a while it worked. Then it started to feel wrong, and it took me a minute to see why.
A restaurant bill from Tuesday belongs to Tuesday. I was there; the meal happened; the scan is evidence of a moment. But a phone invoice dated the fourteenth doesn't belong to the fourteenth in any real sense. It arrived on the fourteenth. It could have arrived on the twelfth or the sixteenth and nothing about my life would have been different. The date is an accident of the billing cycle, not a fact about me.
Those two documents look identical — PDF, date, amount, vendor — but they are different kinds of thing, and the calendar was flattening the difference.
The axis that actually matters
The distinction isn't "bill versus invoice," and it isn't "one-off versus recurring." It's this: is the document evidence of an activity, or evidence of an agreement?
Activity-related — the dinner, the museum ticket, the tank of fuel. Also, and this surprised me, the purchase invoice: buying a television is something I did, on a day, often in a place. A purchase is an activity, not an agreement. So the furniture I ordered files next to the photos of the day I ordered it, and quietly becomes an asset too.
Agreement-related — the phone subscription, the insurance premium, the energy bill, the tax notice. None of these is a moment. Each is the monthly shedding of a standing relationship. One KPN invoice is interchangeable with the next; what they have in common isn't a date, it's a contract.
Activity receipts answer "what did I do?" Agreement receipts answer "what am I committed to?" File them by the question they answer, not by the date they carry.
Why the date lies
The calendar is the right spine for a life, because a life is lived in days. But an agreement isn't lived in days — it's held across them. Pinning a recurring invoice to its billing date is false precision: it dresses an arbitrary timestamp up as a meaningful one, and the cost is that your telecom relationship ends up scattered across twelve day-folders a year, invisible as the single thing it actually is.
So agreement-related documents don't go to a day at all. They go to the year — the finest grain that still means something for a thing that repeats identically every month — grouped by category, and under it by party: 2022/admin/telecom/KPN/. Now the KPN relationship is one place, one folder, one story. The drift you couldn't see when it was smeared across the calendar becomes a thing you can read in a single glance.
This is just modelling, wearing ordinary clothes
Here's the part I find quietly funny. Deciding where a scanned receipt lives is not filing. It's data modelling — the same work I do for a living, on enterprise systems, dressed down in a hoodie.
"Is this an activity or an agreement?" is an entity question: two documents with the same shape belong to different tables because they mean different things. Routing the purchase to the day and the subscription to the agreement is choosing the right grain and the right dimension. And the reason it feels important out of all proportion to a pile of PDFs is that it is important — get the entity wrong and everything downstream inherits the error, whether the downstream is a data warehouse or a shoebox.
The agreement itself is already a first-class entity in my vault — contracts, subscriptions, the promise I made myself about the gym, all modelled as one thing with the evidence linked to it. The scans are simply that evidence arriving over time. Filing an invoice under its agreement isn't a new idea; it's connecting a document to the entity it was always about.
How to make the cut
You don't need a system to start. You need one question, asked of every document before it's filed:
- Did I do this, or did I sign it? A thing I did — a meal, a visit, a purchase — is activity. A thing I signed — a subscription, a policy, a plan — is agreement.
- Activity → the day. Next to the photos, the ticket, the memory. It's part of a moment.
- Agreement → the year, by party. Not the billing date. The relationship. Twelve invoices from one vendor are one story, not twelve events.
- When in doubt, ask what changes if the date moves. If moving the date by a week changes nothing about your life, it's an agreement, and the date was never the point.
The small idea underneath
Most of the mess in a personal archive isn't too little structure — it's one structure asked to carry two meanings. The calendar is a beautiful spine for what you lived. It's the wrong home for what you're bound to. Separate the two and each becomes legible: your days stay a record of life, and your agreements stop hiding in plain sight, one arbitrary invoice date at a time.
Two documents. Same shape. Different truth. The whole discipline is noticing the difference before you file.