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 Using the Net Terms Payment Method

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 Using the Net Terms Payment Method

This is the recommended process to follow to register a child account with responsibility level 2, 3, or 4 for a paid plan after the parent account was created and with matching parent and child billing dates:

  1. Create the child account.
  2. Generate a pending invoice for the child account.
  3. Approve the pending invoice.
  4. Aria automatically transfers the child account’s balance to the parent account.
  5. Aria automatically sends the statement to the parent account holder.

Assumptions

The process described in the net terms payment 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 a child account with no orders.
  • Making the child account’s billing date the same as the parent account’s billing date.

Preconditions

Use Aria6 to create paid plans. For each paid plan, you must specify the status that an account should have when a customer registers for the plan.

Postconditions

At the end of the account registration process described in the net terms payment flow for registering a child account with responsibility level 2, 3, or 4 for a paid plan after the parent account was created and with matching parent and child billing dates:

  • A new child account exists.
  • The parent account holder receives a statement.

Process Flow Diagram

The diagram below illustrates the recommended process to follow to register a child account with responsibility level 2, 3, or 4 for a paid plan after the parent account was created and with matching parent and child billing dates:

parent-child-flow8.png

Notes

  • Call the create_acct_complete, gen_invoice, and manage_pending_invoice methods again for each additional child account that the customer added.
  • The grey boxes indicate functions automatically performed by Aria.

Instructions

Follow the steps below to register a child account with responsibility level 2, 3, or 4 for a paid plan after the parent account was created and with matching parent and child billing dates:

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

Precondition: A customer using the net terms payment method visits your website to create a child account with responsibility level 2, 3, or 4 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. Leave the status_cd field blank. The account status is automatically set based on the status specified in the plan that the customer selected.
  4. Set the do_full_invoicing field to true.
  5. Set the do_prorated_invoicing field to true.
  6. Set the resp_level_cd field to 2, 3, or 4.
  7. Set the senior_acct_no field to the account number of the parent account.
  8. Set the master_plan_no field to the number of the master plan that the customer selected for the child account.
  9. Set the userid field to the customer’s user ID.
  10. Set the password field to the customer’s password.
  11. 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 call to match the parent and child billing dates and generate a prorated, pending invoice for the child account.

 

Preconditions:

  • A child account was created.
  • An account number for the child account was returned by the create_acct_complete call that you will 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 should 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 19thof 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/15, etc.
  • If the child account creation date is 11/21/15 and the parent account is billed on the 20thof 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:  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. Repeat Steps 1‐2 for each additional child account that the customer added.


Step 4. Use the manage_pending_invoice call to approve the pending invoice generated for the child account.

Preconditions:

  • The customer confirmed account, plan, and invoice information.
  • The gen_invoice call generated a pending invoice for the child account.
  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 used to generate an invoice for the child account.
  4. Set the action_directive field to 1 to approve the pending invoice.

Postconditions:

  • The pending invoice for the child account is approved.
  • The balance of the child invoice is transferred to the parent account.


Step 5. Repeat Step 4 for each additional child account that the customer added.


Step 6. Aria transfers the child account’s balance to parent account.


Step 7. Aria sends the statement to the parent account holder.

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.