Create an Account with a Future Plan Assignment and a Queued Rate Change

Last updated
Save as PDF

Overview

You can create an account with a future plan activation date (assignment) if:

You have a customer who wants service to start on a date after the account creation date; or

You first need to complete processes such as these:
- Install equipment; or
- Screen/obtain confirmation from the customer.

You can optionally assign the customer a rate schedule different from the default rate schedule. Be sure to assign your chosen rate schedule that will be in effect on the future activation date.
Example: For business reasons, you may want to ensure that a customer is assigned a specific rate schedule that you plan to charge at a future date.

To create an account with a future plan activation date and a queued rate change, pass values into the create_acct_complete_m API as shown in the sample call below.

Note: Please see Account Registration Best Practices for important notes about queuing rate schedule changes, additional use cases, and other information about creating accounts.

Instructions

Sample Call

Call the create_acct_complete_m API using the fields in the basic registration use case.

Pass values into the additional fields in the create_acct_complete_m API identified below.
In this example, we will:

Create an account on 10 October 2020 with a plan activation date of 10 November 2020.
Assign a rate schedule that is set to change from $40 to $45 on 14 October 2020.

Note:

The <alt_start_date> that you pass in cannot be more than one billing cycle into the future.
You cannot use <alt_start_date> and <alt_bill_day> in the same call.
When you create an account with a future plan assignment, ensure that the desired rate schedule is active on the plan activation date. The customer will be charged the rate that is active on the plan activation date. Please see Account Registration Best Practices for more important notes about queuing rate schedule changes.

Sample Response

You can use the <acct_no> returned by the API to search for the customer in the Aria application and confirm that the account was created correctly as described in the use case above.

Note: In this example:

We created an account on 10 October 2020 with a plan activation date of 10 November 2020.
We assigned a rate schedule that was set to change from $40 to $45 on 14 October 2020.
On the plan activation date (10 November 2020), Aria will bill the customer $45 since that rate was in effect on 10 November 2020.