Service item expiration and renewal
Every service item has a start date and an expiration setting. The expiration setting controls when the service item stops being current, which in turn determines whether MSP Manager flags the tickets attached to it.
Set the expiration in one of three ways.
Contract end date options
| Option | What it does | Use it for |
|---|---|---|
| Contract length | Runs for the number of months you enter, counted from the contract start date. | Fixed-term agreements where the term matters more than the calendar date, for example a 12-month contract from activation. |
| End date | Runs until the calendar date you select. | Agreements tied to a specific date, such as a contract that ends at a customer's financial year end. |
| Never expires | Extends the service item by a further 12 months, 90 days before its current end date, and keeps doing so. The service item stays active with no manual renewal. | Ongoing or recurring services with no defined end date, such as managed services or monitoring agreements. |
Switch between these options at any time as a customer agreement changes.
What happens when a service item expires
An expired service item does not stop your team working:
- MSP Manager flags tickets attached to an expired service item in the Ticket List and in the ticket editor, so you can see the expiry without opening the service plan.
- You can create new tickets against an expired service item. Log, track and resolve them as normal while a renewal is in progress.
Expiration still applies to billing. A service item must be active and up to date to bill against, so renew or extend it to avoid gaps in billable time tracking.
What do you want to do?