Future Rate Versioning

Overview

Rate schedule versioning for Aria Billing Cloud supports accurate invoicing with positive or negative bill lag days. This feature, enabled by a new client parameter, ensures invoices reflect the correct rate schedule version effective at the time of invoice generation, considering future rates set in the product catalog.

This article is currently being drafted for Release 67 of Aria Billing Cloud.

Important Notes

[]

Best Practices

[]

Prerequisites

[]

Use Cases

API-related Proration Support

You can perform various actions on customers' plans using Aria's API. Depending on the type of service on the plan, and dates you specify, plan change APIs can result in proration.

Aria picks rates for proration calculation based on various date fields, depending on which plan change API you are calling. The following table outlines various plan actions and the date fields related to proration for the various service types:

Action	Service Type	Comment (if more than one date present, the precedence is listed in order)
Assign	Recurring	The application will use the below input parameter for picking the rate version, else the application will make use of current plan assignment date a) alt_start_date b) retroactive_start_date c) alt_proration_start_date
	Activation
	Recurring Arrears	The application will use the below input parameter for picking the rate version, else the application will make use of current plan assignment date a) override_bill_thru_date b) override_dates_mp_instance_no/id c) alt_proration_end_date Note: For SP both (a) and (b) are not applicable, instead alt_proration_end_date can be used to override date, but its applicable only for plan instance that is of daily/weekly billing interval type.
	Minimum Fees
Replace	Recurring	The application will use the actual replacement date (current/VT) for picking the rate version. In case the user is passing any of these inputs, then the application will consider it a) alt_proration_start_date
	Activation
	Recurring Arrears	For Old Plan, it will be charged till previous day For New Plan, the application should consider the new plan’s bill thru date for picking the rates. In case the user has passed the below inputs, then the application will consider it for picking the rates. a) alt_proration_end_date—If valid inputs, then the applicaton will consider this input for picking the rate version, but it’s applicable only for plan instance that is of daily/weekly billing interval type.
Update	Recurring	The application will make use of this input “alt_proration_start_date” for determining the rate version, else the application will use the current (VT) for picking the rate version
Update	Recurring Arrears	For update units/rate schedule, the application will consider the bill thru date of the current plan.
Cancel	Recurring Arrears	The application will be calculated till previous date during cancel.
Replace and Cancel	Cancellation	For cancellation service the application will be calculated till previous date during cancel and replace action.
Replace and Cancel	Usage	During cancel and replace the application will rate usage till current timestamp. So, it will be using the current date for picking the rate version