Britecore Release Notes

Enhancements

Task Management

BriteCore’s Task Management module (Tasks) centralizes and streamlines how work is initiated, assigned, tracked, and completed across claims and policies. The module is tightly integrated with the core system so that tasks always live in the context of a specific entity (such as a policy or claim) and each user gets their own task workbench to manage the workload efficiently.

• Adding default ‘None’ value for empty Line Item Questions (BC-20791)
  Default value initialization for line item questions was updated to avoid populating empty placeholder objects for structured question types such as address and contact-like fields. Instead of inserting empty structures, initialization logic was revised so these question types defaulted to None, reducing confusion and preventing downstream logic from treating placeholders as meaningful answers. These changes improved the accuracy of underwriting and validation flows that depend on whether a question was truly answered versus merely pre-populated.

• Store payor name and email from secure payment (BC-19430)
  BriteCore has added support for receiving payer identity details from the external payment flow and persisting them with the payment record. Previously, the platform was not capturing and displaying the name and email address of the payor for electronic payments made with Stripe, which reduced visibility for billing and accounting teams reviewing payment history. Clients now have improved traceability for reconciliations and customer service follow-ups.

• Defaults to first property in policy property list and adds editable option for multi-property policies when associating property to claim (BC-18452)
  This enhancement streamlines claim workflows by automatically preselecting the first property on a policy when users need to associate a property when creating a claim. Previously, users had to manually select a property even in common scenarios where the first property was the intended choice, which added unnecessary clicks and slowed down claim intake and processing. When a policy contains multiple properties, the selection remains editable so users can quickly choose the appropriate alternative property without losing flexibility.

• Allow automatic filling of counties for business locations (BC-13853)
  This enhancement improves configuration efficiency by allowing administrators to automatically populate counties for a selected state when setting up business locations. Previously, the county setup required manual entry or repetitive selection, which was time-consuming and increased the likelihood of missing or inconsistent configuration.

• Add detailed invoice allocation info to payment retrieval and payment-made events (BC-20454)
  Enhanced the payment retrieval API to return invoice-level allocation details for a payment, including invoice_amount, amount_paid (for that specific payment), and amount_due, plus supporting metadata (e.g., invoice identifiers/descriptions, status, revision/external references, and due dates where applicable). Covered scenarios such as partial payments, multiple payments completing an invoice, and excluding invoices already fully paid by prior payments, with accompanying unit tests.

Defects

• Disable username input alias for users in BriteAuth Sites (BC-21328)
  BriteCore now displays the username alias as read-only on the contacts page for users on sites using BriteAuth. BriteCore resolved an issue where in cases when the user was already invited, the username alias input should have been displayed as read-only on the contacts page. Editing it would not have had an effect but it was still shown as editable.

• Wrong error message when revision not found - api/v2/quotes/delete_full_quote (BC-21302)
  When users invoked the delete quote endpoint using an external system reference and the quote could not be found, the API returned a confusing “Not Found: None” message that did not indicate which identifier failed. The error handling has been adjusted so the correct identifier is preserved and surfaced consistently in the error message. This ensures that when a delete request fails, additional details are provided as part of the error message.

• Quote changes not persisting while STP is pending underwriting review (BC-21216)
  When a quote was in a workflow state that restricted editing, users could still make changes and click Rate & Save, but the system would silently refuse to persist those updates. This created a misleading experience where the UI appeared to accept changes, yet a refresh reverted values to their previous state with no explanation. The behavior was corrected so the system returned a clear, user-facing warning when an edit attempt was blocked by the configured review-state lock. This ensured underwriters and other users understood that the quote was not editable in its current review state and why their changes were not saved. The improvement reduced confusion and prevented users from assuming rating or underwriting adjustments had been captured when they had not. Overall, the quote workflow behaved more transparently and predictably in locked review states.

• Quote/policy new attachments UI delete folder was not working (BC-21176)
  BriteCore resolved an issue where occasionally, when users attempted to delete a read-only attachment or folder in the new attachments interface, the deletion request could fail but the UI still reported success. This created an inconsistent experience where users believed content had been removed even though it remained in place. The deletion workflow has been updated so the UI validates the server response and only reports success when the delete operation actually succeeds.

• Claims displayed military time and inconsistent date formats across components (BC-21171)
  Claims had displayed dates and date-times using inconsistent formats across different screens and dialogs, which created confusion for users reviewing loss details, transactions, and notes. This change standardizes date presentation across the claims experience so users can see a consistent format.

• Read permissions did not enforce read-only behavior in the contact module (BC-21110)
  The Contact module had not consistently enforced read-only behavior when a user only had “Read” access, which meant interactive controls could appear enabled even when edits should not have been permitted. As part of this fix, more granular permissions are checked and enforced that override less granular permissions. As a result, users now experience a more consistent authorization experience across all workflows.

• Vehicle model changed after saving when entered manually (BC-21014)
  Vehicles created through an external prefill import could arrive without a populated vehicle model, prompting users to manually enter a model value during quoting. When the vehicle was later saved or updated, an automatic VIN-based prefill could run and overwrite the user’s manual entry, which was confusing and led to unexpected data changes. The fix enriches imported vehicles with VIN-based prefill data earlier in the workflow so the model value is correctly populated at the time of import when available. This prevented user-entered values from being replaced by background lookups.

• Rating not invalidated when adding or removing properties (BC-21006)
  BriteCore resolved an issue where properties were added or removed from a quote but the system did not consistently invalidate the existing rating state, which allowed stale premium values to remain visible and sometimes actionable. The fix centralizes rating invalidation so that adding, removing, or updating property locations reliably resets the rated state and prompts the appropriate re-rate behavior.

• Alert email link opened claim in legacy claims interface instead of new Claims interface (BC-20901)
  Claim alert emails had included links that could open claims in the legacy claims interface even when the new Claims experience was intended, causing inconsistent navigation for users. The fix introduces conditional redirects that account for claim type and configuration flags so that the correct interface is used consistently for the intended scenarios.

• Underlying policy email type caused errors in PUP contact editing (BC-20795)
  When a contact was mapped from an underlying policy into a PUP workflow, an email type value could appear that was not supported in the PUP contact editing UI, leading to validation errors when Users attempted to save edits. This mismatch stemmed from inconsistent email type options across different parts of the application and legacy values that did not align with the current dropdown choices. The fix standardized the supported email types across the platform to a canonical set and aligned UI labels and defaults with that canonical behavior. It also added stronger backend defaults and validation so newly created email records consistently had an appropriate type and did not rely on inconsistent legacy values. A migration script normalized existing stored values into the canonical set so pre-existing records would not continue to break editing flows. As a result, Users could edit and save contacts in the quoting workflow without encountering confusing validation failures caused by unsupported email type values.

• E-signature completion page blocked (BC-21433)
  After an agent completed an embedded e-signature session, the signing experience could be blocked on the completion step due to updated security restrictions from the eSignature provider. This release updates how we handle the completion state so the embedded flow can finish cleanly without trying to load the blocked completion page. Agents should now consistently reach a successful end state after signing.

Original source Report a problem

Enhancements

• New Claims experience | Claims Notes Content Field Improvements (BC-20568)

  Claims adjusters needed more flexibility in how claim note content was captured. BriteCore no longer requires content in the note, only the title.

• Report Retrieval API Enhancements (BC-20884)

  Machine users authenticated via BriteAuth can now successfully access the /api/v2/reports/retrieve_reports endpoint. This change restores API-based report retrieval, enabling automated workflows and faster access to reporting data.

• Adding an Additional Interest Type for STP Configurations (BC-20913)

  This change is specific to Straight-Through Processing (STP) rules and adds the ability to expose and reference an Additional Interest type within STP configurations. As a result, the STP engine can apply automation rules based on the presence and classification of Additional Interests, improving control over eligibility, routing, and automated decisioning while increasing transparency into how Additional Interest details influence processing outcomes.

• Remove Read-Only Notification Icon for BriteData Reports (BC-21108)

  The read-only icon for BriteData reports has been removed from the report list. This change reduces visual clutter and makes the report list easier to scan and use.

• Changing Privacy Settings to Attachment Folders and Contents (BC-20820)

  In Claims, when a folder’s privacy setting is changed to Public, the system will now automatically apply that same Public setting to the items contained within the folder. This helps ensure visibility is consistent and reduces the need to manually update privacy on individual items after making a folder public.

• SQL Editor – Date Formatter Time Zone Changes (BC-21098)

  In the SQL Editor table preview, date formatters were incorrectly applying a time zone offset, causing dates to appear as the previous day for users in GMT-X time zones. This has been corrected, so dates now display accurately and consistently with the underlying query results.

• DocuSign Anchor String Support (BC-19897)

  Document signatures required a more precise placement of the anchor strings. This enhancement improves signing accuracy and reduces document rework.

• E-Signature Support for Dynamic Document Templates (BC-20554)

  This enhancement supports DocuSign e‑signatures for Dynamic Documents by adding signature anchor metadata to the template context, enabling templates to control where signatures are placed. It also supports multiple agents and insureds by generating anchors in sequence for all required signers.

• Separate Min/Max Payment Enforcement (BC-20760)

  This enhancement splits payment amount enforcement so minimum and maximum payment rules can be managed independently for Secure Online Payment and Accounts Receivable. Previously, a single configuration applied the same enforcement across both channels, which constrained internal servicing scenarios that required more flexible payment entry. The change preserves existing behavior by defaulting the new settings to match the prior single-setting configuration unless explicitly adjusted.

• New Revision History User Interface (BC-20816)

  The Revision History screen has been updated with a cleaner layout that makes it easier to review policy changes over time, including an expand option to see coverage-level premium changes and a more visible Declarations Generated indicator.

  To use the expand option:

  1. Open a policy and select Show Revision History.
  2. Review each revision’s effective date, policy status, endorsement date, revision state, and premium before and after the change (including the difference).
  3. Select a row to see which coverages drove the change.

  To allow agents to view revision history through the Accounts Receivable screen, enable the display_revision_history_ar_agent advanced setting.

• Tagging Policy Attachments to use in Straight Through Processing

  Policy attachments uploaded in the Quote Wizard for New Business, Endorsements, and Renewals can now be tagged with a File Type selected from a dropdown at upload time. This File Type is a business document category (not the file’s technical format like PDF/JPG), making it easier to identify what was submitted and enabling more reliable Straight-Through Processing (STP) validation and routing based on required document tags. The available File Types come from the configurable lookup table, which includes default values and can be extended to support customers’ use cases. In addition, the policy’s attachment page has a new look and feel.

• Updated Policy Attachments Experience

  The Policy Attachments screen has been refreshed to align with the Claims Attachments experience, delivering a more consistent and streamlined way to upload, organize, and manage documents across BriteCore. Users can now tag attachments with a searchable Type, add optional Descriptions, and view this information directly in the attachment list and file details. Enhanced search by Type makes it easier to find documents on policies with large attachment volumes, while updated edit functionality allows existing files to be renamed or reclassified without losing prior data.

Defects

• SQL Editor – Text Report Delimiter Fix (BC-20785)

  Text reports generated with the delimiter set to None no longer default to tab-delimited output. Selecting None now produces output with no delimiter between columns, while all other delimiter options continue to behave as expected.

• New Written Premium Commission Algorithm (BC-19559)

  Multiple issues were corrected in the written premium commission calculation. Flat cancellations were incorrectly producing a small commission (e.g., $0.01) instead of zero, and commissions after mid-term rate changes were not using the original rate as expected. Users can expect more reliable commission processing with greater reliability for premium commission calculations.

• NSF Cancellation Processing (BC-16066)

  BriteCore fixed an issue where an NSF payment on a policy that had previously been placed into Cancellation Pending – Non-Payment could incorrectly generate a second non-pay entry, assess an additional non-pay fee for the same invoice, and reset/extend the policy’s cancellation date. With this update, when the NSF is processed using the Allow policy to cancel option, BriteCore reactivates the original non-pay so the original cancellation date is honored and duplicate non-pay fees are not charged.

• Credit Score Not Found Error (BC-20874)

  When a credit score could not be retrieved, the system returned an error instead of handling the situation gracefully. The issue has been resolved, so users can continue their workflow without interruption.

• Duplicate Payments (BC-18184)

  BriteCore fixed an issue where manual payments submitted from the Daily Cash Receipt (DCR) screen could be unintentionally submitted twice, resulting in duplicated (doubled) payments—sometimes showing auto-filled details instead of the values entered by the user. The update adds a submission lock to prevent duplicate submissions triggered by rapid or overlapping user actions (e.g., double-clicking Add or pressing Enter and clicking Add).

• Delayed Commission Dialog (BC-18970)

  BriteCore fixed an issue where users had to write off delayed commissions one entry at a time by letting them write off all delayed commission entries for an agency in a single action. The update also requires users to select a reason (Collected from Agency or Forgiven) and record an explanation.

• Task Age Display Error (BC-20886)

  Task date handling has been improved to ensure accurate and consistent displays across the Task Workbench and Task Detail views: task age no longer appears as NaN, task creation dates no longer default to 1/1/1970, and task due dates no longer shift based on the user’s time zone, ensuring the same due date is shown everywhere.

• Restore Delete Button in BriteData (BC-21020)

  The Delete button has been restored for BriteData reports. This allows users to delete reports as needed, supporting normal data cleanup and corrections.

• Fix for E2Value Page Load Failure (BC-19516)

  BriteCore fixed an issue where sometimes the E2Value Replacement Cost Value screen would error out instead of rendering when Dynamic Documents was enabled. The fix ensures the E2Value callback screen is rendered without invoking Dynamic Documents for this workflow, avoiding template resolution failures and allowing the E2Value submission to complete normally.

• SQL Editor Output Filename Preservation (BC-21039)

  Custom output filenames are now reliably preserved when loading and exporting reports. Previously, filenames could be overwritten during report initialization, causing names set in SQL Editor to revert unexpectedly. This has been corrected to prevent unintended changes.

• Base Policy Number Retrieval (BC-21073)

  BriteCore fixed an issue where policy lookups could fail in environments using custom numbering configurations and prevent the system from finding an existing policy. With this update, policy number handling now only evaluates policy-specific numbering sequences, improving accuracy and restoring reliable policy retrieval in affected workflows (including document preview scenarios).

Original source Report a problem

Enhancements
Support Comprehensive List of Excel Formats for Columns in SQL Editor (BC-20389)
An enhancement has been implemented to provide comprehensive support for Excel column formatting in the SQL Editor. Previously, Excel reports did not support customizable column formats. This update modernizes and extends the Excel formatting features with the following improvements:
• Currency formatting: Negative values are now displayed as -$1,234.56 (no parentheses) for improved readability.
• Phone numbers and ZIP codes: Original formatting and leading zeros are preserved, even when values are sourced as integers from the database.
• Integer currency amounts: Values are displayed without unnecessary decimal places, improving clarity and usability.
• Data integrity: Invalid data is gracefully handled and written as text, preventing corruption or runtime errors.
• File size formatting: A new file size type is supported, automatically converting bytes into human-readable units (KB, MB, GB, TB).
This enhancement improves both user experience and overall system reliability.
Month-end "written" commission without Data Frames or Premium Records (BC-17864)
BriteCore improved month-end "written" commission calculations without relying on data frames or premium records. The current “written” commission algorithm depends on premium records. Sites with disable-britedata=true will not generate premium records. We have created a new “written” commission algorithm, currently serving net commission calculations in production.
• Payments Received Report (BC-18516)
• Custom Fee Totals Report (BC-18517)
• Payoff Amounts Reports (BC-18795)
The above reports have been rewritten to use SQL Views as a part of the stock reporting project. Full documentation on the reports is available online in BriteCore and source to the queries is visible in SQL Editor for carriers to customize upon demand.
Support Custom Parameters (BC-20167)
We’ve improved how custom parameters work in SQL Runner reports, making it easier and more intuitive to run parameterized reports.
You’ll now see clearly defined parameter input fields when running SQL Runner reports, allowing you to enter values directly without relying on legacy date range logic. Behind the scenes, we’ve simplified how parameters are handled so date and other inputs are processed more consistently and reliably.
These improvements provide a cleaner, more predictable reporting experience and ensure SQL Runner reports behave consistently with the SQL Editor. Overall, this update makes running and maintaining parameterized reports faster, easier, and more flexible.
Multi-Client | Enhanced Invoice Cloud File Upload Tracking & Resend Support (BC-18459)
We’ve improved how Invoice Cloud file uploads are tracked and managed across multiple clients to ensure files are delivered more reliably.
Uploads to Invoice Cloud are now more accurately tracked, allowing the system to clearly identify when a file has been successfully delivered. In addition, we’ve added tooling that makes it easier to resend files when needed, reducing delays and the need for manual intervention.
These improvements help prevent missed invoice deliveries, streamline recovery when issues occur, and provide a more reliable billing and invoicing experience for customers.
Suspension Rules Enhancements (BC-18583)
We’ve improved how policy suspensions are defined and managed, giving underwriting teams more control and precision when configuring suspension rules.
You can now define multiple rules within a single suspension, with at least one restriction required. This helps ensure suspensions are intentional, targeted, and easier to manage. We’ve also added new ways to narrow where suspensions apply, including Policy Type, Policy Type Item, and Subline, allowing suspensions to be aligned more closely with specific products and configurations.
In addition, when enabled, the system can automatically combine overlapping or adjacent suspensions, reducing duplication and simplifying suspension management. These improvements maintain full compatibility with existing suspension behavior, ensuring suspension maps and automated processing continue to work as expected.
Create Full Quote API Timeout & Policy Sequence Improvements (BC-19569)
We’ve improved the performance and reliability of the Create Full Quote API, helping quotes complete more consistently—especially during periods of high activity.
Policy number assignment is now handled more efficiently, reducing delays and minimizing the risk of timeouts when creating quotes. In addition, automated load testing has been added to help ensure the system remains stable as usage scales.
These improvements result in faster, more reliable quote creation and a smoother experience for users relying on automated or high-volume quoting workflows.
Expose Loss History Report Number to STP Rules (BC-19675)
We’ve improved how the system handles errors when retrieving LexisNexis CLUE/ISO loss history during Straight-Through Processing (STP). This release introduces the ability to expose the loss history report number to STP (Straight Through Processing) Rules within the BriteCore platform. By making this information accessible, underwriters and automated rule engines can more efficiently reference and apply criteria based on an applicant's prior loss history.
STP Enhancements | Access to “Rate Per” Inputs (BC-19708)
This release introduces enhanced support for "rate per" inputs within STP advanced triggeres, enabling more flexible and precise configuration of rating parameters. Users can now define and utilize rate inputs dynamically based on contextual data, ensuring that calculation logic accommodates varying input scenarios efficiently. This feature streamlines workflows and improves the accuracy of rate calculations, contributing to a more robust and adaptable rating engine experience.
Instant Add-on Quoting | Category Mapping from Underlying Policies (BC-19859)
This update introduces enhanced mapping functionality for categories derived from underlying policies in the BriteCore platform. With these improvements, category information from the base policy can now be automatically referenced and utilized, streamlining data integrity across related policy records. The integration ensures more accurate and consistent category assignment, reducing manual effort and potential for errors in policy administration workflows.
Audit Trail for MVR Report Requests (BC-19887)
BriteCore added improved visibility into Motor Vehicle Report (MVR) requests to make it easier to understand when and how MVRs are run. Introduced audit trail logging for Motor Vehicle Report (MVR) requests. Each MVR pull now records who initiated it, when it occurred, and whether it was system-triggered or manual.
Task Definition Management Improvements (BC-20058)
You can now manage task definitions (task types) directly through the user interface, making it easier to configure and customize tasks to fit your workflows.
Previously, task definitions could only be updated through API calls or with assistance from BriteCore, which made changes harder and slower. With this update, you can create and manage task types on your own, giving you more flexibility and control over how tasks are defined and used.
This improvement simplifies configuration, reduces reliance on manual updates, and helps ensure task workflows better align with your operational needs.
Task Definitions | Configure Task Assignees in the UI (BC-20060)
Administrators can now configure task definition assignees directly through the user interface, making task management faster and more flexible.
Previously, changing who tasks could be assigned required assistance from BriteCore, which could slow down workflow updates. With this new interface, authorized users can view task definitions and easily update eligible assignees in real time.
This enhancement removes configuration bottlenecks, reduces dependency on technical support, and allows operations teams to quickly adapt task assignments as workflows and team structures change.
API Support for Downloading Import Schema Files (BC-20186)
We’ve added new API capabilities that make data migration and imports easier and more predictable.
You can now download schema files directly through the API, allowing you to see the exact structure required for supported data imports before submitting data. The API includes predefined schemas for a wide range of import types—such as insureds, agencies, and payments—and provides endpoints to list available schemas and generate the appropriate schema file for each import type.
These improvements reduce guesswork during data migration, help prevent import errors, and provide a flexible foundation for supporting additional import schemas in the future. This work was delivered as part of the broader Data Migration API initiative
STP Rule Waiver Support for Underwriter Approvals (BC-20203)
BriteCore added core waiver functionality to Straight-Through Processing (STP) that allows underwriters to approve and waive triggered rules, with those waivers automatically respected in future STP runs. When an underwriter grants approval, the system records the waiver, logs an audit note, and ensures the waived rules are treated as completed (“run”) rather than re-triggered, preventing duplicate reviews and unnecessary workflow interruptions. Waivers are currently applied in an all-or-nothing manner (all rules waived or none), and legacy engines configured to “Run Always” are unaffected. This enhancement improves underwriting efficiency, reduces repeat work, and provides clearer traceability and consistency across policy revisions.
Instant Add-on Quote | Controlled Mapping from Underlying Policies (BC-20430)
We’ve improved how information is carried over from an underlying policy when creating a an instant add on quote, giving teams more control over what data is included. This update introduces the ability to synchronize configuration data between add-on policies (ex. Umbrella) and their underlying policy records within the BriteCore platform. The new feature ensures consistent and reliable data synchronization for policy information, reducing the risk of discrepancies and improving operational efficiency across policy management workflows.
Audit & Change Tracking for SQL Editor Reports (BC-20475)
We’ve added enhanced audit and change-tracking capabilities to the SQL Editor to support compliance and improve visibility into report changes.
Updates to SQL Editor reports are now automatically tracked, including who made a change, when it was made, and what was changed. You can view a history of edits, compare versions, and filter changes by date—providing a clear audit trail for at least one year.
These improvements bring the same versioning and transparency available in stock reports to user-created SQL reports, making it easier to support compliance requirements, troubleshoot changes, and maintain confidence in reporting.
Claims Feedback | Enable Multi-Select and Bulk Actions on Files (BC-20500)
This update introduces bulk action capabilities to the new Attachments UI, allowing users to efficiently manage multiple files at once. With this enhancement, users can now select and perform actions on several attachments simultaneously, streamlining workflows and improving overall usability within the Attachments section.
Client Feedback | Expand Past Claim Data Display in Claims UI (BC-20517)
An enhancement was implemented to address client feedback by expanding the past claims data displayed in the new Claims UI to match legacy functionality. The Past Claims section now shows key details including loss date, incurred amount, status, and loss type, supports sorting and direct navigation to individual claims, and respects existing permission settings. No new data fields were introduced—this is a display-only improvement.
Rating documentation in app (BC-20546)
Rating documentation is now available directly within BriteCore. Users can access in-app documentation describing available variables and functions when setting up evals. The documentation can be within the user interface that is used to define the eval.
Instant Add on Quoting | Enable/Disable Setting for Estimated Quote(BC-20590)
An enhancement was implemented to improve configurability of the estimated quote feature for Instant Add-on Quotes by introducing a new advanced setting, estimated-quote-enabled, which is enabled by default. This setting allows carriers to enable or disable the estimated quote section in the sidebar; when disabled, the sidebar displays an informational message only.
Tasks | Expanded Task Status Options (BC-20649)
We’ve expanded the task status options to better reflect the full lifecycle of a task.
Instead of being limited to just two statuses, tasks can now be assigned from a broader set of status values. This provides greater clarity into progress, helps teams track work more accurately, and makes it easier to manage tasks as they move through different stages.
Reporting | Manage Report BriteCore Update (BC-20731)
We’ve made updates to Manage Report functionality in BriteCore to improve reliability and overall system behavior.
These changes ensure report management actions function as expected and align with defined requirements, supporting a smoother and more consistent reporting experience.
Attachments | File Type Selection Added During Quoting (BC-20750)
We’ve enhanced the attachments experience in the quote wizard by allowing you to select a file type when uploading policy documents.
When adding attachments, you’ll now see a file type dropdown with predefined categories—such as Loss History, Financial Statements, and Certificates of Insurance. You can upload multiple files and assign different types to each, making it easier to organize and identify documents. File type selection is optional, so you can continue uploading files without interruption.
This improvement helps keep policy documents better organized and easier to manage throughout the quoting process.
Policies | Binder Policies Now Reinstate Correctly After Payment (BC-20872)
We’ve improved how binder policies are reinstated after a non-payment cancellation.
When a binder policy enters a cancellation-pending status due to non-payment and the insured completes payment, the policy will now correctly reinstate to Binder Active, rather than moving directly to Active. All appropriate billing, reinstatement, and notification events are also triggered as part of this process.
This update ensures binder workflows behave as expected, improves accuracy in policy status tracking, and supports a smoother experience when resolving non-payment cancellations.
Data Migration | Error Logs Now Returned on Job Failures (BC-20899)
We’ve improved visibility into data migration failures by ensuring error logs are always returned when a migration job fails.
When a data migration script encounters an error or crashes, detailed error logs are now sent back through the API. This makes it easier to understand what went wrong, diagnose issues quickly, and take corrective action without additional investigation or guesswork.
This enhancement improves reliability, reduces troubleshooting time, and provides clearer feedback when data migration jobs do not complete successfully.
SQL Editor | Light and Dark Theme Support (BC-20911)
We’ve updated the SQL Editor to fully support both light and dark themes.
Text, icons, backgrounds, menus, buttons, and tables now adapt automatically to the selected theme, ensuring consistent readability and a cohesive look and feel across the interface. This improvement enhances usability, reduces eye strain, and keeps the SQL Editor visually aligned with the rest of the platform.
Reporting | Export Options Now Available in the UI (BC-20919)
We’ve made report export options visible directly in the user interface.
When running a report, available export options now appear in the Run Report sidebar, allowing you to select how results are delivered without needing assistance from support or technical services. This gives users more control, speeds up report delivery changes, and simplifies report management.
Attachments | Clear Error Message for Large File Uploads (BC-21034, BC-20893)
We’ve improved the attachments experience to provide clear, user-friendly feedback when uploading large files.
If you attempt to upload a file larger than 200 MB, the system now displays a clear notification explaining the size limit. This helps prevent confusion, avoids silent upload failures, and makes it easier to correct the issue before retrying.
This improvement helps keep policy documents better organized and easier to manage throughout the quoting process.
Reporting | Improved Accuracy in ISO A-Plus Monthly Reports (BC-14960)
We’ve improved how ISO A-Plus monthly reports are generated to ensure claim data is reported accurately.
Archive-only records are now excluded from submissions, and updates to existing claims—such as changes to the cause of loss—are sent as corrections rather than creating new claim records. These improvements help ensure reports accurately reflect true claim activity, reduce duplicate or incorrect submissions, and support cleaner downstream reporting.
Improved Monitoring for Declaration Email Delivery (BC-19311)
We’ve improved monitoring and visibility for agency and agent declaration emails to help ensure they are delivered as expected.
Additional logging and metrics have been added to track the declaration email delivery process, making it easier to identify when emails are sent and to troubleshoot issues if delivery does not occur. These improvements strengthen system monitoring and support faster resolution when questions arise.
Overall, this update improves reliability and transparency around declaration email distribution and helps ensure agents and agencies receive the documents they need without delay.
Defects
Claims | Consistent Claimant Sorting Across Tabs (BC-17622)
BriteCore fixed an issue that caused claimants to appear in a different order when navigating between the Exposures and Accounting tabs within a claim. This release introduces improved ordering of exposures across multiple endpoints, now sorted by claimant, coverage, and loss. Users can expect more intuitive navigation and data presentation within claims processes, making it faster and easier to review exposures by claimant, coverage details, and associated losses.
Billing | Pre-Authorized Payment Schedule Amounts Corrected (BC-18269)
We’ve fixed an issue where pre-authorized payment schedules could generate incorrect payment amounts.
Payment schedules are now calculated correctly based on policy premiums and billing terms, ensuring statements reflect accurate amounts. This improvement helps prevent billing discrepancies, reduces confusion for customers, and supports more reliable payment processing.
Claims | Select from Multiple Applicable Catastrophes (BC-18925)
BriteCore fixed an issue that affected catastrophe selection during claim creation when more than one catastrophe applied to the date of loss. BriteCore now enables users to easily select the relevant catastrophe when creating a new claim, only when multiple catastrophes are applicable to the incident.
Renewal Mailings | Improved Form Inclusion Accuracy (BC-19474)
We’ve fixed an issue that caused extra forms to be included in renewal mailings when certain form details were missing.
Renewal mailings will now correctly exclude forms that do not have valid Form Code and Edition Number values. This ensures that only the appropriate, required forms—such as privacy disclosures—are included based on proper business rules.
This improvement reduces unnecessary paperwork, helps prevent confusion for policyholders, and supports compliance by ensuring renewal mailings contain only relevant and correctly validated documentation.
Corrected Underwriting Rule Timing in QW (BC-19542)
We’ve fixed an issue in Quick Quote (QW) where underwriting rules were not consistently applied after certain coverage selections were changed.
In some cases, when an optional coverage—such as Water Backup—was selected, deselected, and then selected again, the system could temporarily display coverage limits that were not allowed based on underwriting rules. This could lead to higher limits appearing as available when they should have been restricted.
With this fix, underwriting rules are now applied consistently as coverage selections change, ensuring that only valid options are presented. This improvement prevents incorrect limit selections, maintains underwriting intent, and ensures a more reliable quoting experience for agents.
Claims | Loss Notice Preview Restored (BC-19790)
We’ve resolved an issue that prevented Loss Notice documents from being generated using the Preview function.
You can now successfully preview Loss Notice documents before finalizing them, allowing you to review and confirm the content as part of the normal claims workflow.
Policy | Improved Copy LED Handling with Prior Deletions (BC-19792)
We’ve fixed an issue with the Copy LED (Line / Exposure / Detail) feature where policy type information was not always recognized correctly when copying revisions that included prior deletions.
The system now consistently identifies and maintains the correct policy type during the copy process, even when earlier revisions included deleted items. This ensures copying policy structures works reliably across complex revision histories.
This improvement enhances data integrity, reduces errors during policy changes, and supports smoother workflows when modifying or reusing existing policy structures.
Claims | Audit Notes Added for Authority Limit Changes (BC-20010)
We’ve improved audit visibility for changes to claims authority limits. When authority limits are updated, the system now automatically creates notes documenting the change, ensuring a clear and reliable audit trail.
This makes it easier for teams to verify when authority limits were changed, what was updated, and supports compliance and review requirements without manual tracking.
Rules | Subjectivity Rule Changes No Longer Cause Errors (BC-20153)
Previously, users experienced errors when editing and saving Rules after adding Subjectivities to a policy workflow. The issue occurred when a Rule’s event type was changed to "Subjectivity" after the initial save, which resulted in UI errors and disrupted normal operations.This release resolves the root cause, allowing users to create and edit Rules involving Subjectivities without encountering errors.
Endorsement Effective Date Changes Now Properly Restricted (BC-20194)
We’ve fixed an issue in the quote wizard endorsement flow where agents could change a policy’s effective date outside of allowed limits. Agents are now prevented from modifying the effective date to an earlier or otherwise invalid date when processing endorsements. This ensures endorsements follow the correct policy timeline and aligns the workflow with underwriting and configuration rules.
Policies | Line Item Data Validation Prevents Processing Errors (BC-20218)
We’ve fixed an issue where incorrect line item data could cause errors during policy processing.
Line item information is now validated and formatted correctly before being processed, preventing interruptions that could block transactions. This improvement increases system stability and ensures policies can be updated and processed smoothly without unexpected errors.
BriteQuote | Improved Suspension Messages for County and ZIP Code Closures (BC-20274)
We’ve fixed an issue with quoting suspensions that could cause confusing or overly detailed error messages when quoting in suspended counties or ZIP codes.
When a quote falls within a suspended area, the system now displays clear, concise suspension messages instead of listing all restricted locations. This prevents temporary loading issues and makes it easier to understand why quoting cannot proceed.
Claims | Reinsurer Now Available in Accounting (BC-20379)
We’ve fixed an issue in the new Claims experience where reinsurers were not visible or selectable in the Accounting tab. Reinsurers are now displayed and available for selection, matching the functionality previously available in the legacy Claims interface. This ensures recovery-related workflows work consistently across the new and existing Claims experiences.
Data Validation | Prevent Invalid Year Entries (BC-20416)
We’ve fixed an issue that allowed invalid year values (such as “0025”) to be entered and saved, which could cause downstream processing and vendor upload failures.
The system now validates year values correctly before saving, ensuring only valid dates are accepted. This improves data integrity, prevents vendor integration errors, and reduces processing failures.
Claims | Adjuster and Supervisor Email Notifications Restored in New UI (BC-20448)
We’ve fixed an issue where email notifications were not sent or logged when adjusters or supervisors were assigned using the new Claims interface.
Email notifications are now sent correctly and recorded when assignments are made, restoring parity with the legacy Claims experience. This ensures assignment changes are communicated properly and remain auditable.
Quotes API | Validation Errors Returned for Stateless Quotes (BC-20456)
BriteCore fixed an issue where stateless quote creation via API did not return validation errors in API responses. Stateless quotes now return the same clear, actionable validation messages as stateful quotes, making it easier to identify and resolve issues during quote creation..
Credit Score Checks | Vendor Requirement Handled Correctly (BC-20477)
We’ve fixed an issue where credit score checks were still required even after a credit score vendor had been removed. Credit scores are now only required when a vendor is configured. This allows users to rate and submit quotes without errors when no credit score provider is in place, improving flexibility and preventing unnecessary blocking errors.
Claims | Loss Cause Updates Now Reflected in Claims Search List (BC-20497)
We’ve fixed an issue where changes to a claim’s loss cause were not immediately reflected on the Claims list page. Updates to loss causes now display correctly in the list view, ensuring claim summaries remain accurate and up to date. This improves visibility and reduces confusion when reviewing or managing claims.
Create Quote Extended API Returns Clearer Error Details (BC-20528)
We’ve improved error handling in the Create Quote Extended API to provide more specific and actionable feedback. When required inputs are missing, the API now returns detailed error information identifying exactly which coverage or field needs attention, rather than a generic error message. This makes it easier for users and integrations to diagnose and resolve quoting issues quickly.
Claims | JPEG Uploads Restored in New Attachments Experience (BC-20535)
We’ve fixed an issue in the new Claims Attachments experience that prevented JPEG image uploads. Adjusters can now upload photo documentation as expected, restoring a key part of the claims workflow. This fix eliminates delays caused by failed uploads and ensures images can be attached reliably to claims.
Payments | Hide “Agency Sweep” Options for Agents (BC-20556)
We’ve added a new configuration setting that allows administrators to hide “Agency Sweep” payment options from the Agent user interface.
This gives carriers greater control over which payment options are visible to agents, ensuring agents only see payment methods that align with their role, permissions, and business processes. The result is a cleaner interface and a more focused, intuitive payment experience for agents.
Claims | “Email, but Do Not Print” Option Now Works as Intended (BC-20558)
We’ve fixed an issue with Claims Custom Documents where the “Email, but Do Not Print” option was not being honored. When this option is selected, the system will now correctly save the print preference and prevent the document from being printed. This ensures documents are delivered exactly as specified, reduces unnecessary printing, and improves efficiency in claims document handling.
Policies | New Status for Streamlined STP-Approved eSignature Processing (BC-20148)
We’ve introduced a new policy status—PENDING_E_SIGNATURE_STP_APPROVED—to improve visibility and automation during policy approvals. This status clearly indicates when a policy has passed Straight-Through Processing (STP) and is waiting for eSignature completion. By making this stage explicit, the system reduces manual follow-ups, improves transparency into approval progress, and supports a smoother, more efficient policy commitment process.
Custom Deliverables | Installment Billing Statement Generation Restored (BC-20584)
This release resolves an error that occurred when generating Custom Document Templates for Installment Billing Statements. The bug prevented successful generation of these documents, potentially disrupting billing communications and customer notifications. The fix ensures Installment Billing Statements using Custom Document Templates now generate correctly without errors, restoring reliable document production. This improvement enhances billing workflow efficiency, ensures timely delivery of billing statements to customers, and reduces manual intervention required to address generation failures.
Applications | Audit Notes Generated for Application Question Changes (BC-20587)
We’ve fixed an issue where changes to application questions were not generating notes, resulting in missing audit history.
Notes are now correctly created whenever application question answers change, restoring full traceability and audit visibility. This ensures changes are properly recorded and can be reviewed as needed.
Documentation | Brand API Spec Builds Successfully (BC-20602)
We’ve resolved an issue that prevented Brand API specification files with attachments from building correctly.
Documentation builds now complete successfully, ensuring branded API specifications are generated reliably for supported clients. This improves consistency and stability for API documentation delivery.
Applications | Improved Performance on Application Questions Screen (BC-20604)
We’ve fixed a performance issue that caused slow response times when interacting with application questions.
The Application Questions screen now processes changes more efficiently, reducing unnecessary system calls and restoring fast, responsive behavior. This results in a smoother experience and reduced wait times.
Compliance | Financial Antiterrorism Cross-Reference Restored (BC-20625)
We’ve fixed an issue that prevented Financial Antiterrorism (OFAC) cross-reference reports from running due to a certificate error.
Reports can now be requested successfully, restoring access to required compliance checks and eliminating unnecessary blocking errors.
Quotes API | Numeric Inputs Supported in Create Quote Extended (BC-20630)
We’ve fixed an issue that prevented numeric input values from being submitted through the Create Quote Extended API.
Numeric responses are now accepted and validated correctly, allowing quotes to be created without errors and ensuring full support for all question types.
Payments | Improved Handling of Timeout Scenarios (BC-20732)
We’ve improved how the system handles payment timeouts to ensure transaction results are recorded accurately.
When a payment request times out, the system now listens for delayed confirmation updates and reconciles the final outcome automatically. This ensures both successful and declined payments are captured correctly, even when responses are delayed.
These improvements reduce uncertainty around payment status, improve reliability during peak processing periods, and support more consistent payment handling as part of the ongoing Stripe Connect integration enhancements.
Applications | Default Questions Now Apply After Underwriting Rule Changes (BC-20754)
We’ve fixed an issue where default application questions were not applied after certain underwriting rule changes.
When policy details—such as the policy form—are updated, default supplemental questions will now populate correctly. This ensures the application questions reflect the current underwriting configuration and prevents missing or incomplete information during quoting.
This fix improves consistency and ensures required questions are applied as intended throughout the quote process.
Contacts | Login Information Can Now Be Set Correctly (BC-20762)
We’ve resolved an issue that prevented login information from being set on contact records in multi-client environments.
Contact login credentials can now be created and saved successfully, restoring full functionality for user access and portal management. This improvement simplifies onboarding, improves access control, and ensures contacts can log in as intended.
Claims | Clear Error Messages for Large File Uploads (BC-20807)
We’ve fixed an issue in the new Claims experience where large file uploads could fail without any visible error message.
When uploaded files exceed the supported size limit, the system now provides clear feedback to let users know why the upload could not be completed. This helps prevent confusion and allows users to take corrective action—such as reducing file size or splitting uploads—without relying on trial and error.
This improvement makes document uploads more transparent and improves the overall claims experience.
Reporting | Policy Term Expirations Stock Report Fixed (BC-20850)
We’ve resolved an issue affecting the Policy Term Expirations stock report.
The report now runs and displays results correctly, ensuring users can reliably access expiration data for tracking, planning, and reporting purposes.
STP Events | Referred to Underwriting Details Handled Consistently (BC-20912)
We’ve fixed an issue where Straight-Through Processing (STP) referral details were not always returned in a consistent format.
Referred-to-underwriting event details are now provided in a consistent structure across all scenarios, ensuring reliable handling by downstream processes and integrations. This improves stability and prevents errors related to unexpected data formats.
Agent Portal | Replacement Cost Value Updates Now Display Immediately (BC-20915)
We’ve fixed an issue in the Agent Portal where replacement cost values updated by a property lookup did not appear right away.
Replacement cost values now display immediately on the rating screen as soon as they are calculated, without requiring a manual page refresh. This eliminates confusion, ensures agents see up-to-date information, and helps prevent quoting errors caused by delayed UI updates.
Platform | Cache Expiration Handling Corrected (BC-20959)
We’ve fixed an issue with the system’s cache expiration logic that could allow expired values to remain in memory under certain conditions.
Expired cache entries are now properly cleared before new values are stored, ensuring the system always returns current, accurate data. This improvement strengthens reliability and prevents unexpected behavior related to stale cached values.
Reporting | Agency Experience Report Generation Restored (BC-20982)
We’ve resolved an issue that caused Agency Experience reports to fail for some clients.
Reports now generate successfully, restoring access to critical reporting data. This fix also improves system robustness and helps prevent similar issues in the future.
Renewals | Improved Error Notification for Renewal Revisions (BC-21025)
We’ve fixed an issue where errors during renewal revisions were not clearly communicated.
Customers are now properly notified when a renewal revision encounters an issue, making it easier to understand what happened and take appropriate action. This improves transparency and reduces confusion during the renewal process.
Rating | No-Risk Policy Types Now Rate Without Errors (BC-21066)
We’ve fixed an issue affecting policy types that are configured to allow policies without risks or properties.
Quotes for these policy types can now be rated successfully when no properties are present, without triggering state or country validation errors. When a policy does include one or more properties, standard validation rules still apply to ensure the primary property matches the policy’s rating state and country.
This improvement ensures policy types designed to support no-property scenarios behave as intended and allows users to move quotes forward without unnecessary blockers.
Attachments | Folder Move and Edit Actions Restored (BC-21072)
We’ve fixed issues in the new Attachments interface for quotes and policies.
Attachments can now be moved between folders as expected, and editing attachments no longer causes UI errors. This restores full attachment management functionality and ensures documents can be organized and updated without interruption.

Original source Report a problem

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