Rerating of usage in Subscription Billing

[norbertsarfi]

Dear Community,

in the Subscription Billing help page (https://help.sap.com/docs/CLOUD_TO_CASH_OD/e4aa21cd43494cc1a8a90ea0f3dab8bb/73cdd5a0a91a480e868a3349eaab4c95.html?locale=en-US) for rerating it says: "In case an active subscription is updated, the rating results up to this point are reversed, the subscription is rerated, and a new bill is created. The same holds true for changes to a rate plan used in an active subscription ... Changes in an active subscription, or in a rate plan used in a active subscription, require you to resend usage records to manually trigger a rerating."

How exactly is this functionality working? In which case will a new bill created? Example: it turns out that price for a usage has been wrong for a period where the bill is already closed, is it possible to do a rerating with the updated prices (rate plan based on pricing scheme)?

Thanks a lot in advance!

Best regards
Norbert Sarfi

[CarstenJ · Accepted solution]

Dear Norbert,

the rating process reacts on events like changes to subscriptions and rate plans, or creation or updates of usage records.
In case such a change is rating relevant - you can also change subscription data which is irrelevant for rating - the existing rating results are reverted and the new status rated again.
But we need to distinguish between one-time, recurring and usage-based charges and if an already existing bill has been closed or not.

If the bill is still open, the rerating will typically result in an update of the existing bill. However, depending on configuration settings the reverted and newly rated amounts could also lead to a new bill.
For usage-based charges (rating variant Aggregated), which are always billed in arrears, there is currently no creation of a new bill holding the corrected charges.
This is mentioned in the help page https://help.sap.com/docs/CLOUD_TO_CASH_OD/e4aa21cd43494cc1a8a90ea0f3dab8bb/8b99e178ad06409a80868777... (Closing of bills).

This topic is address by one of our roadmap items (Support for late arrival of usage data).

Best regards,

Carsten