Budget season approves renewals nobody has read

The budgeting calendar is fixed. For many businesses it runs in the autumn, because that is when next year's plan has to be ready. The contract calendar is not fixed at all. Renewal dates are spread across all twelve months, notice periods range from thirty days to a year, and neither one has any relationship to when finance happens to be asking for numbers.

That mismatch decides, quietly, which vendor lines a budget round can actually influence. A contract with a ninety-day notice window renewing in December has its decision point in September, a month before the budget template goes out. One renewing in March with a sixty-day window has its decision point in January, two months after the budget is signed off. Only a narrow band of contracts land inside the window while the budget conversation is still happening.

Picture a European operations team that runs its budget round every October. One of its contracts, a scheduling platform worth around €90,000 a year, renews the following January with a ninety-day notice period. The act-by date falls squarely inside the October round, which makes it the exception rather than the rule. Most of the rest of the spreadsheet had already been decided by the time anyone opened it.

Part of why this goes unnoticed is that the two calendars belong to different people. Finance owns the budget round. Whoever originally signed the vendor agreement, who may well have left the business since, owns the notice period sitting in a clause nobody has reopened. There is no job description that says compare these two calendars against each other, so nobody does, until the invoice arrives at a number the budget never accounted for.

Two things sit behind every vendor line that a spreadsheet copied forward will never show you. The first is the contractual uplift, the actual percentage or formula the agreement uses to set next year's price, which is frequently higher than whatever round number the budget process assumes and is sometimes linked to an index nobody in the department has looked up. The second is the notice window, whether the line is still changeable at all by the time the budget gets approved, or whether the decision was already made the moment nobody sent a cancellation letter.

Some of these uplifts are fixed, an agreed percentage written in at signing. Others are tied to an index, a price benchmark that moves on its own schedule and has nothing to do with whatever figure the finance team typed into the template. Either way, the number already exists on the day the contract is signed. It only needs someone to read the clause before the budget round closes, rather than finding it out from the invoice after.

Take a department carrying a £64,000 vendor line. It gets copied forward at the usual three percent, taking the budgeted figure to roughly £65,920. The contract behind it carries a seven percent uplift clause, an escalator agreed years ago and never revisited, which puts the actual invoice closer to £68,480, a gap of well over £2,500 that nobody planned for and finance only discovers when the invoice lands. Worse, the ninety-day notice window on that contract closed in September, before the budget template was even sent out. There was never a decision to make here, only a number to get right, and the spreadsheet got it wrong by assuming a percentage instead of reading a clause.

Neither of these facts lives anywhere a budgeting exercise normally looks. They live in the contract, which is exactly why copying last year's number forward feels efficient and is actually just skipping the two questions that matter.

1. Build the contract register before the budget template goes out. Vendor, renewal date, notice period, and uplift clause, for every recurring agreement. This is the one step that has to happen first, because everything else in the list depends on it existing.
2. Sort every line by act-by date, not renewal date. A $40,000 platform renewing in April with a sixty-day notice period has an act-by date in February, eight months before an October budget round opens. Sorted by renewal date it looks comfortably far off. Sorted by act-by date it is already overdue.
3. Tag each line committed, decidable, or watch-next-cycle. Committed means the notice window has already closed for the coming budget year. Decidable means the window is still open and falls before or during the current budget round. Watch-next-cycle means the window will not open until after this budget is signed, so there is nothing to do yet beyond noting the date.
4. For every line tagged committed, use the actual uplift clause, not the assumed percentage. That is the number the vendor is going to invoice regardless of what the budget round decides, so the budget should reflect it exactly rather than guess at it.
5. Assign a named owner and a deadline to every line tagged decidable. A number with nobody responsible for it and no date attached to it behaves exactly like a line that was never flagged at all.

The first time a department runs this exercise, most of what it finds is bad news of the ordinary kind. A surprising share of the register turns out to be already committed for the coming year, decided by a notice window that closed before anyone thought to look. That is not a wasted exercise. Knowing which lines are locked and by how much is worth more to a budget than a number that looks precise and is not.

The second year is different, because the register already exists and the act-by dates are known months in advance rather than discovered in the same week as the deadline. A contract worth €28,000 with a ninety-day window and a January renewal has an act-by date in October, squarely inside a typical budget round. That is a line the budget process can still change, provided somebody knew to look for it in September rather than finding out in January that the window had gone. Repeat the exercise for a year and the share of the register that is genuinely decidable, rather than already settled, starts to grow.

None of this needs new software, a bigger finance team, or a change to when the budget round falls on the calendar. It needs the register built before the round starts, and someone willing to sort it by act-by date instead of alphabetically by vendor name.

Renewly does the first step. It reads each agreement, pulls out the renewal date and the notice period, calculates the last day you can act, and tells you before that day passes, so the number that goes into the budget is the one the contract actually says rather than the one last year happened to say.

See how it works

Related reading: why your January renewals have an October deadline, why software renewals are rising faster than inflation, and how FP&A teams should forecast renewal costs.