Contracts are defined per entity with combined resolution criteria: the assigned group and the ticket category must match for the ticket to be linked to the contract. A contract can also cover the child entities, with a single balance: a customer with several units uses one contract, and each unit's usage is shown separately in the Statement and in the portal. Unused hours can roll over to the next period. The module warns when a contract is about to expire or reaches its alert threshold and, with the Block + Alert option, prevents new tickets from being opened in the portal when the hours of all of the entity's contracts are exceeded, including through service catalog forms. Outside its validity period, a contract stops receiving hours: they go to the entity's default balance, and the technician is warned on the ticket.

In the portal, customers follow the Hours Consumption dashboard, with quota, hours worked and balance for each contract they can see and, if their profile allows it, the time logged on their own tickets. Management uses the Hours Statement, with CSV export and invoice, and, with the included My Dashboard, the ready-made Operations and Management dashboards, with the same numbers as the Statement. Retroactive time edits are recorded in an audit trail. When each cycle closes (monthly, quarterly, half-yearly or yearly), the invoice is sent to your system by webhook, recorded with its delivery status and resent automatically if the destination is down, without duplicates; a closing that did not run on the day is done on the next run, with the correct period.