|
Caution: Do not modify or delete prepaid accounts with Core Tool when SAP Convergent Charging is integrated with a CRM application or a provisioning system. Creating, modifying, or deleting prepaid accounts may result in inconsistencies between the two systems because of data replication and synchronization mechanisms. Refer to the caution about subscriber accounts. |
A prepaid account is a monetary counter associated to a currency. Funds are placed in the account before the service begins, and then the charges linked to the services consumed by the end customers are debited as much as necessary.
Setting up a prepaid account, Definition tab, Alerts tab.
The balance of an account is defined by a minimal value (threshold). Depending on service providers' requirements, the threshold is usually close to the value of 0. Usage is rejected when the balance reaches the threshold. However, if overspending (refer the note below) is authorized for specific usage, the threshold is ignored, and the usage can be debited from the account even though the balance of the account is less than the threshold.
Crediting a fee to a prepaid account consists in increasing the amount of its balance. Conversely, debiting a fee consists in decreasing the amount of its balance.
It is the minimal value of a balance ensuring that the account is sufficiently funded to pay an account fee, for example, or to reserve money in order to limit the processing error of the vendor. When the threshold is reached, usage or events are rejected.
Prepaid account balances can be connected to expiration and amount alerts.
Depending on the ways you allow the end customers to make a refill (credit pre-purchased or cash advance), taxes may have been paid or not.
The holder of this account can be subject to pay the tax according to the tax settings configured in SAP Convergent Charging.
A prepaid account can be:
Active: The prepaid account is charged depending on how you configure the default or internal reference components in the related charging plan. The prepaid account can be refilled. If overspending is authorized, debiting is possible. You can block, lock, or close an active prepaid account.
Blocked: The prepaid account is charged depending on how you configure the default or internal reference components in the related charging plan. The prepaid account can be refilled. If overspending is authorized, debiting is possible. You can reactivate, lock, or close a blocked prepaid account.
Locked: The prepaid account is charged depending on how you configure the default or internal reference components in the related charging plan. Refills and overruns are authorized. If overspending is authorized, debiting is possible. You can reactivate, block, or close a locked prepaid account.
Closed: The prepaid account is charged depending on how you configure the default or internal reference components in the related charging plan. Refills and overruns are forbidden. Once closed, you cannot change a prepaid account any more.
You can schedule the states of a prepaid account.