In the account registration (also referred to as "registration") process, a customer visits your account registration website and signs up for one or more master plans and any chosen supplemental plans using a payment type (electronic or payment terms) accepted by your company. You can create accounts for your customers using the create_acct_complete_m API. This API allows you to assign multiple payment methods, billing groups, and dunning groups to an account.
The structure of the create_acct_complete_m API is described in this walkthrough.
In order to implement the account registration use cases listed below, you must first complete these steps:
- Whitelist your IP addresses.
- Obtain your client number and authorization key.
- Allow statements to be sent to your customers: In the Aria application (under Configuration > Billing > Invoice Settings), set the Suppress Regular Statements parameter to Send.
If the Suppress Regular Statements parameter is set to Suppress, the statements will not be sent.
Note: You can also specify, at the currency level, whether to send or suppress statements.
Queuing Rate Schedule Changes
- Aria will assign a plan's default rate schedule to a plan subscription unless you specify a different rate schedule.
- If rate schedule 1 (RS1) expires on 30 September 2020 and rate schedule 2 (RS2) goes into effect on 1 October 2020, pre-existing accounts with RS1 will not get switched over to RS2 on 1 October 2020. Pre-existing accounts will continue to be charged RS1. You can assign RS2 to new accounts as of 1 October 2020.
- If rate schedule 1 (RS1) switches from $25 to $30 on 1 October 2020, pre-existing accounts with RS1 will be charged $30 as of 1 October 2020. New accounts created as of 1 October 2020 will be charged $30.
- You can assign a rate schedule only if it is available (in effect or not expired) on the plan activation date.
Example: on 30 September 2020, you cannot assign a plan with activation on 30 September 2020 or 15 October 2020 with a rate schedule that will be in effect on 15 October 2020. Use the Schedule Future Rate Change feature if you want to assign a rate schedule that will be in effect at a later date.
- If you create an account with an immediate or a retroactive start date, then the rate that is active at the time of account creation will be applied to the assigned plans.
Example: You have RS1 that will change from $40 to $50 on 12 April 2020:
- If you create an account on 10 April 2020 with a retroactive start date of 1 April 2020 and assign RS1, then the customer will be charged $40 for the first month.
- If you create an account on 16 April 2020, with a retroactive start date of 13 April 2020 and assign RS1, then the customer will be charged $50 for the first month.
- If you create an account with a future plan activation date, then the rate that is active on plan activation date will be used.
Example: You have RS1 that is set to change from $40 to $45 on 14 October 2020. If you create an account on 10 October 2020 with a plan activation date of 10 November 2020 and you assign RS1, the customer will be charged the new rate of $45 on 10 November 2020.
Before implementing the account registration process, it is recommended that you identify these key pieces of information for your company:
Click on any of the links below to see instructions for implementing basic and complex registration uses cases involving a variety of scenarios such as different plan selections or billing options:
- Basic Registration Use Case
- Create an Account with Immediate Activation and a Queued Rate Change
- Create an Account with 2 Master Plans Billed Separately
- Create an Account with a Retroactive Start Date and an Alternate Bill Day
- Create an Account with a Retroactive Start Date and a Queued Rate Change
- Create an Account with a Future Plan Assignment and a Queued Rate Change
- Create an Account with a Future Plan Assignment and a Prorated Invoice
- Create an Account with a Contract and a Destination Contact
For instructions for implementing parent-child account uses cases, please see Parent-Child Account Best Practices.