Enhancement 

Tenants as Contacts. The tenant role is now available in the contacts module, enabling efficient tenant management within policies. A tenant of a location is a business or individual that occupies the space, such as operating a store, living in an apartment, or other activity. Key enhancements include the ability to add and remove tenants to a location, generate PDF Evidence of Insurance (EoI) for tenants, and perform tenant-related actions seamlessly from various modules. When enabled, key enhancements included:

• Property Tab Updates: Within the risk (property) tab of a policy, both individuals and organizations can be added and removed as tenants for each property, streamlining tenant management.
• Tenant Role in Contacts: In the Contacts module, a dedicated tenant role is now available, simplifying the identification and organization of tenants. Users can also search by the tenant role.
• Evidence of Insurance (EoI): Administrators can generate EoI PDFs directly from the policy Administration builder page.
  • When generating EoIs, a property can be selected in the generation dialog box.
  • The generated EoI includes the following fundamental data:
    • Property Address
    • Property Name
    • Tenant Names
    • Start Date (Set to Endorsement Date or Effective Date)
    • End Date (Set to Expiration Date)
  • Please note that EoIs generated are not stored in the system; they are designed for immediate download and use.
• BriteQuote V2: Quote Wizard seamlessly integrates the Tenants as Contacts, allowing agents to:
  • Add tenants to a property
  • Remove tenants from a property
  • Create new tenants

How to Use:

To make use of these enhancements, administrators can access the advanced settings. Here, you will find a setting titled "enable-adding-tenants-to-properties." This setting can be configured on a per-policy type basis, allowing flexibility to tailor the feature as needed. It's important to note that tenants may not be required for all lines of business, so administrators can selectively enable this feature to suit specific policy types (BC-11064).

Email Notification Update for Claim Status "Historical, Reporting Only". BriteCore has made an adjustment to ensure that a change in claim status to "Historical, Reporting Only" will no longer trigger email notifications to the named insured. This update enhances the precision of our notification process by aligning it with the intended status change, providing a more streamlined and accurate experience (BC-12294).

Empowering Administrative Changes to Streamline Policy Endorsements. Carrier employees lacked the ability to modify a policy's status during the endorsement creation process. This limitation hinders agents from progressing with the endorsement after it has been initiated by an administrator.. Now Carrier employees (such as underwriters) have been granted the capability to change the policy state to "unsubmitted." This adjustment streamlined approach to handling policy endorsements (BC-11972).

Defects

Hidden Mandatory Line Items missing in Rating. In response to the identification of a defect where hidden mandatory line items were not being included in the rating process, BriteCore has enhanced the line module to ensure the inclusion of mandatory sub-lines and line items, even when they are hidden from view. This fix leads to a more comprehensive and precise property record, ultimately improving the efficiency of the renewal process (BC-12284).

Timing Issue with 'Notice of Cancellation' Notices Across Policy Types. BriteCore has resolved a timing issue related to 'Notice of Cancellation' notices when selecting the underwriting cancellation reason. This problem was previously noticed in endorsement and renewal situations, where the selection of a cancellation reason and date within the policy administration dialog box did not effectively override the original cancellation timeframe. Britecore is pleased to inform you that this issue has now been rectified (BC-12343).

Issue with endorsement Invoices Impacting Auto-Pay Processing via Invoice Cloud. Clients utilizing Invoice Cloud for payment processing have encountered an issue where endorsement invoices were resulting in a zero due balance within Invoice Cloud, leading to auto-pay withdrawals failing. BriteCore corrected the data being sent to Invoice Cloud so that the endorsement invoices display the correct amount due (BC-12515).

Paperless Invoice Notification Issue with Invoice Cloud: Resolving Date Mismatch. Clients utilizing Invoice Cloud as their payment vendor have experienced an issue concerning paperless email invoice notifications sent to policyholders. Notably, there was an increased incidence of non-payment cancellations and subsequent reinstatements. Upon investigation, it was identified that the paperless email invoice notifications were being dispatched on the due date of the installment or premium payment, rather than the intended invoice date (BC-12307).