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.