Customer and commercial details have been generalised.
Context
A recurring-revenue business needed a controlled way to apply contractual price increases. Natural renewals and a one-time mid-term increase followed different operational rules, while Salesforce and the finance platform both needed to hold a consistent contract history.
The constraint
Changing an active contract in place risked conflicting dates, unclear lineage and incorrect billing. The design had to preserve the original agreement, stop duplicate charges and give administrators a process they could review before committing the change.
Delivery design
EKWIS designed a template-led renewal model. End-of-term contracts could follow the standard renewal route with the correct uplift already assigned. A separate guided Salesforce Flow handled the mid-term case by creating a successor contract from the anniversary date, carrying forward the required commercial data and initiating the controlled retirement of the original contract.
How risk was controlled
- The mid-term action was limited to the roles accountable for contract operations.
- Eligibility criteria kept the process to the intended contracts and prevented repeated use.
- The original contract remained available for audit and record lineage.
- Reports surfaced contracts approaching an anniversary before action was required.
- Contract dates stayed aligned even when the operational work happened before a weekend or bank holiday.
Acceptance definition
The agreed design required both renewal routes to apply the right uplift, preserve key dates and relationships, maintain a visible audit trail and prevent the old and new contracts from billing at the same time.