Recurrent Monetary Balance
The Recurrent Monetary Balance in the OCS.io is designed to track and manage the allocation of funds for a specific type of usage, such as calls to off-net destinations. It provides flexibility in configuring the balance’s validity period, rollover options, and notifications to ensure efficient utilization of the allocated resources in real-time.
Key features of the Recurrent Monetary Balance functionality include:
-
Validity Period Configuration: Service providers can define the validity period, specifying how long the allocated funds remain active and available for usage. For example, funds for calls to off-net destinations can be valid for a specific time frame, such as 30 days from the activation or renewal date.
-
Rollover Options: Service providers can configure whether unconsumed funds are rolled over to the next period and, if so, for how long. This allows customers to carry forward unused funds and maximize their usage over an extended period.
-
Priority of Consumption: In cases where rollover funds are available, service providers can set the priority of consumption for rolled-over funds. For example, they can prioritize the usage of newly allocated funds before utilizing any carried-forward funds, ensuring that customers fully utilize the most recent allocations first.
-
Threshold-Based Notifications: The system allows the configuration of up to three independent notifications based on predefined threshold levels, such as 0%, 80%, and 100% utilization. These notifications can be delivered via various channels, such as SMS or email, helping customers stay informed about their usage and make informed decisions.
-
Real-Time Monitoring: The system provides real-time monitoring of the balance, ensuring that any usage is immediately reflected in the balance. This allows for accurate and up-to-date tracking of the available funds.
Configuration in the GUI
This section describes the configuration of the Recurrent Monetary Balance in the GUI.

Item | Description | ||
---|---|---|---|
Create Balance At |
Chose when recurrence occurs:
|
||
Every X (Recurrence Period) |
Enter the length of the Recurrence Period. |
||
Execute immediately |
If checked, Balance is applied immediately. If not checked, Balance is applied from the next Recurrence Period. |
||
Pro-Rate when Activated |
If checked, Balance is Pro-Rated. This is applicable when the state becomes Active for the first time. |
||
Pro-Rate when Not Charged |
If checked, Balance is Pro-Rated. This is applicable only for the Suspended state when the appropriate State Reason is flagged as Charged. |
||
Pro-Rate Mode |
Choose how Pro-Rate functionality behaves:
|
||
Recurrence Cycles |
Enter the number of Recurrence cycles for which Balance is applied. |
||
Granted Balance |
Enter Balance which will be granted. |
||
Tax Included |
If checked, Balance is inclusive Tax. |
||
Reject when 100% Threshold reached |
If checked, charging of event will be rejected when 100% threshold is reached.
|
||
First Usage |
If checked, the First usage Notification will be triggered. |
||
On Recurrence |
If checked, the On Recurrence Notification will be triggered. |
||
Threshold #1 (%) |
If a value is provided, the Threshold #1 Notification will be triggered when the defined threshold is reached. |
||
Threshold #2 (%) |
If a value is provided, the Threshold #2 Notification will be triggered when the defined threshold is reached. |
||
Threshold #3 (%) |
If a value is provided, the Threshold #3 Notification will be triggered when the defined threshold is reached. |
||
Recurrent Balance Roll Over |
Choose if and how unused Balance will be rolled over to next period. Possible values are:
|
||
Roll Over Cycles |
Enter the number of cycles how long unused Balance will be rolled over. |
||
Include sub-classes |
If checked, subordinate Charging Classes will be included in the evaluation of Balance application. |
||
List of Charging Classes |
Check all Charging Classes for which Balance will be applied. |