How to run monthly flux and variance analysis on Starch
Monthly flux analysis — comparing this month's actuals against last month, against budget, and against the same month last year — is the core recurring task that tells you whether your business is moving in the direction you think it is. It sounds simple. In practice, it's the workflow most operators either rush through or skip entirely, because pulling the numbers from accounting software, matching them to a budget that lives in a spreadsheet, and writing the variance commentary takes a couple of hours every month cycle that nobody has budgeted for.
What this looks like in practice depends heavily on your setup — how you categorize expenses, whether you're on accrual or cash, how granular your budget is, whether you're reporting to investors or just keeping yourself honest. The core job is the same: explain the delta between what you planned and what happened, and flag anything that warrants a decision.
On Starch, the end state is a dashboard where your actuals, your budget, and month-over-month trends are already assembled — pulled from your bank accounts and accounting system without a manual export. When something moves more than expected, you see it flagged automatically with the magnitude and the category. The variance commentary you still write, but you're writing it against a clean, current number instead of spending thirty minutes getting to one.
Why it matters
Without a regular flux process, surprises accumulate quietly. A vendor contract that renewed at a 40% increase doesn't surface until the quarter is already blown. An expense category that's been creeping for three months looks like a one-time anomaly when you only look monthly. Done consistently, variance analysis gives you a short feedback loop between decisions and their cost — so you're adjusting spend in week three of a bad month, not week two of the next one.
Common pitfalls
The most common mistakes: mixing cash and accrual in the same comparison (your bank feed says one thing, your P&L says another, and you're comparing them directly); using last month's exported spreadsheet as the budget baseline without checking whether actuals were restated; treating every variance as noise instead of sorting by materiality first; and writing commentary that describes what happened ('marketing was over by $12k') without explaining why or whether it recurs. The last one is where most flux analyses fail — they describe the number instead of answering the question behind it.
Starch apps used
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Choose your operator
A version of this guide tailored to your role — same recipe, different starting context.
The AI stack built for small finance teams.
The AI stack built for the founder's office.
The AI stack built for CPG brands.
The AI stack built for boutique professional services firms.
The AI stack built for foundation and nonprofit ops teams.
The AI stack built for DTC founders.
The AI stack built for independent clinic owner-operators.
The AI stack built for small investor relations teams.
Related workflows in Finance & FP&A
Vendor and category spend analysis means knowing, at any point in time, where your money is actually going — which vendors are getting paid, how much, how often, and whether that number is creeping up or down relative to last month.
Read guide →AP invoice approval is the process of reviewing incoming vendor bills, confirming they match purchase orders or contracts, getting the right sign-off, and releasing payment.
Read guide →A 13-week cash flow forecast is a rolling, week-by-week view of what hits your account and what leaves it — covering roughly one quarter ahead.
Read guide →An annual operating budget is a forward-looking plan that maps expected revenue against planned spending for the next 12 months, broken into categories you'll actually track — payroll, software, marketing, COGS, facilities.
Read guide →