Enhancement

Underwriting Subjectivities in BriteCore

Subjectivities are specific conditions or requirements that an insured party must fulfill for their insurance coverage to become effective or remain valid. They are essentially contingencies set by the insurer, often detailed in a quote, binder, or policy document, that must be satisfied before the policy is fully binding or before claims can be paid. When enabled, Subjectivities must be met before a policy can be bound or continue in force. These could include receiving documentation, completing inspections, or meeting specific underwriting criteria. With this release, BriteCore provides a dedicated way to handle these requirements within the system.

Key Capabilities

• Define Subjectivities Users can now create standardized subjectivity definitions through rules that can be reused across policies. Definitions include fields such as name, description, due date, status, and whether the requirement is mandatory.
• Manage Subjectivities in the Policy UI Subjectivities can be added to individual policies through an intuitive interface. Users can easily create, view, modify, and remove requirements directly from the policy screen, streamlining workflows and reducing the need for external tracking.
• Track Completion Status Each subjectivity includes status tracking and can be marked as satisfied once completed. This gives underwriters clear visibility into what’s outstanding before taking further action on a policy.
• Permission Controls A new set of permissions governs access to subjectivity features. This ensures only authorized roles can create or modify subjectivities, maintaining data integrity and operational control.
• Audit & Notes Any action taken on a subjectivity, whether it’s created, modified, or deleted,  is logged automatically in the system. Notes are generated with each update, supporting compliance and transparency.
• Document Integration Subjectivity data is now available for use in custom policy documents and deliverables, allowing these requirements to be clearly communicated to insureds or agents.

Taurus National Flood Services Integration (BC-16460)

BriteCore has launched a new integration with Taurus National Flood Services, enabling agents to offer flood insurance alongside standard policies. This release introduces an embedded user experience that allows agents to access Taurus flood quotes directly from the application and rate screens. The integration includes a dynamic UI that adjusts to user actions, retrieves real-time premiums via Taurus APIs, and supports cross-selling through a streamlined iframe solution. This enhancement empowers agents with seamless access to flood insurance options, improving efficiency and expanding product offerings within the quoting workflow.

Declaration Package (with Forms) as Custom Deliverable (BC-15057)

A new option, "Declarations (with Forms)," has been added to the top of the Custom Deliverable popup on the Policy Information page. This enhancement allows users to easily generate previews or attachments (e.g., PDFs) of the policy declarations page along with all associated forms. The update improves usability and supports client requests for easier access and sharing of complete policy documentation.

Defects

Resolved Issue with IVANS DBCS File Generation (BC-17467)

BriteCore has resolved an issue that prevented IVANS (NxTech) DBCS files from generating and uploading automatically at month-end for several clients. The root cause has been addressed, and updates to the background processing logic ensure these files are now generated and delivered reliably without manual steps.

Improved SSN Validation Logic for Policy Applications (BC-17635)

BriteCore has resolved an issue where Social Security Number (SSN) validation was incorrectly triggered during policy application, even when no credit score vendor was configured. To prevent this issue from recurring, the validation logic has been refined: it will now only apply when legacy ISO or LexisNexis credit score integrations are actively enabled. If no vendor is configured, the SSN validation is skipped entirely. Additionally, for new or custom credit integrations, SSN checks will be handled within the integration itself, eliminating unnecessary validation from the core system and ensuring more accurate, vendor-specific handling.

Claims Import UI and Delimiter Handling Improvements (BC-17740)

BriteCore has released enhancements to the Claims Import functionality, addressing two key issues impacting user experience and file processing. First, validation error messages were overflowing outside the modal window, making them difficult to read. This has been resolved by containing error text within a scrollable modal, improving readability with proper text wrapping, padding, and scroll bar visibility. Second, the system was using the comma character (",") as the delimiter and are now using the semicolon character (";") as the delimiter.This is to ensure compatibility with backend processing, resulting in more reliable and successful file ingestion.

Underwriting cancel shows as non-pay cancellation (BC-17473)

A policy set for underwriting cancellation was incorrectly canceled for non-payment. Specifically, when a non-pay cancellation was also triggered with the same effective date, the system canceled the policy for non-pay instead of the original underwriting reason.

Unable to save coordinates on property page (BC-17514)

This release includes a fix to a UI defect where latitude and longitude values displayed on the Property page were not being saved to the database. Although the coordinates appeared visually, they were not persisted unless the input fields were manually clicked. This issue has been resolved to ensure coordinates are consistently saved, enabling accurate rating without requiring additional user interaction.

Performance degradation for Support Tool (BC-16863)

Addressed performance and reliability issues in the Transfer Agency Policies support tool. Previously, agency transfers experienced excessive delays and, in some cases, failed to complete without confirmation. Enhancements were made to improve processing speed, ensure accurate transfer completion, and provide clearer traceability in system logs. This update ensures large book transfers execute more reliably and transparently.