Newer Version Available

This content describes an older version of this product. View Latest

Issue Multi-Root Policy

The policy issuance process begins after the policyholder accepts the quote provided by the insurance company. This process creates a parent–child insurance policy structure in which a parent policy serves as a lifecycle container for one or more insured child policies.

Make sure you have these details before issuing a multi-root policy:

  • The Quote ID of the finalized multi-root quote.
  • A fully priced context to pass to the Multi-Root Policy Issuance API.
  • For multi-root quotes configured through the Quote UI, click the Reprice All button on the Transaction Line Item Table (TLT) after all products are configured to ensure pricing and aggregate amounts are correctly reflected at the quote level.
  1. Create Quote—Create a quote by using one of the following methods
    Creates the quote and generates the quote ID.
  2. Get Quote Context—Retrieve the quote context by using the quote ID through one of the following methods
    Returns the context ID that contains the quote context.
  3. Issue Multi-Root Policy—Use the context details, specifically the context ID, to issue multi-root policy by using one of the following methods
    • You can override the context data, such as policy name, policy number, effective-from date, effective-to date, and any other additional fields, to provide values for the custom fields during the API call. You can also specify a name for the transaction record that’s created as part of the policy issuance process. This transaction record is used for audit tracking and financial reference.
    • Pricing does not occur during this lifecycle event. The context that you pass to this request must already be fully priced.
    • All policy lifecycle operations occur only on the parent policy and not on child policies. The parent policy isn't associated with any product and doesn't have any line items or attributes, except for its associated child policies.
  • Returns an Async Request ID as a response to track the job status.
  • Creates a multi-root policy with the following structure:
    • A parent policy that represents the policy lifecycle.
    • One or more insured child policies, created for each root product bundle and linked to the parent policy.
  • Rolls up premiums and taxes from child policies to the parent policy for a consolidated financial view.
  • Creates a corresponding transaction record for each child policy. In addition, creates a parent policy transaction that represents the rolled-up premium from all associated child policy transactions.
  • Sends a success or failure notification after the process completes.