Out-of-sequence changes and policy transactions

PolicyCenter supports out-of-sequence policy transactions. A policy transaction is out-of-sequence if its effective date is earlier than the effective date of another policy transaction that is already bound on the policy for that contractual period. PolicyCenter warns you that the policy transaction is out-of-sequence and prompts you to address any conflicts that occur as a result.

When a policy transaction begins, PolicyCenter checks to see if the transaction is out-of-sequence. The transaction is out-of-sequence if at least one completed transaction on the policy has an edit effective date later than the edit effective date of the current policy transaction. So when you click Start either on the Start Policy Change, Start Cancellation, or Start Reinstatement screens, PolicyCenter displays a confirmation message about the out of sequence change. If you click OK, then the policy transaction starts.

See also

• Out-of-sequence jobs

Out-of-sequence policy transaction combinations

Since there are many different types of policy transactions, it is helpful to know which policy transactions may be out-of-sequence with respect to another. The following table shows all possible pairs of policy transactions. A cell marked in row X and column Y indicates that policy transaction X may be out-of-sequence with respect to policy transaction Y. Policy transaction X may be started and completed even if its edit effective date is earlier than the edit effective date of a previously bound policy transaction Y.

Note the following:

• Cancellation and reinstatement – When you cancel or reinstate a policy, you cannot make additional changes to that policy. Therefore, if a policy transaction is out-of-sequence with respect to a cancellation or reinstatement policy transaction, there are no conflicts to resolve.
• Rewrite – If rewrite is out-of-sequence with respect to renewal, then you receive a warning that the rewrite changes are not applied to the renewal.
• Submissions, issuances, and rewrite new account – Can never be future-bound policy transactions.
• Submissions – Can never be out-of-sequence because no policy exists until a submission is complete.
• Renewals – Can never be out-of-sequence because no other policy transactions with later effective dates can be started until the renewal completes. However, if PolicyCenter promotes a renewal period, then any subsequent policy transaction in the expiring period will always be out-of-sequence with respect to the renewal.
• Audits – Since PolicyCenter never promotes audit branches, they are never in an out-of-sequence relationship.
• Rewrite new account – If rewrite new account is out-of-sequence to another policy transaction, the out-of-sequence policy transaction occurred on the source policy. (Remember that rewrite new account rewrites a source policy to a new target policy on a different account.) That out-of-sequence policy transaction is a transaction on the source policy but not on the target policy. However, both the source and target policies have a slice representing the out-of-sequence policy transaction.