Renewal policies
Zenskar offers three distinct policies to govern how an expired contract is handled:| Policy | Effect | Use case |
|---|---|---|
| Don’t renew automatically | The contract reaches its end date and terminates without further action. | One-time projects or fixed-term agreements. |
| Renew with same contract terms | The contract is renewed while preserving all customizations (discounts, custom pricing) applied to the original template. | Long-term partnerships with negotiated, non-standard rates. |
| Renew without customer-specific prices | The contract is reset to the default values of its parent template before renewal. | Standardized price increases or moving a customer back to “market” rates. |
The decision hierarchy
Zenskar processes expired contracts every 25 hours by applying a specific hierarchy of renewal logic:- Contract-level policy: The system first checks if a specific policy was assigned during the creation of the contract.
- Organization-level policy: If no contract-level policy exists, the system applies the global organization-level policy.
- Termination: If neither a contract-specific nor an organization-level policy is found, the contract is not renewed.
How-to: Configure organization-level renewal
To set a global fallback policy for all contracts in your organization:- Click on the bottom-left menu containing your profile name.
- Navigate to Settings > Contract & Invoices.
- Enable the renewal setting toggle.
- Select your preferred Contract Renewal Policy from the dropdown menu.
Reference
| Detail | Specification |
|---|---|
| Processing frequency | Every 25 hours. |
| Scope | All contracts expired within the last 24–25 hour window. |
| Default behavior | No renewal (if no policy is defined). |
- To learn how to apply these policies to a specific agreement, see the [How-to: Create a contract] guide.
- Would you like me to draft a guide on [Handle ingestion failures] to ensure your renewed contracts have accurate usage data?