Change to treatment of overrides in sum rules

Scenario

Purchases in CloudBilling can have Overrides for the Unit Price, Unit Cost, and Total Purchase Price. The Override Unit Price and the Override Unit Cost were ignored when passed to aggregating pricing rules (e.g. SUM, LADDER, GROUP PRICE). The quantities of the purchases were, at the same time, not taken into consideration by the aggregating pricing rules.

The change now enforces the overrides to be handled explicitly, by the use of a PRICE pricing rule. 

Reason

Before this change, if a purchase with an override price or cost went into a sum rule without first passing through a price rule, the sum rule would simply take over the override price and cost of the purchase. This is not neccesarily correct for the price and almost certainly incorrect for the Override Cost (because the quantity is not considered). This may result in incorrect values or costs on your invoice.

What has been changed?

Aggregating pricing rules (e.g. SUM, LADDER, GROUP PRICE) will now not allow the input of Overrides on purchases, as this is very likely incorrect behaviour and will result in unexpected results on the invoice.

To make sure the abovementioned scenario does not occur unbeknownst to you, it will now cause an error on the invoice, enabling you to address the issue.

How does this functionality work?

When a purchase with an override price or cost goes into an aggregating pricing rule without first passing through a price rule, the invoice gets an 'Error' status. If you hover over the 'Error', it will show the text 'CalculatedError'.

How can you start using this functionality?

First verify internally why the overrides are used, what is the expected outcome of the use of the overrides on the purchases.

• If the override is needed, the pricing plan might need to change as it is currently not functioning as expected.
• If the override is not needed, the purchases should not specify an override, as it is not used in the pricing plan. 
• If the override is not needed, but it still needs to be specified, please contact support.

This change has been deployed in June of 2023 and is active on your environment. If you encounter the abovementioned error, please send in a ticket to support@cloudbilling.nl and we will address the issue.