Enhancements

Update accounting transactions table to aggregate payments (BC-19451)

The BriteCore platform was enhanced to improve the display and management of multiple payments within the accounting transactions table. Previously, the system did not aggregate multiple payments, making it difficult for users to view and reconcile payment details efficiently. This change provides a clearer, more consolidated view for users and simplifies payment reconciliation.

Update payment modal to support multiple coverages (BC-19450)

Users previously could only process a single payment per coverage, limiting flexibility in handling complex claims scenarios. With this update, the user interface was redesigned to allow selection and payment for multiple coverages at once. The enhancement ensures that payments are handled efficiently, accurately reflected in transaction records, and aligned with authority and configuration settings.

Defects

Enhance payee details display in Payment modal (BC-19774)

Britecore has fixed an issue where users encountered challenges identifying the correct payee when multiple parties were associated with a claim, leading to possible confusion or errors in payment selection. The updated implementation introduced clearer labeling and additional contextual information about each payee, such as their relationship to the claim and relevant identifiers. 

Add support for batch endorsement processing (BC-19686)

BriteCore fixed an issue where the Notice of Cancellation was not generated after a policy was put into pending cancellation via the non-pay job process. Now, when a policy is committed (either by an agent or admin copying an existing quote) and the non-pay job process is triggered through the support tools, the system correctly generates the Notice of Cancellation when the policy enters pending cancellation status.

Event-based underwriting rules not triggering when policy is committed (BC-19346)

BriteCore resolved an issue where backend rules related to multiple limits were being triggered incorrectly. This update ensures backend rules now properly handle scenarios involving multiple limits, preventing unintended triggers and improving overall system reliability. Users will experience more accurate backend rule enforcement when working with policies or workflows involving multiple limits. 

ISO Loss History | data retrieved from vendor but not parsed correctly (BC-18963)

BriteCore fixed an issue where ISO Loss History reports from vendors were being retrieved but not parsed correctly, resulting in the UI showing no loss history. The parsing logic was enhanced to detect and process new patterns and additional test cases were added to prevent future regressions. 

BriteQuote Settings - Email required is not being enforced (BC-18398)

BriteCore resolved an issue in BriteQuote settings where enabling the “Email Required” option did not enforce email input validation as part of a quote process. Previously, users could proceed without entering an email address even when the field was set as required. With this fix, the system now correctly enforces the requirement, ensuring that an email address must be provided before continuing with the quoting process.

Agents unable to select new mortgagee (BC-18006)

BriteCore  resolved an issue where agents were unable to select a newly added mortgagee in the billing section when processing endorsement quotes. Previously, only the previous mortgagee was available for selection, which could result in invoices being sent to the wrong party. With this fix, agents can now correctly select new mortgagees, ensuring accurate billing and improved workflow.

Allow None and No Hit to be considered for credit score validation based off the Credit Tier table (BC-16692)

We have enhanced the credit score validation process to better support clients who wish to allow quote submissions when no credit information is returned for the applicant. Previously, applications with a “None” or “No Hit” credit score could not be submitted if a credit score was required, even if the client’s configuration allowed for such cases. With this update, the system now respects the “None” and “No Hit” values in the credit tier table, enabling clients to configure whether these applications can proceed. This change provides greater flexibility and ensures that business is not blocked when credit information is unavailable.

Incorrect reinsurance retention shown on claims accounting overview (BC-15017)

We have enhanced the Claims Accounting process to ensure that reinsurance retention is now selected based on the loss date of a claim. Previously, the system did not always apply the correct reinsurance retention when the loss date fell under a different contract term, which could lead to inaccurate retention amounts being shown. With this update, the appropriate retention is automatically applied according to the loss date, improving both accuracy and compliance in reinsurance processing.

Fix suspensions geometry query (BC-18815)

We fixed an issue where zip code suspensions without an end date were not working correctly in the Quoting Wizard. Previously, suspended zip codes were not highlighted on the map and suspensions could take a long time to load, especially when many zip codes were involved. With this update, open-ended suspensions are now properly recognized and displayed, and performance has been improved for large suspensions. This ensures agents are accurately informed about suspended zip codes during quoting.

Credit Score “No Hit” handling and retry option for agents (BC-19244)

Agents can now more easily handle situations where a credit score check returns a “No Hit” result. Previously, this prevented agents from submitting applications and required manual intervention to retry the check. With this release, agents will see a new “Retry” button when a “No Hit” result occurs, allowing them to update applicant information and reattempt the credit check without restarting the application process. This enhancement streamlines workflows and improves efficiency for agents.