Timing, one-time, or structural: the only three things a variance can be

Your cloud bill is up $6,000 this month. Your legal fees are up $6,000 this month.

One of these is a problem and one of these is a Tuesday. The number does not tell you which. The category does.

Founders who review their financials monthly tend to stop at the number. They spot the line that moved, satisfy themselves that they know roughly why, and move on. The step they skip is the one that makes the review worth doing: deciding what kind of variance it was, because the kind determines what you do about it.

There are three.

Timing

The money was always going to be spent. It just landed in this month instead of last.

An annual insurance premium that hits in March. A vendor who invoiced six weeks late. A month with three Fridays and therefore an extra payroll run. A card charge that posted on the 1st instead of the 31st.

Timing variances reverse themselves. They need explaining so nobody panics, and then they need nothing else. If you carry a timing variance into a forecast you will double count it: once when it shows up early and once when the model expects it in its normal slot.

The test: will the annual total be the same either way? If yes, it is timing.

One-time

Real spend, genuinely non-recurring.

Legal fees for a financing. Laptops and desks for three new hires who started the same week. A conference sponsorship. A one-off contractor to clean up a data migration.

These matter for the month and should be pulled out when you talk about run rate. The failure mode here is not misclassifying them, it is forgetting to strip them out later, which turns a $40,000 legal bill into a $480,000 annual legal budget.

The test: if this month repeated twelve times, would that be absurd? If yes, it is one-time.

Structural

The shape of the business changed.

Your cloud bill is up because usage is up, and it will keep climbing. Your gross margin fell because your customer mix shifted toward a segment that costs more to serve. Your support headcount ratio moved and it is not moving back.

Structural variances are the ones that deserve a founder's attention, and they are the ones most easily lost in a pile of timing noise. A structural change often looks small in month one. Cloud costs up 9% is not dramatic. Cloud costs up 9% every month for five months is a different business than the one you were running in January.

The test: is next month's baseline different because of this? If yes, it is structural.

The ambiguous ones

Plenty of lines resist the sort, and the honest answer is that you sometimes cannot tell until month three.

A vendor that quietly moved from $400 a month to $1,900 could be a one-off overage or a plan that auto-upgraded and will now bill at $1,900 forever. You do not know yet. Write down that you do not know, tag it provisionally, and check it next month. That is a better outcome than a confident guess, because the note itself becomes the reminder.

The point of sorting variances at all is that it separates noise from signal. It is the signal that changes what you do next.

What the sorting buys you

Board meetings. The most common failure mode in a board deck is a financials slide the founder cannot narrate. When every material line already has a written explanation and a category attached, you are reading rather than improvising, and you can say "three of these reverse next month" out loud instead of hoping nobody asks.

Forecasting. A forecast built on a P&L you have not decomposed is a forecast built on averages, and averages carry every one-time item forward as though it recurs. Once the variances are tagged, you know which lines to project and which to strip.

Diligence. In a raise or an acquisition, someone will ask why a line moved eighteen months ago. Having that answer written down at the time, rather than reconstructed under pressure from a general ledger export, is the difference between a smooth data room and a bad week.

Error detection. This is the underrated one. Period-over-period review catches bookkeeping mistakes at least as often as it catches business changes. Miscategorized transactions, duplicate bills, a vendor booked to the wrong account. These are invisible in a transaction list and obvious the moment you put two months side by side. A variance you cannot assign to any of the three categories is very often not a variance at all. It is an error.

Try it on last month

Pull your five biggest movers from your most recent close. Write one letter next to each: T, O, or S.

The ones you cannot label are the ones to look at first.