Generating renewal records in Salesforce CPQ can be initiated by marking the ‘Renewal Quoted’ checkbox to TRUE on a Contract record, detailed in the Renew from the Contract help article. When a Renewal Quote is generated from Sales or Service Contracts in Salesforce CPQ by checking Renewal Quoted, there are several factors that may change how Start Date and End Date fields are populated on Renewal Quotes and Renewal Quote Lines (QL).
Renewal Term and Amendment & Renewal Behavior fields on the contract can determine how the Renewal Quote and Renewal Quote Line fields are populated. Factors in the behavior include the Subscription or Contract Line Item Start Date and End Date and type of product being renewed.
The following example will look at how Renewal Quotes are generated when the Contract's Start Date is 1/1/2025, End Date is 12/31/2026, and Renewal Term is 24. We will break this example into several use cases depending on how fields are populated on your Contract or Service Contract.
In each example listed above we will include a fixed price Subscription product and a yearly segmented MDQ product.
(1) Creating a renewal quote where all Subscriptions or Contract Line Items have the same End Date (no Contract fields have been modified)
| Record | Start Date | End Date | Term |
| Contract | 1/1/2025 | 12/31/2026 | Renewal Term: 24 |
| Renewal Quote | 1/1/2027 | 12/31/2028 | Subscription Term: Null |
| Record | Name | Segment Start Date | Segment End Date | Start Date | End Date |
| Subscription (Year 1) | Annual MDQ | 1/1/2025 | 12/31/2025 | 1/1/2025 | 12/31/2026 |
| Subscription (Year 2) | Annual MDQ | 1/1/2026 | 12/31/2026 | 1/1/2026 | 12/31/2026 |
| Subscription | Subscription | Null | Null | 1/1/2025 | 12/31/2026 |
| Renewal QL (Year 1) | Annual MDQ | 1/1/2027 | 12/31/2027 | ||
| Renewal QL (Year 2) | Annual MDQ | 1/1/2028 | 12/31/2028 | ||
| Renewal QL | Subscription | Null | Null |
When Salesforce CPQ calculates the Renewal Quote Term if the Contract's Renewal Term is Null, the Contract Term will be used to determine the Renewal Quote's End Date.
When Quote Line Start Date and End Date are Null, the Quote Line's Effective Start Date and Effective End Date are used to calculate the Quote Line's Prorate Multiplier. The Effective Start Date is equal to the Quote's Start Date and the Effective End Date is equal to the Quote's End Date.
(2) Creating a Renewal Quote where Subscriptions have different End Dates and Amendment & Renewal Behavior is set to Latest End Date
| Record | Start Date | End Date | Term |
| Contract | 1/1/2025 | 12/31/2026 | Renewal Term: 24 |
| Renewal Quote | 1/1/2027 | 12/31/2028 | Subscription Term: Null |
| Record | Name | Segment Start Date | Segment End Date | Start Date | End Date |
| Subscription (Year 1) | Annual MDQ | 1/1/2025 | 12/31/2025 | 1/1/2025 | 12/31/2026 |
| Subscription (Year 2) | Annual MDQ | 1/1/2025 | 12/31/2026 | 1/1/2026 | 12/31/2026 |
| Subscription | Subscription | Null | Null | 1/1/2025 | 12/31/2026 |
| Renewal QL (Year 1) | Annual MDQ | 1/1/2027 | 12/31/2027 | ||
| Renewal QL (Year 2) | Annual MDQ | 1/1/2028 | 12/31/2028 | ||
| Renewal QL | Subscription | Null | Null |
(3) Creating a Renewal Quote where Subscriptions have different End Dates and Amendment & Renewal Behavior is set to Earliest End Date
| Record | Start Date | End Date | Term |
| Contract | 1/1/2025 | 12/31/2026 | Renewal Term: 24 |
| Renewal Quote | 1/1/2026 | 12/31/2027 | Subscription Term: Null |
| Record | Name | Segment Start Date | Segment End Date | Start Date | End Date |
| Subscription (Year 1) | Annual MDQ | 1/1/2025 | 12/31/2025 | 1/1/2025 | 12/31/2026 |
| Subscription (Year 2) | Annual MDQ | 1/1/2026 | 12/31/2026 | 1/1/2026 | 12/31/2026 |
| Subscription | Subscription | Null | Null | 1/1/2025 | 12/31/2026 |
| Renewal QL (Year 1) | Annual MDQ | 1/1/2027 | 12/31/2027 | ||
| Renewal QL (Year 2) | Annual MDQ | 1/1/2028 | 12/31/2028 | ||
| Renewal QL | Subscription | Null | Null |
000381693

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.