Home > Aria6 User Documentation > Best Practices > Account Registration > Registering Parent-Child Accounts > Registering a Child Account with Responsibility Level 2, 3, or 4 for a Paid Plan after the Parent Account was Created with Matching Parent and Child Billing Dates – Credit Card or Electronic Check (ACH)

Registering a Child Account with Responsibility Level 2, 3, or 4 for a Paid Plan after the Parent Account was Created with Matching Parent and Child Billing Dates – Credit Card or Electronic Check (ACH)

Overview

Follow this process to register a child account with responsibility level 2 for a paid plan after the parent account was created. In this use case, the child account’s billing date is the same as the parent account’s billing date:

  1. Create the child account.
  2. Generate a pending invoice for the child account.
  3. Approve the pending invoice for the child account.
  4. On the parent account holder’s billing date:
    1. Collect the payment from the parent account holder.
    2. Send the statement to the parent account holder.

Assumptions

The process described in this flow for registering a child account with responsibility level 2, 3, or 4 for a paid plan after the parent account was created deals with:

  • Creating an account with no orders.
  • Making the child account’s billing date the same as the parent account’s billing date.

Note: If the parent account holder is using the electronic check payment method, funds might not be available in the customer’s bank account when the collection transaction is settled.

Preconditions

  • To automatically collect a payment from a customer after a pending invoice is approved, set this option to True in Aria6:
    • Auto Collect On Pending Invoice Approval.
  • To automatically send a statement to a customer after a pending invoice is approved, set this option to True in Aria6:
    • Auto Send Statement On Pending Invoice Approval.

Postconditions

At the end of the account registration process described in the credit card payment flow for paid plans when the billing date is the same as the account creation date, the following results are achieved:

  • One or more new child accounts exist.
  • If you enabled the option in AdminTools to automatically collect a payment from a customer after a pending invoice is approved, a payment is collected from the parent account holder.
  • If you enabled the option in AdminTools to automatically send a statement after a pending invoice is approved, the parent account holder receives a statement.

Process Flow Diagram

The diagram below illustrates the recommended process for registering a child account with responsibility level 2 for a paid plan after the parent account was created with matching parent and child billing dates:

flow-diagram1.png

Note: Call the create_acct_complete, gen_invoice, get_invoice_details, and manage_pending_invoice
APIs again for each additional child account that the customer added.

The dark grey boxes indicate functions automatically performed by Aria.

Follow the steps below to create a child account for paid plans with responsibility level 2 for a paid plan after the parent account was created:

Step 1: Use the create_acct_complete call to create a child account.

Precondition: A customer visits your website to create a child account with responsibility level 2 after the parent account was already created.

  1. Set the client_no field to your Aria‐assigned ID number.
  2. Set the auth_key field to your Aria‐assigned authorization key.
  3. Set the do_full_invoicing field to false. This prevents the account from being invoiced at this point.
  4. Set the resp_level_cd field to 2, 3, or 4.
  5. Set the senior_acct_no field to the account number of the parent account.
  6. Set the master_plan_no field to the number of the master plan that the customer selected for the child account.
  7. If the status in the master plan is not billable, set the status_cd field to a billable status. Refer to the status_cd legend in the API create_acct_complete documentation for the list of account statuses.
  8. Set the userid field to the customer’s user ID.
  9. Set the password field to the customer’s password.
  10. Set additional fields based on your company’s requirements.

Postcondition: The account is created and an account number is returned.


Step 2: Use the gen_invoice API call to match the parent and child billing dates and generate a prorated, pending invoice for the child account.

Preconditions:

  • A child account exists.
  • An account number for the child account was returned by the create_acct_complete call that you can pass into the gen_invoice call.
  • The child account is in a billable status.
  1. Set the client_no field to your Aria‐assigned ID number.
  2. Set the auth_key field to your Aria‐assigned authorization key.
  3. Set the acct_no field to the account number returned by the create_acct_complete call.
  4. Set the alt_bill_day field to the day of the month on which the child account should be billed. This billing date must be the same as the parent account’s billing date.

Examples:

  • If the child account creation date is 11/1/15 and the parent account is billed on the 19th of every month, set this field to 19. Because a prorated invoice is created, the child account is billed for a period from 11/1/15 to 11/18/15, then from 11/19/15 to 12/18/16, etc.
  • If the child account creation date is 11/21/15 and the parent account is billed on the 20th of every month, set this field to 20. Because a prorated invoice is created, the child account is billed for a period from 11/21/15 to 12/19/15, then from 12/20/15 to 1/19/16, etc.
  1. Set the force_pending field to true.

Note: If the pending invoices option is set to false in your Aria implementation, the API call
overrides the setting in your Aria implementation.

Postconditions:

  • A pending invoice is generated for the prorated amount. When an invoice is pending, a collection is not attempted.
  • An invoice number is returned. 


Step 3: The get_invoice_details API call obtains the details of the invoice for customer confirmation.

Precondition: An invoice number was returned by the gen_invoice call.

  • Set the client_no field to your Aria‐assigned ID number.
  • Set the auth_key field to your Aria‐assigned authorization key.
  • Set the acct_no field to the account number returned by the create_acct_complete call.
  • Set the src_transaction_id field to the invoice number returned by the gen_invoice call.

Postconditions:

  • The invoice details are returned.
  • The customer confirmed the account, plan, and invoice information.

Step 4: Repeat Steps 1‐3 for each additional child account that the customer added.

Step 5: If the customer added multiple child accounts, obtain the total combined balance of all the child
accounts for customer confirmation.

Step 6: Use the manage_pending_invoice call to approve the pending invoice.

Preconditions:

  • The customer confirmed the account, plan, and invoice information.
  • A pending invoice was generated by the gen_invoice call.
  1. Set the client_no field to your Aria‐assigned ID number.
  2. Set the auth_key field to your Aria‐assigned authorization key.
  3. Set the invoice_no field to the invoice number returned by the gen_invoice call.
  4. Set the action_directive field to 1 to approve the pending invoice.
Postconditions:
  • The pending invoice is approved.
  • The balance due on the child account’s invoice is transferred to the parent account.

Step 7: Repeat Step 6 for each additional child account that the customer added.

Step 8: The Auto Collect On Pending Invoice Approval option in Aria6 collects the payment from the parent account holder on that account’s billing date.

Preconditions:

  • The Auto Collect On Pending Invoice Approval option in Aria6 is set to True.
  • The pending invoice was approved.

Postcondition: The payment is collected from the parent account holder.

Step 9: The Auto Send Statement On Pending Invoice Approval option in AdminTools sends the statement to the parent account holder.

Preconditions:

  • The Auto Send Statement On Pending Invoice Approval option in Aria6 is set to True.
  • The pending invoice was approved.

Postcondition: The statement is sent to the parent account holder’s billing email address.

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.