How FP&A Teams Should Forecast SaaS Renewal Costs (Without Nasty Surprises)

Traditional FP&A forecasting models handle recurring costs well. Payroll is predictable. Rent is predictable. Even variable costs like cloud infrastructure follow patterns you can model.

SaaS renewals don't behave like any of these.

The problem isn't the cost — it's the timing and ownership:

• Contracts are signed by IT, ops, or department heads — not finance. The renewal date, auto-renewal terms, and uplift clauses live in a PDF that finance has probably never seen.
• There's no single system of record. Salesforce renewals might be tracked in procurement. Marketing tools might be tracked by the marketing ops lead. Developer tools might not be tracked by anyone.
• Renewal dates don't align to fiscal quarters. A contract signed in March 2024 renews in March 2025. A contract signed in September renews in September. There's no natural rhythm that forces visibility.
• Auto-renewal means no approval trigger. When a contract auto-renews, there's no purchase order, no sign-off, no approval workflow. The invoice just appears. By then, the company is already committed.
• Uplift clauses compound invisibly. A 5% annual uplift on a $60,000 contract adds $3,000 in year two, $6,150 in year three, $9,458 in year four. Over a five-year relationship, that single clause adds $30,000+ that was never in the forecast model.

The result: FP&A teams discover SaaS renewals the same way everyone else does — when the invoice arrives. And by then, the negotiating window has closed.

Missing a renewal in your forecast doesn't just cause budget variance. It eliminates your ability to do anything about the cost.

Most vendor contracts include a 60–90 day notice window before auto-renewal. If you want to cancel, renegotiate, or right-size the contract, you need to act before that deadline.

Here's the timeline that finance teams rarely see:

By the time the invoice hits the P&L, the company has already lost:

1. Negotiating leverage — you can't threaten to walk away from a contract you've already renewed
2. Right-sizing opportunity — if headcount dropped or usage changed, you're paying for capacity you don't need
3. Competitive bidding window — alternative vendors needed 60–90 days' lead time for a proper evaluation
4. Budget accuracy — the variance is already locked in for the quarter

A single missed renewal might cost $10,000–$50,000 in overspend. Across a portfolio of 50–150 SaaS contracts, the cumulative impact is typically 8–15% of total SaaS spend — money that was available for negotiation but wasn't, because finance didn't know the deadline existed.

Most FP&A teams have a software line item in their budget. It's usually a single number: “Software & Subscriptions — $X/quarter.” That's not a forecast. That's a guess with a label.

A proper renewal forecast model tracks each vendor contract individually and includes these fields:

Required Fields

Calculated Views

From these fields, your model should generate:

• Rolling 12-month renewal calendar — every renewal plotted by month, with notice deadlines highlighted
• Quarterly renewal spend — total committed renewal spend per fiscal quarter
• At-risk value — total ACV of contracts currently inside their notice windows (where you can still act)
• Expired-window value — total ACV of contracts where the notice window has already closed (locked in)
• Uplift impact — the difference between current ACV and forecasted renewal cost, summed across the portfolio
• Contracts needing action this month — filtered view of contracts with notice deadlines in the next 30 days

This isn't a nice-to-have dashboard. It's the minimum data finance needs to forecast SaaS spend accurately. Without it, you're budgeting by invoice — which is the same as not budgeting at all.

If you're starting from zero, here's how to build a working renewal forecast in Google Sheets or Excel. This will take 2–4 hours depending on how many contracts you have.

Step 1: Build the Contract Register

Create a sheet called “Contract Register” with the columns listed above. Start populating it. Sources:

• Accounts payable records — pull every recurring vendor payment from the last 12 months
• IT asset management / CMDB — if IT tracks SaaS subscriptions, pull their list
• Department heads — ask each department lead: “What vendor tools does your team pay for?” You will find contracts nobody else knows about. This always happens.
• Expense reports — individual expense claims sometimes contain SaaS subscriptions purchased on personal cards

Expect this process to surface 20–40% more contracts than you thought existed.

Step 2: Extract Notice Windows

For every contract with an auto-renewal clause, find the notice period and calculate the deadline. This is the most tedious step — it requires reading the “Term and Termination” section of each contract.

Record the notice period in days and calculate: Notice Deadline = Renewal Date - Notice Period.

Step 3: Build the Rolling 12-Month View

Create a second sheet called “Renewal Calendar.” Generate a row for each of the next 12 months. Use SUMIFS to pull total renewal value per month from the contract register.

Add conditional formatting:

• Red — contracts where the notice deadline has already passed
• Amber — contracts with notice deadlines in the next 30 days
• Green — contracts with 60+ days remaining before the notice deadline

Step 4: Add the Summary Dashboard

Create a third sheet with headline metrics:

• Total renewal spend this quarter and next quarter
• Number of contracts renewing each month
• Total at-risk value (notice windows closing within 30 days)
• Total uplift impact (sum of price increases across all renewing contracts)
• Contracts with no assigned owner (these are your highest-risk items)

Step 5: Set Calendar Reminders

For every contract with a notice deadline in the next 6 months, create calendar invites for the contract owner at 30, 60, and 90 days before the notice deadline.

This is the step that breaks down first. Calendar reminders don't update when contracts change. They don't escalate when nobody responds. They die when someone leaves. But it's better than nothing.

The spreadsheet approach works until it doesn't. The inflection point is usually one of these:

• Contract count exceeds 50–80. Manually maintaining the register, extracting notice windows, and setting calendar reminders becomes a part-time job.
• Staff turnover breaks ownership. Three people leave in the same quarter. Their contracts become orphaned. The spreadsheet says “Sarah — Marketing” but Sarah left four months ago.
• Amendments change terms mid-cycle. A vendor agrees to extend the notice period or change the renewal date. The spreadsheet doesn't get updated. The old deadline is still in the calendar.
• Multiple currencies and entities. If you operate across the UK, EU, and US, the forecast model needs currency conversion, entity-level rollups, and jurisdiction-aware notice period tracking.
• Finance needs real-time data, not monthly updates. The CFO asks “what's our total committed renewal spend for Q3?” and the answer requires 45 minutes of spreadsheet reconciliation.

The spreadsheet doesn't fail dramatically. It degrades gradually — one stale row at a time — until the forecast it produces is fiction dressed as data.

Renewly isn't a CLM platform, and finance teams shouldn't have to become contract managers. Here's what changes when contracts are in Renewly instead of a spreadsheet:

Automatic extraction replaces manual data entry. Upload a vendor contract PDF. In under 10 seconds, the extraction engine pulls vendor name, contract value, renewal date, notice period, auto-renewal terms, and uplift clauses. No reading page 14 of a 30-page MSA.

Notice deadlines are tracked separately from expiry dates. The dashboard shows both. Finance sees when the window to act closes — not just when the contract ends.

Escalating alerts go to the right person. Alerts fire at 7, 30, 60, and 90 days before the notice deadline. They go to the contract owner, not a shared inbox. If nobody responds, they escalate.

Portfolio analytics replace spreadsheet reconciliation. Total renewal spend by quarter. Value at risk. Contracts inside their notice windows. Uplift impact across the portfolio. All calculated in real time, not during a monthly spreadsheet update.

Team collaboration keeps ownership current. When someone leaves, their contracts can be reassigned. The new owner inherits the alert timeline. Nothing falls through the cracks because an email address was deactivated.

Finance doesn't need to run the system. Finance needs the output: a reliable, real-time view of what's renewing, when, and at what cost. That's what the analytics dashboard provides.

Here's the minimum viable renewal forecast for any FP&A team:

1. A complete vendor register — every SaaS and recurring vendor contract, with owner, value, and renewal date
2. Notice deadlines, not just expiry dates — the date after which you lose the ability to act
3. Uplift modelling — what each contract will cost at renewal, not what it costs today
4. A rolling 12-month calendar view — every renewal plotted by month, filterable by department, risk level, and value
5. At-risk value tracking — the total spend that's currently inside a notice window and can still be influenced
6. Automated alerts with escalation — because calendar reminders die when people leave

If your current process doesn't give you all six, your SaaS renewal forecast has gaps. Those gaps will show up as budget variance, overspend, and a quarterly conversation with the CFO that nobody enjoys.

Start by building the spreadsheet. When it breaks — and it will — you'll know exactly what the system needs to replace.