Contingents

Purpose

Contingents control which quantities or amounts are available to a customer within a contract period in Professional Services. They therefore connect the promised service scope with recurring provisioning and actual consumption in ticket, work-order, and billing processes.

Prerequisites

• a suitable sales contract exists and is prepared for recurring services
• the contingent type, method, and reference period are defined
• if the contingent is linked through SLA or billing types, the related templates and assignments exist

Functional focus

Contingent type and billing logic

Contingents can be quantity-based or amount-based. They can also be capped or uncapped. This determines whether excess consumption is billed separately once the limit is reached or whether the service scope remains fully covered by the agreed service price.

Loading through contract activation and recurring billing

A contingent can be provided once or replenished periodically. Typical loading points are the activation of a sales contract or recurring billing, which makes the agreed quantity or amount available for a defined period.

Consumption in tickets and service billing

Actual deduction happens through operational service cases. When tickets or work orders are linked to a contingent, the consumed services are taken into account in Service Billing and offset against the available quantity or amount.

Periods, transparency, and control fields

Contingent periods make it visible how much quantity or amount has been loaded, consumed, and is still available. Key control fields include the reference period, payment type, rounding, deduction method, work type, and whether the service price is already included in the contract.

Outcome

Contingents turn contractually promised service scope into an operational control model. They connect SLAs, sales contracts, recurring invoicing, and actual service consumption in one consistent structure.