Salesforce Renewal Testing
Salesforce renewal testing validates the journey that carries a customer's recurring revenue into the next term — a renewal opportunity and quote generated from an active contract, subscriptions carried forward with the right quantities, pricing method and uplift, and the renewed contract picking up where the last one ended. It proves that renewal revenue is forecast and quoted correctly without reps rebuilding deals by hand.
Renewal journeys are part of the revenue and CPQ coverage available for demonstration and proof-of-concept validation.
How renewals are generated in Salesforce CPQ
In Salesforce CPQ, a renewal starts from an activated Contract and its SBQQ__Subscription__c records. Checking Renewal Forecast on the contract creates a renewal opportunity; checking Renewal Quoted creates a renewal quote on that opportunity, with lines built from the subscriptions. Many orgs automate both flags from a Flow or a scheduled job a set number of days before the contract end date, so renewals appear in pipeline without anyone clicking.
What lands on the renewal quote depends on several settings working together: the renewal pricing method (Same, List or Uplift) set on the contract or account, the renewal uplift percentage, the renewal model, the product's subscription pricing and term, and whether contracted prices or discount schedules apply. If multiple contracts are renewed together, co-termination and combined renewal settings decide how their terms and end dates are merged.
Renewal testing picks up after quote-to-contract testing has proven the original contract, and it is distinct from amendment testing, which covers changes made during a term rather than at its end. An amended contract, however, is one of the most important inputs to a renewal.
Why renewal defects cost more than they look
Renewals are high-volume and often lightly supervised, so a small configuration defect repeats across every customer due for renewal.
Lost uplift
The renewal pricing method falls back to Same instead of Uplift for some accounts, and contractual price increases are never quoted.
Missing subscriptions
Subscriptions added by an amendment, or ended early, are wrongly included or excluded from the renewal quote.
Broken continuity
The renewal term starts a day late or overlaps the original, creating a gap or double billing when the order reaches billing or the ERP.
Duplicate renewals
Automation sets Renewal Forecast twice, or a rep renews manually after automation already did, producing two renewal opportunities in pipeline.
Forecast distortion
Renewal opportunities are created with the wrong amount, close date or forecast category, inflating or hiding recurring revenue.
Owner and access gaps
Renewal opportunities are assigned to an inactive user or a queue a renewal manager cannot see.
The renewal happy path, step by step
SyntraFlow is designed to follow a contract from activation to renewed contract, asserting the values carried forward at each stage.
Start from a known contract
Seed an activated contract with subscriptions, quantities, net prices, a start and end date, and a known renewal pricing method and uplift.
Trigger the renewal
Set Renewal Forecast directly or let the scheduled automation fire, and assert that exactly one renewal opportunity is created with the expected amount, close date, owner and forecast category.
Generate the renewal quote
Set Renewal Quoted and assert that the quote's start date follows the original end date and that each line matches a renewable subscription.
Verify renewal pricing
Compare every renewal quote line price to the expected result of the pricing method — prior net price, current list price or prior price plus uplift.
Adjust and accept
Add a new product, change a quantity or remove a line as a renewal manager would, then submit for any required approval and accept the quote.
Order and renewed contract
Create the order and new contract, confirming the renewed term, subscriptions and prices are continuous with the prior contract and ready for downstream billing.
Renewal pricing assertions
The pricing method is where renewal testing earns its keep. These rows show what to assert for each common setup.
| Renewal setup | Input | Expected renewal line price |
|---|---|---|
| Pricing method Same | Prior net price 1,000 | 1,000, regardless of current list price |
| Pricing method List | Prior net price 1,000; current list 1,100; standard discount 10% | Current list less applicable discounts, recalculated |
| Pricing method Uplift at 5% | Prior net price 1,000 | 1,050, with uplift applied once |
| Uplift with amendment mid-term | Original line 1,000 plus amended line at prorated price | Each line uplifted from its annualized net price, not its prorated value |
| Contracted price on account | Contracted price record active for the renewal date | Contracted price used where the setup gives it precedence |
| Multi-year term | Three-year contract with yearly segments | Renewal term and segment prices follow the configured segmentation |
Exception paths worth exercising
Renewals branch in ways that are easy to overlook until they affect a real customer.
- A contract with an early-terminated subscription, confirming the ended subscription does not appear on the renewal quote.
- Two contracts for the same account renewed together, testing co-termination to a single end date and combined renewal quote behavior.
- A renewal triggered, cancelled and triggered again, confirming no duplicate or orphaned opportunity remains.
- A customer that churns: the renewal opportunity is closed lost and no renewed contract or order is created.
- A product retired from the catalog since the original sale, confirming the renewal behavior matches the business's replacement or exclusion policy.
- A renewal quote requiring discount approval, run through approval process testing paths including rejection.
- A currency or price book change on the account between original sale and renewal.
Test data and time
Renewal tests depend on dates. A realistic setup needs contracts at different points in their lifecycle — just activated, amended mid-term, within the renewal window, and already expired — along with their subscriptions, the accounts' renewal settings and the automation that watches end dates. Creating those contracts by running the full quote-to-contract flow for every test is slow, so renewal suites commonly seed contracts and subscriptions directly with controlled dates. CPQ test data covers seeding those records consistently.
Scheduled renewal automation should also be tested without waiting for a calendar date. Setting contract end dates relative to the run date, or invoking the scheduled path directly in a sandbox, lets the test prove the trigger window without changing system time. Roles matter as well: renewal managers, account executives and deal desk users often have different access to renewal opportunities and quote fields.
Suggested test scenarios
A representative set that covers generation, pricing, continuity and churn.
| Scenario | What it proves | Expected result |
|---|---|---|
| Automated renewal forecast | Scheduled automation creates renewals on time | One renewal opportunity per contract in the window |
| Uplift renewal quote | Uplift applies once to each line | Line prices equal prior net price plus uplift |
| Amended contract renewal | Amendments carry into renewal correctly | All active subscriptions present at annualized prices |
| Co-terminated renewal | Multiple contracts align to one term | Single end date and continuous service |
| Churned customer | Loss path is clean | Opportunity closed lost; no renewed contract |
| Renewed contract continuity | No gap or overlap in service | New start date equals prior end date plus one day |
Evidence and where renewals continue
A complete run is designed to capture the source contract and subscriptions, the renewal opportunity values, every renewal quote line with its computed and expected price, and the renewed contract dates. Finance and revenue operations can use that evidence to confirm that recurring revenue carries forward exactly as contracted.
Renewed orders frequently flow on to billing or an ERP, where continuity errors surface as duplicate or missing invoices. Extending the scenario across that boundary is covered by Salesforce-to-ERP order testing, and rerunning renewal suites after CPQ package upgrades belongs with CPQ regression testing.
Related pages
Business Processes
The full library of Salesforce business process tests renewals belong to.
Amendment Testing
Mid-term contract changes that become key inputs to every renewal.
Quote-to-Contract Testing
How the original contract and subscriptions a renewal depends on are created.
Revenue Cloud Testing
Broader coverage of subscription and recurring revenue processes.
CPQ Test Data
Seeding contracts and subscriptions at controlled lifecycle dates.
Forecasting Testing
Proves renewal opportunities roll into forecasts with the right amounts and categories.
Renewal testing FAQs
What is Salesforce renewal testing?
It is testing the process that turns an active contract into a renewal opportunity, a renewal quote and a renewed contract. Tests confirm that the right subscriptions carry forward, the renewal pricing method and uplift are applied correctly, and the renewed term is continuous with the original.
How is renewal testing different from amendment testing?
Amendment testing covers changes made during a contract term, such as adding licenses with prorated pricing. Renewal testing covers what happens at the end of the term. The two meet when an amended contract renews, which is one of the most important scenarios to test.
How do you test scheduled renewal automation without waiting?
Seed contracts with end dates positioned relative to the run date so they fall inside the renewal window, then run the automation or its scheduled path in a sandbox. This proves the trigger logic and window without changing system time or waiting for real dates.
Why is uplift a frequent source of defects?
Uplift depends on the renewal pricing method, where it is set, and which base price it applies to. Defects include uplift applied to prorated rather than annualized prices, applied twice on recalculation, or skipped because a different pricing method took precedence for some accounts.
Should renewal tests include the renewed order reaching billing or an ERP?
Where renewed orders flow downstream, yes. Continuity errors such as a one-day gap or overlap often only become visible as a duplicate or missing invoice. Cross-system scenarios extend the same test into the receiving system and reconcile both sides.
Is renewal testing available in SyntraFlow today?
Renewal scenarios are part of the revenue and CPQ coverage available for demonstration and proof-of-concept validation. The renewal models, pricing methods and automation in scope are confirmed per engagement.
Carry recurring revenue forward with confidence
Map your renewal settings, uplift rules and contract scenarios to a repeatable renewal test in a short working session.