To forecast SaaS spend for the annual budget, build one renewal calendar for every committed contract, then model true-up exposure by comparing contracted seats to your hiring plan for each seat-based vendor. Accrue the expected true-ups and renewal uplift monthly, and you replace quarter-end surprises with a number finance can defend.
Why SaaS spend is hard to forecast
SaaS spend resists a clean forecast for three structural reasons. First, it is spread across corporate cards, departments, and auto-renewals, so the total lives in a dozen places and no single system holds it. Second, there is rarely one renewal calendar, so contracts renew on scattered dates and finance learns the number when the invoice arrives. Third, many contracts are usage-based or seat-based, so the cost moves with headcount and consumption rather than sitting still at the figure you budgeted. A forecast built on last year's actuals will miss on all three.
The result is a line that is technically operating expense but behaves like a series of small capital events, each landing on its own schedule. The method below replaces the guesswork with two inputs finance can actually control: a calendar of what you have committed to, and a model of how much that commitment will grow.
Step 1: build the renewal calendar
The forecast backbone is a single calendar of every contract: the vendor, the owner, the renewal date, the notice window, and the committed annual amount. Sort it by renewal month. Once every commitment sits on one timeline, the annual number stops being a guess and becomes a sum you can watch build, month by month. This is also the artifact that lets you negotiate on time rather than after lock-in. Our SaaS renewal management guide covers how to assemble and maintain it. Committed spend by month is the first half of the forecast.
Step 2: model true-up exposure from headcount
The second half is the part most budgets miss: true-ups. For each seat-based vendor, line up three numbers: contracted seats, currently deployed seats, and the seats your hiring plan will add over the year. Multiply the gap between contracted and projected deployed seats by the per-seat rate, and you have the expected true-up for that vendor. Microsoft Enterprise Agreement seats, Adobe named users, and Salesforce licenses are the usual drivers, because each grows with headcount and reconciles on a fixed date. Our software license true-up guide explains how each vendor counts, and the Microsoft true-up preparation guide walks through the largest one in detail. Do this for your top five seat-based vendors and you capture most of the exposure.
Usage-based vendors need a second method. For cloud infrastructure, data platforms, and some AI tooling, the cost tracks a driver rather than a seat, so forecast from that driver, whether it is compute hours, active users, or events processed, and carry a contingency for the months a project spikes. Seat-based contracts are the predictable part and belong in the base forecast; usage-based lines carry a wider range and a note on what would move them.
Step 3: accrue monthly instead of absorbing the invoice
A true-up that lands as a single quarterly charge blows a hole in the quarter it arrives in. The fix is a monthly accrual. Take the expected true-up plus any known renewal uplift for the year, divide by twelve, and book one twelfth each month. Reconcile the accrual against the real deployed count 90 days before each anniversary, and adjust. If the gap is smaller than you accrued, release the excess back into the forecast; if it is larger, you still have time to fund the difference or deprovision unused seats before the count is taken. By the time the invoice arrives, it reconciles against money already set aside, and the variance conversation never happens. Accruing monthly turns a surprise cash event into a planned expense finance controls.
Step 4: separate committed spend from discretionary spend
Not all SaaS spend behaves the same way, so report it in two lines. Committed spend is everything under a signed contract through its term: the renewals on your calendar and the true-ups you modeled. Discretionary spend is month-to-month subscriptions and mid-year expansion you can start or stop. A signed three-year Salesforce agreement is committed for its full term; a team's month-to-month workspace tool is discretionary. Tag every line one way or the other, and the split falls out of the inventory. Committed spend is the floor you must fund; discretionary spend is the lever you can pull if the number needs to come down. Reporting both, rather than one blended figure, tells leadership which part of the budget is fixed and which part is a choice.
A worked example
Take a 1,200-employee company running 140 applications, with three seat-based contracts. The renewal calendar shows the committed base, the true-up model estimates the growth, and the monthly accrual spreads it across the year.
| Vendor | Contracted seats | Projected deployed | Per seat per year | Renewal month | Expected true-up |
|---|---|---|---|---|---|
| Microsoft EA (M365 E3) | 1,000 | 1,180 | $360 | March | $64,800 |
| Adobe Creative Cloud | 120 | 150 | $600 | June | $18,000 |
| Salesforce | 200 | 230 | $1,500 | September | $45,000 |
Total expected true-up is about $128,000. Divided across twelve months, the company accrues roughly $10,700 per month and reconciles each vendor 90 days before its renewal. In the P&L, the committed base and the accrual sit on the SaaS line together, and each vendor's true-up clears against its own accrual in the month it reconciles. The annual budget carries the committed base from the calendar plus this accrual, and none of it arrives as a surprise. If hiring slows and the September count comes in at 215 seats instead of 230, finance releases the difference rather than explaining an overspend.
What to ask IT and SAM for
Finance cannot build this alone. Ask IT and software asset management for five data points, and the two teams share one number instead of two:
- The full contract list with renewal dates, notice windows, and committed amounts.
- Contracted seats versus currently deployed seats for each seat-based vendor.
- The true-up or reconciliation date for every enterprise agreement.
- Real utilization, so you can tell paid-but-unused seats from genuine growth.
- The hiring plan mapped to the tools that new roles consume.
That last point is where finance and asset management meet: headcount drives deployment, and deployment drives the true-up. Our SaaS spend management guide covers the operating model that keeps these answers current.
Key takeaways
- Build one renewal calendar. Committed spend by month is the forecast backbone.
- Model true-up exposure from contracted seats, deployed seats, and the hiring plan.
- Accrue expected true-ups and uplift monthly, and reconcile 90 days before each anniversary.
- Report committed and discretionary spend as two lines, so leadership sees what is fixed and what is a choice.