Minor bug identified in the approval process/finalizing purchases - August 2024

Modified on Mon, 19 Aug at 2:55 PM

Our development team has found a minor bug in the invoice approval process. This bug may result in missing data on invoices. This issue occurs for recurring purchases on two subsequent invoices that are being approved at the same time. An example of a case in which this could happen can be found below.


Case

  1. There are two open invoices for customer A.
  2. The CloudBilling user selects these two most recent period invoices of customer A to start the approval process.
  3. The user requests approval for these two invoices.
  4. The first one is approved.
  5. The second one (the one of last period) is rejected.
  6. The recurring purchase that should be on both invoices isn't present on the second invoice.


This occurs because the billing engine marks the recurring purchase as finalized when it is on the invoices that it should be on that aren't 'open'. The status Approving is seen as not Open, so the purchase was finalized after putting the two invoices to Approving. By rejecting the second invoice and after recalculting it, the purchase is seen as complete and therefore not included in the second invoice.


Advice

Until a fix is deployed for this issue deployed for this issue, we advice to go through the period invoices each month and to approve or close them per month instead of processing multiple invoices per customer in one go. 


Follow-up

Our product team has identified this bug and is looking for a way to resolve this issue. We will provide an update on the support portal and in our Product Update newsletter as soon as we know when this will be resolved.


In case you have any questions on this bug, please contact [email protected] or submit a ticket via the support portal.






Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article