Spreadsheets feel free. They're already open, everyone knows how to use them, and starting a new tab costs nothing. But the prepaid schedule, the accrual tracker, and the allocation model you maintain alongside QuickBooks aren't free at all. They're a second set of books you keep by hand — and that parallel system charges rent every month.
We call it the spreadsheet tax: the recurring cost of holding your close logic off-ledger. It rarely shows up as a line item, which is exactly why it's easy to underpay attention to. Here's where it actually gets collected.
The reconciliation tax
Every off-ledger schedule has to be reconciled back to the ledger. Your prepaid tab says one thing; QuickBooks says another; someone has to confirm they agree and key the entries that make them agree. That round-trip happens every period, for every schedule, forever. It's not hard work — it's repetitive work that never compounds. You do it in March and you do all of it again in April.
The drift tax
Spreadsheets fall out of sync quietly. An assumption changes — headcount, a contract term, a vendor split — and the sheet that depended on it doesn't know. There's no error, no warning, just a number that used to be right and isn't anymore. You discover drift the way you discover a leak: late, and usually because something downstream broke.
A spreadsheet never tells you it's out of date. Someone has to remember to check — and remembering is the whole job.
The key-person tax
Off-ledger close logic lives in one person's head as much as in the file. They know which tab feeds which, why a formula has a hardcoded override, which schedule needs a manual nudge in months with five Fridays. When that person is out — or leaves — the close doesn't just slow down, it gets risky, because the knowledge that made the spreadsheets trustworthy walked out with them.
A quick test: if your most senior finance hire took a two-week vacation during close, would the books still be correct when they got back — or just done?
If the honest answer is “done,” the rigor lives in a person, not in a system.
The audit tax
When the logic lives in spreadsheets, the audit trail does too — which is to say, it mostly doesn't exist. A cell gets overwritten and the prior value is gone. A correction looks identical to an error. Come diligence or audit time, “why is this number what it is?” becomes an archaeology project across file versions and email threads instead of a drill-down to the entry that produced it.
Paying it down
The point isn't that spreadsheets are bad. They're a brilliant place to think. They're a poor place to operate a recurring, correctness-critical process that other people depend on. The fix isn't more discipline applied to the spreadsheets — it's moving the logic into a system that carries it for you:
- Schedules that post their own entries, so there's nothing to reconcile back.
- Rules that apply themselves every period, so drift has nowhere to hide.
- An immutable audit trail, so every number has an explanation that outlives the person who made it.
That's the trade Granite is built around: replace the spreadsheets, keep the rigor. The rigor was never the problem. The place you were keeping it was.