Search Engine: Elastic

Article ID: 122382, created on Jul 16, 2014, last review on May 6, 2015

  • Applies to:
  • Business Automation 5.5
  • Business Automation 6.0


According to the PBA-E Providers Guide, the following behavior is expected when Prepaid PACI is enabled:

To prevent the situation when the whole amount of deposit would apply to new orders, causing a debt, the system automatically reserves the amount on customer’s Account Balance. The reserved amount value is calculated as follows:

<Total amount cost> + <Suspend service limit> - <Credit limit>.

Thus the system should not allow to buy new services in a postpaid mode if new Sales Order sum is more than:

Sum of opened payments including deposit (account balance) - Total amount cost (including all Nip and other unpaid orders).

However in certain cases the system allows to buy new services, that cost higher than the difference described above.


During Order processing reservation mechanism detects if Current account's balance (excluding reserved amount) is enough to pay for new order.

  • If yes - the order proceeded and provisioned without creation of new payment.
  • If no - New payment is created.

However if the Order has some of the existing opened payments (for example, deposit fee) attached manually (this can be done from Providers Control Panel before opening the order), reservation mechanism considers that the order has zero balance and does not require new payment creation.


This behavior is by the Product design. In order for reservation mechanism to work correctly while new order is placed, payments should not be attached to such orders manually.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 801221f8cd76fba7300d1e6817c8e08b 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF