Flux & Variance
Explaining an account made of forty small charges
Software and subscriptions is the usual suspect. The variance clears your threshold, but no individual charge is worth investigating — and there are forty of them.
This is a genuinely awkward category. The account is material in aggregate and immaterial line by line. Investigating every charge costs more time than the account deserves. Investigating none of them leaves you unable to say what drove the movement.
What works is deciding, explicitly, that most of it doesn't get explained.
Set a per-item floor and bucket below it
Pick a dollar figure below which an individual item won't be examined. Everything under it gets aggregated into a single line:
Then explain, individually, only the items that are new, discontinued, or that moved meaningfully. In most months that's three to six things, not forty.
The reason this survives review is that it's honest. You aren't claiming to have looked at a $40 renewal. You're stating a rule, applying it, and naming what's above it. A reviewer can accept that. What a reviewer can't accept is commentary implying an investigation that didn't happen.
Use both a dollar floor and a percentage
A threshold on dollars alone drags in every small account that moved a lot proportionally. A threshold on percentage alone misses large-dollar movements in large accounts.
Requiring both — a line flags only when it clears a dollar floor and a percentage — keeps the flagged population close to what someone would actually ask about.
The specific values are yours: thresholds get set during risk assessment and control scoping, not invented at close. The point here is applying whatever rule you have consistently down the whole schedule, and being able to state it if asked.
What to actually look at
| Look for | Why |
|---|---|
| New vendors | A first-time charge is the most common cause of a step change, and it's the item most likely to recur |
| Items that stopped | A cancellation shows up as a favorable variance with no obvious cause unless you look for absence |
| Annual renewals | A yearly charge landing in one month distorts the comparison entirely and is pure timing |
| Anything repriced | Same vendor, different amount — easy to miss because the line looks familiar |
| Count of items | If the number of charges jumped, that's a driver in itself and worth a clause |
Watch the timing distortion
Accounts like this are unusually prone to false signals from annual billing. One renewal landing in the current month can move the account more than any genuine change in usage.
If that's what happened, say so plainly rather than describing a spend increase. The underlying run rate didn't change, and the same variance will reverse next month.
Where the tooling helps and where it doesn't
The compilation is mechanical and worth automating: pull the detail, group by vendor, compare against prior period, sort by movement, flag anything appearing for the first time. That's tedious by hand and reliable to automate.
What doesn't automate is deciding which of the items above the floor are worth narrating — that depends on knowing which programs matter to the business. And if the charges arrive as journal entries without vendor-level detail, none of this works, because the information you need was never posted. More on that distinction here.
The underlying point
Not every line in an account needs an explanation. It needs a rule, applied consistently, that a reviewer can follow.
Commentary that says "numerous small charges" with no threshold behind it reads as a shrug. The same sentence with a stated floor and the exceptions called out reads as a decision.
If you work this in Excel: the free flux template flags what needs explaining and shows the residual your drivers don't cover. The CloseOps Flux & Variance System ($79) starts from your trial balance instead: confirm each account's classification and it builds the income statement and balance sheet flux statements, then ranks what to investigate.
Related: month-end flux, start to finish, flux flags what moved — the exceptions are structural, and why some accounts can be explained from the detail and others can't.
Found something wrong or missing? Tell me here — anonymous, thirty seconds.