Overview

An orphan LOB policy occurs when a Line of Business (LOB) policy remains linked to a parent monoline policy, causing the parent policy to be restricted by the LOB’s values. This can lead to errors during actions such as renewals if the LOB’s effective and expiration dates do not align with the parent policy. For example, you may see the error: Policy Effective Date must be between its parent Policy's effective and expiration dates.

Common causes

The following are common causes of orphan LOB policies:

• A user enters a monoline policy in the LOB policy’s LOB Parent Policy field. This creates a connection, but because the parent is monoline, the relationship does not appear on the parent policy record.

• A user changes the Policy/Coverage Type of a package policy to a monoline policy without first removing the associated LOBs (for example, changing a Commercial Package policy to a Commercial Property policy while LOBs are still attached). To correctly convert a package policy to a monoline policy, see 📄 Convert an LOB into a monoline policy.

This article explains how to identify orphaned LOB policies and resolve this error if it occurs.

Identifying orphan LOB records

To proactively identify orphan LOB records associated with monoline policies, create a report using the following criteria.

1. Click on Reports.

   

2. Select New Report.

   

3. In the Create Report modal, select All.

   

4. Then, in the Search, enter and select "Policies with LOB's Parent Policy".

   

5. Click on Start Report.

   

6. In Columns, use the Add Column search bar to add the following recommended fields:

   1. Policy: Policy

   2. Policy: Record Type

   3. Effective Date

   4. Expiration Date

   5. LOB's Parent Policy: Policy

   6. LOB's Parent Policy: Record Type

   7. LOB's Parent Policy: Monoline/Package

   8. LOB's Parent Policy: Effective Date

   9. LOB's Parent Policy: Expiration Date

      

7. Select Filters. Then, use Add filter and enter the following:

   

   1. Show Me: All policies

   2. LOB's Parent Policy: Created Date: All time

   3. Policy: Record Type:

      1. In Values, select:

         1. Prospective PL LOB

         2. Prospective CL LOB

         3. Remarket PL LOB

         4. Remarket CL LOB

         5. Written CL LOB

         6. Written PL LOB

      2. Then, click Apply.

         

   4. LOB's Parent Policy: Monoline/Package:

      1. In Values, select Monoline

      2. Then, click Apply.

         

8. Select Run.

   

Resolving effective date errors

If you receive an error on a monoline policy related to an LOB policy, the error message will include the record ID causing the issue.

1. Copy the 18-character ID that appears after:
   “Update failed: first exception on row 0 with id…”
   (Do not include the semicolon.)

2. Paste the ID into your browser after .com/ to open the record.

3. Review the Effective Date and Expiration Date on the LOB policy and confirm they fall outside the renewal policy’s date range.

4. Resolve the issue by either:

   • Updating the LOB policy’s dates to match the renewal policy, or

   • Having a System Admin delete the LOB policy if it is not needed.

After correcting or removing the LOB policy, you should be able to complete the renewal.

Considerations

• LOB policies linked to a monoline parent policy may not appear on the Account record.

• Only a System Administrator can delete policies. Contact your admin if a policy needs to be removed.

• You may not be able to edit the LOB policy dates if the record owner is an inactive user. A System Administrator may need to update the owner or modify the dates.

• If your organization has restricted sharing settings, you may not have access to the policy causing the issue. A System Administrator can help locate or access the record.