---
title: "Monitoring Usage"
slug: "monitoring-usage"
updated: 2026-08-10T20:22:00Z
published: 2026-08-10T20:22:00Z
canonical: "help.idibilling.com/monitoring-usage"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.idibilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring Usage

The IDI platform calculates billable usage as a percentage of the total available units on a service and compares the result to configured thresholds. Usage is calculated as X/Y where:

- X = Units within a discount category used in the current bill period
- Y = Units within a discount category available in the current bill period (recurring allotment + roll over)

> [!NOTE]
> Note
> 
> You must properly configure the discount categories.

Usage is typically checked once per day. Usage in each applicable category (minutes, data and/or messages) is checked independently. On each instance when usage is checked, if usage has reached or exceeded a specified threshold, the IDI platform takes the appropriate action according to configured automation rules. When loading/rerating of usage fails, the IDI platform does not send notifications until the error has been resolved, loading/rerating is successfully completed and the job is run again (either wait for the next iteration or manually via clerk/service request).

This example illustrates how usage is monitored and compared to configurable thresholds, where notification thresholds are set at 80%, 90% and 100%, and monthly allotment = 100 units. Unused units from bill periods 1 and 2 are rolled over and added to the remaining totals for bill periods 2 and 3 respectively. In bill period 3, by mid-month the subscriber has already used 80% and so a notification is sent. Two days later, the usage reaches 90% so a second notification is sent. By 7/22 the subscriber has used 100% so a notification is sent and overage is charged.

| Units Count | Bill Period 1 (May) | Bill Period 2 (June) | Bill Period 3 Thru July 15 | Bill Period 3 Thru July 17 | Bill Period 3 Thru July 22 |
| --- | --- | --- | --- | --- | --- |
| Recurring Allotment | 100 | 100 | 100 | 100 | 100 |
| Roll Over | 0 | 25 | 35 | 35 | 35 |
| Used | 75 | 90 | 108 | 121.5 | 135 |
| Remaining Raw Units | 25 | 35 | 27 | 13.5 | 0 |
| % Used | 75% | 72% | 80% | 90% | 100% |

This example illustrates the operation of the configurable wait period. In this case the wait period = 7 days. In bill period 3, by mid-month the subscriber has used 80% and so a notification is sent. Two days later, the usage is still at 80%. Since the wait period has not expired, a second notification is not sent. On 7/22 usage is still at 80% and the wait period has expired so a second notification is sent.

| Units Count | Bill Period 1 (May) | Bill Period 2 (June) | Bill Period 3 Thru July 15 | Bill Period 3 Thru July 17 | Bill Period 3 Thru July 22 |
| --- | --- | --- | --- | --- | --- |
| Recurring Allotment | 100 | 100 | 100 | 100 | 100 |
| Roll Over | 0 | 25 | 35 | 35 | 35 |
| Used | 75 | 90 | 108 | 108 | 108 |
| Remaining Raw Units | 25 | 35 | 27 | 27 | 27 |
| % Used | 75% | 72% | 80% | 80% | 80% |