Key Takeaways

  • A clause that stays in a PDF cannot change an invoice, so renewal terms have to become data before anything is automated.
  • Finance needs eight terms for every contract that renews, including the uplift rule, its base, the notice window and the co-term rule.
  • Four checkpoints, each tied to a date the contract already sets, catch a wrong renewal price before the customer sees it.
  • A system can price the renewal, prorate co-termed add-ons and flag notice deadlines, while a person still reads the ambiguous clause and approves a waived increase.

A customer renews in March. The invoice goes out at last year’s price, because the clause that allowed an annual increase is in a signed PDF and nowhere else. Finance finds out at the next renewal. On a $200,000 contract with a 5% increase, that is $10,000 not billed, and next year’s increase starts from the lower price. Asking for it back a year later is a hard conversation to start.

Renewals look simple from outside: the same customer buys the same product for another year. Inside finance, three things land on one date. The price changes. Add-ons bought during the year have to line up with the main agreement. And the contract sets deadlines for giving notice. You can automate renewals, uplifts and co-terming in B2B contracts once the terms exist as data, and a few decisions still belong to a person.

Why Do Renewals Go Wrong in Billing?

The arithmetic is easy. What goes missing is the input, on the day it is needed.

  • The terms live in documents. Uplift clauses, notice periods and price caps sit in order forms and master agreements. The billing system holds a price and an end date.
  • The dates depend on calendars. A reminder fires, or someone remembers. When that person is out, the notice deadline passes.
  • Add-ons bring their own end dates. Each mid-term purchase can start its own clock, so one customer ends up with several renewal dates to track.
  • The increase is traded away. Sales waives or trims it to close the renewal, and finance hears late or not at all.

Which Contract Terms Does Finance Need as Data?

Record each of these for every contract that renews. Where the contract is silent on one, record that too.

  1. Term dates. Start, end, and whether the end date is the last day of service.
  2. Renewal type. Automatic or by signature, and the length of the renewal term.
  3. Notice window. How many days before the end date either side must give notice not to renew, and how much notice a price increase needs.
  4. Uplift rule. A fixed percentage, an index such as CPI, the greater of the two, or a move to current list price. Anniversary step-ups inside a multi-year term belong here too.
  5. Uplift base. What the increase applies to: the subscription fee only, or usage rates, overage rates and minimums too. And whether it is calculated on the price the customer pays or on list.
  6. Caps, locks and expiring discounts. Limits on increases, multi-year price locks, and first-term discounts that end at renewal.
  7. Co-term rule. Whether add-ons end with the main agreement, and how a partial period is priced.
  8. Billing terms after renewal. Frequency, in advance or in arrears, payment terms, and whether the customer needs a new purchase order.

How Should an Uplift Be Calculated and Applied?

An uplift holds three decisions, and each can be read more than one way.

The base. An increase applied to the price the customer pays today keeps last term’s discount inside the new price. An increase applied to list price, after a first-term discount has expired, produces a larger invoice. The contract should say which. If it does not, decide once and read every contract the same way.

The index. A CPI-linked increase needs four parts written down: which index and series, which month’s reading, the comparison period, and any cap or floor. Index figures are published after the month they measure, so the rule has to name a reading that will exist on the day the invoice is prepared. The series matters because a seasonally adjusted figure can be revised after it is published. Where the rule is the greater of a fixed percentage or CPI, the calculation needs both inputs and the comparison.

The effective date. The increase starts on the date the contract sets: the renewal date, or each anniversary inside a multi-year term. An anniversary has no renewal to prompt anyone, so it belongs on the checkpoint list too. With annual billing in advance, the renewal invoice carries the new price. With monthly billing, the first invoice after the change may cover days at both prices and needs a split.

If the contract requires written notice of an increase, the increase depends on that notice going out on time. Give the notice an owner and a due date, like any close task.

How Does Co-Terming Work, and Where Does It Break?

Co-terming means everything a customer buys ends on the same date as the main agreement, so there is one renewal date and one renewal to price.

Consider a hypothetical example. A customer on a January to December term adds seats on October 1 at $12,000 a year. Co-termed, the add-on runs to December 31 and is billed for that partial period. On January 1 everything renews together for a full year. Prorated by month, the partial period is 3 of 12 months: $3,000. Prorated by day, it is 92 of 365 days: $3,024.66. Neither is wrong. Billing one customer one way and the next the other way is.

Three questions decide whether a co-termed add-on is billed right.

  • Proration. Daily or monthly, and on what day count. Pick one method, write it into the order form, and use it for every customer.
  • The first uplift. Does an add-on bought in October take the January increase with everything else? Customers ask this, so the order form should say.
  • The revenue schedule. The add-on usually gets its own short revenue schedule, then joins the main one at renewal. A discounted add-on can change that, so show it to whoever owns recognition. Where invoices and revenue schedules are kept in separate files, this is where they drift apart.

What Checkpoints Keep Renewal Invoices Right?

Each checkpoint hangs on a date the contract already sets.

  1. Before the notice window opens. List every contract whose notice deadline or anniversary step-up falls in the coming quarter. Confirm the renewal type, the uplift rule and the base price. Send any required price notices. Share the list with sales and customer success.
  2. Before the renewal date. Build the renewal price line by line: prior price, uplift, expiring discounts, add-ons at their full-term price. Preview the first invoice. A second person approves anything non-standard. A waived or reduced increase needs a named approver and a reason, recorded with the renewal.
  3. At the first invoice. Compare it with the preview. Check the purchase order number, the billing entity and the tax treatment, which can change at renewal without anyone telling finance.
  4. At close. Confirm the new revenue schedule started on the renewal date. Compare renewed revenue with what the first checkpoint predicted. Log every renewal that went out at the old price, and why.

The log from the fourth checkpoint gives you two numbers worth tracking: the share of renewals invoiced at the right price the first time, and the increase you billed as a share of the increase your contracts allowed.

What Can You Automate in Renewals, Uplifts and Co-Terming?

Once the terms are data, most of the routine runs without a reminder.

TaskWith the terms as data
Notice deadlines and anniversary step-upsFlagged a quarter ahead, from the term dates and the notice window
The upliftCalculated from its rule and its base, with any cap applied
A co-termed add-onProrated by the one method the contract names, then folded into the renewal
The renewal invoiceRaised at the new price on the effective date, and split where a period covers two prices
What stays with a personReading an ambiguous clause, approving a waived or reduced increase, and reviewing what the system flags

That moves the first three checkpoints from a calendar to a system, and people review the exceptions.

Where Does Vayu Fit, and What Does Simetrik Show?

Vayu’s contract agent reads the contracts, order forms and renewals in your CRM and pulls out pricing terms, billing rules, renewal dates and commitments. Finance reviews and approves that logic before it produces an invoice. In Vayu’s pricing models, finance can change effective dates, billing rules and uplifts for a customer without waiting on engineering. Whichever vendor you talk to, us included, ask which of the eight terms its system holds as data and which stay in the PDF.

Simetrik is a public example of renewal rules run from data. Its contract terms, including renewal rules and CPI flags, flow from Salesforce into Vayu, and finance defines the rules once instead of applying CPI increases by hand. Sales and customer success can see each customer’s renewal status and upcoming price changes without asking finance. As CFO Felipe Pardo puts it in the case study: “Customer Success didn’t have visibility with certain customers. Now we have real-time data in one place, so we can operate with customers better.”

For changes that arrive between renewals, see our guide to contract amendments. A renewal also repeats the first of the four contract to cash handoffs, where signed terms become billable logic.

Frequently Asked Questions

How do you automate renewals, uplifts and co-terming in B2B contracts?
Hold the renewal terms as data instead of text in a PDF: term dates, renewal type, notice window, uplift rule and base, caps and expiring discounts, co-term rule and billing terms. A billing system can then price the renewal, prorate co-termed add-ons and raise the invoice, while finance reviews the exceptions.

What is co-terming in a subscription contract?
Co-terming aligns the end date of every add-on with the end date of the main agreement. An add-on bought mid-term is billed for the partial period to that date, and everything renews together afterward.

When does a contractual price uplift take effect?
On the date the contract sets: the renewal date, or an anniversary inside a multi-year term. It applies only if any notice the contract requires was given on time, and the first invoice after that date should carry the new price.

How do you automate renewals and annual price increases for IT services contracts?
The same way as for software. Hold the renewal type, the notice window, the increase rule and its base as data, then apply the increase on the date the contract sets. Services contracts often price by rate card or by counts of users or devices, so record which rates the increase applies to.

Do you know which of next quarter’s renewals carry an increase? Book a billing logic review and walk one renewal from the signed terms to the invoice.