Last verified with: 10.8.6.0
Overview #
Service Status Types and State Transitions give businesses a powerful way to align pricing to the lifecycle of a service.
Instead of treating a service as if it always has the same commercial meaning, the platform allows that service to move through clearly defined states such as pre-active, active, suspended, trial, on-hold, or canceled. Each of those states can carry different billing behavior.
This makes it possible to charge differently when a service is fully active, reduce or stop recurring charges when it is temporarily suspended, and apply one-time charges when the customer moves from one state to another.
What They Are #
At a business level, Service Status Types define the lifecycle states a service can be in.
Typical examples include:
- pre-active,
- trial,
- active,
- suspended,
- seasonal hold,
- and canceled.
These statuses are not just labels. They control how the platform treats the service for billing purposes.
Each status is tied to a base billing behavior:
- Billable: recurring charges are allowed while the service is in that state.
- Non-Billable: recurring charges do not apply while the service is in that state.
- Canceled: the service is permanently ended and cannot move back into another state.
State Transitions define the movement from one service state to another.
Examples include:
- pre-active to active,
- active to suspended,
- suspended to active,
- trial to active,
- or active to canceled.
These transitions are important because they let the business attach commercial meaning to a change in lifecycle, not just to the service itself.
How They Work #
From a business perspective, the model is straightforward:
- A set of Service Status Types is created to represent the lifecycle states the business wants to manage.
- Each status is defined as billable, non-billable, or canceled.
- State Transitions are configured to define the allowed movement between statuses.
- Recurring pricing can be configured differently for each status of the service.
- One-time transition charges can be configured for specific state changes.
- When the customer’s service changes status, the platform applies the pricing behavior associated with the new state and any transition charges tied to that move.
- If the status changes mid-billing period, charges can be prorated so each portion of the billing period reflects the state the service was in at the time.
This allows the billing model to follow the real lifecycle of the service rather than forcing one flat price across every operational condition.
How They Are Configured #
The capability is configured in two connected layers.
First, the business defines the Service Status Types it wants to use. This establishes the lifecycle vocabulary for the service model.
Second, the business defines the State Transitions between those statuses. This determines which changes in state should be recognized and monetized.
Pricing is then attached to the lifecycle in two ways:
- recurring pricing can vary by service status,
- and one-time pricing can be applied to specific transitions.
This means the lifecycle model and the pricing model work together. The status determines the ongoing billing posture of the service, while the transition determines whether a one-time event charge should apply when the service moves between states.
Why This Matters #
Many businesses do not want to bill a service the same way throughout its entire lifecycle.
A service in testing may need to be free or discounted. A suspended service may need reduced pricing or no recurring charge at all. A reactivated service may need a one-time fee. A canceled service should stop recurring billing entirely.
Without lifecycle-aware pricing, teams often rely on manual billing adjustments, duplicate catalog items, or operational workarounds to reflect those scenarios. That creates complexity, inconsistency, and revenue risk.
Service Status Types and State Transitions solve that problem by making lifecycle-based pricing part of the product model itself.
Business Benefits #
This capability delivers value in several important ways:
- More precise lifecycle pricing. A service can carry the right recurring price for its current commercial state instead of one flat price for every condition.
- Better support for activation and reactivation charges. Businesses can monetize important lifecycle events such as activation, unsuspension, delivery, or reinstatement.
- Cleaner handling of temporary holds and suspended services. Recurring charges can be reduced or stopped without canceling the service entirely.
- Better customer alignment. Pricing can better reflect what the customer is actually receiving at each stage of the service lifecycle.
- Less catalog duplication. Teams do not need separate services or packages just to represent trial, active, suspended, and canceled commercial states.
- Better billing governance. Permanent cancellation is enforced as an end state, helping prevent accidental reactivation flows that should be modeled differently.
- More accurate mid-cycle billing. When a service changes state during the billing period, the platform can prorate charges so the invoice reflects the actual time spent in each state.
Pricing Scenarios #
Different Recurring Prices By State #
One of the most valuable aspects of this capability is the ability to assign different recurring prices to the same service depending on its status.
Examples:
- a full monthly price while active,
- a discounted recurring price while on hold,
- no recurring price while suspended,
- or a special low-cost price during a pre-active or trial period.
Benefit:
- Lets pricing follow the actual commercial state of the customer relationship.
- Avoids creating separate products just to represent the same service in different operational conditions.
- Makes lifecycle pricing easier to understand and manage.
One-Time Charges On State Change #
Some lifecycle events should trigger a one-time charge rather than a new recurring price.
Examples:
- an activation fee when a service moves from pre-active to active,
- a reactivation fee when a suspended service returns to active,
- or a delivery or provisioning fee when a service changes from an inventory state to a delivered state.
Benefit:
- Lets businesses monetize high-value lifecycle events directly.
- Creates a clean way to bill operational actions without changing the recurring price model.
- Supports more realistic commercial terms for activation, restoration, and fulfillment.
Prorated Billing Across Multiple States #
If a service changes status during a billing period, the platform can bill each state proportionally for the time the service spent in that state.
For example, a service could be active for part of the month and suspended for the rest, with each portion billed according to its own pricing treatment.
Benefit:
- Improves billing accuracy.
- Helps invoices reflect real service history.
- Reduces the need for manual credits or adjustments when services change state mid-cycle.
Telecom Examples #
Active Versus Suspended Connectivity #
A telecom provider may want a connectivity service to bill at full recurring price while active, then move to a lower charge or no recurring charge when the line is suspended.
Benefit:
- Supports temporary service holds without full cancellation.
- Aligns charges to the level of service actually being delivered.
- Improves customer fairness while preserving operational continuity.
Activation And Reactivation Fees #
A provider may charge a one-time fee when a line first becomes active, and another fee when a previously suspended line is restored.
Benefit:
- Recovers operational costs tied to provisioning and restoration.
- Monetizes important lifecycle events directly.
- Avoids burying operational fees inside recurring rates.
Seasonal Service States #
A telecom business serving seasonal customers may keep a service in a lower-priced holding state during the off-season, then return it to full active pricing when service resumes.
Benefit:
- Supports seasonal commercial models without rebuilding the product.
- Helps retain customers who do not want to fully cancel.
- Creates a more flexible contract and retention strategy.
SaaS Examples #
Trial To Paid Conversion #
A SaaS company may define a trial state with reduced or zero recurring price, then move the customer into an active paid state when the commercial term begins.
Benefit:
- Creates a clean path from trial to monetization.
- Keeps trial and paid logic inside one lifecycle model.
- Makes the commercial handoff more transparent and controllable.
Temporary Suspension For Non-Use #
A software business may allow an account or environment to move into a suspended or paused state with reduced billing while the customer is temporarily inactive.
Benefit:
- Supports flexible customer retention strategies.
- Preserves the service relationship without forcing cancellation.
- Gives the business more control over how partial-service periods are billed.
Provisioning Or Enablement Charges #
A SaaS provider may apply a one-time charge when a service moves from a setup state into a live production state.
Benefit:
- Supports implementation, enablement, or provisioning charges.
- Separates setup monetization from ongoing subscription pricing.
- Gives the provider more flexibility in structuring onboarding commercial terms.
Why Customers Value This Capability #
Customers value this capability because it allows pricing to reflect the real lifecycle of a service instead of forcing every situation into a single billing pattern.
That matters when a service can be tested, activated, paused, resumed, or canceled over time. It matters when operational events such as activation or restoration should carry a separate charge. And it matters when customers expect invoices to reflect the actual timing and state of the services they received.
For providers, the result is a cleaner product model, better billing accuracy, and more flexibility to support sophisticated commercial offers without creating unnecessary catalog complexity.