Search Engine: Elastic

Article ID: 115488, created on Feb 1, 2013, last review on May 1, 2014

  • Applies to:
  • Business Automation 5.5
  • Business Automation 5.4


  • PBA version is 5.4.0 - 5.4.15 or PBA version 5.5.0-5.5.1;
  • renewal orders for some of the subscriptions created one day later than expected.

An example:

A subscription expiration date is set to October 16, 2012, and the subscription is configured to be automatically renewed 1 day before the expiration date. However, PBA did not generate a renewal order for the subscription when the Daily Billing Process was run on October 15, 2012, it was only generated on October 16.


In the affected PBA versions (see in the symptoms) the following formula is used to check if it is necessary to automatically renew a subscription with the Renew Point set to X days before expiration:

ExpirationDate < Current Date + RenewOrderInterval (in days) + 20 hours


ExpirationDate - The subscription expiration date
CurrentDate - Midnight of the day when Daily Billing Process is run. For example, if the Daily Billing Process is run on Feb. 11, 2013 at 04:00:00, the CurrentDate will be Feb. 11, 2013 00:00:00.
RenewOrderInterval (in days) - Renew Point in days configured in the subscription properties

Note: All dates above are Unix time stamps.

If the expression above is true, the Daily Billing Process generates a renewal order for the subscription.

All subscriptions provisioned late in the evening (and which, therefore, have expiration dates set to late evening) are renewed one day later than expected.


To avoid the issue, update to PBA 5.4.16/PBA 5.5.2 or above, where the issue is fixed.

92711db0799e8aefe8e51f12dace0496 caea8340e2d186a540518d08602aa065 198398b282069eaf2d94a6af87dcb3ff 210d017ddc3a076d22f0f865b1cf0730 801221f8cd76fba7300d1e6817c8e08b e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF