Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!



 

Home > Aria Crescendo Documentation > User Self-service Best Practices > Add Multiple Plans Immediately with Different Billing Intervals

Add Multiple Plans Immediately with Different Billing Intervals

This article applies to:Aria Crescendo

Overview

If you have a customer who wants to purchase more than one plan (product), you can assign plans at the same time by calling the update_acct_plan_multi_m API once instead of calling separate APIs to assign one plan at a time. The structure of the update_acct_plan_multi_m API is described in this walkthrough.

 

Notes: 

  • Using the update_acct_plan_multi_m API will allow you to complete many updates in one call to avoid a lot of back and forth traffic between your system and Aria.
  • Aria recommends using lighter weight APIs (such as assign_acct_plan_m) that provide fewer details and may provide better performance by reducing the load on your system. This is a more incremental approach that involves calling a series of APIs to complete separate actions instead of completing multiple actions at the same time using 1 API.

    Example: Instead of calling the update_acct_plan_multi_m API to assign 3 plans at the same time as shown in the sample call below, you can call the assign_acct_plan_m API 3 times in a row to assign those same 3 plans separately, as briefly described here:
    • Assign a new master plan (MP) and align its anniversary date with that of pre-existing MP by passing the plan instance number of the pre-existing MP into the <override_dates_mp_instance_no> field.
    • Then assign 2 new supplemental plans and specify that they should be associated with the newly-assigned MP by passing the plan instance number of that MP into the <parent_plan_instance_no> field.

 

Depending on your product structure, you might have plans with different billing periods. You may decide that, to avoid billing the customer on too many different dates, you want to align the billing dates of the new plans with the billing date of an existing master plan on the account.

You may also want to prorate the charges for the new plans if you assigned them in the middle of an existing billing period.

In the sample call shown below, for demonstration purposes, we will use the update_acct_plan_multi_m API to assign these plans that will go into effect immediately: an annual master plan, a quarterly supplemental plan, and a monthly supplemental plan.

 

Instructions

Sample Call

A. Complete the prerequisites

  1. Authenticate the customer logging into your user self-service (USS) application by calling the set_session_auth_m API.
  2. Call the get_acct_details_all_m API to obtain the customer's billing group and dunning group information. 
  3. Call the get_client_plans_basic_m API to obtain the plans that the customer can add.

B. Call the update_acct_plan_multi_m API as follows:

  1. Pass in your client number and authorization key:
    <lit:client_no>12345_sample_client_no</lit:client_no>
    <lit:auth_key>AbCdEfG_sample_auth_key</lit:auth_key>
  2. Identify the customer who is adding plans by passing in the customer's account number as shown below:
     <lit:acct_no>3374227</lit:acct_no>
    
  1. In the first <plan_updates> array, pass in arguments as described below to assign the first plan. In this example, we will assign an annual master plan first.
  1. Specify the action that you want to take on the plan. In this example, we will pass "1" into the <plan_directive> field, which means that we are assigning the plan.
    <lit:plan_directive>1</lit:plan_directive>
    
  1. Pass in your chosen plan identifier that you can use to reference the master plan multiple times in this call. In this example, we will pass "1" into the <plan_instance_idx> field to identify the master plan being assigned. This identifier will then be passed into additional fields described below to associate the supplemental plans with this master plan.
     <lit:plan_instance_idx>1</lit:plan_instance_idx>
    
  1. Identify the new master plan to be assigned as shown below. Pass the plan identifier into the <new_plan_no> or   <new_client_plan_id> field.

    Obtain the identifier of the new plan from the <plan_no> field returned by the get_client_plans_basic_m API.

Note: Pass in the master plan before the supplemental plan, as shown below. That way you won't get an error because you tried to assign a supplemental plan before its corresponding master plan.

  • 
                   <lit:new_plan_no>161832</lit:new_plan_no>
                   <lit:new_client_plan_id></lit:new_client_plan_id>
    
  1. Identify the quantity of the new product that the customer wants to purchase as shown below. Pass the requested number of plan units into the <plan_units> field.
    <lit:plan_units>1</lit:plan_units>
    
  1. Specify the status that the new plan should be in as shown below. In this example, the plan status is active (1).
           <lit:plan_status_cd>1</lit:plan_status_cd>
    
  • Specify the billing group to be associated with the new plan as shown below:

    This will ensure that payments for the new plan are made using the payment method associated with that billing group.

    Obtain the billing group identifier from the <billing_group_no> or <client_billing_group_id>  field returned by the get_acct_details_all_m API.
      <lit:billing_group_no>1598765</lit:billing_group_no>
    
  1. Specify the dunning group to be associated with the new plan as shown below.

    This will ensure that if the customer is behind on payments for this new plan, Aria will take actions on the account as you specified in the dunning process associated with that dunning group.

    Obtain the dunning group identifier from the <dunning_group_no> or <client_dunning_group_id> field returned by the get_acct_details_all_m API.
     <lit:dunning_group_no>1751952</lit:dunning_group_no>
    

For your reference, all of the fields passed into the first <plan_updates> array, in this example, are shown together below:

clipboard_e813c442bb2a7e2a364851f4f627960b8.png

  1. In the second and third <plan_updates> arrays, pass in arguments as described below to assign additional plans. In this example, we will assign a quarterly supplemental plan and a monthly supplemental plan.
  1. Specify the action that you want to take on the plan. In this example, we will pass "1" into the <plan_directive> field, which means that we are assigning the plan.
    <lit:plan_directive>1</lit:plan_directive>
    
  1. Identify the new supplemental plan to be assigned as shown below. Pass the plan identifier into the <new_plan_no> or  <new_client_plan_id> field.

    Obtain the identifier of the new plan from the <plan_no> field returned by the get_client_plans_basic_m API.
     <lit:new_plan_no>139819</lit:new_plan_no>
     <lit:new_client_plan_id></lit:new_client_plan_id>
    
  1. Identify the quantity of the new product that the customer wants to purchase as shown below. Pass the requested number of plan units into the <plan_units> field.
    <lit:plan_units>1</lit:plan_units>
    
  • Specify the master plan with which the supplemental plan should be associated as shown below. Find the identifier that you passed into the <plan_instance_idx> field in the first <plan_updates> array and pass it into the <parent_plan_instance_idx> field.
     <lit:parent_plan_instance_idx>1</lit:parent_plan_instance_idx>
    
  1. Specify the status that the new supplemental plan should be in as shown below. In this example, the plan status is active (1).
           <lit:plan_status_cd>1</lit:plan_status_cd>
    

For your reference, all of the fields passed into the second and third <plan_updates> arrays, in this example, are shown together below:

clipboard_e2b6d3fbe4b9580f09c7cc85706746aaa.png

  1. Pass in the following additional arguments:
  • Specify when the three new plan assignments should take place and which proration rule should be applied as shown below. In this example, we will set the <assignment_directive> to "4", which means that the three plans will go into effect immediately with a prorated invoice.

Notes:

  • If you do not pass in an <assignment_directive>, then by default:
    • A new master plan will go into effect on the day on which you called the API (current date).
    • A new supplemental plan will go into effect on the corresponding master plan's next anniversary date (plus the number of billing periods that you passed into the  <offset_interval> field, if any).
  • The proration rule that you specify will match or override your Invoicing Options On New Master Plan Assignment parameter (in the Aria application under Configuration > Billing > Invoice Settings).
  • <lit:assignment_directive>4</lit:assignment_directive>
    
  1. Specify whether to align the new master plan's anniversary date with any existing master plan's anniversary date as shown below. In this example, we will align the new master plan's anniversary date with the anniversary date of master plan instance number "4251245". To do so, we will pass that number into the <override_dates_mp_instance_no> field.

Note: If you do not pass in an <override_dates_mp_instance_no> then, by default, the anniversary date of the new master plan will be set to the plan assignment date (current date or your specified future date or retroactive date).

  •   <override_dates_mp_instance_no>4251245<override_dates_mp_instance_no>
    
  1. Specify which proration rule should be applied as shown below. This additional input is required if you want a prorated invoice and the plan assignment will not take place in the future. In this example, we will pass "2" into to the <invoicing_option> field, which means that prorated invoicing will be performed.

Note: The proration rule that you specify will match or override your client setting for proration.

  • <lit:invoicing_option>2</lit:invoicing_option>
    

For your reference, all of the additional fields passed into the API, in this example, are shown together below:

clipboard_ea37f245401ce2001e1205419fd15de30.png

 

Sample Response

You can check the customer's account in the Aria application to confirm that the plan additions were completed correctly as described in the use case above.

clipboard_e4858fdc724372f5ee239831090e33890.png

clipboard_ed4cd8bfc84bc2ce8460aaa6fc10082a0.png

clipboard_e62067f5ffd1eacb5e305f8deecb45d29.png

clipboard_e2d71f1429d7b7ae85c01e861292f58fe.png

clipboard_e5b6e6f9ca3953c0f63d7c7c0b35db0b8.png

 

Note: On the new master plan's anniversary date, Aria will create a full invoice for all three plans. Then Aria will bill the customer monthly, quarterly, and annually based on each plan's billing interval.

Example: You assigned the three plans on 17 May 2019. You aligned the master plan's anniversary date with a previously-assigned master plan whose anniversary date is on the 16th. Aria will create invoices for the new plans as follows:

  • prorated invoice for all three new plans covering 17 May 2019 to 15 June 2019;
  • full invoice created on 16 June 2019 for all three plans (covering 1 year for the annual plan, 3 months for the quarterly plan, and 1 month for the monthly plan);
  • full invoice created on 16 July 2019 for only the monthly plan (and, for the monthly plan, on the 16th of every month after that);
  • full invoice created on 16 September 2019 for only the new monthly and quarterly plans (and for quarterly plan, on the 16th of the month, every 3 months after that);
  • if the customer renews all 3 plans, full invoice created on 16 June 2020 for all three plans (covering 1 year for the annual plan, 3 months for the quarterly plan, and 1 month for the monthly plan). 

 


Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.