The operational problem
A recurring-revenue business may need to apply a price increase at renewal or during an existing term. Those paths need different rules, while the original agreement, successor contract and billing dates must remain understandable.
Updating an active agreement in place can obscure its history. The design needs to show which contract applies on each date and prevent overlapping billing.
Two paths through the same contract lifecycle
For an end-of-term renewal, a template-led route can prepare the successor contract with the correct uplift. A separate guided Flow can handle the mid-term case, carrying forward the required commercial data and starting the successor agreement from the relevant anniversary.
The original contract stays available for audit. Eligibility checks, role-based access and a review step determine when the action can run. The Salesforce and finance-system changes need to be assessed together.
What needs to be checked
Test dates, price calculations, related records and finance behaviour for both routes. Include repeated clicks, early preparation, weekends and bank holidays, and failures part-way through the process.
Acceptance should show the correct uplift, preserved agreement history and no period in which both contracts generate the same charge.