Britecore Release Notes

New Features and Enhancements

Auto Data Prefill Captures Marital Status and Length of Driving Experience (BC-23088)

BriteCore now captures marital status and driving experience length in driver information during quoting via Auto Data Prefill. These fields support more accurate auto data pre-fill and rating.

Adding Items With an External Reference via the Quote API (BC-22767)

BriteCore added external referenced items to the the full-quote modification API endpoint. Integrators attempting to add these items did not have the possibility before.

Conviction Date can now be Required on the Driver Screen (BC-22874)

BriteCore updated the Driver screen so that a carrier can configure the conviction date to be required. Previously, the date could be left blank. Requiring the conviction date improves the completeness and accuracy of driver data captured during the quoting and underwriting process.

Bug Fixes

Clear Error Explanation When a Cancellation Conflicts With a Claim (BC-23344)

When a policy cancellation is blocked because of an open or paid claim with a conflicting loss date, BriteCore now returns a clear validation message instead of a generic system error. This error explanation helps users and integrations quickly understand why the cancellation could not be completed and take the appropriate next steps.

Improved Handling of Common Payment Gateway Failures (BC-22903)

BriteCore improved error handling for common payment gateway failures so transient gateway problems are detected and surfaced more reliably. Payments that previously failed with unclear results left users uncertain of the outcome. Clearer feedback and better prevention of duplicate or stuck transactions now make payment processing more reliable.

Void Pending ACH Payments from Account History (BC-23365)

BriteCore updated the Account History experience to allow eligible in-flight ACH payments to be voided when appropriate. This change affects only how the transaction is managed within BriteCore's Account History and does not void or refund the payment with the external payment processor. It also corrects an issue where the Void action was unnecessarily unavailable for eligible transactions.

Deleting Saved Payment Methods Detaches Them on Stripe (BC-17911)

When a saved payment method is deleted in BriteCore, it is now also detached on Stripe so the two systems stay in sync. This prevents orphaned payment methods from remaining on the Stripe account after removal.

Correct User Name Recorded When Adding a Payment Method (BC-19725)

BriteCore identified and resolved an issue where adding a payment method recorded the wrong user name in the associated note. The note now reflects the user who actually added the payment method, improving the accuracy of the audit trail.

Effective Date Revisions No Longer Reset the Term Credit Score (BC-23329)

BriteCore resolved an issue where processing an effective date revision reset the term credit score to zero. Because the credit score feeds rating, this situation could impact the proper calculation of premium on affected policies. Effective date revisions now preserve the existing term credit score.

Policy Contacts Wizard Error for Organization Contacts (BC-23343)

BriteCore resolved an issue that prevented organization contacts from being added or edited in certain configurations.

Delay Cancellation Date Now Updates Correctly (BC-20855)

BriteCore resolved an issue where the delay cancellation date did not update as expected. Users adjusting a delayed cancellation saw the original date persist. The cancellation date now updates correctly when changed..

Geography Override Honored When Geocoding Returns No State (BC-23470)

BriteCore resolved an issue where a manual geography override was ignored when the address geocoder could not determine a state. This could lead to incorrect territory assignment on affected risks. The system now respects the geography override even when the geocoder returns no state.

Graceful Handling of Missing Address Fields During Catastrophe Score Processing (BC-23399)

BriteCore resolved an issue where missing property address fields caused an exception during catastrophe (AON Cat Score) processing on revision import. The failure could interrupt revision imports for affected properties. The process now handles missing address fields gracefully so imports complete.

Policy Declaration Generation Error (BC-22341)

BriteCore identified and resolved an issue where generating a policy declaration could fail with a "PDF file not found." error when selecting View Dec. Affected users were unable to produce the declaration document. Policy declarations now generate reliably.

Renewal Declarations Not Generating After a Workflow Interruption (BC-22051)

BriteCore resolved an issue in which a policy could fail to generate its renewal declaration after a specific workflow interruption. Affected renewals were left without a declaration document. Renewal declarations now generate even when the workflow is interrupted.

Commission Delay Alerts Sent to the Updated Recipients (BC-23437)

BriteCore resolved an issue in which the commission-payments-delayed alert email used a stale recipient list and ignored the updated admin-alert recipients. Intended recipients could miss important commission notifications. The alert now applies the current admin-alerts recipient configuration.

Agency Commissions Bulk Export Returns All Rows (BC-23266)

BriteCore resolved an issue in which the bulk export on the Agency Commissions page returned only a single row instead of the full result set. Users relying on the export received incomplete commission data. The bulk export now includes all rows.

Original source

New Features and Enhancements

Agent Quote Submission Blocked Until Straight Through Processing Reviews Complete (BC-23037)

BriteCore added a safeguard in the agent quote flow that prevents an agent from submitting a policy when Straight Through Processing (STP) reviews have been triggered but are still awaiting approval, or when the Straight Through Processing evaluation fails to complete. In these cases the agent now sees a clear validation message and the submission is held, so policies cannot bypass required underwriting review or enter an invalid state.

Report Hide Control Now Limited to Administrators (BC-22943)

BriteCore restricted the report hide control, the eyeball icon at the end of each row on the report list, so that it now appears only for administrators. Non-administrator users can no longer hide or unhide reports, while administrators retain the ability to hide reports to tidy the workspace or prepare them for deprecation.

Bug Fixes

Payments No Longer Blocked by a Deleted Future Revision (BC-23157)

BriteCore identified and resolved an issue where deleting a future renewal revision could leave a term without a usable effective-date revision and then block payments on the current term, with processing failing because the policy accounting class could not be initialized. Current-term payments now process correctly even when a future renewal revision has been removed or was never created.

Reinstatement Now Clears the Cancellation Date Across All Term Revisions (BC-15659)

BriteCore identified and resolved an issue where reinstating a policy did not clear the cancellation date on every revision of the term, which could create an out-of-sequence data condition and display an incorrect cancellation effective date on notices such as the Notice of Non-Renewal. Reinstatements now clear the cancellation date across all affected revisions so dates report correctly.

Policies Can Now Be Canceled on the Term Expiration Date (BC-17575)

BriteCore identified and resolved an issue where canceling a policy effective on the expiration date of the current term could fail with a system error when the system attempted to move the cancellation to a new effective date and could not locate the associated policy type. These cancellations now process successfully.

Automatically Calculated Coverage Limits Now Save Correctly During Policy Creation and Rating (BC-23155)

BriteCore identified and resolved an issue affecting coverage limits that the system calculates automatically rather than having a user enter them, such as Coverage D (Loss of Use), which is set as a percentage of another coverage. These limits were calculated in the

PolicyBuilder

for display but were written to the database only when the policy went through a rating pass. Policies created through the API endpoint without that rating step, including converted policies and policies that were committed without being rated, could therefore store the limit as zero even though the correct amount appeared in the user interface, and that zero could carry through to the Declarations. BriteCore now saves automatically calculated limits both when a policy is created through the API endpoint and whenever it is rated, so the stored value matches the displayed value and the Declarations reflect the correct amount.

Motor Vehicle Report Validity Period Now Honored in Auto (BC-18976)

BriteCore identified and resolved an issue where the configured Motor Vehicle Report (MVR) validity period was not honored on automobile policies, causing new reports to be ordered at renewal before the validity period had elapsed. The system now respects the configured validity period so reports are reordered only when they are due.

Unpaid Prior Term Balances Now Carry Forward to Renewal (BC-21958)

BriteCore identified and resolved an issue where a small outstanding balance from a prior term was not always added to the renewal bill, payoff amount, or current amount due. Cross-term debits now carry forward to the renewal term as expected.

Builder Renewals No Longer Fail When a Coverage Has No Default Limit (BC-23374)

BriteCore identified and resolved an issue where a policy renewal could fail during the Persistent Builder copy step when a coverage used a rate configured with a chosen limit but no default limit row. On affected policies the renewal could not complete and was automatically rolled back, returning only a generic error that directed the user to open a support ticket, and the failure recurred on every nightly and manual renewal attempt. The system now treats a missing default limit row as a valid configuration that means no default limit is applied, so these renewals complete as expected.

Opening Contacts No Longer Returns a Server Error (BC-23293)

BriteCore identified and resolved an issue where opening the Contacts page on certain sites returned an internal server error. The Contacts page now loads as expected.

Agents Can Now Proceed Past the Risk Screen in the Quote Flow (BC-23320)

BriteCore identified and resolved an issue where users working in the agent view were unable to move past the Risk screen in the quote flow because of a script error. Users can now navigate through the quote flow as expected.

SQL Editor Now Saves a Delimiter Choice of None for CSV and Fixed Width Reports (BC-23111)

The delimiter setting in SQL Editor report settings applies to CSV and fixed width text output formats and determines whether output values are wrapped in quotes. BriteCore identified and resolved an issue where selecting a delimiter of None did not save correctly, which caused text output files containing spaces to be wrapped in quotes, adding extra characters that invalidated the report. Reports can now be saved with no delimiter as intended.

Declaration Documents No Longer Fail Silently During Generation (BC-23273)

BriteCore identified and resolved an issue where a declaration document could silently fail to generate when concurrent document jobs for the same policy contended for the same database records, leaving an empty file stuck in the print queue with no automatic retry. The affected insured could then be missing required documents without anyone being alerted. Document generation now handles this contention so declarations produce reliably.

Duplicate Commission Alert Emails No Longer Sent Daily (BC-15726)

BriteCore identified and resolved an issue where a recurring system entry to zero out a commission could trigger a commission payment alert email to be sent to the carrier every day. These duplicate daily alert emails are no longer generated.

Adjusted Commission Totals Now Save and Export Correctly (BC-23286)

BriteCore identified and resolved an issue where manual commission adjustments updated the Total to Be Paid shown on the Agency Commissions page but did not update the stored payment amount, so the commission export could use the original, unadjusted amount and risk overpaying. The adjusted total now syncs to the stored and exported payment amount so the amount paid matches what is shown.

Commission Report Amounts Now Reconcile with Payments (BC-17352)

BriteCore identified and resolved an issue where the amounts shown on individual agency commission reports did not always match the amount the insured paid, including occasional small rounding correction lines. Commission report amounts now reconcile with the payments received.

Stripe Payments Now Included in Payment Log Totals and Electronic Payment Report (BC-19282)

BriteCore resolved an issue affecting one-time credit card and ACH payments submitted through the public payment gateway (Secure Payment). Previously, these payments appeared as individual entries in the

Payment Log

but were excluded from the credit card and ACH totals displayed at the bottom of the report. They were also omitted from the

Electronic Payment Report

. BriteCore updated the transaction classification and reporting logic so that Secure Payment credit card and ACH transactions are now included in both the

Payment Log

totals and the

Electronic Payment Report

, alongside all other electronic payments. Carriers can now rely on these reports to provide accurate totals regardless of where the payment was collected.

Payment Modal No Longer Closes When Clicking Outside It (BC-20419)

BriteCore identified and resolved an issue where the payment modal closed unexpectedly when a user clicked anywhere outside it, which could interrupt users while they were reviewing or entering payment details. The modal now closes only when the user selects the X (close) button.

Debit Card Payments at Secure Checkout Now Charge the Displayed Debit Card Fee (BC-23126)

BriteCore identified and resolved an issue on the secure checkout page where changing the card entered from a credit card to a debit card could result in the payment being charged the credit card convenience fee even though the debit card fee was displayed, so the amount charged could differ from the amount disclosed. The displayed payment method, fee, and charged amount now stay synchronized, and the amount charged always matches the amount shown.

Payment Receipts Now Correctly Itemize Payments Split Across Two Terms (BC-23167)

BriteCore identified and resolved an issue where the receipt for a single payment applied across two policy terms could show a grand total that did not match the amount charged, display convenience fees incompletely, and list both portions under the same policy number with no indication of which term each applied to. Receipts for split payments now identify each term, display fees consistently, and show a grand total that matches the full amount charged.

Convenience Fee Settings Now Load on the Payments Settings Page (BC-23383)

BriteCore identified and resolved an issue where the Payments settings page failed to load convenience fee settings because of a script loading error. The page now loads correctly and convenience fee settings display as expected.

Original source

New Features and Enhancements

Agent Quote Submission Blocked Until Straight Through Processing Reviews Complete (BC-23037)

BriteCore added a safeguard in the agent quote flow that prevents an agent from submitting a policy when Straight Through Processing (STP) reviews have been triggered but are still awaiting approval, or when the Straight Through Processing evaluation fails to complete. In these cases the agent now sees a clear validation message and the submission is held, so policies cannot bypass required underwriting review or enter an invalid state.

Report Hide Control Now Limited to Administrators (BC-22943)

BriteCore restricted the report hide control, the eyeball icon at the end of each row on the report list, so that it now appears only for administrators. Non-administrator users can no longer hide or unhide reports, while administrators retain the ability to hide reports to tidy the workspace or prepare them for deprecation.

Bug Fixes

Payments No Longer Blocked by a Deleted Future Revision (BC-23157)

BriteCore identified and resolved an issue where deleting a future renewal revision could leave a term without a usable effective-date revision and then block payments on the current term, with processing failing because the policy accounting class could not be initialized. Current-term payments now process correctly even when a future renewal revision has been removed or was never created.

Reinstatement Now Clears the Cancellation Date Across All Term Revisions (BC-15659)

BriteCore identified and resolved an issue where reinstating a policy did not clear the cancellation date on every revision of the term, which could create an out-of-sequence data condition and display an incorrect cancellation effective date on notices such as the Notice of Non-Renewal. Reinstatements now clear the cancellation date across all affected revisions so dates report correctly.

Policies Can Now Be Canceled on the Term Expiration Date (BC-17575)

BriteCore identified and resolved an issue where canceling a policy effective on the expiration date of the current term could fail with a system error when the system attempted to move the cancellation to a new effective date and could not locate the associated policy type. These cancellations now process successfully.

Automatically Calculated Coverage Limits Now Save Correctly During Policy Creation and Rating (BC-23155)

BriteCore identified and resolved an issue affecting coverage limits that the system calculates automatically rather than having a user enter them, such as Coverage D (Loss of Use), which is set as a percentage of another coverage. These limits were calculated in the PolicyBuilder for display but were written to the database only when the policy went through a rating pass. Policies created through the API endpoint without that rating step, including converted policies and policies that were committed without being rated, could therefore store the limit as zero even though the correct amount appeared in the user interface, and that zero could carry through to the Declarations. BriteCore now saves automatically calculated limits both when a policy is created through the API endpoint and whenever it is rated, so the stored value matches the displayed value and the Declarations reflect the correct amount.

Motor Vehicle Report Validity Period Now Honored in Auto (BC-18976)

BriteCore identified and resolved an issue where the configured Motor Vehicle Report (MVR) validity period was not honored on automobile policies, causing new reports to be ordered at renewal before the validity period had elapsed. The system now respects the configured validity period so reports are reordered only when they are due.

Unpaid Prior Term Balances Now Carry Forward to Renewal (BC-21958)

BriteCore identified and resolved an issue where a small outstanding balance from a prior term was not always added to the renewal bill, payoff amount, or current amount due. Cross-term debits now carry forward to the renewal term as expected.

Builder Renewals No Longer Fail When a Coverage Has No Default Limit (BC-23374)

BriteCore identified and resolved an issue where a policy renewal could fail during the Persistent Builder copy step when a coverage used a rate configured with a chosen limit but no default limit row. On affected policies the renewal could not complete and was automatically rolled back, returning only a generic error that directed the user to open a support ticket, and the failure recurred on every nightly and manual renewal attempt. The system now treats a missing default limit row as a valid configuration that means no default limit is applied, so these renewals complete as expected.

Opening Contacts No Longer Returns a Server Error (BC-23293)

BriteCore identified and resolved an issue where opening the Contacts page on certain sites returned an internal server error. The Contacts page now loads as expected.

Agents Can Now Proceed Past the Risk Screen in the Quote Flow (BC-23320)

BriteCore identified and resolved an issue where users working in the agent view were unable to move past the Risk screen in the quote flow because of a script error. Users can now navigate through the quote flow as expected.

SQL Editor Now Saves a Delimiter Choice of None for CSV and Fixed Width Reports (BC-23111)

The delimiter setting in SQL Editor report settings applies to CSV and fixed width text output formats and determines whether output values are wrapped in quotes. BriteCore identified and resolved an issue where selecting a delimiter of None did not save correctly, which caused text output files containing spaces to be wrapped in quotes, adding extra characters that invalidated the report. Reports can now be saved with no delimiter as intended.

Declaration Documents No Longer Fail Silently During Generation (BC-23273)

BriteCore identified and resolved an issue where a declaration document could silently fail to generate when concurrent document jobs for the same policy contended for the same database records, leaving an empty file stuck in the print queue with no automatic retry. The affected insured could then be missing required documents without anyone being alerted. Document generation now handles this contention so declarations produce reliably.

Duplicate Commission Alert Emails No Longer Sent Daily (BC-15726)

BriteCore identified and resolved an issue where a recurring system entry to zero out a commission could trigger a commission payment alert email to be sent to the carrier every day. These duplicate daily alert emails are no longer generated.

Adjusted Commission Totals Now Save and Export Correctly (BC-23286)

BriteCore identified and resolved an issue where manual commission adjustments updated the Total to Be Paid shown on the Agency Commissions page but did not update the stored payment amount, so the commission export could use the original, unadjusted amount and risk overpaying. The adjusted total now syncs to the stored and exported payment amount so the amount paid matches what is shown.

Commission Report Amounts Now Reconcile with Payments (BC-17352)

BriteCore identified and resolved an issue where the amounts shown on individual agency commission reports did not always match the amount the insured paid, including occasional small rounding correction lines. Commission report amounts now reconcile with the payments received.

Original source

Release Version Number: BriteCore_release_2606_2_2

Release Visibility & Version Verification

To improve release transparency, each release note now includes the corresponding platform version number. After a release is deployed, administrators can verify that their site has received the update by comparing the version number listed in the release notes with the version number displayed in your BriteCore Instance by selecting the help Icon.

Please note that release dates are subject to change as part of our commitment to delivering stable, high-quality software. When issues are identified during final validation, releases may be delayed to ensure the best experience for our customers. We recommend referencing the version number as confirmation that a release has been successfully applied to your site.

New Features and Enhancements

BriteData Report Migration Tool (BC-22696)

BriteCore introduced an AI-assisted migration tool that converts legacy BriteData reports into SQL Editor reports, including automated comparison and validation of the results.

Redesigned Report Notes Page (BC-22938)

BriteCore redesigned the report notes page with an always-visible date-range filter in the page header and a dedicated New Note dialog, replacing the previous modal-based filter and inline row creation while preserving existing note workflows.

Configurable Totals in Excel Reports (BC-18579)

Users can now have totals in Excel reports highlighted and configured on a per-sheet basis, making it easier to identify and customize summary data.

Convenience Fee Settings by State for Stripe Payments (BC-21641)

Carrier administrators who use Stripe as their payment processor can now configure their payment convenience fee settings, including per-card-type fee formulas and disclosure messages, and apply them globally or by state. These disclosures are consistently shown to payors across all payment surfaces (account receivables, policyholder portal, This allows carriers to comply with states that prohibit convenience fees while charging them where permitted.

Deep Links to Prefill the Secure Payment Page (BC-22786)

Policyholders can now follow a link that pre-populates the Secure Online Payment page with their policy number and zip code, reducing friction when paying from an email, text message, or QR-code reminder. Existing validation rules are preserved.

Consistent Invoice Frequency Change Experience on the Builder Screen (BC-22886)

When an administrator changes the billing schedule during a revision on the Builder screen, BriteCore now shows the same Change Billing Schedule confirmation prompt available on the Billing Setup screen, letting the administrator choose whether to preserve or regenerate previously sent invoices. The change is not persisted until the revision is committed.

Additional Interest Date of Birth Available to Rules (BC-21275)

Users can now write rules and evaluations against an additional interest's date of birth, allowing carriers to enforce validations such as age requirements on those parties.

Agency Contacts Can Use a Social Security Number (BC-20619)

Users can now enter agency contacts using a Social Security Number instead of a Federal Employer Identification Number, supporting sole-proprietor agencies that operate under a Social Security Number.

Bug Fixes

Read-Only Users Can Navigate to Agencies from Contacts (BC-22887)

BriteCore resolved an issue where users with read-only reporting permissions could not see the icon to navigate from a contact to its associated agency or agency group. These users can now navigate to agencies directly from the Contacts page.

NSF Row Preserved After Effective Date Change (BC-20991)

BriteCore resolved an issue in which the non-sufficient funds (NSF) row in the accounting history table could disappear from the display after a user changed the revision effective date for a submitted policy with a payment. The NSF entry now remains visible.

Automatic Payment Drafting After Endorsement Reprocessing (BC-20640)

BriteCore resolved an issue in which a policy on an automatic payment schedule could stop drafting payments after an out-of-sequence endorsement was reprocessed, forcing manual payment entry. Scheduled payments now continue to be drafted as expected.

Payment Method Showing as None Selected When Configured (BC-23087)

BriteCore resolved an issue in which the initial bill contact payment method displayed on the Accounts Receivable page as "None Selected" even though an active payment method was configured for the policy term. The configured payment method now displays correctly.

Convenience Fee Rounding Causing Payment Declines (BC-23103)

BriteCore resolved an issue in which convenience fees that landed at an exact half-cent were rounded differently than the payment processor expected, causing credit card payments to be declined during application submission. Fees are now calculated to match the processor's rounding so payments are accepted.

Credit Report Retrieval During Extended Quote Creation Through the API (BC-22576)

BriteCore resolved an issue in which creating a quote via the extended quote creation API endpoint, with credit report retrieval enabled, failed with a rating error. Quotes that pull a credit score now rate correctly through the API endpoint, matching the behavior in the interface.

Hazard Hub Data Triggering Unnecessary Persistent Builder on Renewals (BC-22829)

BriteCore resolved an issue where renewals could unnecessarily trigger persistent builder because Hazard Hub category data differed between the prior term and the renewal. Affected policies now renew and map the category correctly.

Silent Non-Renewal from a Same-Day Endorsement on the Effective Date (BC-21542)

BriteCore resolved an issue in which a policy could be silently skipped by the automatic renewal process when a same-day endorsement was opened on the term's effective date, without generating a failure notification. Affected policies are now correctly evaluated for renewal.

Out-of-Sequence Policy Cancellation Failures (BC-22845)

BriteCore resolved an issue in which processing a manual policy cancellation out of sequence could fail with a generic error, leaving the latest revision active, skipping the return premium, and failing to generate cancellation confirmation documents. Cancellations now complete consistently across terms or roll back fully with a clear error message.

Removing a Named Insured When Another Is Present (BC-22942)

BriteCore resolved an issue where users could not remove the original named insured after adding another named insured. Users can now remove a named insured contact when at least one other named insured remains on the policy.

Agent Permission Enforcement for Policy and Contact Changes (BC-21059)

BriteCore resolved a permissions issue where an agent could assign another agent who was not associated with the policy's agency and could improperly grant that agent an agency role. Permission checks now prevent agents from accessing policies they are not associated with or modifying other agents' contact roles.

Date of Birth Field Overlap on the New Contact Form (BC-23169)

BriteCore resolved a layout issue on the New Contact form where the date of birth field overlapped the Risk ID Number field. The fields now display correctly.

Year-to-Date Totals on Individual Commission Reports (BC-15265)

BriteCore resolved an issue where the year-to-date amount paid column on individual commission statements showed an incorrect total. The column now correctly sums commissions paid for the year through the report date.

SQL Editor Report Save Blocked by Visible Parameters Without Defaults (BC-23018)

BriteCore resolved an issue where saving a SQL Editor report failed when a visible parameter, such as an As of Date, had no default value, even though that value is supplied at run time. These reports now save successfully, while genuine validation problems produce clearer, actionable messages.

Deleting and Hiding SQL Reports (BC-22762)

BriteCore resolved an issue where users could not delete or hide certain reports from the SQL Editor, where the delete and hide icons produced no action and no error message. Users can now reliably delete and hide these reports.

SQL Report CSV Export Silently Succeeding Without a File (BC-22906)

BriteCore resolved an issue where exporting a SQL report to CSV or text reported success even when no output file was created, causing a downstream failure. Affected reports, including those with empty sheet lists or templated sheets, now export correctly.

Daily SQL Report Export Email Failure on Non-UTF-8 Data (BC-22904)

BriteCore resolved an issue where scheduled SQL report export emails could silently fail to send when an attachment contained non-UTF-8 characters. Affected carriers now reliably receive their daily report emails with the attachment intact.

Report Status Page Mobile Layout (BC-22994)

BriteCore resolved an issue where the Report Status page became unusable on mobile devices after a recent update, with each report filling the entire screen. The page now displays multiple report executions at once in a compact mobile layout.

Loss Payments Incorrectly Exported to Intacct as Adjusting Expense (BC-23082)

BriteCore resolved an issue in the new claims experience in which loss-only payments were incorrectly exported to Intacct as adjusting expenses due to how zero amounts were compared. Loss payments are now correctly coded and mapped to the loss account.

Trailing Whitespace in Contact Names Breaking QuickBooks Commission Sync (BC-23112)

BriteCore resolved an issue where a contact name ending in trailing whitespace caused commission checks to fail to post to QuickBooks and the integration to enter a retry loop. Contact names are now normalized consistently so commission payments sync correctly.

Original source

Release Visibility & Version Verification

To improve release transparency, each release note now includes the corresponding platform version number. After a release is deployed, administrators can verify that their site has received the update by comparing the version number listed in the release notes with the version number displayed in your BriteCore Instance by selecting the help Icon.

Please note that release dates are subject to change as part of our commitment to delivering stable, high-quality software. When issues are identified during final validation, releases may be delayed to ensure the best experience for our customers. We recommend referencing the version number as confirmation that a release has been successfully applied to your site.

New Features and Enhancements

BriteData Report Migration Tool (BC-22696)

BriteCore introduced an AI-assisted migration tool that converts legacy BriteData reports into SQL Editor reports, including automated comparison and validation of the results.

Redesigned Report Notes Page (BC-22938)

BriteCore redesigned the report notes page with an always-visible date-range filter in the page header and a dedicated New Note dialog, replacing the previous modal-based filter and inline row creation while preserving existing note workflows.

Configurable Totals in Excel Reports (BC-18579)

Users can now have totals in Excel reports highlighted and configured on a per-sheet basis, making it easier to identify and customize summary data.

Convenience Fee Settings by State for Stripe Payments (BC-21641)

Carrier administrators who use Stripe as their payment processor can now configure their payment convenience fee settings, including per-card-type fee formulas and disclosure messages, and apply them globally or by state. These disclosures are consistently shown to payors across all payment surfaces (account receivables, policyholder portal, This allows carriers to comply with states that prohibit convenience fees while charging them where permitted.

Deep Links to Prefill the Secure Payment Page (BC-22786)

Policyholders can now follow a link that pre-populates the Secure Online Payment page with their policy number and zip code, reducing friction when paying from an email, text message, or QR-code reminder. Existing validation rules are preserved.

Consistent Invoice Frequency Change Experience on the Builder Screen (BC-22886)

When an administrator changes the billing schedule during a revision on the Builder screen, BriteCore now shows the same Change Billing Schedule confirmation prompt available on the Billing Setup screen, letting the administrator choose whether to preserve or regenerate previously sent invoices. The change is not persisted until the revision is committed.

Additional Interest Date of Birth Available to Rules (BC-21275)

Users can now write rules and evaluations against an additional interest's date of birth, allowing carriers to enforce validations such as age requirements on those parties.

Agency Contacts Can Use a Social Security Number (BC-20619)

Users can now enter agency contacts using a Social Security Number instead of a Federal Employer Identification Number, supporting sole-proprietor agencies that operate under a Social Security Number.

Bug Fixes

Read-Only Users Can Navigate to Agencies from Contacts (BC-22887)

BriteCore resolved an issue where users with read-only reporting permissions could not see the icon to navigate from a contact to its associated agency or agency group. These users can now navigate to agencies directly from the Contacts page.

NSF Row Preserved After Effective Date Change (BC-20991)

BriteCore resolved an issue in which the non-sufficient funds (NSF) row in the accounting history table could disappear from the display after a user changed the revision effective date for a submitted policy with a payment. The NSF entry now remains visible.

Automatic Payment Drafting After Endorsement Reprocessing (BC-20640)

BriteCore resolved an issue in which a policy on an automatic payment schedule could stop drafting payments after an out-of-sequence endorsement was reprocessed, forcing manual payment entry. Scheduled payments now continue to be drafted as expected.

Payment Method Showing as None Selected When Configured (BC-23087)

BriteCore resolved an issue in which the initial bill contact payment method displayed on the Accounts Receivable page as "None Selected" even though an active payment method was configured for the policy term. The configured payment method now displays correctly.

Convenience Fee Rounding Causing Payment Declines (BC-23103)

BriteCore resolved an issue in which convenience fees that landed at an exact half-cent were rounded differently than the payment processor expected, causing credit card payments to be declined during application submission. Fees are now calculated to match the processor's rounding so payments are accepted.

Credit Report Retrieval During Extended Quote Creation Through the API (BC-22576)

BriteCore resolved an issue in which creating a quote via the extended quote creation API endpoint, with credit report retrieval enabled, failed with a rating error. Quotes that pull a credit score now rate correctly through the API endpoint, matching the behavior in the interface.

Hazard Hub Data Triggering Unnecessary Persistent Builder on Renewals (BC-22829)

BriteCore resolved an issue where renewals could unnecessarily trigger persistent builder because Hazard Hub category data differed between the prior term and the renewal. Affected policies now renew and map the category correctly.

Silent Non-Renewal from a Same-Day Endorsement on the Effective Date (BC-21542)

BriteCore resolved an issue in which a policy could be silently skipped by the automatic renewal process when a same-day endorsement was opened on the term's effective date, without generating a failure notification. Affected policies are now correctly evaluated for renewal.

Out-of-Sequence Policy Cancellation Failures (BC-22845)

BriteCore resolved an issue in which processing a manual policy cancellation out of sequence could fail with a generic error, leaving the latest revision active, skipping the return premium, and failing to generate cancellation confirmation documents. Cancellations now complete consistently across terms or roll back fully with a clear error message.

Removing a Named Insured When Another Is Present (BC-22942)

BriteCore resolved an issue where users could not remove the original named insured after adding another named insured. Users can now remove a named insured contact when at least one other named insured remains on the policy.

Agent Permission Enforcement for Policy and Contact Changes (BC-21059)

BriteCore resolved a permissions issue where an agent could assign another agent who was not associated with the policy's agency and could improperly grant that agent an agency role. Permission checks now prevent agents from accessing policies they are not associated with or modifying other agents' contact roles.

Date of Birth Field Overlap on the New Contact Form (BC-23169)

BriteCore resolved a layout issue on the New Contact form where the date of birth field overlapped the Risk ID Number field. The fields now display correctly.

Year-to-Date Totals on Individual Commission Reports (BC-15265)

BriteCore resolved an issue where the year-to-date amount paid column on individual commission statements showed an incorrect total. The column now correctly sums commissions paid for the year through the report date.

SQL Editor Report Save Blocked by Visible Parameters Without Defaults (BC-23018)

BriteCore resolved an issue where saving a SQL Editor report failed when a visible parameter, such as an As of Date, had no default value, even though that value is supplied at run time. These reports now save successfully, while genuine validation problems produce clearer, actionable messages.

Deleting and Hiding SQL Reports (BC-22762)

BriteCore resolved an issue where users could not delete or hide certain reports from the SQL Editor, where the delete and hide icons produced no action and no error message. Users can now reliably delete and hide these reports.

SQL Report CSV Export Silently Succeeding Without a File (BC-22906)

BriteCore resolved an issue where exporting a SQL report to CSV or text reported success even when no output file was created, causing a downstream failure. Affected reports, including those with empty sheet lists or templated sheets, now export correctly.

Daily SQL Report Export Email Failure on Non-UTF-8 Data (BC-22904)

BriteCore resolved an issue where scheduled SQL report export emails could silently fail to send when an attachment contained non-UTF-8 characters. Affected carriers now reliably receive their daily report emails with the attachment intact.

Report Status Page Mobile Layout (BC-22994)

BriteCore resolved an issue where the Report Status page became unusable on mobile devices after a recent update, with each report filling the entire screen. The page now displays multiple report executions at once in a compact mobile layout.

Loss Payments Incorrectly Exported to Intacct as Adjusting Expense (BC-23082)

BriteCore resolved an issue in the new claims experience in which loss-only payments were incorrectly exported to Intacct as adjusting expenses due to how zero amounts were compared. Loss payments are now correctly coded and mapped to the loss account.

Trailing Whitespace in Contact Names Breaking QuickBooks Commission Sync (BC-23112)

BriteCore resolved an issue where a contact name ending in trailing whitespace caused commission checks to fail to post to QuickBooks and the integration to enter a retry loop. Contact names are now normalized consistently so commission payments sync correctly.

Original source

New Features and Enhancements

Embedded Analytics Dashboard Errors Now Return Accurate Error Responses (BC-22885)

Previously, when an embedded analytics dashboard failed to load, the system returned a success response even though an error had occurred, making failures harder to detect and troubleshoot. The system now returns a proper error response for upstream dashboard failures while preserving the detailed error message shown in the user interface.

SQL Reports Are Now Validated When Saved (BC-22764)

Previously, a SQL report could be saved with errors such as references to columns or tables that do not exist, and the problem would only surface when the scheduled report later failed to run. BriteCore now validates each report sheet's SQL at save time, checking syntax, table and column references, and unresolved parameter tokens, so configuration mistakes are caught immediately instead of causing failed report runs.

SQL Editor Now Prevents Invalid Excel Worksheet Names (BC-22759)

Excel rejects worksheet names that are too long, blank, or contain certain characters, and previously the SQL Editor only surfaced these problems after a report failed to save or generate. The SQL Editor now validates worksheet names as users type, shows an inline explanation next to the offending sheet, and disables saving until the name is corrected, so generated Excel reports open cleanly.

Larger SQL Definitions Now Supported for Multi Sheet Reports (BC-22728)

The storage capacity for report sheet SQL definitions has been significantly increased, allowing users to build larger and more complex multi sheet SQL reports without hitting the previous size limit.

Report Filenames Now Support Custom Parameter Formatting (BC-22627)

Report output filenames and display titles are now generated consistently across all report types, and users can customize how parameters appear in filename templates. A new format syntax supports custom date formatting along with uppercase, lowercase, and title case options for text parameters.

Defects

Quote API Now Accepts Phone Numbers Supplied in the Phones Array (BC-21282)

BriteCore identified and resolved an issue where, with the required phone number setting enabled, the quote creation API did not recognize phone numbers supplied in the phones array as satisfying the requirement, which could block contact processing and prevent a rate from being returned. The API now accepts a valid phone number provided through any supported phone field, and rating proceeds normally.

Lockbox Payment Processing No Longer Fails After a Database Rollback (BC-22714)

BriteCore identified and resolved an issue where an error during automated lockbox payment processing could cause a database rollback that prevented the remaining payments in the batch from posting, leaving some policies incorrectly headed toward pending cancellation. Lockbox batches now process reliably so payments post as expected.

Automated Payments No Longer Pull When No Balance Is Due (BC-21156)

BriteCore identified and resolved an issue where the system could incorrectly pull an automated payment on a policy even though a manual payment had already brought the balance to zero, resulting in an unwanted charge and an inaccurate underpaid summary on the payment record. Automated payments now correctly respect the current balance and the scheduled withdrawal date.

Manual Payments Now Process for Policy Numbers Containing Special Characters (BC-21080)

BriteCore identified and resolved an issue where manual payments, such as checks or cash, could not be applied to policies whose policy numbers contained certain special characters. The payment screen displayed an invalid number warning and the payment was not processed. Manual payments now process correctly regardless of special characters in the policy number.

Claim Activity Notes Now Show Readable Labels Instead of Internal Identifiers (BC-22840)

BriteCore identified and resolved an issue where claim activity notes for added, updated, or deleted exposures and claim properties displayed a long internal record identifier instead of meaningful information. These notes now display a human readable label built from the coverage, loss, and claimant details so adjusters can immediately understand what changed.

Claim Payments With Accounting Details No Longer Fail With an Exposure Error (BC-22754)

BriteCore identified and resolved an issue where claim payments could fail with an exposure identifier error when invoice number, vendor identifier, and vendor location details were entered on the Accounting tab. Claim payments with accounting details now process successfully.

Claim Payment Integration Errors No Longer Report Misleading Connection Failures (BC-22391)

BriteCore identified and resolved an issue where a claim payment could be reported as failed with an integration connection error even though the payment had actually been issued successfully by the accounting integration. The error reporting has been corrected so claim payment statuses accurately reflect the outcome of the integration request.

Loss Reserves Defined by Underwriting Rules Now Auto Populate on Claim Exposures (BC-22347)

BriteCore identified and resolved an issue where loss reserves configured through underwriting rules for a specific loss cause did not automatically populate when an exposure was added to a claim. Reserves defined by these rules now populate on claim exposures as configured.

Coverage Limit Selection Restored on the Auto Quote Rating Step (BC-22934)

BriteCore identified and resolved an issue where the coverage limit selection was missing from the rating step when creating a new auto quote, preventing the quote from being rated or submitted. The limit selection now displays correctly so auto quotes can be completed.

Vehicle Lookup Now Works Using Year Make and Model When a VIN Is Not Provided (BC-22556)

BriteCore identified and resolved an issue where the vehicle lookup on the auto quote flow silently skipped attribute prefill when a VIN was not provided, even though a complete year, make, and model had been entered. The lookup now retrieves vehicle attributes from year, make, and model when no VIN is available, while preserving the existing behavior when a VIN is present.

Quotes Created Through the API No Longer Hang on the Risk Details Screen (BC-21390)

BriteCore identified and resolved an issue where quotes created through the extended quote creation API caused the Agent Portal to hang indefinitely when navigating to the Risk Details screen. These quotes now load normally so agents can continue working them in the portal.

Require Explicit Selection Setting Now Respected for Standard Rating Categories (BC-20522)

BriteCore identified and resolved an issue where the setting that requires users to make an explicit selection in the Policy Wizard, rather than accepting a pre selected default, was not honored for standard rating categories. With the setting enabled, the wizard now correctly prompts for a selection on first load while preserving values the user has already chosen.

Agent Contact Page Loads Faster for Contacts With Many Policies (BC-21449)

BriteCore identified and resolved a performance issue where the contact information page took a long time to load for agent contacts associated with a large number of policies. The page now loads significantly faster for these contacts.

Agents Can Now Reliably Find Policies in Search (BC-19533)

BriteCore identified and resolved an issue where a policy could stop appearing in search results for a specific agent even though other users could find it, and rebuilding the search index only fixed the problem temporarily. The search index now stays consistent so agents can reliably find the policies they have permission to view.

Property Coverage by Limit Report No Longer Fails for Similar Agency Names (BC-22881)

BriteCore identified and resolved an issue where the Property Coverage by Limit report could fail to generate when it included agencies whose names shortened to the same Excel worksheet name, differing only in letter casing. The report now automatically generates unique worksheet names so it completes successfully in these cases.

Nightly Report Data Refresh Jobs Now Recover From Temporary Database Congestion (BC-22793)

BriteCore identified and resolved an issue where nightly report data refresh jobs could fail when many sites accessed the database simultaneously, causing the entire job to restart from scratch. These jobs now automatically retry after temporary database connection errors, making overnight report data refreshes more reliable.

Financial Anti Terrorism Cross Reference Report No Longer Fails With Certificate Errors (BC-21082)

BriteCore identified and resolved an issue where the Financial Anti Terrorism Cross Reference report, used for OFAC (Office of Foreign Assets Control) screening, could fail with a certificate error when contacting the screening service. The underlying request library has been updated so the report runs reliably without requiring a configuration workaround.

Document Generation No Longer Fails When the Recipient Has No Email Address (BC-22833)

BriteCore identified and resolved an issue where generating a document for email delivery failed when the recipient contact had no email address on file, even though the PDF itself had been generated successfully. The system now handles contacts without an email address gracefully instead of marking the entire document task as failed.

Endorsement Billing Statements Now Generate and Deliver Correctly (BC-22753)

BriteCore identified and resolved an issue where billing statements triggered by endorsements failed during post processing in the standard document generation path. Although the PDF was created, it never entered the print queue for mailing and did not appear under the policy documents. Endorsement billing statements are now processed, queued, and displayed correctly.

Document Generation No Longer Produces Empty Files After a Database Conflict (BC-22501)

BriteCore identified and resolved an issue where a temporary database conflict during document generation could cause the process to fail in a way that left a zero size document indexed on the policy. Document generation now handles these conflicts correctly so deliverables are produced completely and reliably.

Endorsements No Longer Blocked by an Outdated Recurring Billing Contact (BC-22603)

BriteCore identified and resolved an issue where an endorsement could not be committed when the recurring billing schedule was tied to a contact who was no longer on the policy, because the current named insured was missing from the recurring billing dropdown. The named insured on the policy is now available for selection so users can update recurring billing and commit the endorsement.

Negative Commission Delays Now Calculate Correctly at the Agency Group Level (BC-21347)

BriteCore identified and resolved inconsistencies in how delayed negative commissions were handled when agencies are paid at the agency group level. Previously the negative balance check was always performed for each individual agency, which could incorrectly delay amounts that the group total would cover, or incorrectly mark amounts as paid when the group total was negative. A new setting allows the delay decision to be made against the agency group total so commission records accurately reflect what was paid.

Nightly Policy Transaction Export No Longer Fails on Certain Question Values (BC-22711)

BriteCore identified and resolved an issue where the nightly policy transaction export to a downstream data vendor failed with a generation error caused by certain question values in the policy data. The nightly export now completes successfully.

Mailings With Large Document Sets Now Create Successfully (BC-22367)

BriteCore identified and resolved an issue where creating a mailing could fail when the combined set of documents for the mailing was too large. Mailings with large document sets now process successfully.

Convenience Fee API Endpoints Now Accept an Optional Policy Identifier (BC-22967)

The convenience fee retrieval API endpoints now accept an optional policy identifier parameter, allowing callers to retrieve and preview convenience fees in the context of a specific policy. This was shipped as a hotfix to support a BriteApps release.

Agency Download Initial Load Files Now Generate Successfully (BC-22755)

BriteCore identified and resolved an issue where generating the initial load files for agency download integrations failed due to a permissions error when accessing stored credentials. Initial load files for agencies now generate successfully. This fix was shipped as a hotfix.

Original source

New Features and Enhancements

Asynchronous Document Generation for Policy Submissions (BC-22645)

BriteCore updated the policy submission process to generate declaration documents asynchronously for applications approved through straight-through processing (STP). Agents are no longer blocked by a submission modal during document generation; instead, the interface updates progressively as documents are produced in the background. This reduces user-perceived submission time and resolves timeout-related failures that could leave policies without attached documents.

Create Task Effect for Underwriting Rules (BC-22635)

BriteCore added a new Create Task effect to underwriting rules. Administrators can now configure rules to automatically generate policy tasks when a rule condition is met, including specifying task priority and the number of days until the task is due. This allows underwriting teams to automate follow-up workflows without requiring manual task creation after each rule evaluation.

Additional Information Field Available in New Claims Experience (BC-22177)

The Additional Information field is now available in the new claims experience during First Notice of Loss entry. Previously available only in the legacy claims experience, this field allows agents to capture key contact details for the insured that outside claims adjusters rely on to initiate contact. Information entered in this field now appears in its expected location rather than only in the claim Notes section.

Settings to Control Loss and Claimant Association in Exposure Creation (BC-17611)

BriteCore added two new settings under Settings > Modules > Claims that control the visibility of the Loss and Claimant fields during exposure creation. Administrators can toggle either field off to prevent users from associating losses or claimants with exposures, accommodating business rules that do not require these associations. Both settings are enabled by default, preserving existing behavior.

Configurable Maximum Number of Loss Causes Per Claim (BC-17599)

BriteCore added a new configurable setting under Settings > Modules > Claims that allows system administrators to limit the number of loss causes that can be attributed to a single claim. When the configured limit is reached, the system blocks additional loss causes from being added and displays a validation message. The setting defaults to no limit, preserving existing behavior.

State-Based Convenience Fee Configuration and Debit Card Fee Control Available (BC-20434)

BriteCore expanded the payments convenience fee advanced settings to support state-specific fee configuration and introduced a new setting that controls whether convenience fees apply to debit card payments. Administrators can now define a global convenience fee and disclosure message, with optional per-state overrides; when a payment is initiated, the system applies the fee configured for the insured's state, falls back to the global fee if no state-specific configuration exists, and applies no fee if neither is configured. Payment screens now display pricing and legal disclosure language appropriate to the insured's state and payment method, with the display format adjusting based on whether fees apply to debit cards, credit cards, or neither. The updated fee logic applies consistently across the Admin Payment screen and the Secure Online Payment page, and a checkbox to save payment method details for future use is now available when processing payments on the Admin Payment page.

Bug Fixes

Recurring Billing Dropdown Includes Current Named Insured During Endorsement (BC-22603)

BriteCore resolved an issue that prevented users from committing endorsements on policies in which the recurring billing schedule referenced a contact no longer associated with the policy. Previously, the named insured on the policy did not appear in the recurring billing dropdown, preventing users from updating the billing configuration and completing the endorsement. The named insured on the policy is now correctly listed in the dropdown, allowing users to select the appropriate contact and successfully commit the endorsement.

Category Deletion from Policy Type Items Works Correctly (BC-22540)

BriteCore resolved an issue where users were unable to delete a category from a policy type item when an evaluation table was present in the rate chain. Categories can now be deleted successfully in all configurations.

Report SFTP Delivery Settings Preserved During Edits (BC-22498)

BriteCore resolved an issue in which the SFTP delivery configuration for a report was cleared each time the report was edited in the SQL Editor. Report SFTP settings are now preserved when editing, eliminating the need to re-enter delivery details after each change.

Claims Attachments Page Loading Correctly (BC-22768)

BriteCore resolved an issue in which the claims attachments page failed to load, displaying a blank screen due to a missing component registration introduced by a recent update. The page now loads correctly in all configurations.

Quote Wizard Rating Errors Resolved for Certain Configurations (BC-22626)

BriteCore resolved an issue where the quote wizard displayed rating errors for certain policy configurations involving TigerCQ rules. Quotes now rate correctly in the wizard experience when TigerCQ override settings are applied.

Contact Phone Update No Longer Causes Database Errors (BC-22610)

BriteCore resolved an issue where updating a contact phone list caused a database constraint error when the submitted list did not include the current primary phone. The system now correctly updates the primary phone reference before removing the associated record, preventing the error.

Nightly Processing Stripe Payment Failures Resolved (BC-22547, BC-22555)

BriteCore resolved an issue in which a third party's temporary infrastructure outage caused some Stripe payments processed during nightly processing to remain in a pending state and incorrectly trigger non-pay notices for affected policies. BriteCore improved payment recovery logic to ensure the system can properly synchronize payment records once processing resumes.

IVANS DBCS Commission File Auto-Generation Restored (BC-21742)

BriteCore resolved an issue in which the IVANS DBCS commission file was not automatically generated at the end of the month, requiring manual intervention to produce it each month. The scheduled generation now runs reliably at the end of the month.

Original source

New Features and Enhancements

Unified Report Filename Generation with Parameter Format Support (BC-22627)

BriteCore standardized how generated report filenames are produced. Reports now consistently support the <<$Param.{format}>> token, allowing users and configurations to control filename formatting from a single source of truth across stock and custom reports.

PolicyBuilder Line Item Limit Errors Can Be Bypassed (BC-22445)

BriteCore added the ability to bypass PolicyBuilder errors that prevented users from saving when line item limits were exceeded. Authorized users can now proceed past these errors when business rules allow, reducing friction in policy configuration workflows.

Improved Effective Date API Endpoint Performance (BC-22344)

BriteCore optimized the retrieve_effective_date API endpoint, reducing response times for screens and processes that depend on it. Quote retrieval, endorsement workflows, and any view that resolves a policy effective date now feel noticeably faster.

Policy Legal Report by County Available as a SQL Editor Stock Report (BC-22339)

BriteCore added the Policy Legal Report by County to the SQL Editor as a stock report. Carriers can now run and tailor this report directly from the SQL Editor for self-service legal and county-level reporting, with automated parity testing against the legacy Excel version.

Policies Can Be Rewritten with Earlier Effective Dates (BC-22307)

BriteCore now supports rewriting a policy with an effective date earlier than the original. This gives carriers and underwriters greater flexibility when correcting backdated coverage scenarios that previously required manual workarounds.

Court Lookup Configuration List for Claims Disputes (BC-22076)

BriteCore introduced a configurable Court Lookup list for use on Claims Disputes. Administrators can now maintain the list of courts that adjusters select from when documenting a dispute, ensuring consistent values and easier reporting.

To Export Column Restored on the Return Premium Queue (BC-22071)

BriteCore restored the To Export column on the Return Premium Queue. Users can again see and act on items flagged for export directly from the queue, eliminating the need to drill into individual records to verify export status.

Updated Name Population Behavior for Organizations (BC-22066)

BriteCore refined how an organization's name is populated across the application. The displayed name now follows the configured organization naming rules consistently, reducing discrepancies between screens and downstream documents.

Search Claims Attachments by Attachment Type (BC-21865)

BriteCore added the ability to filter and search Claims attachments by Attachment Type and code value. Adjusters can quickly locate the right document, such as a police report or estimate, without scrolling through the full attachment list.

Claim Adjuster Information Now Displayed on the Dispute Tab (BC-21818)

BriteCore now surfaces the assigned Claim Adjuster on the Dispute tab, pulling the value from the main claim Information screen. Adjusters and supervisors handling disputes can immediately see ownership without switching tabs.

Cause of Loss Carries Over to Bifurcated Claims (BC-21814)

BriteCore now copies the Cause of Loss from the originating claim to any bifurcated claims created from it. This ensures consistent reporting and removes a manual data-entry step for adjusters working with split claims.

System Tags Included in Claim Payment Notes (BC-21787)

BriteCore now appends selected System Tags to the Note generated when a claim payment is made. The resulting payment note carries the same tagging metadata as other claim activity, improving auditability and reporting.

Download All Reports Option on the Agency Commissions Page (BC-21784)

BriteCore added a Download All option to the new Agency Commissions page. Users can now retrieve every available commission report in a single action, replacing the prior workflow of downloading reports one at a time.

New Support Tool to Suppress City, County, and ZIP Combinations (BC-21739)

BriteCore introduced a Support Tool that allows authorized users to suppress specific City, County, and ZIP combinations. This addresses cases where a ZIP code resolves to a county that should not be offered for that address, giving admins a self-service way to correct the mapping.

Claims Supervisor Added Automatically When Adjuster Is Assigned (BC-21619)

BriteCore now automatically assigns the appropriate Claims Supervisor whenever an Adjuster is added to a claim. The supervisor relationship is maintained without manual intervention, reducing missed assignments and supporting downstream review workflows.

Setting to Limit Adjusters and Supervisors to One per Claim (BC-21618)

BriteCore added a configurable setting that limits each claim to a single active Adjuster and a single active Supervisor. Carriers that operate under this policy can now enforce it at the system level rather than relying on procedure.

Unified Accounting Tab Replaces Separate Exposures and Accounting Tabs on Claims (BC-21524)

BriteCore consolidated the Exposures and Accounting tabs on a claim into a single unified Accounting tab. A new "View Accounting For" dropdown lets adjusters switch between a Claim Level view (Overview, Recoveries, Transactions) and an individual exposure view (Coverage and Exposure Information, Losses Details, Recoveries, Transactions). All existing functionality, including creating, editing, and viewing exposures, deductible overrides, recoveries, and transactions, is preserved in the new layout.

Improved Rating Factors Lookup Performance (BC-20591)

BriteCore optimized the query that loads rating factors during quoting and rating. Pages that depend on rating factor resolution, including the quoting wizard and policy issuance flows, now load and rate measurably faster.

Accounting Detail Report Available as a SQL Editor Stock Report (BC-19662)

BriteCore added the Accounting Detail Report to the SQL Editor as a stock report. Carriers can now run and customize the Accounting Detail Report directly from the SQL Editor, expanding the catalog of self-service stock reports.

Edit Exposure Details Without Deleting and Recreating the Exposure (BC-18454)

BriteCore now allows users to edit key details on an existing exposure, including associated claimant, exposure type, coverage, description of loss, and date of loss, without deleting and recreating the exposure. Existing validation, audit history, and business-rule restrictions on exposures with related payments continue to apply.

Bugs (Fixes)

Billing Schedule Changes Now Regenerate Installments (BC-22673)

BriteCore identified and resolved an issue where modifying a policy's billing schedule did not trigger regeneration of the underlying installments. Updated installment plans now reflect the new schedule immediately after the change is saved.

Application Questions Now Save in the Quoting Wizard (BC-22590)

BriteCore identified and resolved an issue where answers entered for Application Questions in the Quoting Wizard were not persisting. Responses are now saved correctly and remain available across sessions and quote revisions.

Write-Offs and Waives Report Now Includes Waives From Prior Revisions (BC-22550)

BriteCore identified and resolved a defect in the Write-Offs and Waives stock report where waives posted on prior policy revisions were dropped. The report join was corrected from a term-level association to a revision-level association so all qualifying waives appear in the output.

Removing an Additional Interest No Longer Deselects the Agent (BC-22493)

BriteCore identified and resolved an issue where removing an Additional Interest from a policy unexpectedly cleared the selected Agent. The Agent selection is now preserved when Additional Interests are added or removed.

Default Bill Whom Set Activity Note Now Attributed to the System (BC-22478)

BriteCore identified and resolved an issue where the Default Bill Whom Set activity note was credited to the end user who triggered an unrelated action. The note is now correctly attributed to the system, restoring an accurate audit trail.

Support Tools Page Now Displays All Available Tools (BC-22472)

BriteCore identified and resolved an issue that caused the Support Tools page to render only the Manage County Suppressions for a ZIP entry while hiding all other tools. The full Support Tools list is now displayed to authorized users.

Rating No Longer Errors When Driver License Status Is Missing (BC-22348)

BriteCore identified and resolved a rating error caused by a missing driver_license_status attribute on the safe driver fallback path. Quotes now rate successfully when this attribute is not present, falling back to the configured default behavior.

Vehicles Wizard Page No Longer Issues Duplicate Rules Calls (BC-22343)

BriteCore identified and resolved a watcher feedback loop on the Vehicles wizard page that caused duplicate rules and run calls. The page now issues a single round of rules execution per change, improving responsiveness and reducing server load.

Vehicles Wizard Startup Now Avoids Duplicate Data Fetches (BC-22342)

BriteCore identified and resolved redundant startup fetches on the Vehicles wizard, including duplicate calls for billing schedule, vehicles, and watercrafts data. Initial load time is reduced and downstream rendering occurs sooner.

Report Status Page Rendering, Export, and Ordering Improvements (BC-22325)

BriteCore identified and resolved several defects on the Report Status page, including incomplete rendering of the report list, broken export_data downloads, and inconsistent ordering across sections. The page now renders the full list, downloads complete successfully, and ordering is unified.

Vehicles Wizard No Longer Crashes When Risk Types Are Undefined (BC-22322)

BriteCore identified and resolved a regression where the Vehicles wizard component crashed when a policy type's supportedRiskTypes value was undefined. The component now handles this case safely and renders without error.

Select a CAT Button on the First Notice of Loss Screen Now Works (BC-22321)

BriteCore identified and resolved an issue with the Select a CAT button on the First Notice of Loss (FNOL) screen. Users can again open the catastrophe selector and assign a claim to an active catastrophe event.

Improved Performance on the Agent Policy List (BC-22320)

BriteCore identified and resolved an N-plus-one query pattern in the policy list retrieval path that caused two to three second delays for agents. The agent Policies list now loads consistently within expected timeframes.

Premiums Receivable Trial Balance Report Now Supports Net Commission (BC-22195)

BriteCore identified and resolved a failure in the custom Premiums Receivable Trial Balance report caused by a missing Net Commission entry in the TransactionType enumeration. The report now recognizes and includes Net Commission transactions, allowing the report to generate successfully.

Check Number Now Displayed in the New Claims Experience (BC-22175)

BriteCore identified and resolved an issue in the new Claims experience where the check number on a claim payment was not displayed. Adjusters can again see and reference the check number directly within the new interface.

Stripe Duplicate Payment Issue Resolved (BC-22046)

BriteCore identified and resolved an issue that allowed a Stripe payment to be processed twice for a single transaction. The payment flow now guards against duplicate submissions and reconciles correctly with Stripe.

Agent Quote Now Enforces Straight-Through Processing After Effective Date Changes (BC-21932)

BriteCore identified and resolved a defect where switching an Agent Quote to a newer Latest Effective Date could bypass Straight-Through Processing (STP) and submit the application without the required checks. STP rules are now reapplied whenever the effective date is changed.

Pre-Authorized Payment Schedule Now Handles Missing Payment Methods Gracefully (BC-21890)

BriteCore identified and resolved an application error that occurred when previewing or generating Pre-Authorized Payment Schedules for non auto-pay policies that had no payment method on file. The flow now displays a clear validation message instead of failing with an error.

Copy Effective Date No Longer Fails on Underwriting Rule References (BC-21878)

BriteCore identified and resolved a foreign key constraint error that occurred during the Copy Effective Date workflow when underwriting rule effects referenced a custom error code. The copy now completes successfully and preserves the underwriting rule effect references.

CLUE Reference Now Displayed in Generated Dynamic Documents (BC-21730)

BriteCore identified and resolved an issue in the Dynamic Documents Generator where the Comprehensive Loss Underwriting Exchange (CLUE) reference was missing from the output. The CLUE reference is now included in Dynamic Documents that consume it as a token.

Claims Description Field Updates Now Persist After Edit (BC-21646)

BriteCore identified and resolved an issue where updates to the Description field on a claim did not persist or reflect on screen after editing. Description edits now save reliably and update the displayed value immediately.

New Support Tool to Recover Broken Dynamic Documents (BC-21511)

BriteCore identified and resolved a class of broken Dynamic Documents produced during a Dynamic Documents Generator outage by introducing a new Recover Broken Deliverables tool under Support Tools. Authorized users can identify affected Dynamic Documents and trigger regeneration in bulk.

360 Valuation Link Dropdown Now Selectable by Agents (BC-21366)

BriteCore identified and resolved an issue where the 360 Valuation link dropdown could not be selected by agents. The dropdown now opens and accepts selections for all user roles authorized to view it.

Claims System Tags Now Persist After Selection (BC-21182)

BriteCore identified and resolved an issue where Claims System Tags appeared to disappear after selecting and saving an alphanumeric tag. Selections are now persisted reliably and the tag continues to display on the claim.

HSB File Upload Failures Resolved (BC-20726)

BriteCore identified and resolved an issue that prevented certain HSB-related files from uploading. The upload path now accepts these files and persists them to the associated record as expected.

Sweep Account History Report Retrieval Restored (BC-20646)

BriteCore identified and resolved an issue where agents could not retrieve the Sweep Account History report. The report now generates and downloads successfully for users with the appropriate permissions.

Scheduled Items Table Alignment Corrected on the Agent Interface (BC-19142)

BriteCore identified and resolved a layout issue on the Agent Interface where the Scheduled Items table columns were misaligned. Columns now line up with their headers across the screen widths agents commonly use.

Admin Alerts Now Trigger on Per-Risk Excess Reinsurance Contracts in Claims (BC-19127)

BriteCore identified and resolved an issue where Admin Alerts did not trigger on Per-Risk Excess Loss reinsurance contracts within Claims. Configured alerts now fire as expected when matching claim activity occurs against these contracts.

Installment Billing Dynamic Documents No Longer Generate as Zero-Byte Files (BC-22315)

BriteCore identified and resolved an issue where Installment Billing Dynamic Documents could be produced with a zero-byte file, leaving recipients without a usable document. The generation path now validates output before completion and produces the full document reliably.

Failed Generation Alert Email Now Includes Policy Number and Installment Details (BC-22052)

BriteCore identified and resolved an issue where alert emails sent for failed Dynamic Document generation omitted the policy number and installment information, making the messages difficult to act on. The alerts now include the relevant policy and installment context so support teams can respond without additional lookup.

InsVista HO and BG File Extracts Now Include All Daily Entries (BC-22557)

BriteCore identified and resolved an issue where the InsVista Homeowners and Business extract files reported only a single entry for a given processing date instead of the full set. The extracts now include every qualifying record for the period.

Save Button Now Enables When Report Settings Are Modified on Initial Load (BC-22548)

BriteCore identified and resolved an issue where the Save button on the report settings screen remained disabled when changes were made immediately after the page first loaded. The button now becomes available as soon as a setting is modified, matching expected behavior.

Save Button on SQL Editor Reports Now Enables After Modifications (BC-22545)

BriteCore identified and resolved an issue in the SQL Editor where the Save button could remain disabled after a report was modified, blocking users from saving valid changes. The button now activates correctly when modifications are made.

Commission Statements No Longer Stall in Pending Status (BC-22476)

BriteCore identified and resolved an issue where multiple Commission Statements could remain stuck in a Pending status in the report queue. Statements now progress through generation and appear as expected in the completed list.

Original source

Enhancements

Global Fields for Dynamic Document Templates (BC-21919)

BriteCore now supports global fields in Dynamic Document Templates, allowing you to control wording dynamically at the time a document is generated. Instead of maintaining separate templates for different states or scenarios, you can define reusable logic that adjusts language automatically based on your data. These calculated fields support dependencies between fields and include a built-in testing tool, making it easier to validate and manage your document logic in one place.

Permission to Prevent Editing of Issued Check Payments (BC-21811)

BriteCore added a permission that controls whether a user can edit check payments on claims via the claims processing screen. Carriers can now restrict who is able to alter issued checks, reducing the risk of unauthorized or fraudulent changes.

Save As Button in the SQL Editor (BC-22128)

BriteCore added a Save As button to the SQL Editor so users can duplicate reports directly without copy-pasting content across multiple tabs. Previously a multi-tab report was very difficult to recreate with a different name.

Calculation Line Items Included in the list_sub_lines API Endpoint Response (BC-22115)

The list_sub_lines API endpoint now returns calculation line items alongside coverages, matching the behavior of the list_coverages API endpoint for consumers that need both types of data in a single call.

Faster Policy List Filter Options Endpoint (BC-22145)

BriteCore eliminated an inefficient query pattern in the policy list filter options endpoint, dramatically reducing response times from several seconds to near-instant for users opening the policy list.

User Alert for Oversized Email Attachments (BC-15957)

BriteCore resolved an issue where email attachments over 18 megabytes were silently removed from outgoing policy and claims emails, causing recipients to receive messages without the intended documents. The system now warns users before sending or attaching oversized files.

Bugs (Fixes)

Improved Handling of Deleted Reports in the SQL Editor (BC-22031)

Improved SQL Editor behavior when reports are deleted in another tab or session. The editor now detects deleted reports and prevents stale report names from appearing, ensuring the UI reflects the current state.

Reliable File Execution and Naming in the Report Copilot (BC-22058)

BriteCore corrected out-of-sync behavior in the SQL Editor where renaming and saving reports could cause the wrong report to run. Buffer detection, save state, and the executed report name are now consistent with each other.

Preserve Report Content When Applying Copilot Fragment Suggestions (BC-22059)

BriteCore corrected the Copy to Report behavior in the Report Copilot so that agent-suggested fragments no longer overwrite the entire report buffer when a user chooses to apply them.

Report Scheduler Filename Handling for FTP Delivery (BC-21960)

BriteCore corrected a defect where the report scheduler inserted extra spaces into destination filenames during variable substitution when delivering reports to FTP or sFTP servers. Scheduled reports now arrive with the expected filenames.

Multi-Exposure Claim Payments After a Voided Payment (BC-21053)

BriteCore resolved a floating-point calculation edge case that could cause multi-exposure claim payments to fail after a prior payment had been voided. Payments now process reliably across exposures.

Endpoint Locking During Rapid Claim Status Changes (BC-21907)

Rapid claim status changes could previously leave the endpoint locked without any user-facing message. Locking behavior and error messaging have been improved so users see clear feedback and can recover quickly.

Persistent Builder Resolution When All Line Items Are Complete (BC-21997)

BriteCore resolved a case where the Persistent Builder refused to resolve even when all line items showed as completed, which had been blocking rating and saving for affected policies.

Claim Parties With the Other Role Now Persist (BC-22086)

BriteCore corrected a defect where adding a claim party with the Other role appeared to succeed but was never actually saved. Contacts added with the Other role now appear on the Parties tab as expected.

Adding an Inspected Date to a Claim Dispute (BC-21933)

BriteCore fixed an error that appeared when adding an Inspected Date to a claim dispute, allowing dispute details to be saved successfully.

HazardHub Mappings Populate on Policy Type Change (BC-21872)

BriteCore fixed an issue where HazardHub data was not propagating to the Builder tab after a policy type change, which had forced agents to manually re-select values that should have populated automatically.

Policy Number Displayed After Claim Assignment (BC-22165)

BriteCore corrected the claim interface to show the policy number, rather than an internal database identifier, after a policy is assigned to a claim, and added a progress indicator while the assignment is in flight.

Default Agency Setting Behavior on New Quotes (BC-21767)

When the default-agency setting is disabled, the Agency field on new quotes now appears blank and only shows agencies actually assigned to the agent, hiding discontinued agencies from selection.

Rules API Endpoint Validates Category Against Policy Type (BC-22116)

The rules API endpoint now validates that a rule's category is allowed for the target policy type, preventing, for example, property-specific rules from being created on auto policies.

Validation Error Rule Effect Configuration (BC-22196)

BriteCore fixed the Validation Error rule-effect configuration screen so it no longer displays unrelated fields while the effect is being configured.

Audit Trail for the Process Policy as Renewal Setting (BC-21359)

Toggling the Process Policy as Renewal setting now writes a policy note capturing who changed the setting and on which term, improving auditability of renewal processing decisions.

Original source

Enhancements

Evaluation Tables for Lines Configuration (BC-21970)

A new Evaluation Table rate chain object has been added to Lines configuration. This provides a spreadsheet-like table for mapping input values to output variables, eliminating the need to write free-form evaluation code for common lookups like deductible factors.

Liability and Medical Payments Symbol Fields for Vehicles (BC-21967)

Liability (ISO L) and Medical Payments (ISO M) symbol fields have been added to the Vehicle model. Lines configurators can now use these symbol values in rate chain evaluations to calculate premiums using ISO L and ISO M symbol factors.

Check Number Support for External Payment API Endpoint (BC-21928)

The Store External Payment API endpoint now supports passing a check number, enabling proper financial tracking and reconciliation when third-party vendors store payments in BriteCore.

Claim Payments: Setting to Remove “Or” Payment Option (BC-21808)

A new setting has been added that allows carriers to remove the “Or” option from claim payment payee configurations, so only “And” payee groupings are available when creating payments.

ISO ClaimSearch: Scheduled Re-Search and Manual Re-Search (BC-21126)

Scheduled re-searching and manual re-search capabilities have been added for ISO ClaimSearch. Users can now trigger re-searches directly from the Claims History screen, and scheduled re-searches run automatically for eligible claims.

System Tags Export and Import Updates (BC-20680)

The export and import API endpoints for System Tags have been updated to generate valid packets for all global System Tags based on the selected Policy Type, supporting the updated schema definitions.

Bugs (Fixes)

Declaration Mailing Date Applied Incorrectly Across All Forms (BC-21994)

Fixed an issue where the “use-revision-commit-date-as-dec-mailing-date” setting was being applied to all form types within declaration attachments, rather than only to declaration forms. Print dates now display correctly per form type.

Uninsured Motorist 3-Year Error (BC-21747)

Resolved an error that occurred when adding Uninsured Motorist coverage with a 3-year term on Personal Auto policies.

Required Supplemental Question Bypass on Application (BC-21576)

Fixed an issue where the required supplemental question (“I have verified that None of the above conditions exist”) was no longer blocking users from advancing past the Questions screen without providing a response.

Task Assignment Email Generates Incorrect Claim Link (BC-21534)

Fixed a bug where task assignment emails for policy-level tasks generated broken claim links instead of linking to the correct policy.

Mailings Failing Due to Unmergeable Documents (BC-20827)

Resolved an issue where certain policies were not generating mailing documents, causing documents to be printed individually rather than being grouped by policy number into categories such as New Business.

Original source

Enhancements

Multi-Select Coverage and Bulk Exposure Creation (BC-18453)

Within the new claims experience, exposures can now be created for multiple coverages at the same time. Users can select multiple coverages from a list and create corresponding exposures in a single action, significantly reducing the time required to process complex claims with multiple applicable coverages.

Reinsurance Visibility Controls Added to New Claims Experience(BC-20822)

To restore parity with the Legacy Claims experience and eliminate reliance on backend configuration, we introduced a user-facing control in the New Claims Experience to manage reinsurance visibility. Previously, key reinsurance functionality, such as the Reinsurance LAE cell and recovery category, was only accessible through the advanced setting, creating friction and dependency on Admin intervention. With this update, users can directly enable or disable reinsurance visibility at the claim level, instantly surfacing or hiding the Reinsurance LAE fields and recovery options in the Accounting section without requiring a page refresh. This enhancement improves workflow efficiency, reduces administrative bottlenecks, and ensures users regain necessary control while preserving all existing financial data, reporting, and system integrity.

Bugs (Fixes)

Application Questions Now Save and Update Quotes as Expected (BC-21963)

BriteCore identified and resolved an issue where answers entered in Application Questions were not saving or updating the umbrella quote when working in the Agent experience. Previously, Agents could enter responses, but the system would not recognize the changes, which could lead to confusion and inaccurate results. With this fix, any updates to Application Questions are now properly captured and immediately reflected in the quote, ensuring a smoother and more reliable quoting experience for agents.

Stateless Quote Rating with Latitude/Longitude (BC-20747)

Stateless quotes using the create_quote_extended API now correctly handle latitude/longitude geolocation requirements for carriers that use location-based rating. Quotes submitted through the stateless path now return accurate premiums as expected.

Bill Whom Not Updated When Named Insured Changes (BC-21010)

When an agent changes the Named Insured during an endorsement, the Bill Whom contact now automatically updates to reflect the new insured. This prevents the incorrect billing warning message from appearing during endorsement submission.

Add a Location Button Not Working in Agent Flow (BC-21335)

The Add a Location button in the Property Grouping agent flow now functions correctly. Previously, clicking the button had no visible effect until after visiting policy-wide coverages, and would then add two locations instead of one. This behavior has been corrected.

ZIP Code Validation Error Message (BC-21381)

When a ZIP code entered during quoting is not on the configured options list, the system now displays a clear and informative error message rather than throwing an uncaught error. This allows agents to identify and correct the issue without the quoting workflow being blocked unexpectedly.

SSN Masking Not Working in Quoting and Auto Wizards (BC-21412)

The mask-ssn-on-edit-contact advanced setting now correctly masks Social Security Numbers when editing contacts in the Agent Quoting Wizard. Previously, SSNs were visible during contact editing despite the masking setting being enabled.

False “User Updated” Notes When Navigating Tabs (BC-21430)

Navigating between tabs on a quote or policy in the Admin view no longer generates incorrect system notes attributing data changes to a user. Previously, simply visiting the Risk or Builder tabs could create false audit entries such as “Latitude/Longitude updated” or “Billing schedule updated” even when no changes were made.

InsVista Transactions Not Being Reported (BC-21556)

Escrow-billed policies now correctly generate and upload billing files to InsVista, restoring the flow of renewal billing notifications to mortgage companies. An issue preventing InsVista transactions from being uploaded and escrow billing files from being generated has been resolved.

Policy Fees Missing from Quote Premium within Newest Quoting Experience (BC-21565)

Policy-wide fees marked as mandatory are now correctly included in the total premium displayed on the Coverages screen during quoting for Umbrella policies. Previously, the premium shown in the user interface differed from the quote summary and application conversion total due to the missing policy fee.

Pop-Up Message Rule Effect Not Functioning (BC-21795)

Administrators can once again create and configure pop-up messages within Rules for applicable states without needing to copy existing rules as a workaround. An issue preventing administrators from adding new pop-up message rules in production environments has been corrected.

Original source

Enhancements

Print All Forms Capability (BC-20980)

A new Always print on endorsement setting within Lines allows users to print all associated policy forms at once when preparing documentation packages, reducing the risk of missing required forms and eliminating the need to open each one individually.

Support Blank Default Values for Loss Fields (BC-19540)

Some loss-related fields in the Quote Wizard's loss history required a default value even when one wasn't appropriate, which could lead to inaccurate data being recorded. Administrators can now configure these fields without a default value, giving users more flexibility during claims entry.

Export Preview Data to CSV (BC-21040)

A new export option in SQL Editor now allows users to download preview results as a CSV file for easier reporting and analysis. Users reviewing query results in the SQL Editor had no direct way to export the previewed data and now they do. This meant data had to be manually copied or recreated in external tools.

Receipt Link Added to Accounts Receivable Page (BC-18300)

A direct receipt link has now been added to the Accounts Receivable page, making it easier to retrieve payment receipts. An email button has also been added to email a receipt directly from the policy’s Accounts Receivable screen.

Claims transaction Filtering and Sorting (BC-18442)

New filtering and sorting options have been added to improve usability within the transaction table within the exposures and accounting tab. Users can now more easily locate and review relevant feedback entries.

Updated Claims Reserve Editing Experience (BC-20564)

Users can now update multiple reserve categories (such as Loss, Legal, Adjusting, etc.) directly within an inline table by entering new values for several categories in a single action. This enhancement restores the efficient workflow previously available in legacy claims and reduces the need to open separate modals for each reserve adjustment.

Ability to view applicable coverages within Claims information (BC-21189)

In the new claims experience, an Applicable Coverages sub-section has been added to the Claim Information tab, providing users with a faster way to review coverages that may apply to a claim. The new sub-section includes a View action that opens a Coverages dialog and supports search.

SQL Editor User Interface Improvements (BC-21611)

Improvements to the SQL Editor interface include an updated layout that enhances readability and provides a more user-friendly experience when working with queries.

Defects

Restore ability to open BriteApps/BriteData Reports (BC-21732)

Access to the legacy BriteApps/BriteData report editor has been restored, allowing existing reports to be viewed, edited, and deleted, including updates to embedded constants required for many reports to function. Report creation remains disabled as BriteCore continues developing a translation path from BriteData reports to the SQL Editor.

“GP” Quick Function available on all pages (BC-21522)

Quick administrative functions now operate consistently across all client environments such as using the keys GP. Improvements were made to ensure these functions operate consistently across all environments. This helps users perform common tasks more reliably.

Explicit Selection Required in Quote Wizard (BC-21409)

An issue where the Quote Wizard automatically applied certain selections without user confirmation has been corrected, ensuring options are explicitly selected before being applied to a quote.

ZIP Code Validation Error (BC-20908)

Valid ZIP codes entered during quoting and policy entry are now accepted correctly.

E-Delivery Invitation Issue (BC-21050)

An issue preventing some policyholders from receiving electronic delivery invitations has been corrected.

Invoice has a wrap on the policy number (BC-21738)

A text wrapping issue that caused policy numbers longer than 15 characters to be cut off on the billing statement stub has been corrected.

Commission Calculation Error (BC-21606)

The commission calculation error that could produce incorrect amounts when an agent change occurred on an endorsement, causing discrepancies in financial reporting and agent compensation records, has been corrected.

Missing revision print Descriptions Corrected (BC-21643)

Revision history entries that previously lacked descriptive information now correctly display activity descriptions.

Contacts Security Issue (BC-20965)

A vulnerability in the Contacts module that allowed Role changes via HTML markup injection has been addressed through improved input validation and safeguards.

Invoice Frequency Reset Issue (BC-20970)

Invoice frequency selections made within the Quote Wizard no longer revert to a default value after being saved.

External Adjuster Selection Issue (BC-21277)

An issue preventing users from selecting an external adjuster when paying a claim has been corrected.

Claims Auto-Assignment Issue (BC-21393)

An issue where claims configured for automatic assignment were not always routed to the correct adjuster has been corrected.

ISO A-Plus Report Retrieval Issue (BC-21519)

An issue preventing users from retrieving ISO A-Plus reports has been resolved.

Tasks Workbench Page Freezing (BC-21164)

Performance improvements prevent the Tasks Workbench page from becoming unresponsive when managing tasks.

Missing Event Logging for Deleted Records (BC-21364)

Audit logs are now properly created when records are permanently deleted.

Original source

New Features & Enhancements

• Support Custom Default parameters in SQL Editor (BC-20715)

  The BriteCore SQL Editor now supports custom default parameters for report execution, allowing users to specify custom values that are used as defaults when running reports. This enhancement streamlines report generation workflows by reducing the need for manual parameter entry each time a report is executed.

Bug Fixes

• Renewal Stability and Validation Improvements (BC-21452, BC-21448, BC-21440, BC-21438, BC-19578, BC-19388)

  BriteCore delivered several fixes to improve the reliability and integrity of policy renewals. Multiple defects that previously caused renewal failures due to loss cause errors, formatting issues, data type mismatches, or revision creation problems, have been resolved. Both automated and manual renewals now execute successfully without system errors or interruption.

  In addition, validation safeguards were implemented to prevent renewals from processing when open endorsements exist, ensuring proper sequencing and avoiding conflicting policy states. Document generation logic was also corrected to ensure renewal documents are consistently produced as expected.

  Together, these updates strengthen renewal processing stability, improve data integrity, and ensure a smoother, more reliable experience for carriers.

• TypeError when adding loss disclosure (BC-21287)

  A carrier received the error message at /gateway in the user interface upon adding an Insured Loss Disclosure on a quote. BriteCore corrected type comparison logic that caused runtime errors during loss disclosure processing. The system now properly validates data types before evaluation. This ensures smoother claims and disclosure workflows.

• Premium doesn't display during application (BC-20954)

  BriteCore fixed display inconsistencies that prevented premium values from showing during application workflows. The update ensures recalculated premiums are displayed immediately and accurately. Users now have consistent visibility into pricing details.

• Unable to rate and save an endorsement: premium basis line Item (BC-20272)

  Corrected premium calculation logic affecting premium basis line items. The application showed a traceback error. Financial reporting and billing accuracy are now improved.

• Policies moving out of cancellation pending when agents quote a change (BC-20006)

  Resolved policy state transition logic that incorrectly modified cancellation statuses during quoting changes. The correction preserves intended lifecycle states. This prevents unintended status shifts and improves data integrity.

• Upon revision creation, error in the 'Evaluation' rate object reported (BC-19307)

  The system now explicitly carries forward MunichRe vendor data when creating revisions on the term effective date with a newer Lines Effective Date available, preventing exceptions during auto-rating.

• Remove A report is currently being generated message (BC-21374)

  The misleading message, "A report is currently being generated" has been removed from the user interface, eliminating confusion about report generation status. This improves the user experience by removing stale or inaccurate status messaging that did not reflect actual system behavior.

Original source

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

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