Create Out of Sequence Policy Endorsement

Perform a backdated change on a policy in the past, current, or future policy term, even when another policy version with an effective date later than the endorsement date already exists. The impacted policy versions are canceled and replaced with new, repriced versions that include the change. The premium impact for each affected policy term is captured in an individual out-of-sequence endorsement transaction.

Make sure you have the following details.

Policy ID of the active insurance policy to be endorsed.
Effective date for the endorsement must fall within a valid policy term.
(Optional) FieldSetIds to copy selected fields (policy, asset, participant, coverage) from cancelled versions to the new versions.

Example

If a policy has three active versions (V1, V2, and V3) within a single term, and you need to make a change from an effective date which lies in the tenure of V2. You can prepare the context for out-of-sequence endorsement using the Rating API. Get the context from policy V2 and pass this context to the patch rating API. Make additions, deletions, or updates to generate an updated context and then pass this context to out-of-sequence endorsement request.

This diagram outlines the sequence for creating an out-of-sequence policy endorsement without using a quote.

oose_without_quote

Get Policy Context—Use the policy ID to get the context either by:
- Making a GET request on the Insurance Policy Details Connect API, or
- Using the Get Insurance Policy invocable action.
Generate Price-Adjusted Context—Use the context ID and make a PATCH request on the Insurance Product Ratings Connect API.
- Modify coverages, limits, or deductibles in the payload.
The returned context includes updated premiums and tax details.
Submit out of sequence endorsement request—Use the retrieved context to endorse a policy either by:
- Making a POST request on the Out-of-Sequence Endorsement Connect API, or
- Using the Create Out of Sequence Policy Endorsement invocable action.
Specify the policyId, contextId, effectiveDate and transaction details during the API call.

The request returns a jobIdentifier that you can use to track the async process through a custom report.
- Identifies and fetches the impacted policy versions.
- Locks impacted policy versions to prevent any other operation on the impacted policies when the OOSE request is in progress.
- Applies deltas (add, update, delete) across all impacted versions and reprices the context.
- Unlocks the impacted policy versions and sends a success or failure notification.
- Publishes a platform event that subscribers can use for tracking status.

Expected Results:

Creates a new policy starting from the effective date of the OOSE endorsement.
Cancels impacted future versions and replaces them with updated versions.
Sets the effective-to date of older versions to endorsementDate – 1 and resets the term premiums and taxes to zero.
Recalculates premiums and taxes on the new versions and prorates them based on the endorsement date.
Creates a transaction record for each policy term and links it to the original policy version of that term for auditing and financial tracking.