Balances
A balance is a quantity of a currency or asset that is used for tracking and charging for service usage and service-related operations, such as recurring cycle fees.
Balance properties are defined in templates, and balance templates are derived from a balance class. You define both balance classes and balance templates during pricing plan creation. When you create a new balance, you must define a credit limit threshold for it. Pricing validation requires a credit limit threshold to be defined within the pricing repository for all balances.
Simple Balances and Meters
Simple balances and meters use one balance or meter instance for the entire validity period of the balance or meter. As rating occurs against the instance, the value can increase and decrease according to the applied charges, discounts, or grants.
When the end date occurs, the instance is no longer valid and cannot be used.
A private balance end date (EndTime) can be modified through the MtxRequestSubscriberTopUpBalance SubMan API. A private balance start date (StartTime) cannot be modified.
For balances, you typically use the effective dates to grant subscribers prepaid assets that expire, but they can also be used for postpaid assets or currencies.
Subscribers and groups can have any number of simple balances in their wallets.
Asset Balances
Assets are financial non-monetary mediums of exchange, such as minutes and megabytes. Both represent a subscriber's liability to a service provider. If Include in Cost is selected in the asset balance, it is reported as a cost balance in SubMan responses and notifications.