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. When policyholders or insurance brokers issue an out-of-sequence policy endorsement, the
changes automatically apply to all future policy versions to maintain consistency.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions of
Digital Insurance Platform
Performing an out-of-sequence endorsement follows the same steps as a normal endorsement. You
request changes to your policy, review the quote, and apply the endorsement. The difference is
that out-of-sequence endorsement also identifies and updates future versions of your policy
that are impacted by the change, based on the effective date you selected.
Supported out-of-sequence-endorsement usecases
Future term policies – Out-of-sequence endorsement applies changes to policies that are
already renewed for a future term. For example, if you add a vehicle to the current policy,
the renewed version also reflects the change.
Past term policies – Out-of-sequence endorsement applies corrections to past versions of a
policy. For example, if you fix an address from a past effective date, the correction
carries forward into all later versions.
How normal endorsements work
When users click Modify Policy in the active policy version, the flow calls the createQuote
IA to generate an endorsement quote. After users update the quote and click Endorse Policy,
the flow calls the endorsePolicy IA to create a new policy version with the applied
changes.
How out-of-sequence endorsements work
OOSE follows the same steps as a normal endorsement. The difference is that changes made with
an effective date earlier than existing versions also impact future versions of the policy.
Users need visibility into these impacted versions before moving forward with an endorsement.
This functionality isn’t available out of the box. A custom flow is required to display the
impacted versions, give users the necessary context before quote creation, and determine
whether the action should use the endorsement invocable action or the OOSE invocable action.
Set Up Out Of Sequence Endorsement Flows Configure flows to support Out-of-Sequence Endorsements (OOSE). Create a Modify Policy flow to show impacted policy versions before generating an endorsement quote, and update the Endorse Policy flow so it calls the correct invocable action depending on whether the endorsement is normal or OOSE.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.