Britecore Release Notes

Enhancements

• Stock Reports Rewritten to use Unified Data Views (BC-18514, BC-18788, BC-18509, BC-11942)
  The stock reports Credits on Cancelled Policies, Return Premium, Aged Accounts Receivable, and Paid Premiums and Fees were updated to use unified data views. Source code for these reports is available in SQL Editor. These stock reports can be used as the basis for customization by carriers, as well as increasing performance and consistency across reports.
• Smart SQL autosuggest added to SQL Editor (BC-19475)
  SQL Editor usability was significantly improved with smart auto-suggestion capabilities, providing real-time query completion and reducing syntax errors. Now when typing a query the user will be presented with suggestions for the next appropriate things to type, making common query patterns easier to generate automatically.
• Enable SQL Editor to format excel columns (BC-20395)
  Added feature to SQL Editor to allow formatting columns as a feature that is often used with Excel reports.
• Unified SQL Views added v_related_policies (BD-20616)
  A new v_related_policies view was added to simplify Underlying Policy Reporting.
• Display privacy indicators, and allow files to be individually marked as private within new claims UI (BC-20499)
  This enhancement allows users to mark individual files as private within the Claims module, bringing full feature parity to between new claims UI and the prior claims UI. Updated privacy icons and tooltips make it easy to distinguish between private and public files, while permission rules ensure only authorized users can adjust privacy settings. These improvements provide clearer visibility, stronger control over sensitive information, and a seamless transition from the legacy claims workflow.

Defects

• County info was not displayed in the Claim information UI (BC-20191)
  An inconsistency was addressed that prevented county information from being displayed in the Loss Address card of the Claims Information tab. BriteCore now ensures county details are included in the claim loss address.
• Conditional print logic failed in forms (BC-20145)
  Conditional print logic for policy forms was corrected after forms failed to appear in required contexts, particularly for renewal terms. BriteCore traced the defect to faulty category matching and normalization in the print decision logic. The corrected implementation validates against unmangled values and improves the display of forms on policy declarations.
• Missing username prevented login when inviting new user (BC-19642)
  Onboarding of new users was streamlined by fixing an issuewhere invited contacts had missing usernames and were unable to log in. The change resolved spinning login screens and improved the administrative experience for onboarding new users.
• Agents unable to edit existing contacts without full permission (BC-19857)
  BriteCore addressed an issuethat previously prevented properly permissioned agents from adding new phone numbers or email addresses to insured contacts when using the Edit Contact feature, unless they had full system permissions. This update restored standard workflow and ensured agents could manage key contact information as expected.
• Non-Renewal docs not attaching to policies (BC-19791)
  Notice of Non-Renewal documents were failing to attach to policies due to absent generation logic in support tools. BriteCore implemented correct deliverable creation during expiration processes and mapped non-renew reasons as expected.
• Rate and save error in policies (BC-19789)
  Application errors during policy rating and saving were resolved by normalizing datetime comparisons where naive and aware types were mismatched. Changes within BriteCore have standardized type handling and eliminates failures, restoring expected policy renewal and rating flows for impacted users.
• Melissa Data autosave function: missing data blocks quote flow (BC-20154)
  Workflow resilience was improved by correcting the autosave integration logic for address data, letting users proceed with manual entry when a property was not found. Previously, missing data blocked the quote process. BriteCore revised logic to present error messages and allow continuation, resolving a significant workflow blocker.
• Claims system tags disappearing (BC-19613)
  A UI refresh issue was resolved where system tags appeared to disappear after being added to claim information. Backend and frontend logic was synchronized to update tag visibility immediately, with users now seeing persistent tags across navigation events without requiring screen refreshes.
• ISO/APLUS files missing last name (BC-19519)
  Name parsing logic for ISO/APLUS exports was enhanced to handle suffixes and avoid misassignment of last names, restoring correct external claim matching. This latest update lets imported files properly record both last name and suffix components for insureds, improving integration accuracy.
• Totality of the payment was applied to each policy (BC-19537)
  The payment application algorithm for group payments was corrected to properly distribute payments across policies rather than applying the total amount to each policy, which previously resulted in erroneous credits. BriteCore implemented improved accounting logic, with stakeholder validation confirming accurate premium and credit calculations.
• Future dated cancellations trigger incorrect accounting (BC-19412)
  Accounting for future dated cancellations was corrected to use end-of-term balances, preventing excessive or erroneous refunds when policies were prematurely cancelled. The update improved transparency and reliability for both administrators and policyholders.
• Bill Whom insured with insured payment plan causing error (BC-19462)
  Billing schedule validation logic was updated to properly allow the Insured as the Bill Whom for certain pay plans, correcting an issue that incorrectly blocked application submission. The resolution aligned system rules with intended billing behaviors.
• Straight-Through-Processing (STP) | Expose property address including zip code (BC-19557)
  Underwriter automation capabilities were expanded to expose full property address and ZIP code information as rule variables in STP workflows. Documentation updates clarified new trigger possibilities, expanding rule options for advanced address-based reviews.
• Straight-Through-Processing (STP) | Expose variables from all rate object types (BC-19386)
  All variables generated by rate objects, such as Flat Rate and Deductible, are now surfaced for evaluation and comparison within STP rules, adding substantial flexibility for business logic alignment. The enhancement harmonized rating and underwriting calculations, with internal benchmarks confirming no performance regressions.
• Task definitions | API permissions (BC-20057)
  API access controls for task definition endpoints were enhanced to require explicit permissions, reducing inappropriate access for sensitive create and modify operations. Documentation clarified criteria for API usage and supported fine-grained access management.
• Task definitions | Create and update APIs (BC-20056)
  New APIs were introduced for task creation and updating, supporting enhanced workflow flexibility and integration extensibility. The changes supported additional metadata and control structures, expanding the system’s automation capabilities.

Original source Report a problem

Enhancements

• Added “Date Inspected” Field in the Claims Record (TS-2426)

  Within a claim, a new field labeled “Inspected” has been added under the Information tab. It is located with the Dates section.

• Added Ability to Set Default Answers for Supplemental Questions (BC-19288)

  When setting up supplemental questions within Lines, BriteCore added the ability to set default answers for supplemental questions to streamline data entry.

• Exposed Scheduled Item Details to STP Engine (BC-19379)

  Exposed scheduled item details to the STP engine to enable rule-based triggers through advanced triggers.

  for item in schedule_items:
  print(item["Test"], item["Test2"], item["Test3"], item["Test4"])

• Introduced Logic for Using Existing Credit Score to Quote Wizard (BC-19391)

  In the Wizard, if a contact already has a valid credit score, the system will reuse it as long as it falls within the configured validity period. A new credit score will only be pulled if the existing one has expired or if key contact details (date of birth, SSN, or name) have been modified.

• Added STP Events for Analysis and Underwriting Referrals (BC-19888)

  Added two new STP-related system events for analysis and underwriting referrals. Within the payload, Britecore included the policy ID, Revision ID, and Contact ID.

• Retrieve Deleted Quotes (BC-20372)

  The retrieve_full_quote API now returns revisions even if they are soft-deleted.

• Rewrote Existing Stock Reports using SQL Views (BC-18506) (BC-19200) (BC-19204)

  BriteCore redesigned the following reports to use the SQL Views and made the source code available to BriteCore carrier clients

  • Reinsurance Received Recovered Report
  • Incomplete Contacts Report
  • Policy Term Expirations Report

  By rewriting these reports, they are more accurate, performant, and allow the SQL code to be used as a basis for further customization in the SQL Editor. Full documentation as to changes can be found in BriteCore’s new inline report documentation.

• Added v_report_docs view to SQL Editor Views (BC-19931)

  A new view has been added to SQL Editor in order to display the report documentation within the tool. The report documentation view will include the report description, version number, changelog, report granularity, and formatting data.

Defects

• Honor is_renewal Flag on create_quote_extended API (BC-20035)

  The create_quote_extended endpoint is currently not honoring the is_renewal flag. As a result, STP checks are applying new business rules instead of the intended renewal rules.

• Email Address Suggestions Limited to Relevant Policy Contacts (BC-19463)

  BrieCore is now limiting email address suggestions to relevant policy contacts to prevent data exposure. Previously, emails were suggested that aren't related to the agency or the policyholders they represent in the Email Policy Information pop-up

• Corrected Logic to Print Optional Forms Based on Category Selection (BC-18814)

  Restored printing logic for optional forms to depend correctly on category selection based on setting enabled “Document Printing depends on selected category values.”

• Ensuring Claim-related Line Items follow Billing and Configuration rules (BC-19268)

  Added validation through Quote_full API to ensure claim-related line items follow billing and configuration rules. Agencies configured for Agency Bill were incorrectly being charged rate chain items, even though these items were marked as “Does not apply if policy is on Agency Billing.” This behavior resulted in inaccurate premium and invoice calculations, as taxes and fees should not be computed or collected for agency-billed policies.

• Corrected Issue in Reapplying Underwriting Rules when Toggling Optional Coverages (BC-19542)

  The fix ensures that Underwriting rules are correctly reapplied to items that are re-added to a policy in BriteCore. Previously, the rules were not triggered when an item was removed and then re-added, potentially causing issues with policy validation. This update addresses that gap by making sure that all relevant rules are automatically re-executed for reintroduced items.

• Subjectivity Not Always Applying (BC-19945)

  Subjectivity requirements were not being applied to policies as expected due to a defect in the logic that processes and enforces subjectivities. This resulted in cases where subjectivity conditions were either not recognized or not enforced during policy handling. The fix ensures that subjectivity logic is now correctly executed and subjectivity requirements are properly applied to all relevant policies

Original source Report a problem

Enhancements

• Disallow negative or zero value quotes from submission or underwriting (BC-19947, BC-19506)

  BriteCore now enforces new validations that prohibit the submission of insurance quotes with a total value of $0 or less. This enhancement ensures that only actionable and valid quotes can move forward in the quoting/underwriting process.

Defects

• Quote Wizard: Rating Values Misaligned (BC-19886)

  In the Quote Wizard, on the Rating tab, coverage values became misaligned after selecting Calculate Rate. This layout issue has been resolved; all coverage fields now display correctly and remain properly aligned after rate calculation.

• Claim Custom Document Prompts for User Input (BC-19796)

  Claim Custom Document generation now correctly prompts for input when dynamic fields are defined, ensuring accurate document creation.

• Validation Error Triggered by Hidden Property Fields (BC-20074)

  This change improves the Quote Rating process by ensuring that hidden Age categories are preserved rather than cleared, which helps maintain accurate quote calculations and prevents data inconsistencies. With this update, quotes will be rated more reliably, reducing the risk of errors and unexpected results.

• Month-End Open Loss Report Not Running Automatically (BC-19901)

  Resolved a scheduling issue preventing some automated month-end open loss reports from executing. These reports now run correctly.

• Incorrect Geographic Coordinates (BC-19473)

  Resolved an issue causing inaccurate latitude and longitude mapping for properties, improving both reinsurance reporting and inspection map accuracy. The Lat/Lon lookup will now only occur when Address Line 1 and ZIP Code are populated, and it will automatically update whenever either field is modified.

• Required Category Fields Not Enforced (BC-18872)

  Fixed an issue where the lines setting “Require explicit selection” in categories did not behave correctly. Quote Wizard now properly enforces user selections.

• Mortgagee Statement Clears When Updating Name (BC-17284)

  Resolved an issue where updating the mortgagee name cleared the mortgagee statement. Statements now persist as expected.

Original source Report a problem

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.

Original source Report a problem

Enhancements

STP Enhancements

BriteCore continues to expand Straight-Through Processing (STP), giving carriers full control to configure and manage their own rules directly in the existing underwriting rules user interface. With these updates, you can now create UI-based STP rules for New Business and Renewals, define more precise conditions with advanced triggers tied directly to rating variables, and see clear error messaging with severity levels when rules fail. All STP results are stored in a unified location for reporting and traceability, and errors are scoped by policy vs. risk so underwriters can quickly identify where action is needed. Together, these changes make it easier to configure automation yourself, without custom code, while giving underwriters greater clarity when handling exceptions.

These enhancements benefit carriers by aligning rules with the same logic that drives pricing and reduces reliance on engineering teams for rule changes. They also make underwriting reviews faster and easier by providing actionable error details, ensuring results are fully traceable, and helping underwriters quickly resolve issues across multiple risks.

Visit our Help Site article for step-by-step guidance on configuring STP rules and reviewing results.

LexisNexis NCF reason codes stored for scoring and letters (BC-18910)

LexisNexis NCF reason codes stored for scoring and letters (BC-18910)
BriteCore added structured support for capturing up to five reason codes from the National Credit File integration, preserving their order of significance. This enhancement ensures consistent storage of codes and descriptions for audit purposes and letter generation, and is particularly important for communicating adverse action decisions.

SSH Key Support for Vendor Integrations (BC-18693)

SSH Key Support for Vendor Integrations (BC-18693)
The Vendor Integrations uploader has been enhanced to support SSH key authentication for SFTP connections, replacing the previous username/password-only approach. A new Uploader via Vendor Integrations option is available under Settings, allowing carriers to configure secure file transfers with SSH keys. In addition, the system can now POST to a designated URL with file details, streamlining integration workflows. This enhancement strengthens security and flexibility across all vendor integrations that rely on SFTP.

Allow updating a rating grid (BC-17667)

Allow updating a rating grid (BC-17667)
BriteCore now permits replacing an existing rating grid by uploading a newer version that shares the same effective dates (LED). During interpolation, the newer grid version will be used so rating outcomes reflect the most up-to-date factors without changing LEDs. This improvement streamlines rating updates by avoiding one-off date adjustments when only minor factor values are changed. It also reduces friction for operational teams who manage grids iteratively.

Defects

Correcting alignment of report list option to hide reports (BC-19301)

Correcting alignment of report list option to hide reports (BC-19301)
BriteCore corrected the alignment of the “hide this report” eyeball symbol to improve visibility and maintain consistency with established UI standards within the BriteCore Platform. The “Hidden Reports” capability supports systematic cleanup of reports by allowing teams to hide reports that are no longer needed. When a hidden report is not needed moving forward, please submit a ticket to BriteCore in order to delete the unneeded report(s).

Hidden reports filter not working when set to yes (BC-18949)

Hidden reports filter not working when set to yes (BC-18949)
BriteCore corrected an issue where the “Hidden Reports” filter on the report list page option did not consistently display and hide reports in the report list. The fix replaces the previous filter with a clear include/exclude control that better reflects carrier intent. As the control is a toggle, no counts are provided anymore. The hidden reports feature is designed to support the systematic cleanup of reports. Carriers can initially hide reports that they suspect are unnecessary, and when those reports go unused over time, they can be permanently removed with confidence.

Documents not rendering properly in deliverables (BC-19421)

Documents not rendering properly in deliverables (BC-19421)
Document previews and PDFs (Quote Summary, Policy Application, Declaration) sometimes failed to generate and the related administrative alert emails didn’t go out. This occurred when changing the effective date triggered an upgrade to a newer quote version, which hid certain underwriting questions. As a result, downstream processes encountered missing data they were expecting in the original structure. Britecore has updated the process to always include defaults for hidden or not-applicable sections and to handle missing answers gracefully. With this change, documents should generate reliably again and the administrative alert emails should be sent as expected.

Property Inspection Request for Bees360 Added to Issuance Flow Rules (BC-19360)

Property Inspection Request for Bees360 Added to Issuance Flow Rules (BC-19360)
A rule action for requesting property inspection via Bees360 was not available in the issuance portion of the rules engine UI. When setting up the rule, administrators can now select Event Type as the module scope, and the Request Property Inspection option will correctly appear as an available effect. This update ensures that property inspections can be properly triggered within underwriting rules, improving compliance and workflow accuracy.

Policy renewals report failures rectified (BC-19135)

Policy renewals report failures rectified (BC-19135)
BriteCore resolved a failure that caused job errors and incomplete output in the policy renewals report. The issue was traced to a naming conflict between a worksheet and a generated cover sheet, which disrupted report assembly in certain conditions. BriteCore renamed the conflicting artifacts and added collision handling so customized names no longer break report generation. The fix does not change report content or filtering logic, only the way the workbook is built.

Melissa not populating rating fields in Quote Wizard (BC-19123)

Melissa not populating rating fields in Quote Wizard (BC-19123)
Melissa returned valid results but the Quote Wizard did not reflect the values in rating fields. BriteCore corrected the mapping so returned fields were properly stored and surfaced on the user interface without requiring a page refresh. The change removes a gap that could affect automated decision-making and related validations.

Post-issue subjectivity could not be satisfied (BC-18894)

Post-issue subjectivity could not be satisfied (BC-18894)
BriteCore fixed a defect that prevented post-issue subjectivities from being updated after commitment. The fix allowed authorized users to mark subjectivities as satisfied, waived, or unsatisfied regardless of the revision’s committed state. We added a confirmation warning when changing an already satisfied or waived item back to unsatisfied to prevent unintended policy impacts. This improves administrative flexibility while ensuring users are made aware of the consequences of reversing prior decisions.

Losses incurred report showed incorrect negative totals (BC-18862)

Losses incurred report showed incorrect negative totals (BC-18862)
BriteCore corrected an issue where the “Losses Incurred” report could display incorrect negative totals in rare timing conditions. Investigation identified a race in claim reserve updates when multiple changes occurred on the same claim in rapid succession. The fix required a per-claim request serialization for reserve updates so each computation used the most recent committed values. Users now see accurate incurred totals.

Eliminate effective date deletion error (BC-19050)

Eliminate effective date deletion error (BC-19050)
BriteCore resolved an issue that previously prevented users from successfully deleting the latest effective date. The fix introduces stronger validations and improved sequencing to ensure dependent configurations are handled gracefully, avoiding system errors. To enhance the user experience, a clear success message is now displayed upon deletion, reducing ambiguity and providing confirmation of the action.

Correct commission calculation for non‑commissionable items (BC-19044)

Correct commission calculation for non‑commissionable items (BC-19044)
BriteCore addressed a defect where commission calculations incorrectly included items that were configured to be excluded, such as certain taxes and fees. The correction aligned the commission engine with account receivable calculations so non‑commissionable amounts no longer inflated commission totals. This change ensures that percentage‑based commissions apply only to the intended premium base, improving billing accuracy.

Renewal processing retried after an anticipated MVR error (BC-18641)

Renewal processing retried after an anticipated MVR error (BC-18641)
The renewal process has been updated to handle invalid driver’s license scenarios correctly. Previously, when an MVR (Motor Vehicle Report) failed due to a rejected license, the system would continue retrying the renewal on subsequent days. With this fix, the renewal now fails immediately after the first MVR error, preventing repeated unsuccessful attempts. In such cases, the policy must be manually renewed once the license information is corrected, ensuring accuracy and reducing unnecessary processing.

Write-off premium default amount was incorrect (BC-18597)

Write-off premium default amount was incorrect (BC-18597)
For some clients, the Write Off Premium pop-up for policies has been corrected to display the proper trailing balance in the Amount to Write Off field. Previously, this field showed incorrect values, leading to confusion and incorrect write-off amounts. With this fix, the system now consistently populates the field with the accurate trailing balance, ensuring write-offs are calculated and applied correctly.

The transfer payment tool did not execute and surfaced no actionable feedback (BC-18352)

The transfer payment tool did not execute and surfaced no actionable feedback (BC-18352)
The Transfer button within the Return Premium screen has been updated to properly handle scenarios where a payment is transferred to a policy without a named insured. Previously, initiating this action provided no feedback, leaving the user uncertain about the outcome. With this fix, the system now clearly displays an error message when such a transfer is attempted, ensuring transparency and preventing incomplete payment transfers.

Fix SQL Editor confirmation on empty editor (BC-19055)

Fix SQL Editor confirmation on empty editor (BC-19055)
BriteCore removed an unnecessary navigation warning from the SQL Editor when no content was present. Previously, users were prompted to confirm leaving the page even in the absence of edits. The enhancement improves clean/dirty state detection so that prompts only appear when unsaved changes exist.

Original source Report a problem

Enhancements

• Policy Submission to Binder Active status (BC-19255)
  Added functionality for admins and underwriters to move policies from “Unsubmitted” directly to “Binder Active” from the Admin Policy view. This update introduces enhanced flexibility in the policy workflow by enabling transitions from the "Unsubmitted" state directly to "Binder Active" for policies. This improvement streamlines policy activation, reduces manual intervention, and supports a more efficient user experience for agents and administrators handling policy submissions.

• Straight Through Processing (STP) for Endorsements (BC-18880)
  Expanded STP to include endorsements. Rules now execute consistently across new business, renewals, and endorsements.

• Add Support for Severity in STP Errors (BC-19171)
  Support for severity levels in STP (Straight-Through Processing) errors has been added to BriteCore. With this enhancement, the underwriter’s view of the STP rule failure generated during STP processes can now be categorized by severity, providing greater clarity and actionable insight.

• Added First Insured Date to lines evals (BC-19655)
  Implemented a new feature that introduces the "First Insured Date" field to capture and utilize the date when an insured party was first added, improving the tracking and historical analysis of policy data. By making the first insured date accessible in the lines evals, this update supports more accurate discounts, such as “advanced shopper” discount calculations. Example evaluation to use within lines:

  max(min((this.revision.effective_date - this.first_insured_date_added).days, 30), 0)
  

• Rules by Transaction Type (BC-19011)
  Enhanced the rules engine to support separate flags for new business, endorsement, and renewal transactions. Rules now apply only to the intended transaction types.

• ISO A-PLUS Data in STP Payloads (BC-19431)
  Enhanced STP processing by including A-PLUS data points such as carrier, loss details, claim status, loss amount, and policy number in payloads. This provides richer information for underwriting and decision-making.

• Hints Based Formatter Function in SQL Editor (TS-2411)
  BriteCore has enhanced the SQL Editor’s report output formatting capabilities, when the output report is defined as Excel format. Now, the SQL Editor automatically formats fields based on field names, saving effort and making report outputs easier to read. Automatic formatting only applies to Excel outputs.

  Automatic formatting can be enabled/disabled using a toggle button in the SQL Editor report settings, found under the image of a cog in the top of the editor window.

Defects

• Commission Calculation Item Rating Fix (BC-19709)
  Resolved an issue where commission calculation items for certain Policy Types failed during post-rating due to the system referencing the current revision instead of the last committed one.. The revision lookup has been updated to prevent self-referencing, ensuring accurate post-rating commission calculations.

• Displaying Available Claim Catastrophe Options during Claim Setup (BC-18041)
  Corrected an issue where only one catastrophe (CAT) option appeared during claim setup when multiple could have applied. All available CAT options are now displayed. Previously, the Catastrophe option was not functioning as expected, causing issues for users attempting to set or modify catastrophe-related claim data. With this update, users can now reliably manage Catastrophe settings during claim setup, ensuring accurate and efficient handling of catastrophe-related claims.

• Calculating and Displaying Dwelling Premiums during the Quoting Process (BC-19581)
  Resolved an issue where the total premium could show as invalid after calculation. Premiums now calculate and display correctly.

• Correcting Display of Auto Coverages Limit (BC-19572)
  Fixed a display issue in the Auto Coverages interface where coverage limits did not appear in the correct format. Limits now show as expected.

• Missing Premium Button during Endorsements within Quote Wizard: (BC-19083)
  Fixed a problem where the “Calculate Premium” button was missing after saving policy-wide changes during endorsements. The button now appears as expected. This update ensures that whenever rates are recalculated or reset, users are now able to view the pending premium, improving transparency and making it easier to track premium changes during rate adjustments.

• Displaying Correct Mailing Address in Declaration Package (BC-19247)
  Resolved an error where declaration packages displayed the wrong mailing address for the named insured. The correct address now appears in all packages. With this update, the logic for selecting and displaying the preferred mailing address has been corrected, ensuring that users' chosen addresses are accurately reflected throughout the relevant documentation and workflows.

• Selecting Mortgagees as Billing Contacts (BC-18622)
  Resolved an issue where mortgagees added on the billing screen could not be selected as billing contacts. Mortgagee contacts now display properly for selection. The changes ensure that billwhom data is consistently updated in response to relevant events and user actions, reducing manual intervention and minimizing errors.

• Adding Default Line Items to New Policies (BC-18298)
  Resolved an issue where default line items were not automatically added to new policies. Default items are now applied as intended. The update ensures that default line items are now correctly included during the relevant processes, improving workflow consistency and reducing the need for manual intervention. Users will benefit from enhanced reliability in the automatic handling of line items, streamlining their operations and minimizing potential errors.

Original source Report a problem

Enhancements

• Enable SQL Editor for all carriers (BC-18931)
  SQL Editor support within the reporting and data modules has been enabled by default, allowing users with appropriate permissions to utilize advanced SQL querying capabilities without additional configuration. This enhancement streamlines access to complex data analysis and custom reporting tools, offering a more robust reporting and analytical environment for insurance operations and enabling custom reporting.

• Losses Incurred Stock Report Rewritten for SQL Editor (BC-18505)
  A new standard “Losses Incurred” report is now available, complete with SQL source access for carrier customization. Carriers can easily copy and modify this report to meet their specific reporting requirements. Typical scenarios include starting from the provided standard report and incorporating additional data fields, empowering carriers to perform comprehensive, independent self-reporting without reliance on BriteCore.

• Open Loss Stock Report Rewritten for SQL Editor (BC-18504)
  A new standard “Open Loss” report is now available, complete with SQL source access for carrier customization. Carriers can easily copy and modify this report to meet their specific reporting requirements. Typical scenarios include starting from the provided standard report and incorporating additional data fields, empowering carriers to perform comprehensive, independent self-reporting without reliance on BriteCore.

• Claims Payments Stock Report Rewritten for SQL Editor (BC-18787)
  A new standard “Claims Payments” report is now available, complete with SQL source access for carrier customization. Carriers can easily copy and modify this report to meet their specific reporting requirements. Typical scenarios include starting from the provided standard report and incorporating additional data fields, empowering carriers to perform comprehensive, independent self-reporting without reliance on BriteCore.

• Add necessary data elements to advanced trigger (BC-18580)
  Advanced triggers within the STP rules engine were enhanced to preload a comprehensive set of data, including all properties, scheduled items, sublines, questions, vendor loss history, disclosures, claims, credit scores, catastrophes, and named insureds. The system now loads this data efficiently when advanced triggers are executed, supporting richer rules logic and improving the accuracy of automated processing.

• Execute Straight-Through Processing (STP) Rules in New Business (BC-18575)
  The execution of Straight-Through Processing (STP) rules for new business was integrated into the core rules service. The new workflow combines results from both legacy and updated STP rule engines, ensuring consistent evaluation of business rules before policy issuance. Changes included updates to the service layer, user interface for error code display, and comprehensive testing of affected endpoints.

• Straight-Through Processing (STP) on Renewals (BC-18244)
  STP rules engine execution was incorporated into the daycron renewal process, allowing policies up for renewal to be evaluated automatically before commitment. The system now logs errors and sends notifications for failed STP rule evaluations, ensuring only eligible policies are renewed. This enhancement automates compliance checks and reduces manual intervention for underwriters during renewals.

• New API Schema for STP Results (BC-18568)
  A new API schema for STP results was introduced, providing robust storage and retrieval of rule execution outcomes. The schema supports detailed tracking of rule evaluations, error codes, and links to specific properties or drivers. A dedicated endpoint for listing results by revision was implemented, supporting paginated requests and responses for efficient integration with external systems.

• Enhanced Rating Grid Management (BC-17253)
  BriteCore has introduced significant enhancements to Rating Grid functionality to support advanced actuarial workflows and improve performance at scale. With this release, users can now manage versioned rating grids, enabling safer updates by uploading new grid versions without overwriting historical data. The system now distinguishes between new business and renewal effective dates, ensuring accurate rating selection based on policy context.

  Additional improvements include the ability to delete grids (via soft-delete with backend cleanup), associate grid points with groups for scoped rating, and enforce state/date uniqueness to avoid conflicts. Performance has been optimized to allow importing large datasets (up to 1M points) in under five minutes, with real-time progress feedback. These changes provide more flexibility, better data integrity, and a stronger foundation for location-based and version-aware rating.

Defects

• Deliverables Not Generated for Specific Workflows (BC-18975)
  A defect was addressed where deliverables failed to generate upon policy commitment for certain workflows. This issue was particularly impactful for customers relying on automated document generation for compliance and operational needs. The solution involved adding additional logging and improving the deliverables generation process, resulting in the successful creation of all required deliverables.

• Alert Pop-up Formatting off (BC-18962)
  Alert pop-up modules displayed when opening policies appeared incorrectly formatted, with squished text and an inappropriate Submit button instead of Done. This was caused by recent changes that unintentionally modified the alert appearance. The update restored proper formatting and button labels, ensuring a readable and user-friendly alert popup consistent with user expectations.

• API modify_full_quote failed to validate the change of policy type when gaps (BC-18938)
  A validation issue was fixed in the API for modifying full quotes, where the system incorrectly prevented changes to the effective date if it resulted in a policy type change, even when not applicable. The solution updated the validation logic to consider both state and policy type, preventing unnecessary errors and allowing users to modify quotes as intended.

• Subjectivity Event not triggered when modifying a subjectivity (BC-18908)
  When subjectivities were modified, the expected SubjectivityModifiedEvent was not triggered, causing downstream workflows and integrations to miss updates. This defect was rectified by ensuring that any update to a subjectivity triggers the appropriate event, improving data synchronization and system reliability.

• Agent Dashboard Text Updates Not saving (BC-18867)
  A defect affecting multiple clients prevented users from saving updates to the agent dashboard text. The system failed to persist changes upon clicking the save button, leading to user frustration and operational delays. The fix corrected the validation logic and expanded test coverage to ensure that all changes to dashboard text are properly saved and reflected in the interface.

• Cannot display Rating Grid points in pop-up (BC-18853)
  A user interface bug prevented the display of rating grid points for Vehicle Prefill types, resulting in an error message. The issue was traced to missing code for handling Vehicle Data Prefill cases, which had been accidentally deleted. The missing logic was reinstated, and users can now view grid points for all relevant rating types without errors.

• Mandatory re-rating check fails intermittently (BC-18840)
  The system's mandatory re-rating check for quotes was unreliable, sometimes allowing agents to print quote summaries before rating was complete. The solution implemented a dedicated function to reliably check quote rating status, ensuring compliance with rating requirements before summary printing.

• Voided payments are being counted as part of payment authority limits (BC-18756)
  A defect was resolved where voided payments were still counted towards payment authority limits, incorrectly preventing additional payments even after a void. The fix updated the logic to exclude voided payments from the authority calculation, ensuring that users can process new payments as appropriate without being erroneously blocked.

• Credit score validity settings now work in the quote wizard (BC-13307)
  The "months-credit-score-valid" and "days-credit-report-valid" settings were not accurately reflected within the quote wizard, causing display discrepancies for credit score dates. The defect was corrected so the wizard now properly calculates and displays credit score validity dates according to the configured settings, improving compliance and user experience.

• Corrected sporadic logout within BriteApps (BC-18635)
  A sporadic logout issue was identified and corrected in BriteApps. Users were occasionally logged out due to a flaw in the "save token" logic, particularly involving timing of token refreshes and session storage. The update refines the session management approach, reducing the incidence of unexpected logouts and enhancing user session stability.

• Avoid penny-off reinstates on delayed cancel (BC-14973)
  A workaround was implemented to bypass code that could introduce penny-off differences during reinstatements following delayed cancellations. This change prevents minor discrepancies in payment calculations and aligns reinstatement outcomes with expected financial accuracy, while a more permanent fix is pursued.

• Policy Renewals Report Fails with “Essential Container Error” (BC-19135)
  BriteCore resolved a critical issue affecting the Policy Renewals Report functionality across multiple clients. Users were experiencing failures caused by an “Essential Container Error,” preventing access to renewal data reports. This fix ensures that the report now executes reliably without throwing backend container errors, restoring full visibility into upcoming renewals for underwriting, operations, and client servicing teams.

Original source Report a problem

Enhancements

Customizing 4 Stock Reports in SQL Editor

BriteCore is pleased to announce significant enhancements to its stock reporting capabilities, streamlining the process for customization. The following reports have been updated to integrate SQL Editor views, and their source code is now accessible for easy duplication and customization:

• Claims by Reported Date (BC-18503)
• Claims by Loss Date (BC-18502)
• Claims by Closed Date (BC-18501)
• Inspections Due Report (BC-18500)

To initiate customization:

1. Access the Report List.
2. Select the desired report from the list above.
3. Click "Design Report" in the right-hand tray.

The SQL editor will open immediately with a customizable copy of the selected report. After making edits, save the customized report under a new, distinct name within your system.

For comprehensive guidance and further details, please visit https://help.britecore.com/hc/en-us/sections/40676934208403-SQL-Editor. BriteCore intends to open-source all stock reports over the coming weeks.

Archiving a Future Policy Now Archives Its Revisions (BC-18290)

When a future policy is archived from the Admin Builder UI, all associated revisions that have not gone into effect are now archived as well. This change ensures consistency in the archival process and prevents orphaned policy revisions from remaining active, supporting cleaner policy management workflows.

Updating Contacts User Interface to Accurately Reflect Permissions Level (BC-18613)

The Contacts UI was updated to reflect permission levels more accurately, including greying out elements when permissions are set to read-only. All actions are disabled when contact permissions are restricted, and this behavior was tested across multiple user roles. The enhancement improves clarity and ensures the UI remains the source of truth for permissions.

Enabling SQL Editor to Save Reports Without Running Report (BC-17981)

A new capability was introduced to SQL Editor enabling users to save reports after validation without requiring a full execution. This change streamlines report creation and editing workflows, reduces wait times, and supports incremental progress for users working with large or complex queries.

Allow editing of payment details in pending approval status (BC-17078)

Users can now edit payment details for claims payments while those transactions are in the Pending Payment Approval status. Previously, there was a need to delete the transaction and re-initiate a new payment if any detail was incorrect, resulting in workflow delays. With this update, editable fields—including payment amount, payor, payment method, and description or notes—were made accessible directly within the Payment Processing screen, but only while the payment is pending approval.

Defects

• Commission Amount Not Updated After Changing Bill Whom (BC-18295)

  A validation enhancement was delivered to ensure the net commission amount resets appropriately when the “Bill Whom” field is changed from agency to insured after a policy committed. The update helps commission calculations remain accurate regardless of changes in billing responsibility, and thorough validation logic was added to maintain data integrity.

• Property Lookup Fixes (BC-18293)

  The property lookup integration was improved to address several small issues: line items with zero limit or deductible values are now correctly included in the payload, empty strings from user input are handled when saving response data, and a new category type for number inputs is supported. These refinements ensure more reliable integration and data handling for property lookup operations.

• Deleted Property on Endorsement Still Affects Rating and Premium Calculation (BC-18611)

  A defect was corrected where deleted properties during endorsements continued to affect rating logic and premium calculations. The fix ensures only active properties are considered during rating, preventing overcharges and maintaining accurate premium totals.

• Insured getting Email Notification for Claim (BC-18533)

  A bug was fixed where the named insured received unintended email notifications when an adjuster was added to a claim. The defect was traced to a configuration error, and the fix ensures that notifications are only sent to the appropriate parties.

• Excessive policy notes generated from quote module (BC-17217)

  A defect was resolved where policy notes were generated for every keystroke in the quote module, leading to clutter. The fix ensures notes are only created when the user leaves the field, making policy documentation more meaningful and easier to review.

• Property disclosure exclude peril (BC-14986)

  A bug was fixed where peril exclusions for certain line items were not properly evaluated during claims surcharge calculations. The update ensures excluded peril rules are applied correctly, improving the accuracy of surcharge assessments.

Original source Report a problem

Enhancements

Announcing the General Availability of SQL Editor (BC-18629)

BriteCore’s SQL Editor custom reporting environment has been promoted to General Release, making advanced SQL-based custom reporting and analytics broadly available. This general release signifies that this custom reporting solution is now production-ready for BriteCore users. Product documentation, including a curated list of pre-built SQL reports, is available on BriteCore’s help site.

Automatic cover page for Excel reports in SQL Editor (BC-18724)

Excel report generation in BriteCore’s SQL Editor custom report environment was enhanced to include an automatically generated cover page for all exported reports. This feature provides a professional and consistent front page, which can be used to display summary information, report metadata, or custom branding. The addition of a cover page improves the usability and appearance of new custom reports, streamlining communication with stakeholders who rely on these documents for analysis or regulatory submissions.

Validate sheet name in SQL Editor (BC-18681)

The BriteCore SQL Editor custom reporting environment now validates Excel sheet names to prevent the use of invalid characters such as [], :, *, ?, /, and , which are not supported by Excel. This validation helps avoid report generation errors and ensures compatibility with downstream tools that consume these Excel files. When users attempt to generate a report within SQL Editor with an invalid spreadsheet name, BriteCore provides an error message, prompting correction before proceeding.

Add claim transaction system tags in SQL Editor (BC-18671)

Claim transaction system tags are now available within the SQL Editor, enhancing the ability to filter, report, and analyze claims data for advanced reporting needs, including regulatory reporting. This addition allows users to classify and extract claim transaction information with greater precision, supporting compliance and operational analysis.

Delivering dynamic fields to generate custom deliverables for policies in legacy claims UI (BC-18461)

The BriteCore Platform now supports the generation of custom deliverables with dynamic fields for policies, including both the admin and legacy claims user interfaces. New pop-up dialogs were introduced for entering dynamic field values, allowing users to create custom letters and communications directly from the BriteCore Platform.

Defects

Improved process to create, publish, delete, rename, and re-create when re-using names for reports in SQL Editor" (BC-18630)

When reusing report names, the process for creating, publishing, deleting, renaming, and re-creating SQL Editor reports now works seamlessly when it hadn’t before. Previously, deletion logic prevented users from re-using the same report name, causing workflow disruptions. This latest update ensures that the full report lifecycle is user-friendly and robust.

Resolved issue with "Print to Deposit" on Daily Cash Receipt page (BC-18742)

An issue was resolved where the "Print to Deposit" functionality on the Daily Cash Receipt page was not working as intended and users saw a message "Please resolve all payments for policies". The defect was corrected, restoring the ability for users to print deposit documentation directly from the page.

Resolved issue with fees appearing incorrectly on Daily Cash Receipt PDF (BC-18706)

A defect was fixed where fees were incorrectly appearing on the Daily Cash Receipt PDF, even for payment types such as cash or cheque where fees should not be displayed. This occurred because the fee calculation logic did not properly filter out certain payment instruments, resulting in misleading receipt documentation. This issue has been resolved.

Resolved issue with Secure Payment appearing on Daily Cash Receipt page (BC-18705)

An issue was corrected in which electronic payments made via the Secure Payment page were appearing on the Daily Cash Receipt (DCR) page, even though the DCR is intended only for cash, check, and money order payments. The logic now filters payment instruments appropriately, excluding electronic and ACH payments from DCR calculations.

Resolved issue with empty radio buttons appearing on Quote Wizard Billing Page (BC-18694)

A visual defect was resolved on the Quote Wizard Billing page, where radio buttons appeared blank or unpopulated, resulting in user confusion. Now all required radio button options are populated and selectable, restoring normal billing workflow.

Underwriting Rules - Displaying pop up message missing from effects option (BC-18608)

A user interface defect was resolved where the option to display a pop-up message as an effect in Underwriting Rules was no longer available after a recent screen update. The option to display a pop-up message has been restored in the effects list.

Correcting renewal error when first revision was not committed (BC-18555)

A renewal processing error was fixed where attempting to renew a policy with an uncommitted first revision would cause the process to fail, particularly when accident and violation integrations were enabled. This latest update ensures that available dates are used where present, allowing renewals to proceed smoothly.

Corrected inability to add claim notes (BC-18262)

A defect was fixed where the “New Note” button in the Claims module’s Notes tab was non-functional, preventing users from adding claim notes. The update restored note creation capability, supporting better claim documentation and communication.

SQL Editor v_recoveries missing Reinsurance values (BC-18034)

A defect was corrected where recoveries related to reinsurance were not properly reflected in financial reports generated in BriteCore’s SQL Editor due to a typo in the logic extracting reinsurance change data. The update ensures an accurate population of reinsurance values, improving financial transparency and reporting reliability.

Resolving issue where agent quoting bypassed mandatory re-rating (BC-17946)

A defect was fixed where agents could bypass mandatory re-rating checks and print quote summaries before a quote had been properly rated. The corrected logic ensures that the quote summary is only available after a successful rating, preventing incomplete or inaccurate summaries and improving rating integrity.

"Use eDelivery" checkbox not tracked correctly(BC-17683)

An issue was fixed where, after adding an email for the insured, selecting the “Use EDelivery” checkbox failed to correctly send the e-delivery invitation. The UI previously did not transmit the correct value for the checkbox after adding a missing email, causing silent failures. The fix ensures that the checkbox state is always sent correctly, so that invitations are reliably issued when the user intends to use e-delivery, reducing friction and errors in digital document workflows.

Declaration didn't generate after revision was committed (BC-17186)

A defect was remediated where committing a policy revision did not always result in generation of the corresponding declaration document, even though the folder for the declaration was created. The update added retry logic and additional error handling to ensure that declaration documents are reliably generated and attached, resolving inconsistencies and preventing missing documentation for completed policy changes.

OFAC reporting down - 504 error (BC-15904)

A defect was resolved when running the Financial Anti-Terrorism Cross-Reference (OFAC - Office of Foreign Assets Control) report which resulted in a 504 error due to long processing times as the policyholder base grew larger. The report logic was reimplemented to run as a background job, with new UI messaging and email notifications for completion or errors.

Unable to request credit score again even after No-Hit (BC-15518)

A defect was corrected where agents were unable to re-pull a credit report after receiving a “No Hit” result, even after updating contact information. The system previously considered “No Hit” as a valid credit score, which triggered the report validity counter and prevented further pulls. The recent update ensures that “No Hit” responses do not start the counter, and that a re-pull is allowed if contact data is corrected. Resolving this issue reduces the need for underwriting intervention and supports more accurate quoting.

Original source Report a problem

Enhancements

• Enhanced Vehicle Quoting Experience with Manual Fallback for VIN Lookup Unavailability (BC-18005)

• Enhanced Vehicle Quoting Experience with Manual Fallback for VIN Lookup Unavailability (BC-18005)

  This release introduces a manual fallback option for situations where VIN lookup services fail or are unavailable. The quoting flow now includes a Manual Lookup button that appears conditionally, allowing users to retrieve vehicle data manually. When no VIN lookup vendor is installed but fallback is configured, the Manual Lookup button appears immediately, enabling users to enter year and cost information. When a VIN lookup vendor is installed and fallback is configured, the system attempts automatic lookup first, displaying the Manual Lookup button only if the VIN lookup fails. These enhancements ensure quoting can proceed smoothly regardless of VIN lookup vendor status, reducing disruptions and improving quoting efficiency.

• Enhance API Response for getToBePrinted (BC-17950)

• Enhance API Response for getToBePrinted (BC-17950)

  Enhanced the system’s response for the api/v1/printing/getToBePrinted operation by adding an optional parameter to include address field. This parameter defaults to false to maintain existing behavior, and when set to true, it includes address components in the response.

• API Update - Support RevisionInvoiceNumber when retrieving documents (BC-17906)

• API Update - Support RevisionInvoiceNumber when retrieving documents (BC-17906)

  Extended the document retrieval API to support querying by Revision Invoice Number. This change allows users to target specific invoice revisions when pulling documents, improving accuracy in scenarios involving reissued or updated billing statements.

• Billing Schedule as rating Factor across all roles (BC-17565)

• Billing Schedule as rating Factor across all roles (BC-17565)

  BriteCore has enhanced the Quoting Wizard to address billing schedule selection issues, especially for pay plans available to non-named insureds. Previously, payment plans like “Escrow Billing” were not available in the billing schedule dropdown because the system defaulted to the Named Insured, and the bill-to-whom could not be selected during the quote phase. With this update, BriteCore now retrieves all billing schedules regardless of the initial bill-to-whom selection and enforces compatibility checks.

• Property Page Rounding Lat/Long (BC-18362)

• Property Page Rounding Lat/Long (BC-18362)

  Precision improvements were made to geographic data handling by ensuring that latitude and longitude values are correctly displayed with 6 decimal points. These changes provide more accurate and consistent geographic data, thereby improving the reliability of geographic-dependent operations, such as mapping, rating and risk analysis.

• Add new rule effect "Generate Deliverable" in rules configuration UI (BC-18213)

• Add new rule effect "Generate Deliverable" in rules configuration UI (BC-18213)

  The rules configuration interface in the Events module now includes a new rule effect labeled "Generate Deliverable." This feature allows administrators to dynamically select from a list of custom deliverable documents, streamlining automated document generation and reducing configuration errors through a structured user interface.

Defects

• Prepared dataframes [ITEMS] does not mirror production structure (BC-18556)

• Prepared dataframes [ITEMS] does not mirror production structure (BC-18556)

  Resolved an issue involving mismatches between data structures used in development and those in the production environment. The resolution ensures consistency and compatibility, significantly reducing the risk of runtime errors and improving the overall reliability of data-driven workflows.

• Advanced setting ‘stp-make-detailed-note’ not working (BC-18546)

• Advanced setting ‘stp-make-detailed-note’ not working (BC-18546)

  Resolved an issue in the STP workflow that caused errors or inconsistencies when creating detailed notes. With the advanced setting

stp-make-detailed-note
enabled, the system now generates accurate notes based on the results returned from STP rules and automatically adds them to the policy’s notes section.

• DMV Virginia report failed (BC-18456)

• DMV Virginia report failed (BC-18456)

  Corrected an issue specifically impacting the generation of DMV reports for Virginia, which previously resulted in failures or incomplete reports. Following this fix, the report generation process functions correctly, ensuring regulatory compliance and accurate record keeping.

• Error When Setting Future LED through Admin (BC-18348)

• Error When Setting Future LED through Admin (BC-18348)

  BriteCore has resolved an issue related to renewal effective date validation. Previously, if policies had been set up for renewal and a user tried to change the LED to an earlier date than the renewal date, the affected policies could not be renewed. With the addition of a new force flag and a detailed table that displays each affected policy details, the user can choose to renew the policies.

• Attachment incorrectly showing in Declaration folder (BC-18261)

• Attachment incorrectly showing in Declaration folder (BC-18261)

  This release enhances the system’s form attachment handling to ensure that documents are accurately managed during policy renewals. The update introduces a dual validation process that cross-checks both form name details (such as form code, edition number, and description) and form identifiers to prevent duplicate attachments. It also improves performance by consolidating multiple database queries into a single, more efficient query, reducing system load without increasing memory usage. These improvements ensure that attachments are processed correctly according to configuration and prevent unexpected documents from appearing in renewal packages. The update resolves previous issues where attachments, such as certificates or privacy disclosures, were incorrectly included in renewal documents despite not being configured to do so.

• Failed Ivans downloads (BC-18176)

• Failed Ivans downloads (BC-18176)

  Corrected an issue causing failures in policy document downloads through the Ivans integration. When a policy was copied then the copied policy wasn’t reported. After the correction, downloads are functioning reliably, restoring confidence in automated document delivery and significantly reducing manual intervention.

Original source Report a problem