Variance Memo Template for CFOs
The format finance teams actually use when the board asks "what happened this month." Covers P&L variance, the three drivers that matter, and the narrative that keeps questions short.
What a variance memo actually contains
A variance memo explains the gap between what you planned (or last period) and what actually happened — across revenue, cost of goods sold, gross profit, and operating expenses. The goal is to give a CFO, CEO, or board member a crisp read in under three minutes.
Every useful variance memo has four parts:
- Executive summary — two to four sentences. What changed, why it matters, what you're doing about it.
- P&L summary table — prior vs. current, absolute change, percentage change. Revenue → COGS → Gross Profit → OpEx → Net Income.
- Material variance drivers — the 3–7 line items that explain 80% of the swing. Every driver gets a dollar amount and a reason.
- Forward look — one paragraph on whether the trend continues, reverses, or is one-time in nature.
The template (copy/paste format)
[2–4 sentences. Revenue was [up/down] [X%] vs. [prior period/budget]. The primary driver was [driver]. Gross margin [expanded/compressed] [X bps] due to [reason]. [What action is being taken or why this is expected to normalize].]
| Account | Prior | Current | Change | % |
|---|---|---|---|---|
| Revenue | $X,XXX,XXX | $X,XXX,XXX | +$XXX,XXX | +X.X% |
| Cost of Goods Sold | $XXX,XXX | $XXX,XXX | +$XX,XXX | +X.X% |
| Gross Profit | $X,XXX,XXX | $X,XXX,XXX | +$XXX,XXX | +X.X% |
| Operating Expenses | $XXX,XXX | $XXX,XXX | +$XX,XXX | +X.X% |
| Net Income | $XXX,XXX | $XXX,XXX | +$XX,XXX | +X.X% |
| Account | Change | Driver |
|---|---|---|
| [Revenue / Product Line / SKU] | +$XX,XXX | [Volume, price, mix, new customer, churn] |
| [COGS driver — e.g. hosting, COGS labor] | +$XX,XXX | [Scale of operations, vendor price change, one-time item] |
| [OpEx line — e.g. S&M, R&D, G&A] | +$XX,XXX | [Headcount addition, campaign spend, one-time item] |
[One paragraph. Is the trend likely to continue, reverse, or was it one-time? What are the leading indicators to watch? What management action is already in motion?]
Worked example: $20M SaaS company, Q1 miss
Here's what a real variance memo looks like for a mid-market SaaS company that came in below plan on net income despite a revenue beat.
Revenue beat plan by 7% on strong enterprise expansion, but gross margin compressed 300 basis points as infrastructure costs scaled faster than revenue. Net income finished at $185K vs. $239K last month — a $54K shortfall driven entirely by hosting and a one-time SLA credit. Infrastructure team is renegotiating the AWS Enterprise Discount Program; we expect margin to recover 150–200 bps by Q2.
- +$150K Enterprise MRR — 3 new logo expansions closed in March, contribution hits April in full.
- +$111K Hosting / Infrastructure — Scaled with February traffic spike; not fully offset by reserved instance coverage. AWS EDP renegotiation in flight.
- +$45K Sales & Marketing — Two AE hires onboarded March 1; first full payroll month.
- +$37K SLA credits issued — One-time payout to 4 enterprise accounts following a 47-minute incident on March 8. Non-recurring.
Enterprise expansion revenue from March closes hits the April P&L in full (+$150K MRR run rate). The AWS renegotiation is expected to yield a 12–15% reduction in hosting cost by Q2, recovering the margin compression. SLA credit is non-recurring. Watch: AE ramp — both hires are in 90-day ramp, quota attainment begins May 1.
The five mistakes that make boards ask follow-up questions
- Explaining the variance instead of the driver. “Revenue was down because sales were lower” is not an explanation. Name the customer, the segment, or the product line.
- Burying the headline. If net income missed plan, say it in sentence one. Boards read the executive summary and stop there if it doesn't demand their attention.
- Listing variances without magnitude. “Infrastructure costs increased” tells the board nothing. Always include the dollar amount and the percentage.
- No forward look. The board's real question is always “will this happen again?” Answer it before they ask.
- Too long. A variance memo is not a 10-K. If it takes longer than 3 minutes to read, it's too long. Every section should earn its space.
How long should this take to write?
For a $10M–$100M company with clean financials in QuickBooks or NetSuite, a competent finance team should be able to produce a first-draft variance memo in 30–60 minutes after close. If it's taking longer, the bottleneck is usually one of:
- Manual trial balance export and formatting
- Hunting for the driver (what actually caused the variance, not just which line moved)
- Rewriting the narrative for the board's preferred level of detail
Pariom handles all three: upload a CSV or connect QuickBooks and the P&L table, driver analysis, and narrative are generated in about 90 seconds.
Not ready to connect? See a live demo →