General Information

While transitioning to BriteCore your renewals will be converted one month at a time. During that period you will have policies expiring in your legacy system and renewing into BriteCore. On occasion, you may need to either cancel or issue a cancellation notice on a policy that is in the transition phase.


BriteCore Processing

The below workflow summarizes actions to take when a policy in the process of being converted is to be canceled prior to its effective date in BriteCore. Click on the image below to open in a new window. Access the raw file here.


How-Tos

Canceling an Uncommitted Policy
Canceling a Committed Policy When No Documents Have Been Mailed
Canceling a Committed Policy When the Renewal Declaration and Invoice Have Been Mailed but the Effective Date of the Policy Is in the Future
Canceling a Policy that is Non-Renewed in Your Legacy System
CPing a Committed Policy When the Effective Date Is in the Future

Canceling an Uncommitted Policy

  1. Issue the cancellation in your legacy system
  2. In BriteCore, set the policy status to Rejected
    • Do not click the X on the policy search as this will permanently delete the policy
  3. If the policy is reinstated in your legacy system, change the policy status back to Active then commit the policy
  4. If the policy is not reinstated in your legacy system by its expiration date, feel free to click the X on the policy search in BriteCore to permanently delete the policy; otherwise, leave the policy set as Rejected

Canceling a Committed Policy When No Documents Have Been Mailed

  1. Issue the cancellation in your legacy system
  2. Cancel the policy flat in BriteCore using the Cancel Policy button
  3. In Attachments, set all deliverables to Do not print
  4. If you are certain the policy will never be reinstated, archive the policy by clicking the X on the policy search. This is so the policy isn’t counted among cancellation numbers (e.g., MCAS). You can search for archived policies using the structure <<ARCHIVE>>policy number, so <<ARCHIVE>>10-2014-1

Canceling a Committed Policy When the Renewal Declaration and Invoice Have Been Mailed but the Effective Date of the Policy Is in the Future

  1. Issue the cancellation in your legacy system
  2. Cancel the policy flat in BriteCore using the Cancel Policy button
  3. Issue any necessary cancellation paperwork
  4. If you are certain the policy will never be reinstated, archive the policy by clicking the X on the policy search. This is so the policy isn’t counted among cancellation numbers (e.g., MCAS). You can search for archived policies using the structure <<ARCHIVE>>policy number, so <<ARCHIVE>>10-2014-1
    If you use InsVista, do not archive the policy until after the InsVista notice has been sent

Canceling a Policy that Is Non-Renewed in Your Legacy System

Retaining the Data for Future Use

In BriteCore, set the policy status to Rejected.

Deleting the Data Permanently

  1. Verify this is the correct action as the data cannot be retrieved once deleted
  2. Click the X on the policy search to permanently delete the policy

CPing a Committed Policy When the Effective Date Is in the Future

  1. Create a custom Notice of Cancellation deliverable using the {cancellation_date} HTML tag
  2. Ensure the appropriate parties receive the deliverable (e.g., insured, agent)
  3. Submit a ticket to IWS
    • (IWS only) In the revisions table, manually set the revisions.policyStatus to Cancellation Pending and enter the correct revisions.cancelDate
    • (IWS only) Generate the custom deliverable
  4. Once the ticket is addressed, mail the custom deliverable

Feedback

Report unclear or missing documentation.