Britecore Release Notes

New Features and Enhancements

Stable Ordering for the Policy Change Log API Endpoint (BC-22659)

The policy change log API endpoint now returns results in a consistent, chronological order. Previously it returned entries without a defined order, so integrations consuming the data had to sort it themselves and risked misreading events that shared a single revision. Results now arrive in a stable order, making it reliable to classify revisions such as cancellations, reinstatements, and endorsements.

Reliable Policy Matching for Shared Legacy Policy Numbers During Migration (BC-25233)

When a carrier moves onto BriteCore, migration keeps existing policy numbers so each policy stays searchable by the number the insured recognizes. Previously, when the same legacy number belonged to both a historical policy and a newer policy that carried it as a previous number, the migration could not reliably tell them apart and sometimes created a duplicate policy. BriteCore now consistently selects the correct policy, preventing duplicates during migration.

Endorsement Controls and Language in the Agent Quote Wizard (BC-25254)

In the agent Quote Wizard endorsement flow, the application page and the post-submit confirmation previously showed controls and wording meant for new business, including a Print Policy Application button and messaging that described issuing a new policy. These now reflect the change transaction, so an agent processing an endorsement sees the correct endorsement controls and language.

Endorsement-Specific Controls and Wording in the Agent Quote Wizard (BC-25563)

In the agent Quote Wizard, endorsements previously showed the same Print Policy Application button, Attachments section, and submission wording used for new business. On endorsement flows, the Print Policy Application button is now hidden, the Attachments section is hidden when the flow has its own Attachments step, and the submission confirmation uses endorsement wording. Both controls are available as Quote Wizard flow features, so administrators can configure them per flow.

Foreign Driver's License Support in the Auto Quote Wizard (BC-24392)

The Driver's Information step of the Auto quote wizard now includes a Foreign driver's license option and a Country Issued field. A driver holding a non-U.S. license can now be quoted end to end, rather than being blocked by the License State field, which previously was always required.

Underlying Platform Upgraded to Python 3 (BC-22569)

BriteCore upgraded its underlying platform to Python 3 and removed the legacy Python 2 interpreter and its dependencies. Document rendering was verified against the previous behavior, with only minor font-level pixel differences that do not affect page flow or page counts. This keeps the platform on a current, supported runtime.

Ranked County Selection in the Quote Wizard (BC-23925)

On the property address step of the Quote Wizard, the system now presents ranked county matches with a confidence indicator and lets users override the selection when needed. When the entered address is left unchanged, the address verification provider's coordinates are preserved instead of being replaced by the geocoder on each save. This gives more accurate county and location data on quoted properties.

Per-Provider Monitoring for Address Geolocation (BC-23927)

Address verification and geolocation calls are now tagged by provider in BriteCore's monitoring, so call volume, latency, and error rates can be tracked for each provider individually. This gives clearer visibility into how each geolocation provider is performing.

Faster Rating in the Quote Wizard (BC-23946)

Selecting Rate in the Quote Wizard previously triggered a chain of sequential requests that added noticeable wall time before a premium appeared. Rating in the Quote Wizard now runs through the unified quote engine, collapsing that chain into a single path. Quotes return their premium faster as a result.

Updated Contacts Settings Page (BC-24465)

The Contacts settings page was rebuilt on BriteCore's current interface framework, bringing it in line with the rest of the Settings area. Existing configuration, including required fields for named insureds and credit tiers, continues to work as before, and this lays the groundwork for policy-type-specific required fields.

Explicit API Key Session Endpoint (BC-25601)

Some integrations, such as the tools used to move a carrier's data into BriteCore, need to sign in to BriteCore to finish their work. These integrations can now sign in only after an administrator grants them permission, and each sign-in is listed in Login History. Integrations without this permission cannot sign in this way. Creating and managing API keys is unchanged.

Revert Option for Overwritten Prefill Values (BC-24445)

When the property valuation prefill service proposes a value that an agent then edits, agents can now see a Revert option, controlled by a Quote Wizard setting, to restore the vendor-proposed value. The underlying change records the last vendor value for each affected field so it can be restored on demand. This gives agents a clear way to undo an edit back to the prefilled value.

Claim Rules in the Simulation Tool (BC-21797)

The simulation tool now supports claim rules alongside the rule types it already covered. Users can model how a claim rule behaves before putting it into use, making it easier to confirm the intended outcome ahead of time.

Bug Fixes

Payment Confirmation Email Wording and Amounts (BC-24305)

In payment confirmation emails, the message body stated only the premium rather than the full amount charged, so an email could read as a lower payment than the attached receipt showed. For group payments, a single email applied the whole payment amount to the first policy. BriteCore corrected the email wording and amounts so the confirmation reflects the actual payment and how it was applied.

Errors Moving Outstanding Fees and Debit Transfers at Renewal (BC-24953)

When renewing a policy that carried an outstanding fee or debit transfer alongside an invoice, BriteCore could either produce an error or move the outstanding balance incorrectly, depending on the order of the charges. BriteCore now transfers these outstanding charges to the new term correctly during renewal.

Vendor Settings Window Will Not Open for Older Payment Configurations (BC-25515)

In Settings under Vendors, clicking the edit pencil beside the Invoice Cloud CloudPay vendor did nothing when the stored vendor record predated a newer configuration section, leaving no popup, error, or feedback. BriteCore corrected the vendor settings window so it opens and supplies the missing section even for these older records.

Required County Not Enforced on Save and Stay (BC-25617)

In the Quote Wizard, Save and Stay could save a property with the required County field left blank, with no validation message shown. BriteCore updated Save and Stay to validate County the same way other required fields are checked, so a property can no longer be saved without a county.

Agents Cannot Save a Property Address in the Quote Wizard (BC-25976)

In the Quote Wizard, agents on tenants using the newer permission engine could not save a new or changed property address on the Property Details step; the save was refused with a permission error and the wizard could not advance. BriteCore updated the permission handling so these agents can save property addresses and continue through the wizard.

Claims Notes Not Defaulting to User Generated (BC-20818)

On the Claims Notes screen, the Note Type field did not default to User Generated even when the Default to User Generated Notes setting was enabled, forcing adjusters to select the type manually for every note. BriteCore now defaults the Note Type to User Generated when that setting is turned on, reducing manual effort and the risk of misclassified notes.

Policy Type Rename Removing Quick Codes From Another Policy Type (BC-24974)

When a policy type was renamed, the system moved its quick codes to the renamed policy type without checking whether another policy type used the same code, causing that other policy type to lose its quick codes and claim tab settings. BriteCore corrected the rename so quick codes shared by another policy type are copied rather than moved, leaving the other policy type unaffected.

Transferred Policies Still Listed on the Former Agency (BC-19657)

After a book of business was moved with the Transfer Agency Policies support tool, policies continued to appear on the former agency's contact page even though they had transferred correctly to the new agency. BriteCore resolved the issue so transferred policies no longer display under the previous agency of record.

Incorrect Cities and Counties in Address Lookup (BC-24710)

When looking up an address by ZIP code on a contact, the city and county options could include values from a different area when the street address matched a similarly named street elsewhere. BriteCore updated the address lookup to exclude results that fall outside the requested ZIP code, so only valid cities and counties are offered.

Continue Does Nothing on Policy Setup for Existing Policies (BC-25921)

In the Quote Wizard, clicking Continue on the Policy Setup step did nothing for existing policies such as endorsements and saved quotes, and the loading indicator never cleared. New quotes were not affected. BriteCore corrected the Policy Setup step so Continue advances for existing policies and endorsements.

Scheduled Reports Skipped After a Brief Database Interruption (BC-25093)

A temporary database interruption while a scheduled report was starting could cause BriteCore to treat the schedule as misconfigured and silently skip it. When every schedule of a report was skipped this way, the report produced no output and did not run, leaving only a warning in the logs. BriteCore now distinguishes a transient database error from an actual configuration problem, so scheduled reports continue to run after a brief interruption.

Column Formatting Unavailable When a Preview Cannot Be Generated (BC-25305)

In SQL Editor, when a query could not produce a preview, the column format controls became unavailable because they depended on the preview grid, so users could not configure column formats for the report. BriteCore restored the ability to configure column formats even when no preview is rendered.

Policy Applications Not Generating After Submission (BC-22918)

Some agents did not receive the Policy Application document after submitting a policy from the agent side. The deliverable failed to generate whenever a supplemental question answer was stored without a value. BriteCore corrected Policy Application generation so it handles these answers and produces the document reliably.

Endorsement Summary Fails on Large Revision Notes (BC-25007)

Generating the Endorsement Summary could fail when a revision accumulated a very large policy note, because the note's contents overflowed a single page and stopped the document from building. BriteCore corrected the Endorsement Summary so large notes no longer break the deliverable.

Spurious Failures From an Unconfigured Billing Statement Deliverable (BC-25153)

A legacy billing statement deliverable that is not configured to produce a file was being queued repeatedly and recorded as a failed document generation, creating a high volume of failure entries each day even though no document was expected. BriteCore no longer queues this legacy deliverable, removing the spurious failures.

Electronic Delivery Status on the Policy Attachments Screen (BC-25434)

On the new Policy Attachments screen, documents that were successfully delivered electronically through BriteApps displayed a print status of To Be Determined or Do Not Print rather than showing them as delivered. This led carriers to believe declarations, disclosures, and forms may not have been delivered across multiple policies and years. BriteCore now reflects the electronic delivery status on the Policy Attachments screen.

Duplicate Invoices From Rapid Billing Schedule Changes (BC-19267)

When a user changed a policy's billing schedule several times in quick succession, BriteCore could create duplicate invoices on the policy. The issue came from overlapping billing-schedule changes running at the same time. BriteCore now prevents the duplicate invoices from being generated.

Zero-Dollar Agency Commission Reports Not Emailed (BC-21888)

Agency commission reports were not being emailed to agencies that had a generated report but no commission payment for the period, including zero-dollar reports that should still be delivered. This was introduced when a new commission page changed how BriteCore determined which agencies to email. BriteCore now emails all generated agency commission reports, including those with a zero-dollar amount.

Transferred Return Premiums Exportable Through the Bulk Utility (BC-25040)

The bulk return premium export utility could export a return premium that had already been transferred back during a reinstatement, even though the standard return premium export correctly blocks transferred records. This left the accounting in an inconsistent state. BriteCore now applies the same block in the bulk export, so transferred return premiums can no longer be exported.

Billing Recipient Not Saving in the Quote Wizard (BC-25106)

On the Billing step of the quote wizard, the Bill Whom and Bill How selections could fail to save, and adding a payment account produced an error. BriteCore was repeatedly resetting the Bill Whom value, so it never persisted. BriteCore resolved the loop so the billing recipient and method save correctly.

Manual Agency Commission Payments Stuck in Reviewed (BC-25115)

On sites that pay agency commissions manually, without a connected check or ACH issuance integration, the Agency Commissions Process Payments action reported success but processed zero payments, leaving manual commission payments stuck in a Reviewed status and preventing the commission month from being closed. BriteCore now processes manual commission payments on these sites so the month can be closed out.

Duplicate Payments From PNC Lockbox Imports (BC-25158)

When a PNC lockbox payment file was imported and one or more entries were resubmitted while the batch was still processing, BriteCore could post duplicate payments with the same date, check number, and amount. A site-wide duplicate-payment setting was overriding the lockbox import's own instruction to block duplicates, and the import was not protected against being applied twice. BriteCore now prevents these duplicate lockbox postings.

Flat Cancellations Retaining Commission Credits on Rewrites (BC-25171)

When a policy was flat canceled after its term expiration, the original net commission credits remained in place even though the cancellation removed the premium, and the cancellation posted a zero-commission entry instead of reversing the credit. The leftover credit then carried into rewritten policies, understating their balances and inflating the return premium. BriteCore corrected the cancellation accounting so commission credits are reversed and no longer distort rewrite amounts.

Void and Delete Unavailable for Electronic Payments (BC-25321)

On the Accounts Receivable screen, carriers using the Invoice Cloud payment vendor could not void or delete any non-cash payment, because the Void and Delete buttons were hidden for electronic and ACH payments. BriteCore restored the Void and Delete actions so these payments can be managed from Accounts Receivable.

Down Payment Disagrees With the First Invoice by a Rounding Penny (BC-25325)

At bind, the down payment quoted and charged in the agent portal could differ from the first invoice BriteCore generated by one cent, because the quoting and invoicing paths rounded installment amounts differently. This overdrew the autopay draft and left a small permanent credit on the term. BriteCore aligned the two calculations so the quoted down payment matches the invoiced amount.

Duplicate Payment Voided Policy Note (BC-25376)

When a payment was voided, BriteCore wrote two identical Payment Voided notes to the policy's Notes list instead of one. BriteCore removed the duplicate, so voiding a payment now records a single Payment Voided note.

Re-Cancellation After Reinstatement Creating an Incorrect Invoice (BC-25402)

When a back-dated cancellation was reinstated and then canceled again to the same date, the system could create a large endorsement invoice instead of the expected unearned premium adjustment and return premium. BriteCore corrected the cancellation accounting so a re-cancellation mirrors the original cancellation.

Non-Pay Cancellation Failing on a Backdated Process Date (BC-25556)

When a non-pay cancellation fee applied and the cancellation was processed for a date other than the current day, the entire cancellation was rolled back and the policy was left uncanceled. BriteCore corrected the cancellation fee handling so the cancellation completes regardless of the process date.

NSF Transactions Recorded on the Wrong Day Near Midnight (BC-25567)

When a payment was marked as non-sufficient funds through the service interface near midnight, the accounting entries could be recorded under the wrong day because the date was taken from UTC rather than the site's local time. BriteCore corrected the date handling so these transactions post on the correct day.

Payment Missing From Account History (BC-25592)

On a policy's Accounts Receivable tab, a payment that had been accepted by the vendor did not appear in the Account History table even though the payment progressed through the normal payment flow. BriteCore corrected payment recording so accepted payments appear in Account History as expected.

Duplicate Installments From the Agent Billing Step (BC-25611)

On the Billing step of the agent policy wizard, clicking Next immediately after changing the billing schedule could save the schedule twice at once, creating duplicate installments and duplicate autopay drafts. BriteCore corrected the billing step so the schedule saves only once, preventing the duplicate installments and charges.

Application Error Downloading InsVista Files (BC-21881)

When downloading InsVista files, carriers encountered an application error that prevented the files from being retrieved. BriteCore resolved the file download process so InsVista files download successfully.

Duplicate Policy Issued Event for Same-Date Revisions (BC-25127)

For carriers using BriteCore's policy event integrations, committing a revision dated on the policy term's effective date for an already-active policy produced a second policy issued event instead of a policy endorsed event. Integration consumers could not tell the endorsement apart from the original issuance. BriteCore now emits the correct policy endorsed event in this situation.

QuickBooks Check Issuance Reinstall Failure (BC-25300)

When reinstalling the QuickBooks Online Check Issuance integration, a leftover connection record from a previous uninstall could cause the install and uninstall actions to fail with a server error, leaving the carrier unable to reconnect the integration. BriteCore resolved the error so the integration can be removed and reinstalled cleanly.

ISO A-Plus Monthly Report Not Marked as Sent (BC-25426)

In Policies, Processing, sending an ISO A-Plus monthly report while that report was still being generated could cause BriteCore to transmit the file but fail to record it as sent. The month then appeared without the Sent marker, leading carriers to believe the report had failed even though it reached ISO. BriteCore now records the report as sent in this situation, so the Sent status reflects the successful transmission.

Configuration Promotion Export and Import Compatibility (BC-24359)

When promoting configuration between sites, exported packets could contain data that the importer rejected, forcing whole sections to be removed before an import would succeed. BriteCore corrected the export and import handling so a promoted configuration packet imports cleanly.

Underwriting Rules Not Matching Deductible Selections in the Builder (BC-25154)

In the legacy policy Builder, underwriting rules that triggered on a selected deductible amount never matched, because the rule compared against an internal reference instead of the chosen dollar amount. As a result these rules never fired, and options they should have suppressed stayed selectable and ratable. BriteCore corrected the comparison so deductible-based underwriting rules evaluate against the selected amount and fire as configured.

Configuration Promotion Excludes Check-Number Counters and Environment Settings (BC-25379)

When promoting Settings configuration between environments, certain operational values were included in the exported package that should not be carried across, including check-number counters and environment-specific identity settings. Importing them could move a check-number sequence backward and overwrite environment identity. BriteCore now excludes these operational values from the promotion, protecting check numbering and environment settings.

Internal Users Cannot Select Policy Types Closed to Quoting (BC-25693)

After a recent release, internal staff could no longer select policy types that a carrier keeps closed to quoting, which blocked them from writing new business on those programs on agents' behalf. BriteCore added a setting, internal-users-can-select-closed-to-quoting-policy-types, that lets internal users select policy types closed to quoting, restoring the previous behavior.

Nightly Renewals Blocked by Unanswered Builder Questions and a Commercial Rule Error (BC-25691)

After an upgrade, nightly renewal processing failed for commercial policies when a persistent builder flagged unanswered questions and a commercial underwriting rule errored while evaluating its trigger, so the night's renewals did not process. BriteCore resolved the underlying change so these policies renew during the nightly run.

Application Error After Deleting a Copied Quote (BC-17065)

When a policy was created with Copy Quote and the original policy was then deleted, agents viewing the new policy encountered application errors across the quoting tabs, and the Copied From reference showed as undefined. BriteCore resolved the issue by clearing the stale Copied From reference when the source policy is deleted and guarding the quoting and rating screens so the new policy loads without errors.

Special Characters Blocking Batch Email Sends (BC-19366)

When a batch of pending emails was sent from the Processing tab, a single contact or document whose name contained an unsupported special character could stop the rest of the batch from sending. BriteCore now processes each item individually, so one problematic record no longer prevents the remaining emails from going out, and it cleans these special characters from newly generated document titles. The failure report also identifies the specific document and record involved.

Application Error When Removing an Empty Underwriting Contact (BC-21024)

On the policy's information page, clicking the remove button next to an empty underwriting contact produced an application error. BriteCore now hides the remove button until a contact has been assigned, so it appears only when there is data to clear.

Policy Number Validation Rejects Non-Breaking Hyphens (BC-22661)

BriteCore now rejects a non-breaking hyphen when saving a policy number, preventing a policy from being stored with a look-alike character that would make it unsearchable by its standard hyphenated number. The save is blocked with a message that identifies the field and the expected standard hyphen.

Coverage Category Copy Updating Removed Items (BC-24690)

When copying coverage category data between policy items, BriteCore could apply the updates to items that had already been removed and still report the copy as successful. BriteCore now excludes removed items from the copy, so updates are applied only to active items.

Incorrect Term Selected When Cancelling a Policy With a Future Term (BC-24698)

When cancelling a policy that has a future term, BriteCore could select the wrong policy term while processing the cancellation and, in some cases, fail with a database error. This occurred when the future term crossed a Lines Effective Date boundary and mapped to a different policy type version. BriteCore now identifies the correct term during cancellation, preventing the error.

Commission Report File Name Collisions for Similar Agency Names (BC-24802)

When generating agency commission reports, two agencies whose names differed only by accented or special characters could produce report files with the same name, causing one to overwrite the other. BriteCore now generates distinct file names for these reports so each agency's report is preserved.

Committing a Revision Affecting an Unrelated Policy Term (BC-24883)

When committing the first revision of a policy term, BriteCore could archive a pending revision that belonged to a different term on the same policy, leaving that term stranded and blocking payments against it. BriteCore now limits this step to the term being committed, so unrelated terms are no longer affected.

Policy List Sorting by Review State (BC-24921)

On the Policy List, sorting by the Review State column could order rows by a value the column does not display, so a policy might appear out of order relative to its shown Review State. This happened for policies that carry more than one review state across their revisions. BriteCore corrected the sorting so the Policy List orders by the Review State shown in the column.

Billing Amounts Missing When Reselecting the Current Schedule (BC-25125)

In Secure Checkout, selecting the billing schedule that the policy already had returned a success response without the updated amounts, which could leave the page unable to display the amount due and stop it from updating. BriteCore now handles this case so the billing amounts display correctly.

Policy Number Validation on Bulk Data Loads (BC-25344)

In the handling of policy numbers, bulk data loads could store a policy number containing a non-breaking hyphen that bypassed the standard validation applied elsewhere. Because searches normalize that character away, a policy number stored this way could not be found by typing it. BriteCore applied the same validation to the bulk write path so these values are rejected consistently.

Property-Level Additional Interests Disappear When Reopening a Policy (BC-25514)

On a policy, additional interests added at the property level did not appear when the policy was reopened, and users had to refresh the page or reselect the line of business to see them again. BriteCore resolved the issue so property-level additional interests display immediately when reentering the policy.

Application Error Rating an Endorsement With Blank Additional Insured Answers (BC-25699)

When endorsing a dwelling policy, clicking Rate and Save in the Builder returned an application error if the Additional Insured questions were left blank. BriteCore corrected the Builder so it handles blank Additional Insured answers and the endorsement rates and saves without error.

Application Error Entering the Quoting Module (BC-17335)

When a carrier left the optional quote effective-date boundary settings without a value, all agents hit an application error when opening the quoting module, after which the page became unresponsive and no new business could be quoted. BriteCore corrected how these boundary settings are read so a missing value no longer causes the error.

Product Description Missing After Effective Date Change in Quote Wizard (BC-17362)

In the Quote Wizard, the product description and underwriting guidelines shown on the Policy Setup screen disappeared when an agent changed the policy's effective date on that screen. The information was present when the policy type was first selected but vanished after the date change. BriteCore now keeps the product description and underwriting guidelines visible after the effective date is changed.

Clearer Warning When Changing a Quote's Effective Date (BC-23848)

When an agent changes a quote's effective date to a date governed by a different Lines Effective Date, BriteCore clears the coverages, risks, and rating on the quote. The confirmation message shown before the change now states plainly that changing the effective date will clear the coverages, risks, and rating on the quote and that the action cannot be undone, so the agent understands the impact before continuing.

False Rating Error for a Mandatory Fee on Dwelling Fire Quotes (BC-24470)

When an agent created a new Dwelling Fire quote and rated it at the full policy level after adding the mandatory policy-wide items, BriteCore could display a rating error incorrectly stating that a mandatory fee was disallowed and had to be removed. The error was transient: dismissing it and recalculating premiums rated the same quote successfully with the fee included. BriteCore resolved the issue so the quote rates without the false error.

Closed-County Quoting Suspension Not Fully Enforced (BC-24714)

In the quote wizard, when a property fell in a county closed to quoting, agents saw the closed-county message on the Risks step but could still advance to later steps and continue working the quote. BriteCore added a hard stop so the wizard prevents moving forward while a property sits in a suspended location, and the quote creation path no longer creates a quote when the suspended location fails to save.

Organization Contacts Unavailable in Restricted Commercial Flows (BC-25625)

In the Quote Wizard for commercial programs configured to allow organization insureds only, agents could not create an organization contact: the form hid the Individual and Organization options but defaulted the contact to individual, showing individual fields with no way to choose Organization. BriteCore corrected the contact form so an organization-only configuration creates an organization contact as intended.

Sidebar Estimate Underprices Compared to the Created Quote (BC-25964)

In the policy wizard, the estimated premium shown in the sidebar did not account for the named insured's credit tier, so it displayed a lower price than the quote actually created when the agent proceeded. BriteCore corrected the estimate to include the credit tier so the sidebar figure matches the created quote.

Quick Quote Spins When Creating a New Quote (BC-25973)

When an agent created a new quote, the page spun and the quote did not load. BriteCore resolved the issue so agents can create a new quote without the page hanging.

Report Runs Orphaned by Uncommitted Tracking Records (BC-25451)

When a report was started from the report list, the background report run could begin before its tracking records were saved. If the web request ended before those records committed, the run was left orphaned, the report query never ran, and no output was produced. BriteCore now commits the run's tracking records before starting the process so reports complete reliably.

SQL Editor Warning for Temporary Measure Tables (BC-25296)

In the SQL Editor, a query could reference a dated measure table that exists only temporarily, and the query would validate and save without warning. Because the cleanup process later drops those tables, the saved report would run successfully for a while and then begin failing with no indication of why. BriteCore now flags these temporary table references so reports are not built on tables that will be removed.

Loss Ratios Over 100 Percent in the Excel Report (BC-25332)

In the Premium Earned to Losses Incurred report, loss ratio percentages greater than 100 percent were scaled incorrectly in the generated Excel file, so a ratio such as 136.15 percent displayed as 1.36 percent. The underlying report calculations were correct; the error occurred when the Excel file was formatted. BriteCore corrected the formatting so loss ratios above 100 percent display accurately.

Invalid SFTP Export Destinations Not Caught at Save Time (BC-25600)

A scheduled report export over SFTP failed on every run because the configured destination host and path were malformed, and the export configuration had been saved without validating them. BriteCore added save-time validation of the SFTP destination so a malformed host or path is caught before the export is scheduled.

SQL Runner Reports Hanging Without Completing (BC-25847)

SQL Runner report jobs could hang indefinitely without producing an output file, remaining in a Running state until they eventually timed out, which left some scheduled reports undelivered. BriteCore resolved the deadlock so these report jobs complete and deliver their output.

Unarchive Records Tool Cannot Find Archived Contacts (BC-25432)

In the Unarchive Records support tool, selecting the Contacts search screen and typing an archived contact's name returned only active contacts, so an archived contact could not be selected or restored. BriteCore corrected the contact search so archived contacts appear and can be unarchived.

Settings Content Overflow With the Sub-Sidebar Expanded (BC-25313)

On Settings pages, expanding the left sub-sidebar in a browser window narrower than roughly 1200 pixels pushed the content to the right without resizing it, so the page overflowed horizontally, clipping the heading on the left and running controls off the right edge. BriteCore corrected the layout so Settings content fits within the window when the sub-sidebar is expanded.

Custom File Transfer Stops After a Single File Error (BC-22789)

In the custom file transfer process, an error on a single policy's document caused the entire process to stop, preventing the remaining files from being transferred. BriteCore now continues processing and sending the other files when one file fails, and reports the file that errored in the daily job report.

Incorrect Credit Tier for Contacts Without a Credit Score (BC-25290)

On the contact view, a named insured added to a quote without a credit score could display a credit tier of Deceased instead of showing no tier. This happened when a carrier's credit-tier configuration included two score-triggered tiers that both matched the no-score value, and BriteCore selected the wrong one for display. BriteCore now displays the correct tier for contacts without a credit score.

Non-Functional Insured Portal Codes for Imported Contacts (BC-24473)

Contacts created through a bulk import received a placeholder portal code of 000000 instead of a generated one, which prevented the insured from verifying and logging into the Insured Portal. BriteCore resolved the issue so imported contacts receive a valid portal code, allowing portal verification to succeed.

Incorrect Payment Methods Shown on Accounts Receivable (BC-21405)

For sites running two payment processors, policies with effective dates after the processor cutoff date showed payment methods from both processors on the Recurring Billing Contact in Accounts Receivable. BriteCore resolved the issue so that only the payment methods belonging to the policy's current processor are displayed.

Named Insured License Number Now Populates from the Driver Report (BC-24819)

On the driver screen, when a named insured was added as the primary contact and the automated driver report was run, the named insured's own driver's license number was not pre-filled from the response, even when a license number was returned for them. BriteCore updated this behavior so that the named insured who generates the driver report lookup now has their license number populated from the response.

System Fee Write-Off Posting a Zero Amount (BC-24954)

BriteCore identified and resolved an issue in the account write-off process where writing off an outstanding system fee balance posted a waive of $0.00 while reporting the action as successful, leaving the balance unchanged. The process now posts the correct write-off amount or fails explicitly instead of silently recording a zero amount.

Convenience Fee Incorrectly Shown on ACH Payment Receipts (BC-24982)

On policies using a legacy payment processor, the Payment Receipt could display a convenience fee on an ACH payment that did not actually carry a fee, because the fee lookup matched on the bank or card brand name rather than the payment method. BriteCore corrected the fee lookup so that ACH payments no longer show a convenience fee that was never charged.

Retained Sessions Under High-Volume API Authentication (BC-25027)

Under high-volume authentication, concurrent requests could leave extra web sessions retained in the session store rather than cleaned up as each session rotated. BriteCore corrected the session rotation handling so that superseded sessions are reliably removed, preventing sessions from accumulating.

Quote Creation Rejecting Requests That Omit Optional Address Fields (BC-25031)

When creating a quote through the quote API endpoint, a request that correctly omitted optional address fields such as the second address line or county was rejected with an error that named the omitted field. BriteCore corrected the handling so that these optional address fields can be left out without causing the request to fail.

Quote Creation Rejecting a Valid Named Insured Email (BC-25073)

When a contact email was configured as a required field, no quote request could both pass validation and save the email, so quotes were incorrectly referred for a missing email even when one was provided. BriteCore corrected the validation so that the supported email format is accepted and the email is saved.

Territory Code Defaulting Incorrectly on the First Rating (BC-25075)

When first landing on the builder page for a new quote, the territory code used for rating defaulted to the first value in the territory table instead of the value matching the garaging address ZIP code, which could produce incorrect rating. BriteCore resolved this so that the territory code resolves from the entered address on the initial rating.

Card Decline Message Shown When Saving a Bank Account (BC-25382)

In the Add Payment Method window, when a user saved a US bank account and the account was rejected, the error dialog displayed Your card was declined even though the user was saving a bank account rather than a card. BriteCore updated the window to show the bank-account-specific explanation for this rejection.

Property County Not Updating After an Address Change in Quote Wizard (BC-25616)

In Quote Wizard, editing a property's address could save the county from the previous address rather than the new one, leaving the required County field showing a single unselected option. BriteCore corrected this so that the county updates to match the newly entered address.

Stale Trigger Field When Changing Items in Claim Rules (BC-21664)

In claim rules, choosing Limit as the Trigger Type and then changing the Item to one that does not support Limit left the Limit field in place. BriteCore resolved the issue so the field now clears when the selected item does not support it.

Attachment Upload Validation for Email Files (BC-22930)

BriteCore reviewed reports that email files dragged directly from Outlook were being rejected when uploaded to claim and policy attachment folders. Investigation found this stems from how Outlook provides the file during a drag and drop, which is outside BriteCore's control; file size validation was strengthened on attachment uploads as part of the review. Users can continue to add these files by attaching them individually.

Indistinguishable Coverage Options on the Create Exposure Screen (BC-23225)

On the Create Exposure screen, when a policy had multiple instances of the same coverage type, every option in the coverage picker displayed the same label with no coverage amount or description, so the adjuster could not tell which item they were selecting. BriteCore updated the picker so that each coverage option is distinguishable by its coverage amount and description.

Show Payment Method Setting Not Honored in Claim Payments (BC-24919)

In Claims, the setting that controls whether the Payment Method dropdown appears on claim payments was not honored in the newer payment entry window, so the Payment Method field continued to display even when the setting was disabled. BriteCore corrected the payment window so that it respects this setting.

Claims Settings Failing to Save When a Field Is Left Blank (BC-25317)

In Settings, saving the Claims module could fail with a server error when a numeric field such as Max loss causes per claim or the maximum claim adjusters and supervisors was left blank on a site that did not yet have that setting stored, and none of the changes on the page were saved. BriteCore resolved this so that the Claims settings save successfully even when such a field is left blank.

Unescaped Column Names in a Database Update Routine (BC-25105)

BriteCore identified and resolved an issue in an internal database update routine where column names supplied by a caller were placed into the query without being escaped, so a specially crafted field name could alter the statement. Column identifiers are now escaped, closing the issue.

Contact Save Operations Accepting Unintended Fields (BC-25108)

BriteCore identified and resolved an issue where several contact save operations accepted any field included in the submitted data, allowing fields that the form does not own, including sensitive account fields, to be set. The save operations now accept only their intended fields.

Corrected Swapped Gender Value Constants (BC-25324)

BriteCore corrected two internal gender value constants that held each other's values. There was no customer-facing impact, and the correction prevents the values from being applied incorrectly in the future.

Restricted Settings Writable Without a Permission Check (BC-25501)

BriteCore identified and resolved an issue where certain settings reserved for internal administrators could be written by a carrier administrator by including them alongside a setting the screen legitimately edits, with no server-side permission check. These restricted settings are now verified on the server before they can be changed.

Validation of Report Parameters Used Outside Quoted Text (BC-24588)

A text or untyped report parameter placed outside a quoted string in a report's query was inserted without a shape check, which could let a crafted value broaden the report's results beyond its intended scope. BriteCore resolved the issue by validating these parameter values so they are treated strictly as data. This keeps report parameters from altering the query's scope.

Missing Print Description on Underwriting Cancellation Notices (BC-20011)

When a policy was cancelled for an underwriting reason on a specific future date, the Notice of Underwriting Cancellation was generated from the currently active revision rather than the cancellation revision, so it was missing the cancellation print description. BriteCore resolved the issue so the notice now uses the correct revision and includes the intended print description.

Declined Commission Payment Note Missing Payee and Amount (BC-25023)

When an electronic commission payment to an agency was declined, the Payment Declined note recorded only the raw processor error, without the payee, amount, or commission reference, and it was written to the global policy notes rather than the agency contact. BriteCore updated the note so that it includes the payee and amount and is recorded against the correct agency contact.

Incorrect Year of Policy Inception on Renewals (BC-24189)

On certain renewals, the Year of Policy Inception category used by a claim-free credit item populated with a stale value that did not reflect the policy's actual inception date, producing an incorrect credit. BriteCore resolved the issue so the category resolves to the correct value based on the policy's real inception date.

ImageRight Nightly Upload Performance with Large File Backlogs (BC-24903)

The nightly process that uploads documents to the ImageRight integration handled eligible files inefficiently, so sites with a large backlog of pending files could not finish the upload within the nightly processing window. BriteCore improved how the process works through the backlog so that large volumes of documents complete within the available time.

Duplicate Database Write on ImageRight Uploads (BC-25111)

Each successful upload to the ImageRight integration recorded the same file tracking value to the database twice. BriteCore corrected the process so that the value is written a single time per upload.

Nightly Dropbox Print Backup Running on Non-Live Sites (BC-25859)

The nightly Dropbox print backup process ran on non-live sites, such as testing clones and demo sites, where it could list and delete files in the client's real Dropbox before attempting its upload. BriteCore added a check so that the Dropbox print backup runs only on live sites.

Partial Payment of Invoices With Different Due Dates (BC-17490)

On a policy with more than one invoice carrying different due dates, the system required paying the full outstanding amount even when only one invoice was actually due, both on the secure checkout page and for electronic payments taken by staff and agents. For example, an installment due mid-month could not be paid on its own once a later endorsement invoice existed. Insureds can now pay the due invoice without being forced to pay one that is not yet due.

Residual Policy Type Error When Switching Policy Types (BC-19189)

When a user cycled through policy types on an open revision, the system sometimes retained items from the earlier selections, causing an error stating that more than two policy types exist on the revision and blocking further work. BriteCore resolved the issue so that switching policy types no longer leaves residual items behind, and the error no longer appears.

Incorrect User Attributed in Policy Notes (BC-19627)

Some policy notes displayed a user as the author of actions they did not perform, attributing changes made by other users or the system to the wrong person. BriteCore corrected the note attribution so that each policy note lists the user who actually performed the action.

Renewal Failing Due to an Empty Territory Multiplier Line Item (BC-21492)

Some policy renewals failed to process because of an empty Territory Multiplier line item that should not have been present. BriteCore addressed the condition so that the renewal processes successfully without the empty line item.

Note Search Date Filter Not Retained While Scrolling (BC-21957)

When searching policy notes with a date range filter applied, the filtered results were not retained after scrolling back up through the notes, so the user lost the filtered view. BriteCore corrected this so that the date range filter remains applied while the user scrolls through the notes.

False Underwriting Rules Triggered Note on the Coverages Tab (BC-24931)

On the Coverages tab, opening the tab without making any edits could add a new Underwriting Rules Triggered note to the policy notes even though no values had changed. BriteCore resolved this so that the note is recorded only when underwriting rules actually change a value.

Report Executions Page Failing Due to Missing Database Columns (BC-25576)

On affected sites, the report Executions page and other report queries failed with a database error because two expected columns were missing from the report records table. BriteCore added the missing columns so that the Executions page and report queries load correctly.

Misleading Agency Save Error for Multi-Agency Agents (BC-22976)

An agent linked to more than one agency who created a quote saw the message There was an error saving the agency on the Policy Setup page of a committed revision, even though servicing the policy worked normally and nothing was actually wrong. The error appeared only for agents and only when the default-agency setting was enabled. BriteCore resolved the issue so the misleading error no longer appears.

Policy Type Appears Deselected After Changing a Quote Effective Date (BC-24394)

With the setting that prevents automatically changing the effective date enabled, changing a quote's effective date made the policy type appear deselected for agents, even though the selection was retained. This led agents to re-select the policy type, which reset the builder. BriteCore resolved the issue so the policy type stays visibly selected when the effective date changes, with no unintended reset.

Cross-Site Scripting Risk in Driver Integration Reports (BC-24765)

On the Drivers tab of the quote builder, the file name of an integration report was placed into the page without being sanitized, so a crafted file name could run script in the builder. BriteCore resolved the issue by rendering the file name as plain text, removing the scripting risk.

Policy Forms Not Generating During New Business Issuance (BC-24890)

During new business policy issuance, a database contention issue could interrupt the generation of policy forms, leaving the Declaration document empty and the remaining attached forms unprinted. BriteCore identified and resolved the underlying session handling so that the Declaration and all attached forms generate reliably when a new policy is issued.

Original source

New Features and Enhancements

Duplicate Form Listings on Policies With Two Named Insureds (BC-24741)

On a policy with two named insureds, every form appeared twice on the Attachments tab under each endorsement's Declarations, because a separate copy of each form is attached for each Declaration recipient. The two copies were identical apart from the recipient they belonged to, so the tab looked as though it was listing the same form in error. Each copy is now labeled with the recipient of the Declaration it belongs to, making it clear why both appear and which recipient each one is for.

Faster Quoting Through Longer Policy Type Configuration Caching (BC-24529)

The cached policy type configuration that quoting reads expired every ten minutes, so stable policy types paid a full rebuild from the database several times an hour. That cache now holds for a week and is cleared explicitly whenever a line configuration is written or published, including through the newer line configuration API endpoints. Quoting avoids the repeated rebuilds while configuration changes still take effect immediately.

Check Number, Check Date, and Cleared Date Writeback for Outbound Payments (BC-24593)

Carriers export outbound checks from the return premium, claim payment, and commission payment queues, but the three types did not carry the same check details, and there was no way to record those details after an export had already run. Return premiums now store a check date, commission payments store a check number, check date, and cleared date, and a new API endpoint writes all three values back for any of the three payment types in a single batch. Carriers can reconcile outstanding checks and manage escheatment from one consistent set of fields.

Large Report Downloads No Longer Exhaust Server Memory (BC-24916)

Downloading a large report sent the whole file through the web server, which could exhaust the available memory and interrupt not only that download but every other request the server was handling at the time. Report downloads, including the link in the report summary email, are now served through a temporary direct download address rather than being held in memory first. Large reports download reliably and no longer affect other users working in the system.

Monitoring and Alerts for Long-Running Background Jobs (BC-20381)

BriteCore added internal monitoring for background jobs, including an alert that fires when a job runs longer than expected. New dashboards show the status of report jobs and of all jobs in one place. Long-running or stalled jobs are now identified and addressed sooner.

Embedded Payment Method Entry for Funding Sources (BC-23257)

Funding source setup now collects card and bank details through a payment form shown directly in the page rather than in a separate window. Once the details are confirmed, the list of saved funding sources refreshes on its own. The control that opens this form arrives in a later update.

Reliable Status Responses for Asynchronous Quote Creation (BC-23395)

When a quote is created asynchronously, checking its status could fail with a data error on larger quotes because the stored result exceeded the size the system could read back. The stored response is now kept small, so status checks return successfully. Agents and integrations that poll for quote completion no longer hit that error.

More Accurate Address Location and County Candidates (BC-23924)

Property addresses can now be resolved through a geolocation service that returns coordinates along with a ranked list of the most likely counties. The accuracy rating for the resolved address is now always recorded with the address, so an edited address no longer carries the previous address's rating into underwriting rules and the property map. The county selection screens that use this information follow in a later update.

Single ISO ClaimSearch Request When a Claim Address Changes (BC-24137)

Editing a claim address sent three requests to ISO ClaimSearch, one for each part of the address that changed, including two unnecessary replacement requests. An address edit is now treated as a single change, so exactly one request is sent. Claims staff see one submission per address update in the integration activity.

New Payments Module in the Main Navigation (BC-24409)

A Payments module is now available in the main navigation, between Claims and Reports, grouping payment pages under Incoming and Outgoing headings. It contains Payment Log, Daily Cash Receipt, Return Premium, Commission Payments, and Agency Commissions, with Payment Log as the landing page. Users see only the pages their role permits, and carriers that have not enabled the module see no change.

Payment Pages Moved to Their Own Web Addresses (BC-24410)

The five payment pages are now reachable under their own Payments web addresses, and the previous Policies addresses redirect to them automatically with any parameters preserved. The Policies menu entries point into the new module and page behavior is unchanged. This also corrects a case where completing a payment from Daily Cash Receipt could leave the user on a missing page.

Quote Changes No Longer Overwritten by Another Session (BC-24442)

In the Quote Wizard, saving a loss payee sent the entire stored quote back to the server, so a change made in another browser, on another device, or by an integration could be silently replaced with older values. Each save now sends only the information it owns and the server merges it in. Property characteristics no longer revert after an unrelated save when more than one person is working the same quote.

Manually Entered Values Protected From Integration Updates (BC-24444)

When a user types a value into a property field, the system now records that a person entered it and holds that value, so a later integration run does not replace it. If an integration proposes a different value for a held field, a line is added to the policy notes naming the field, the value being held, and the value the vendor proposed. The option to revert a held value back to the vendor value arrives in a later update.

Replacement Cost Prefill No Longer Overwrites an Existing Value (BC-24446)

The automatic property prefill wrote a replacement cost estimate on every save, which could replace a refined valuation with a lower automated estimate. It now fills replacement cost only when no value is stored, and it no longer adds a policy note when the value has not actually changed. Renewals remain the exception: the prefill still refreshes replacement cost at renewal so the figure keeps pace with inflation.

Groundwork for Detailed Fee Tracking (BC-24972)

Preparatory data structures were added to support future reporting on which fee produced a given charge and which payment settled it. The new structures are empty and nothing reads or writes them yet, so billing, invoicing, and accounting behave exactly as before. This is the foundation for later work in this area.

Reports Workspace With Multiple Schedules Per Report (BC-24927)

Report Workbench is now called Reports, and its run activity and scheduling views have become two pages of their own, Executions and Schedules. A report can now carry more than one schedule, or cadence, so a single report definition can run on several timetables instead of being limited to one. The workspace also adds export, import, and duplicate for report definitions, reorders the Configuration, Documentation, Prior Runs, and Permissions tabs, and remembers filters such as hiding drafts, making the reporting tools easier to reach.

Separate Payment Fees and Distribution Rules Settings Pages (BC-25302)

Settings > Payments was a single page carrying two unrelated configurations, Payment Distribution Rules and Convenience Fees, as tabs, and a recent change had made Distribution Rules the default tab, so a long standing bookmark to that address opened the wrong configuration. Payments is now a menu section with Payment Fees and Distribution Rules as separate pages, each reachable and selectable in the navigation. The original Settings > Payments address serves the fee configuration again.

Bug Fixes

Application Left Issued With a Quote Number After a Failed Commit (BC-24604)

During straight through processing, an application was marked Active before the background task that actually issues the policy had run. If that task then failed, the record stayed Issued and Active while still carrying its quote number and an open revision, and the duplicate submission guard blocked any retry until underwriting reset the application to Unsubmitted. The change to Active now happens inside the same transaction that issues the policy, so a failed commit no longer leaves the application stranded.

Server Error Opening a Policy With a Double Encoded Builder Value (BC-24712)

One of the paths that reads a policy's builder data decoded the stored value only once, so a cell that had been saved in an already encoded form came back as plain text instead of structured data and the request failed with a server error in the builder and the Quote Wizard. That read now applies the same correction already used on the other paths, so the affected policies open normally.

Underwriting Review Queue Missing Policies With an Open Revision (BC-24779)

A policy that had already been issued and also had a separate open revision sitting in underwriting review did not appear when the Policy List was filtered by Review State, because the search index recorded only the issued revision's review state. Underwriters had no way to find those policies from the list. The review state of an open revision is now indexed as well, so these policies appear in the queue.

Empty Policy Listing for a Contact Whose Only Record Is a Quote (BC-24798)

Listing the policies attached to a contact returned the same empty result whether the contact had no records, had only quotes, or did not exist at all, so a newly quoted named insured appeared to have nothing on file and the caller could not tell the three cases apart. The response now reports whether the contact was found, so an empty result can be distinguished from an unknown contact.

Renewal Forms Left Out of the Printed Declaration After a Second Revision (BC-24821)

Where conversion forms print only when staff select that option as the revision is committed, committing a second revision before the declaration printed lost that selection, so the declaration mailed without its form packet and staff had to generate the package by hand. The selection is now recorded on the policy term and honored by later revisions, so the forms print with the declaration.

Agency Emailed a Superseded Declaration After a Second Revision (BC-24825)

When a renewal was revised again before its declaration was due to be emailed, the agency's copy from the first revision was never marked as superseded, so on the send date the agency was emailed the outdated declaration. The superseded agency copy is now suppressed in the same way as the printed copies, so the agency receives only the current declaration.

Current Declaration Marked Do Not Print by a Delayed Revision (BC-24897)

The step that supersedes an earlier declaration had no guard on the order in which revisions were processed, so a delayed background task belonging to an earlier revision could mark the current revision's declaration as do not print. That declaration would then never print at all. Supersession is now scoped to the policy term and ordered, so only genuinely superseded declarations are suppressed.

Error Opening the Policy Builder for a Property Without Coordinates (BC-24904)

Where waterway polygon lookups are enabled, the policy builder built its location query straight from the property's coordinates without checking whether they were present. A property whose coordinates had not been resolved, which happens whenever a geocode returns no result or an ambiguous one, produced an invalid query and an error. Properties without coordinates now skip the lookup.

Alert Dialog Opening on a Note No Longer in the List (BC-24910)

On the alert notes page, creating a note that also stages an alert queues the alert dialog to open as soon as any dialog already on screen is closed. The list was refreshed in the meantime, so the dialog could open against a note row that was no longer part of the list behind it. The dialog now waits for the created note to reappear in the refreshed list before opening.

Duplicate Note Row After Creating a Note (BC-24911)

The notes list is emptied as soon as a refresh starts but refilled only once the server responds, so a refresh that began before a new note was saved could return afterwards and add a second copy of that note to the list. Responses belonging to a list that has already been replaced are now ignored, and repeated rows are discarded, so a newly created note appears once.

Scheduled Item Limits Understated by Comma Formatted Amounts (BC-25018)

In the agent quote wizard, the total limit for a blanket or scheduled inventory item was added up in a way that stopped reading each amount at its first comma, so an amount saved as a formatted currency value counted only the digits before that comma. The resulting total fell well below the sum of the itemized rows, which produced a credit or refund instead of the expected additional premium. Amounts are now read in full regardless of how they are formatted, so the total matches the rows it is built from.

Repeated Prior Term Revisions From Nightly Non Payment Processing (BC-25071)

Nightly processing selects a policy term by its unpaid invoice, so where a carrier bills ahead of inception it could pick up a future renewal on the day that renewal invoice fell due and then record the non payment against newly created revisions in the prior term. Policies already pending cancellation for underwriting reasons gained a new committed revision every morning. Non payment activity for a renewal invoice now stays on the renewal term and leaves the prior term untouched.

Notes Recorded Against the Wrong User (BC-25076)

Background tasks run on long lived workers that did not reset the acting user between tasks, so a task recording a note without naming a user could attribute it to whoever the previous task ran as, in some cases an agent from an unrelated agency. Notes such as print state changes and application submissions showed the wrong name in the entered by field. The acting user is now cleared at the start and end of every background task, so notes are attributed to the right person.

Reinstatement Failure When the Cancellation Reason Was Deleted (BC-25078)

Deleting a cancellation reason in Settings removes the reason itself but leaves existing revisions still pointing at it. For carriers that enforce underwriting cancellation, reinstating a policy in Cancellation Pending status then failed with a system error. The reinstatement check now handles a cancellation reason that no longer exists, so these policies can be reinstated.

Underwriter Review Report Failing on a Deleted Cancellation Reason (BC-25147)

The Underwriter Review report looked up the cancellation or nonrenewal reason recorded on a revision and used the result without checking that the reason still existed. Where that reason had since been deleted in Settings, running the report for the policy term failed. The report now handles a missing reason and completes.

Policy Cancellation Failing When the Reason Was Deleted During the Session (BC-25148)

If a cancellation reason was deleted in Settings after the cancel policy dialog had loaded its list but before the cancellation was submitted, both the dialog and the programmatic cancellation path failed with an error. Both paths now check that the selected reason still exists rather than failing partway through.

Quote Wizard Ignoring a Policy Type's Configured Term (BC-24700)

When a policy type had exactly one enabled quote term, the Quote Wizard showed no term selector at all and created the quote on a fixed one year term, even where the configured term was something else and the policy type card displayed that other term to the agent. There was nothing on the Policy Setup step to reveal the difference. The Quote Wizard now applies the configured term when only one is enabled.

Disabled Deductible Option Left Selected in the Policy Builder (BC-24836)

When an underwriting rule disabled more than one deductible option and one of the disabled options was processed after the option currently selected, the check that notices the selected option is no longer available was overwritten. The automatic switch to the first available option was skipped, and the quote kept a deductible the rule had removed. That check now holds once any disabled option is found to be selected, so an available option is always chosen.

Duplicate Installments From a Double Submission in the Billing Wizard (BC-24913)

The request that rebuilds a policy term's installment schedule had no protection against running twice at once, so two requests arriving together each cleared and re-created the future invoices without seeing the other's work. The term was left with two live copies of every remaining installment. Schedule rebuilds are now handled one at a time per policy, and a second simultaneous request is refused rather than duplicating the schedule.

Declined Electronic Commission Payments Returned to Pending (BC-25024)

Electronic commission payments are marked as exported when they are queued, before the nightly submission reaches the bank. When the bank confirmed a decline and no funds moved, the payment stayed in Exported status and could not be reprocessed without help from BriteCore. A confirmed decline now clears the export status and releases the payment link, so the commission returns to Pending and the carrier can reprocess it.

Invoices Billing the Prior Premium After a Same Day Endorsement (BC-25077)

When a policy term held more than one live revision sharing an effective date, the step that identifies the current revision had no defined way to choose between them. If it selected the earlier revision, the rebuilt invoices were sized from the previous written premium while still being attached to the newer one, so Policy Details showed the corrected premium while accounts receivable kept billing the old amount. The current revision is now resolved consistently, so invoices are built from the correct premium.

Duplicate Postings of External Payments From a Payment Vendor (BC-25230)

When an external payment vendor sent a payment it had already delivered a second time, the endpoint that records those payments had no check on the vendor's own transaction identifier, so a second payment record was created and the policy was credited twice. Carriers using this integration saw doubled credits and reconciliation totals that did not agree. Recording an external payment is now tied to the vendor transaction identifier, so a repeated delivery of the same transaction is recorded only once.

Unlabeled and Missing Fields When Generating a Custom Deliverable (BC-19547)

When an agent generated a custom deliverable from a quote, fields whose underlying controls carried no name were merged together, so the prompt showed a single unlabeled dropdown offering another field's options while several expected questions never appeared at all. Answers then landed against the wrong questions on the finished document. Every field in a custom deliverable prompt is now kept separate, so agents see each question with its own label and its own options.

Insured Phone Numbers Missing From the Loss Notice (BC-24747)

A phone number saved without a phone type was left off the Loss Notice, even though it appeared on the claim's Parties tab and on the contact record. Phone type is optional throughout the system, so any contact saved without one lost their number on the document. Deliverables now include contact phone numbers whether or not a type has been set.

Duplicate Forms Sent to Print on Policies With Multiple Recipients (BC-24886)

When a new Declaration was generated, the step that suppresses the previous set of form attachments was not limited to the affected recipient and did not reach every record it needed to, so superseded forms stayed eligible for printing. Policies with more than one Declaration recipient could send duplicate sets of forms to the print vendor, including some that had been marked do not print. That suppression is now scoped to the recipient and applied consistently, so only the current set of forms prints.

Duplicate Printing of Regenerated Billing Statements (BC-24887)

When a paper billing statement was generated again, the copy it replaced was never marked as superseded, so both versions printed and were mailed. Suppression had only ever applied to Declarations, and a regenerated statement never reached it. A regenerated paper deliverable now supersedes the copy it replaces, so only the latest version prints.

Superseded Declaration From an Earlier Revision Still Printing (BC-24888)

When a policy was endorsed before its existing Declaration had printed, the older Declaration was not always suppressed, because the check matched only on the document title or the revision and missed the earlier copy. Both Declarations then printed for the same recipient. Suppression now matches within the policy term, so a Declaration replaced by a later revision no longer prints.

Declaration Generation Failure on Forms Uploaded Without Metadata (BC-24938)

A policy type form uploaded before its form code, edition number, and description were filled in left those values empty, and the step that builds the list of forms for a revision combined the three without allowing for empty values. Generating a Declaration for that policy type then failed outright. Forms that have no metadata yet are now handled safely, so Declaration generation completes.

Electronic Document Delivery Silently Skipping Policies (BC-25010)

When a policy's line had no system tags configured, building the electronic document file for that policy raised an error that was caught and discarded, so the policy's documents were left out of the nightly upload to the delivery vendor. Nothing surfaced the failure and the job still reported success, which made the missing documents difficult to notice. A line with no system tags is now handled, so those policies are included in the upload.

Large Reports Failing to Produce a Spreadsheet File (BC-24762)

A SQL Editor report whose results were large enough to push the staged spreadsheet past the size limit of the standard archive format failed while the workbook was being packaged, after hours of query time, and produced no file at all. Report workbooks are now written with large archive support enabled, so oversized reports complete and deliver their output.

Parameter Placeholders Removed From Imported Report Queries (BC-25202)

Importing a report definition passed the sheet query through the same cleaning that is applied to free text, which read a parameter placeholder as markup and removed it. The damaged query still saved and passed validation, so the problem surfaced only when someone ran the report. The query is now preserved exactly as written on import, while descriptions and other free text are still cleaned.

Error Saving a Line Item That Uses a Referenced Category (BC-24406)

Saving a line item whose changed category was a Referenced Category failed with an error and discarded the entire save whenever that category was also used by other line items. Only some category types supply a default option when saved, but the system expected one in every case. The default option is now applied only when it is supplied, so these line items save successfully.

Removing a Producer License From a Contact (BC-23809)

On the Contact Information page, selecting the red remove icon beside a producer license had no effect and the license stayed on the record. The control never triggered the removal, so the request was never sent. Selecting the remove icon now deletes the license as expected.

Activation Code Not Emailed After a Username Correction (BC-24673)

On sites using legacy authentication, correcting a contact's username shortly after the invitation was sent issued a new confirmation code, but the follow-up Login Updated email did not include it. The code the contact was already holding stopped working, and activation failed with a message saying the confirmation code did not match. The email sent after a login update now carries the current confirmation code and activation link, so new contacts can activate their account without anyone resending the invitation.

Return Premium Export Failing on Contact Names With Extra Spaces (BC-19341)

A contact name stored with a trailing space does not look any different on screen, but when names were joined together for an outbound accounting export the extra space became a double space that the receiving system rejected, so the return premium export failed. The usual workarounds of changing the payee before or after the export failed as well. Repeated spaces are now collapsed on outbound accounting names, so these exports complete without a data correction.

Policy Note Wording When a Credit Pull Is Skipped (BC-25102)

When a credit pull was skipped or failed, the note written to the policy said the default credit tier would be applied during rating. Rating actually continues to use each named insured's existing admissible report where one is available, so the note overstated what happened and could mislead anyone later reviewing why a policy rated as it did. The note now describes what the system actually does in each case.

Flood Standing Saved Against a Previous Address (BC-24573)

The flood eligibility lookup saved its vendor result as soon as the response came back, without confirming that the property's address still matched the one the lookup had been made for. After an address change made at the same time, a slower lookup for the earlier address could finish last and store flood standing that no longer applied to the property. The result is now saved only once the address is confirmed unchanged.

Document Uploads Rejected by the Document Management Vendor (BC-25072)

The destination filename for documents uploaded to the document management vendor was built directly from the policy, account, agency, and label values, only one of which was cleaned first. A record containing a tab, a line break, or a backslash produced a path the vendor could not accept, and the upload failed and was retried each night. Every part of the filename is now cleaned before the path is built, so these documents upload successfully.

Report Descriptions Readable in the New Report UI (BC-24720)

Carriers use a report's description to record important notes, such as an instruction not to run a report manually, but the Report Workbench collapsed that text into a single run-on paragraph where those notes were easy to miss. Descriptions now keep their original line breaks and basic formatting, and longer text is shortened with a Show more control. The notes read the way they were written.

Editing a Report Description in the New Report UI (BC-24721)

The New Report UIcould show a report's description but offered no way to change it, so carriers had to go back to the older report list to keep those notes current. An Edit description control on the Documentation tab now opens the existing text for editing and saves it back to the report. Report notes can be maintained in the same place the report itself is managed.

Left Navigation Panel Loading Hidden (BC-24654)

Where the left navigation panel had been collapsed, narrowing the browser past the width at which the mobile layout takes over forced the panel open, and returning to a wider window never restored the saved setting, so the panel sat off screen until the window was resized again. The saved setting is now reapplied when the layout returns to the wider view, and the panel appears as expected.

Explanation When Calculate Premium Is Unavailable on an Endorsement (BC-18013)

When an agent made an endorsement that does not affect rating, such as a mortgagee change, the Calculate Premium button did not appear and nothing explained why, so the only way forward was to change an unrelated value on the rating page to force the button to show. The page now tells the agent which locations still need attention and that opening them is what makes rating available. Agents can act on what is missing instead of guessing whether the page is broken.

Quote Wizard Review Status Continuing to Poll After a Session Expires (BC-25090)

On the Review Status step of the Quote Wizard, the page checked for underwriting review updates every few seconds and carried on checking after the user's session had expired, producing a steady stream of rejected requests against the server. The page now stops checking once the session is no longer valid.

Renewal Premium Attributed to the Wrong Effective Month (BC-25283)

On the Policy Schedule sheet of the stock Premium Written Earned Unearned report, a renewed policy produced one row covering all of its terms instead of one row per term, stamped with whichever term effective date the database happened to return first. Renewal premium was therefore counted in the prior term's effective month, and the date could change from one run of the report to the next. The sheet now returns one row per policy term, so each term's premium stays on its own effective date; grand totals are unchanged and only the date attribution is corrected.

Saving a Note Failing on Sites Using the Legacy Note Path (BC-25370)

On sites where notes are served through the older gateway path, saving a new note on a policy or a claim failed with an application error, and editing an existing note failed in the same way. A permission wrapper added around the endpoint changed the signature that the gateway inspects, so the request body was handed over as a single value rather than being expanded into the arguments the endpoint expected. The wrapper now preserves that signature, and note saving works on those sites again.

Agents Unable to Save the Loss Description on a New Claim (BC-25372)

An agent filing a new claim could not save the Loss Description: typing into the field and clicking away raised a permission message followed by a saving error, and the field was left showing an error state. A newly added permission check tested for an administrative permission path that agent roles do not carry, so it refused every agent. The check now evaluates against the caller's own permissions, so agents can file a claim and record the loss description.

Claim Exposures Saved Against the Wrong Policy Term (BC-25107)

When a claim was created in the agent portal and the policy was attached before the loss date was entered, the coverage and location choices offered were drawn from the term in force that day rather than the term covering the loss. Entering the loss date afterwards did not refresh those choices, so the exposures were stored against the wrong term, and any later attempt to add or remove a coverage failed with a message about zeroing reserve amounts that could not be cleared. Saving the loss date now rebuilds the coverage and location lists for the correct term, so exposures are recorded against the term the loss falls in.

Credit Report Requests Failing on the Unified Quote Engine (BC-25334)

On the unified quote engine, the date of birth sent to the credit reporting service could carry a time component or arrive as an unparsed string, a shape the service rejects when it splits the value into day, month, and year. Credit report enrichment could therefore fail without surfacing an error. The date of birth is now reduced to a plain date before the request is built, so credit pulls complete.

Commission Statements Showing Another Carrier's Branding (BC-25528)

Carriers using the per-site commission statement templates could have their month-end agent commission statements rendered with another carrier's logo and address, or with no logo at all. The template folder is chosen from a site identifier that takes a different form depending on whether the statement is generated on demand or on a schedule, and a mismatch fell back silently to a shared template carrying another carrier's details. That identifier is now normalized on both paths, and a fallback is recorded so a future mismatch is visible rather than silent.

Support Ticket Access for Authorized Users (BC-16015)

Some users who were set up to submit support tickets from inside BriteCore lost that access, because the list of authorized users was held as a single record that was rewritten in full on every change, so authorizing one user could drop another. Affected users found the in-application support option missing, or their submission failed without an explanation. That list is now updated one change at a time so entries are no longer lost, and a ticket is filed using the requester's email address rather than a stored vendor account reference, so access no longer depends on the list being complete.

Copying a Quote for a Contact Without a Social Security Number (BC-16087)

Copying a quote or rewriting a policy into a term that fell in a different calendar year was treated as a renewal, which triggered a vendor credit report lookup that requires a Social Security number. For carriers that do not pull credit, copying a quote for a commercial or other contact without that number failed with a vendor integration error. A copy or a rewrite is now treated as new business on its own first term, so those quotes can be created normally.

Erroneous Nightly Vendor Upload Alerts for Claims (BC-16295)

Carriers using the IVANS claims integration received a nightly vendor upload error email on dates that genuinely had no claim transactions or change logs, and the same alert repeated across weekends and holidays. A date with no claim activity is now treated as a normal empty result and no longer produces an alert. Genuine build failures still report as before.

Property Map Pin Location (BC-16537)

The map on the Property tab of a policy could place the red pin somewhere other than the property address, in some cases in an entirely different city. The map already declined to use stored coordinates recorded with poor accuracy, but that check was never applied on the Open Map path, so poorly located coordinates were used anyway. Those coordinates are now recognized and the map locates the property from its address instead, so the pin displays at the property address.

Session Timeout Handling in the SQL Editor (BC-16737)

The SQL Editor did not act on an expired session, so a user who left a query open and came back later received an unauthorized message when they tried to run it. The page now follows the same inactivity timeout as the rest of BriteCore and prompts the user to sign in again. Users no longer have to interpret an authorization error to realize their session had ended.

Blank Payee Name on the Return Premium Check Export (BC-16829)

When a payment was made on a policy in submitted status and that policy was later rejected, the name field came back blank in the Sungard return premium check export, so the resulting check printed with no payee. The name is now populated for those records. Accounting staff can print return premium checks from the export without correcting them by hand.

Notification When the Nightly Escrow File Is Not Generated (BC-16869)

A nightly escrow and mortgagee file could fail to generate without sending any alert, leaving staff unaware until someone noticed the file was missing. Affected carriers now receive a processing errors email when printed escrow and mortgagee invoices exist for a date but no file was produced. Dates with no qualifying activity stay silent, so the alert does not add noise.

Property Limit Enforced While Quoting (BC-16881)

In the legacy agent quoting flow, the limit on the number of properties configured for a policy type was not applied, so agents could add more properties to a quote than the policy type allowed. That limit is now enforced while quoting. Underwriters no longer receive quotes carrying more properties than their policy type permits.

Application Error When Opening a Policy or Creating a Revision (BC-16916)

Some policies could not be opened and no new revision could be created, returning only a generic application error message. An oversized error detail saved by a failed background process was too large to be read back, which blocked the policy page from loading. That detail is now limited in size so affected policies open and revise normally.

Policies Stuck in Pending E-Signature After Docusign Completion (BC-17221)

After an agent completed a Docusign signature request, some quotes stayed in Pending E-signature instead of moving to Submitted and receiving a policy number. Because no active signature request remained, users also could not void the request to recover. Completed signature requests now advance the policy status and assign the policy number as expected.

Pre-Authorized Payment Schedule Missing Payments (BC-17463)

The automatically generated Pre-Authorized Payment Schedule sometimes listed only a single payment instead of the full schedule, forcing users to regenerate the document by hand. The initial schedule now prints every unpaid installment when it is generated automatically.

Separate Agency Experience Results for Agencies With the Same Name (BC-17545)

The Agency Experience report grouped its output by agency display name, so two agencies with the same name were combined into one document and email routing between them was ambiguous. A new option in the report's configuration groups the output by contact instead, prefixes each file with the agency or producer number, and shows those numbers in the recipient list. The option is off by default, so existing runs are unchanged until a carrier turns it on, and the same screen now exposes the existing setting for generating audit files.

Agency Credit Score Account Used When Pulling Credit Scores (BC-18273)

When a credit score was pulled for an insured on a quote or policy, the carrier's account was sometimes billed instead of the Credit Score Account set up for the agency. The pull now uses the account of the agency on the quote or policy, and bills the carrier only when no agency account can be determined. This keeps credit report charges with the agency that requested them.

Clearing the Default LexisNexis Credit Reporting Configuration Removed Other Settings (BC-18409)

In the LexisNexis Credit Reporting configuration, clearing the default configuration also erased credit tier settings saved at the policy type level. Saving a default configuration now updates only default entries and leaves policy type settings untouched. The same protection applies to the ISO Credit Scoring configuration.

Duplicate Emails for Alerts Sent Immediately From Notes (BC-18435)

When a user created an alert on a note and chose to send it immediately, the system sent the email right away and then sent the same alert again the following day. Alerts sent immediately are now marked as sent, so a single email goes out. This prevents duplicate tasks in external systems that are triggered by alert emails.

Rating Error When Policy Wide Evaluations Reference Primary Exposures (BC-18715)

In the Quote Wizard, an evaluation rate object in the Policy Wide section that referenced an item in Primary Exposures failed to rate and returned an attribute error, even though the same configuration rated successfully in legacy quoting. Policy Wide evaluations can now read values from Primary Exposures, so quotes built on this setup rate as expected.

Invoice Cloud Upload Rejected for a Missing Customer Name (BC-19138)

The daily invoice file sent to Invoice Cloud was rejected when an unpaid invoice remained attached to an archived revision with no usable named insured, leaving the customer name blank on that row. The file now takes a usable name from the invoice's own revision or the closest prior committed revision, and omits a single account rather than failing the whole upload. Any omitted account is recorded in the run log so it can be reviewed.

Credit Report Pull Time Shown as an Hour Old Outside Central Time (BC-19274)

In the Quote Wizard, a credit report pulled by a user outside Central time showed as pulled an hour ago immediately after it ran. The stored pull time is now read as Central time before the relative age is calculated, so a fresh pull reads as a few seconds ago. The same correction applies to the past reports window and the Contacts view.

Files Marked Do Not Print Were Still Sent to the Print Vendor (BC-19350)

Policy documents that a user marked as Do Not Print were still picked up and printed by the print vendor the following day. Setting the print status on an attachment now also updates the underlying form record that printing selects from, so files marked Do Not Print are skipped. This avoids unnecessary print and mailing costs.

Note Alerts Not Saved When Added to a New Note (BC-19553)

When a user set up an alert while creating a new note, the alert was not saved with the note and had to be added again afterward. Alerts composed on a new note now persist the first time the note is saved.

Payment Processor Timeouts Reported as Card Failures (BC-19626)

When the payment processor timed out or returned an internal error, the payment was recorded as a declined card and a Card Failure Notice was generated, even for payments drawn from a bank account. These failures are now classified as a payment processor error, so the card failure notice is not produced and the payment note reflects the actual cause.

Marking a Payment NSF on a Cancellation Pending Policy (BC-19653)

Marking a payment as insufficient funds on a policy already in Cancellation Pending returned an error and left the status unchanged instead of moving it to Cancellation Pending, Non-Payment of Premium. A date comparison problem while creating the new revision caused the failure. The status now updates correctly whether or not the policy is already in Cancellation Pending.

Saving a Contact Role Blocked by an Unrelated Confirmation Email (BC-19941)

Assigning an agency group to an agency contact failed with a message that the confirmation email was already in use, for an address the user had never edited and, on some sites, could not see. The Roles tab posts every field the role owns on each save, and the stored username and confirmation email were checked for uniqueness even when they had not changed, so one pre-existing duplicate blocked every later save on that contact. Only the fields a user is actually changing are now validated, and the message names the address in question and the contact holding it.

Underwriting Cancellation Date Replaced by the Non-Payment Date (BC-20281)

For carriers using the setting that enforces the underwriting cancellation date when the non-payment date is later, a policy manually set to cancel for an underwriting reason reverted to the non-payment cancellation date and status. Nightly processing now keeps the Cancellation Pending status and the underwriting cancellation date when that setting applies, so a manually set cancellation date holds.

Application Error When Submitting a Quote With No Agency Email (BC-20849)

When a quote was set to go to the agency and the agency contact had no email address on file, submitting the quote returned a generic application error. Submission now returns a clear message that an email address is required, so users can correct the contact and continue.

HazardHub No-Data Response Blocked Rating in the Agency Portal (BC-21324)

When an agent rated a quote in the Agency Portal and HazardHub returned no data or was unavailable, rating failed with a blocking error and the quote could not be submitted. Rating now continues when HazardHub returns a not-found or server error, adds the vendor message to the quote's alerts, and records a HazardHub unavailable note. Missing addresses and genuine rating errors still stop the rate.

Removing Login Credentials From a Contact Role (BC-21476)

In Contacts, clearing the username, password, and email under a role's Login Information did not persist: the values returned after saving and reloading the page. Cleared login credentials are now saved as blank, so administrators can disable a user's access without deleting the entire role.

Quote Submissions Reverting to an Unsubmitted State (BC-21589)

In the quote flow, a submitted quote could intermittently revert to an unsubmitted state, with the assigned number reverting to the original quote number. This happened when a request was interrupted partway through saving and partial work was still committed. Interrupted requests are now rolled back cleanly, so a quote either submits fully or remains in its prior state.

Application Question Answers Carrying Forward to Renewal Terms (BC-21659)

On renewal terms, answers entered in Application Questions for a property could appear blank or show No answer provided. This affected policies where the property had been added by endorsement during the prior term. Completed answers now carry forward to the renewal term.

Lines Import Failing After an Item Form Was Changed (BC-21936)

When importing lines configuration, the import failed if a form in the package shared a title with an existing form but carried a different identifier, returning an error about conflicting names and identifiers. The import now completes in this situation, so configuration can be moved between sites after a form has been changed.

Updated Mortgagee Not Reflected on Related Claims (BC-21992)

On claims for policies set to pull the current mortgagee, changing the mortgagee on the policy did not update the mortgagee shown on the claim, and the labels indicating whether a mortgagee changed since the date of loss were missing. The claim continued to display the previous mortgagee. Claims now reflect the current mortgagee from the policy.

All Reinsurance Contracts Listed in the Edit Reinsurance Window (BC-22036)

When adding reinsurance contracts to a claim, the Edit Reinsurance window listed only the first 25 contracts, so carriers with more than 25 could not select the remaining ones. The window now lists every available reinsurance contract.

Pay by Card and Pay by ACH Options Missing on the Electronic Payment Page (BC-22166)

On the policy electronic payment page, the Pay by Card and Pay by ACH options did not appear for some policies until the payment schedule was toggled, and the processing fee message was missing as well. Both payment options and their fee details now display when the page first loads.

Policy Types Not Open to Quoting Appearing During Policy Creation (BC-22338)

When creating a new policy, the list of selectable policy types could include types that were not open to quoting, and in some states it included types carried over from earlier lines effective dates. The rule that determines which policy types may be offered now applies on every path that builds the list, so the options match the selected effective date and state.

Extra Quotes Added to Saved Report Parameter Defaults (BC-22494)

In SQL Editor reports, a numeric parameter saved with a default value was substituted at run time with an extra pair of single quotes, producing invalid SQL. Reports that ran successfully in interactive mode then failed in batch mode with only a generic failure status. Saved defaults now substitute as the value alone, so batch runs match interactive runs.

Property Save Failing on the Risks Screen (BC-22587)

On the Risks screen in the agent experience, selecting Save Property failed immediately with a property lookup error on some quotes. The failure occurred when the policy revision could not resolve its policy type, which could happen after a lines effective date was moved. Properties now save successfully from this screen.

Contact Edits on the Claim Parties Tab Changing the Contact Record (BC-22672)

In the claims experience, selecting Edit on the Parties tab allowed a contact's details to be changed, and those changes were written back to the contact record shared by every policy, claim, and agent that references it. Editing that record from the claim party dialog is now governed by its own permission, while claim level roles and party level fields stay editable. Social Security number and date of birth can also now be entered on a party whose contact record has them blank, which the dialog previously prevented.

Page Navigation in the Commission Payment Queue (BC-22679)

In the Commission Payment Queue, selecting page 2 from the page numbers showed an empty list and removed the pagination controls, leaving a page refresh as the only way to recover. Users can now move between pages using either the page numbers or the arrow controls, and the controls remain visible throughout.

Terminated Agencies Selectable in the Quote Flow (BC-22730)

In the quote flow, agents could see and select agencies they were not assigned to, including agencies that had been discontinued. The agency list now shows only the active agencies an agent is assigned to.

Approved Card Payments Missing From the Payment Log (BC-22859)

When a card payment was approved by the payment processor but the step that applies it to the account did not complete, the payment was stored without appearing anywhere in BriteCore, so an insured could be charged without any record staff could see. Such a payment is now saved in an incomplete state and appears in the Payment Log, making the charge visible for follow up.

Loss Address Selection Failing on Some Claims (BC-22920)

On some claims, selecting the loss address listed on the policy failed and returned a generic error in place of a readable message. The problem affected certain claims rather than all of them, which made it hard to an

Original source

New Features and Enhancements

AI Claims Summary added to Claims Record (BC-22294)

The Claims AI Copilot now generates a written summary of the claim on the claim itself, covering what happened and what has been done so far, and regenerates it as new activity is added. Getting oriented on a claim meant reading the full file, since the loss description, adjuster notes, exposures, and payment activity lived in separate places with no consolidated view.

AI Policy Summary added to Policy and Claims Record (BC-20789)

The AI Copilot now provides a written policy summary covering the insured, applicable coverages, limits, deductibles, and endorsements. The summary appears on the policy itself and in the claim section that describes the policy, so an adjuster can confirm coverage without leaving the claim. Previously, understanding what a policy covers meant reading through the declarations and coverage screens and manually assembling the picture.

Validation for Commission Adjustment Dates (BC-24397)

BriteCore added validation that rejects a period end date beyond the current month and a start date after the end date, preventing accidental future-dated commission entries. Prior to the change, the commission adjustment entry placed no upper bound on its period end date, so a future-dated or mistyped period could create a commission payable dated years away.

Payment Distribution Rules Settings and Automatic Application (BC-24375)

BriteCore added a Settings editor for these payment distribution rules, expanded the conditions they can match to include policy status, and now lets a matching rule apply automatically. Previously, rules for automatically handling overpayments and underpayments could previously only be edited as raw configuration, and the Daily Cash Receipt screen still sent every over- or underpayment for manual distribution even when a rule already covered it.

12-Hour Time Display for Claim Note Alerts (BC-24560)

The alert time now displays in 12-hour AM/PM format while still storing the time accurately, making alerts easier to set and read.

Audit Trail for Flag Changes on Policies, Claims, Contacts, and Properties (BC-24391)

BriteCore now writes a system note on each affected record whenever a flag changes, capturing who made the change and which record triggered the cascade. Before the change, the system did not record when a flag was set on a policy, claim, contact, or property, or how that flag cascaded to related records, so support could not tell who set a flag or why a related record became flagged.

Faster Notes Loading Across Policies, Claims, and Reports (BC-24541)

BriteCore added indexing and paged the query so it reads only what it returns. Notes now load quickly even on the largest accounts. Prior to the change, Notes lists retrieved the entire history for a record on every request instead of only the page being shown, which made notes pages slow to load on accounts with large note volumes.

Faster Quote to Bind Report Execution (BC-24658)

BriteCore added an index tuned to that lookup, and the reports now complete substantially faster. The Quote to Bind reports resolved the newest revision of each policy term with a query that re-sorted data for every candidate row, producing very long run times on large books that could exceed three hours.

Primary Property Available to Document Templates (BC-24241)

BriteCore exposed the primary property to the document context, so templates can reference the correct primary property.Document templates had no way to identify which property on a policy is the primary one, so forms defaulted to the oldest property and could render the wrong address on multi-property policies.

Additional Commission and Vendor Fields for Reporting (BC-23073)

BriteCore added the reason code and its related attribution fields to the commission reporting view and exposed a vendor integration reports view, so report authors can build these reports within the reporting layer. Custom reports written over the reporting layer could not access commission reason codes or the vendor integration report details needed for certain chargeback reports.

Injury Diagnosis Codes Available for Reporting (BC-23163)

BriteCore added a reporting view for injury diagnosis codes, making them available for custom reports. Diagnosis codes captured on claim injuries were stored but not exposed to reporting, so report authors could not report on them.

Legacy Policy Number Available to Dynamic Forms (BC-24454)

BriteCore exposed the legacy policy number for use in dynamic form mapping. The reporting layer could not access the legacy policy number, so it could not map it into dynamic forms.

E-Delivery Setting Available to Dynamic Forms (BC-24918)

The e-delivery enrollment setting was not available to the reporting layer, so dynamic forms could not use it to control content such as e-delivery consent language. BriteCore exposed the e-delivery setting for use in dynamic form mapping.

Written Premium Delta Available for Reporting (BC-24988)

Reports that needed the endorsement written-premium change could not obtain it from the reporting layer, because the revisions reporting view exposed every premium and fee column except that one. BriteCore added the written premium delta to the revisions reporting view, so reports can use it directly.

Correct Coverage Names Across Claim Reports (BC-24708)

Several claim reports labeled each row with a coverage chosen alphabetically rather than the coverage the claim or payment actually related to, so the reported coverage could be wrong. BriteCore corrected these reports to resolve the coverage from the claim's own items, so the coverage names are accurate.

Commission Statement Columns on the Agency Dashboard (BC-24257)

The agency-facing Commission Dashboard did not show several commission statement fields that were already available in the administrative view, such as policy term start and end dates and transaction type. BriteCore added these columns to the Agent Production Commissions table on the Agency Dashboard, so agency users see the same commission detail.

Bug Fixes

Complete Commission Totals for Ranges Spanning a Year or More (BC-24396)

When a commission date range covered twelve months or more, an error in the month calculation could drop up to twenty-three months of exported commission from the totals. BriteCore corrected the calculation so every month in the range is counted, and commission exports and reports now report the full amount for long date ranges.

Complete Multi-Year Commission Projections and Faster Agent Portal Listing (BC-24421)

Forward-looking commission projections that spanned more than one year could silently drop months that shared a calendar month with another year, and the agent portal's commission listing recalculated commissions once for every policy. BriteCore corrected the projection to track each year and month distinctly and reworked the listing to calculate all policies in a single pass. Multi-year projections are now complete and the agent portal listing loads faster.

Accurate Commission Statement Totals for Multi-Branch Agencies (BC-24385)

When an agency spanned more than one group branch, such as after a mid-period group change, each branch's commission statement printed the full agency-wide total instead of the total for that branch. BriteCore now scopes report and year-to-date totals to each agency and group branch, so every statement reflects only the amounts that belong to it.

Quote Report Links Open in a New Tab (BC-24742)

In the admin quote wizard, clicking a driver's Motor Vehicle Report or another attachment link navigated the entire window away to the attachment, removing the user from the quote with no way back. These report and attachment links now open in a new tab, so users stay in the quote while reviewing the document.

Multi-Rule Suspensions No Longer Hide Available Policy Types (BC-24614)

A suspension that combines conditions, such as a ZIP code together with a policy type, is meant to apply only where all of its conditions match, but the policy-type pickers in the agent experience and the quote wizard treated any single matching condition as a full suspension and hid policy types that should have remained available. BriteCore corrected the pickers to honor the combined conditions, so policy types are suppressed only where every condition of a suspension applies.

Valid Quotes No Longer Rejected by Mandatory Coverage Value Copying (BC-24429)

When the unified quote engine automatically added a mandatory coverage item, it copied an answer from any item sharing the same category name without checking the value was valid for the receiving item, and because category names are not unique across items, the borrowed value could fail validation and reject an otherwise valid quote. BriteCore now copies a value only when the receiving item accepts it, so these quotes rate successfully.

Mortgagees Remain Visible After Refreshing the Quote Wizard (BC-24488)

On the Mortgagees step of the quote wizard, mortgagees added to a policy disappeared from the step after a page refresh, showing none were added even though the data was retained. BriteCore now reloads the saved mortgagees on refresh, so they remain visible.

Billing Contact Validated Before Policy Number Assignment (BC-24699)

When committing a revision, the newer commit process assigned a policy number and marked the application before confirming that the term's billing contact was valid, which could advance the policy number sequence for a revision that then failed validation. BriteCore moved the billing contact check to the start of the commit, so a policy number is assigned only after validation passes.

Inland Flood Refresh Persists Only for the Current Address (BC-24559)

When a property address was saved, a deferred inland flood evaluation could run afterward and commit vendor results, or remove Inland Flood Coverage, for an address the property no longer had if a second address save landed in between. BriteCore now persists the inland flood refresh only when it still matches the property's current address.

Reduced Locking During Property Address Edits (BC-24552)

Editing a property's ZIP code held a database lock on the policy revision across an external geocoding call and a search index write, which could block other work on that revision. BriteCore deferred that write until the external calls complete, releasing the lock sooner and reducing contention during address edits.

State Changes Trigger an Inland Flood Coverage Refresh (BC-24538)

On accounts with multi-state properties enabled, changing only a property's state did not re-evaluate inland flood standing, so cached eligibility could keep an ineligible Inland Flood Coverage line item attached. BriteCore now treats a state change as an address change and refreshes inland flood coverage when the state is edited.

Duplicate County Prevention in Business Locations Settings (BC-24402)

The Business Locations settings screen and the county reload path allowed a state's county list to save with duplicate counties, colliding codes, or malformed identifiers, with no uniqueness validation, causing downstream data-integrity problems. BriteCore added validation, so counties save with unique names, codes, and identifiers, and stopped the tools that could create duplicate county records.

Location Numbers Renumber When a Building Group Is Removed (BC-24743)

With property grouping enabled, deleting the only building at a Location removed the group but left the higher Locations at their original numbers, leaving a permanent gap that carried into every later revision. BriteCore now renumbers the remaining Locations when a building group is removed, matching the behavior of the location-level delete.

A Stalled Renewal No Longer Halts the Nightly Renewal Batch (BC-24724)

During nightly renewal processing, a single policy whose eligibility check never returned could consume the entire time budget and abort the whole batch. BriteCore now isolates a stalled eligibility check and continues processing the remaining renewals, so one policy cannot stop the nightly run.

Cancellation Retry Recognizes the Term Where the Cancellation Landed (BC-24692)

When an immediate cancellation's effective date fell outside the requested term, the cancellation was recorded on the term containing that date, but a retry looked for the existing cancellation on the originally requested term and missed it, producing a user-facing error. BriteCore now checks for the canceled revision on the term where the cancellation actually landed, so retries are recognized.

Final Cancellation Completes for Policies in Cancellation Pending (BC-24685)

When a policy already had a committed Cancellation Pending revision with the same date and reason, a final cancellation treated the policy as already canceled and did nothing, leaving it stuck in Cancellation Pending with no canceled revision. BriteCore no longer treats a Cancellation Pending revision as proof of cancellation, so the final cancellation completes.

Reliable Default Primary Property Assignment Under Concurrent Edits (BC-24544)

When a revision had no primary property set, two simultaneous edits could each find the slot empty and both write to it, with the second overwriting the first while both reported success. BriteCore now fills the default primary property with a guarded update, so concurrent edits no longer conflict.

Location Deletion Works After Import When Property Grouping Is Disabled (BC-24551)

On accounts with property grouping disabled, importing a revision copied each property's group reference but did not recreate the matching group record on the new revision, leaving property references pointing at an older revision and causing location deletion to fail. BriteCore now remaps property groups on import, so location deletion works on the imported revision.

Payment Method Import Records the Correct Processing Integration (BC-24675)

When importing a stored payment method, BriteCore recorded the payment processor integration from the most recent unrestricted response rather than the one that owns the method, which could tie a payment method to the wrong processor. The import now records the owning integration, keeping stored payment methods bound to the processor that manages them.

Fallback Charges Blocked on Processor-Owned Payment Methods (BC-24674)

When no payment processor integration was connected, a charge could fall back to a default path that bypassed the ownership check, allowing a payment method tied to one processor to be charged through another. BriteCore now refuses that fallback charge for processor-owned payment methods, so charges run only through the processor that owns the method.

Pending Payment Approvals Bound to the Owning Integration (BC-24669)

The endpoints that approve or decline a pending payment validated the calling integration but did not confirm that it owned the payment being acted on, so one payment integration could approve or decline a payment belonging to another. BriteCore now binds each approval and decline to the integration that owns the payment.

Named Insureds With an Agency Role Can Select Their Own Payment Method (BC-24491)

When a contact both held an agency role and was the named insured on a policy, their own payment methods did not appear in the recurring and automatic payment options, because the contact was treated only as agency-billed. BriteCore now includes the contact's own payment methods in that case, so they can be selected for recurring and automatic payments.

Reinstatement From Cancellation Pending Updates Policy Status (BC-24272)

A policy that fully paid off a Cancellation Pending, Non-Payment balance could remain shown in that status even though the system logged that it had been reinstated, because the status was written to the account history without being saved to the policy. BriteCore restructured the reinstatement so the policy status is set to Active when the balance is cleared.

Pending Payment Settlement Listing Scoped to the Calling Integration (BC-24711)

The endpoint that lists pending payments for settlement validated the calling integration but then returned every pending payment on the account, so one payment processor could see another processor's pending payments. BriteCore now scopes the listing to the integration that made the request.

Committing a Due Cancellation Pending Revision No Longer Reactivates the Policy (BC-24697)

Committing an open revision on a policy in Cancellation Pending, Non-Payment whose cancellation date had already passed could silently return the policy to Active, clear its cancellation date, and re-bill it as an endorsement. BriteCore now keeps such a revision in its cancellation-pending status instead of reactivating and re-billing the policy.

Stored Payment Method Charges Restricted to the Owning Processor (BC-24671)

When two payment processors were connected, charging a stored payment method was delivered to every connected processor rather than only the one that owns the method, risking a double charge. BriteCore now restricts each charge to the processor that owns the payment method.

Correct Prorated Refund When Canceling Off a Pending Revision (BC-24656)

When a policy was canceled mid-term while its in-force revision was still in a pending state with no committed baseline, the cancellation rated with zero written premium and refunded the entire annual premium instead of the prorated unearned amount. BriteCore now includes the pending revision in rating history, so the cancellation returns only the correct prorated amount.

Billing Step No Longer Errors on an Unresolvable Payment Method (BC-24727)

The quote wizard billing step returned an application error when a billing contact had a saved payment method identifier that no longer pointed to a valid record. BriteCore now handles a missing payment method gracefully, so the billing step loads instead of erroring.

Payment Times Recorded for Third-Party Portal Payments (BC-24707)

Payments received through the third-party payment portal were recorded with a date but no time and defaulted to midnight, so on a day with a full cancellation, the payment could sort ahead of same-day cancellation entries in the account ledger. BriteCore now records the actual payment time, so these entries sort in the correct order.

Correct Due Date When Changing From Monthly to Escrow Billing (BC-24681)

Changing a term's billing schedule from Monthly to Escrow could generate a catch-up installment whose due date was copied from the last unpaid monthly invoice, placing it nearly a year out. BriteCore now uses the nearest upcoming unpaid due date for that catch-up invoice, so the due date is correct.

Payment Storage Failures Surface After an Integration Charge (BC-24668)

On the payment processor integration path, a charge that succeeded at the vendor still reported overall success even when saving the payment locally failed, so a completed charge could go unrecorded without any error. BriteCore now surfaces the storage failure after the charge, so the discrepancy is reported.

Convenience Fee Charged Once on Multi-Term Payments (BC-24461)

When a single card payment from a legacy processor was applied across two or more policy terms, the payment receipt stamped the convenience fee on each term and summed them, overstating the convenience fee total and the grand total. BriteCore now charges the convenience fee once per payment on these receipts, so the totals are correct.

Claim Note Alert Dates Saved to the Correct Calendar Day (BC-24313)

In the Add Alert and Edit Alert dialog under Claims Notes, the selected date was converted to universal time before saving, so a user working in the evening in a time zone behind universal time could store an alert dated one day later than the date shown. BriteCore now saves the alert using the local calendar day shown in the picker.

Correct Values When Editing a Claim Note Alert (BC-24312)

In the Claims Notes Edit Alert dialog, the field that loads an existing alert was tied to a shared value rather than to the alert being edited, which could cause it to populate from the wrong source. BriteCore bound the dialog to the specific alert being edited, so it now shows the correct existing values.

Claim Payment Dates Stored on the Correct Day to Keep Reserves Editable (BC-24141)

Claim payment and recovery dates were stored one calendar day ahead of the local entry date, so after an evening payment the claim could reject reserve and exposure edits with a date-ordering error until the clock caught up. BriteCore now stores claim payment dates on the local calendar day, so reserves and exposures remain editable.

Declaration Generation Handles Encrypted Policy Form Documents (BC-24352)

Declaration package generation could fail while processing certain policy form documents because it did not decrypt encrypted form files before merging them. BriteCore now decrypts policy form documents before merging them, so declaration packages generate successfully.

Preserved Credit Score Applied on Endorsement Rating (BC-24703)

On an effective-date endorsement, rating could fall back to a default credit tier even when the policy term already held a valid credit score, because one rating path read a separate first-revision credit lookup that found no report. BriteCore now falls back to the preserved term credit score on that path, so endorsements rate with the credit score already on the term.

Quote Rate Cleared Correctly When Re-Rating Is Needed (BC-24643)

A quote with an annual premium but no written premium wasn't cleared when its rate should have reset, so it kept appearing as rated in the quote wizard. BriteCore aligned the reset to the same premium value the wizard uses to determine rated status, so quotes reset and re-rate as expected.

Readable Audit Notes for Integration Policy Type Changes (BC-24611)

When an integration instance's assigned policy types changed, the Settings audit note listed the entire before and after sets as raw identifiers, often thousands of characters, without naming the instance or showing what actually changed. BriteCore rewrote the note to identify the instance and show only the policy types added and removed, making the change easy to read.

Calculated Selection No Longer Flags a Term Credit Score as Manual (BC-24564)

Choosing the calculated option in the Term Credit Score prompt still marked the term's credit score as manually updated, which pinned the score and prevented it from recalculating. BriteCore now clears the manual flag when the calculated option is chosen, so the term uses its calculated credit score.

Automatic Credit Refetch Restored in the Auto Quote Wizard (BC-24641)

In the Auto Quote Wizard, the automatic credit-score refetch that should run after a named insured is edited had stopped firing because it read a field name that was no longer provided. BriteCore corrected the field name, so the credit score refetches automatically after a named insured change.

Commercial Flood Eligibility Handles Multiple Locations in One Request (BC-24598)

Commercial flood eligibility checks batch properties into groups, and when a single request returned more than one location, an indexing error stopped the check. BriteCore corrected how it matches responses to properties, so eligibility completes when multiple locations are returned together.

Flood Eligibility Cache Refreshes a Stale Property Record (BC-24575)

When a property qualified to carry forward previously retrieved flood eligibility but already had a stored eligibility record whose address key no longer matched, the stale record was left in place, so every later check missed the cache and repeated the lookup. BriteCore now updates the stored eligibility record in that case, so the cached result is reused.

Flood Vendor Reauthorizes After an Expired Token (BC-24574)

When the flood eligibility vendor rejected an expired or invalid authorization token, the logic meant to refresh the token and retry never executed, so the request simply failed. BriteCore made the token refresh and retry reachable, so an expired vendor token is renewed and the request retried automatically.

Credit Tier Lookup No Longer Overwrites a Historical Term's Score (BC-24563)

A credit tier lookup meant only to read data could, under certain conditions, save a credit score onto a policy term, and for a committed revision on an older term it could overwrite that term's historical credit score with a later term's value. BriteCore changed the lookup so it no longer persists credit scores, leaving historical term scores intact.

Agency Validated Before a Credit Report Is Ordered (BC-24702)

On the unified quote path, a billable credit report could be ordered before the quote's agency was validated, so the wrong agency could be billed for the credit pull. BriteCore now resolves and validates the agency before ordering the credit report, so the correct agency is billed.

City Selection for Multi-City ZIP Codes Across Contact Screens (BC-24296)

For a ZIP code that maps to more than one city, the city selection list appeared only on the quote New Contact screen, while adding an additional interest or editing an existing contact card offered no usable city choice. BriteCore now presents the full city list wherever such an address is entered or edited, so the correct city can be chosen consistently.

Primary and Non-Primary Property Rules Re-Evaluate When the Primary Changes (BC-24184)

On an endorsement, changing which property is primary, including when deleting the primary property promoted another, did not re-run rules scoped to primary or non-primary properties, so line items from the previous primary remained. BriteCore now re-evaluates property-scoped rules whenever the primary property changes, so added and removed line items reflect the current primary.

Motor Vehicle Report Prefill No Longer Drops a Driver's Violations (BC-24925)

When several drivers' Motor Vehicle Reports returned at nearly the same time during prefill, one driver's result could be dropped while that driver was still marked complete, causing an empty report with no violations to be saved and then reused for the driver on later quotes for the full validity window. As a result, violations the vendor actually returned could be missing from rating. BriteCore corrected the prefill so every driver's result is captured before the reports are stored, so returned violations are recorded and used in rating.

Property Details Step Loads in All Quote Wizard Configurations (BC-24929)

A recent addition of the property rail to the Property Details step could leave that step blank in quote wizard configurations that use a customized property section, because the customization replaced the shared section without the new bindings and stopped the page from rendering. BriteCore moved the shared Property Details behavior into a common component that every configuration loads, so the Property Details step renders correctly everywhere.

Removed Coverage No Longer Appears on Future Documents (BC-23549)

After an endorsement removed a coverage, the removed coverage's form could continue to print on the Declaration and appear in later revisions and reports. BriteCore corrected the endorsement so a removed coverage is fully cleared, and it no longer appears on documents or in future revisions.

Correct Coverage on the Claims Payments Report (BC-23980)

The Claims Payments report labeled every payment on a claim with the same coverage, chosen alphabetically, instead of the coverage each payment was made against, so payments across different coverages all showed one coverage name. BriteCore corrected the report to show the coverage associated with each payment.

Correct Payor for Mortgagee-Billed Policies on the Declaration (BC-24271)

On policies where a mortgagee is the billing contact, a document field was not populated, so the Declaration's mortgagee section printed the Payor as No even though the mortgagee was the billing recipient. BriteCore now populates that field, so the Declaration shows the correct Payor.

Renewals No Longer Fail on Certain Rate Configurations (BC-24424)

Some policies could not be renewed and failed immediately with an error, because a circular reference in the property rate chain caused the renewal to abort. BriteCore added a guard for that condition, so these renewals complete.

Coverage Re-Added by a Rule Is No Longer Dropped on Quotes (BC-24452)

On quotes run through the unified quote engine, a coverage that a rule removed and then re-added, such as Ordinance or Law, could be dropped, leaving it off the quote and understating the premium. BriteCore corrected the rule processing to honor a re-add after a removal, so the coverage and its premium are included.

Faster Claim Document Preview in the Template Studio (BC-24610)

Loading a claim document for preview in the template studio was very slow, taking well over a minute on some accounts, because the underlying query scanned every claim on the account before filtering to one. BriteCore rewrote that query to resolve a single claim directly, so claim document previews load quickly.

Report Creation Succeeds for New Report Types on New Accounts (BC-24970)

Creating a certain new report type on an account that had no existing reports could fail because a category value was sent under a misspelled key, so the report was not created. BriteCore corrected the field name, so these reports are created successfully.

Login Loop Resolved for Usernames With Special Characters (BC-25006)

After a recent authentication change, users whose usernames contained certain special characters or a space could sign in and pass verification but then be returned to the login page in a loop, locking them out. BriteCore corrected the handling of those usernames, so affected users can log in.

Original source

New Features and Enhancements

Claims Summary in the Claims AI Copilot (BC-22294)

Getting oriented on a claim meant reading the full file, since the loss description, adjuster notes, exposures, and payment activity lived in separate places with no consolidated view. The Claims AI Copilot now generates a written summary of the claim on the claim itself, covering what happened and what has been done so far, and regenerates it as new activity is added.

Policy Summary in the AI Copilot (BC-20789)

Understanding what a policy covers meant reading through the declarations and coverage screens and assembling the picture manually. The AI Copilot now provides a written policy summary covering the insured, applicable coverages, limits, deductibles, and endorsements. The summary appears on the policy itself and in the claim section that describes the policy, so an adjuster can confirm coverage without leaving the claim.

Validation for Commission Adjustment Dates (BC-24397)

The commission adjustment entry placed no upper bound on its period end date, so a future-dated or mistyped period could create a commission payable dated years away. BriteCore added validation that rejects a period end beyond the current month and a start date later than the end date, preventing accidental future-dated commission entries.

Payment Distribution Rules Settings and Automatic Application (BC-24375)

Rules for automatically handling overpayments and underpayments could previously only be edited as raw configuration, and the Daily Cash Receipt screen still sent every over- or underpayment for manual distribution even when a rule already covered it. BriteCore added a Settings editor for these payment distribution rules, expanded the conditions they can match to include policy status, and now lets a matching rule apply automatically.

12-Hour Time Display for Claim Note Alerts (BC-24560)

The Add Alert and Edit Alert dialogs under Claims Notes were the last place in the product that captured time in 24-hour format. The alert time now displays in 12-hour AM/PM format while still storing the time accurately, making alerts easier to set and read.

Audit Trail for Flag Changes on Policies, Claims, Contacts, and Properties (BC-24391)

Setting a flag on a policy, claim, contact, or property, and the way that flag cascades to related records, was not recorded anywhere, so support could not tell who set a flag or why a related record became flagged. BriteCore now writes a system note on each affected record whenever a flag changes, capturing who made the change and which record triggered the cascade.

Faster Notes Loading Across Policies, Claims, and Reports (BC-24541)

Notes lists retrieved the entire history for a record on every request instead of only the page being shown, which made notes pages slow to load on accounts with large note volumes. BriteCore added indexing and paged the query so it reads only what it returns. Notes now load quickly even on the largest accounts.

Faster Quote to Bind Report Execution (BC-24658)

The Quote to Bind reports resolved the newest revision of each policy term with a query that re-sorted data for every candidate row, producing very long run times on large books that could exceed three hours. BriteCore added an index tuned to that lookup, and the reports now complete substantially faster.

Bug Fixes

Complete Commission Totals for Ranges Spanning a Year or More (BC-24396)

When a commission date range covered twelve months or more, an error in the month calculation could drop up to twenty-three months of exported commission from the totals. BriteCore corrected the calculation so every month in the range is counted, and commission exports and reports now report the full amount for long date ranges.

Complete Multi-Year Commission Projections and Faster Agent Portal Listing (BC-24421)

Forward-looking commission projections that spanned more than one year could silently drop months that shared a calendar month with another year, and the agent portal's commission listing recalculated commissions once for every policy. BriteCore corrected the projection to track each year and month distinctly and reworked the listing to calculate all policies in a single pass. Multi-year projections are now complete and the agent portal listing loads faster.

Accurate Commission Statement Totals for Multi-Branch Agencies (BC-24385)

When an agency spanned more than one group branch, such as after a mid-period group change, each branch's commission statement printed the full agency-wide total instead of the total for that branch. BriteCore now scopes report and year-to-date totals to each agency and group branch, so every statement reflects only the amounts that belong to it.

Quote Report Links Open in a New Tab (BC-24742)

In the admin quote wizard, clicking a driver's Motor Vehicle Report or another attachment link navigated the entire window away to the attachment, removing the user from the quote with no way back. These report and attachment links now open in a new tab, so users stay in the quote while reviewing the document.

Multi-Rule Suspensions No Longer Hide Available Policy Types (BC-24614)

A suspension that combines conditions, such as a ZIP code together with a policy type, is meant to apply only where all of its conditions match, but the policy-type pickers in the agent experience and the quote wizard treated any single matching condition as a full suspension and hid policy types that should have remained available. BriteCore corrected the pickers to honor the combined conditions, so policy types are suppressed only where every condition of a suspension applies.

Valid Quotes No Longer Rejected by Mandatory Coverage Value Copying (BC-24429)

When the unified quote engine automatically added a mandatory coverage item, it copied an answer from any item sharing the same category name without checking the value was valid for the receiving item, and because category names are not unique across items, the borrowed value could fail validation and reject an otherwise valid quote. BriteCore now copies a value only when the receiving item accepts it, so these quotes rate successfully.

Mortgagees Remain Visible After Refreshing the Quote Wizard (BC-24488)

On the Mortgagees step of the quote wizard, mortgagees added to a policy disappeared from the step after a page refresh, showing none were added even though the data was retained. BriteCore now reloads the saved mortgagees on refresh, so they remain visible.

Billing Contact Validated Before Policy Number Assignment (BC-24699)

When committing a revision, the newer commit process assigned a policy number and marked the application before confirming that the term's billing contact was valid, which could advance the policy number sequence for a revision that then failed validation. BriteCore moved the billing contact check to the start of the commit, so a policy number is assigned only after validation passes.

Inland Flood Refresh Persists Only for the Current Address (BC-24559)

When a property address was saved, a deferred inland flood evaluation could run afterward and commit vendor results, or remove Inland Flood Coverage, for an address the property no longer had if a second address save landed in between. BriteCore now persists the inland flood refresh only when it still matches the property's current address.

Reduced Locking During Property Address Edits (BC-24552)

Editing a property's ZIP code held a database lock on the policy revision across an external geocoding call and a search index write, which could block other work on that revision. BriteCore deferred that write until the external calls complete, releasing the lock sooner and reducing contention during address edits.

State Changes Trigger an Inland Flood Coverage Refresh (BC-24538)

On accounts with multi-state properties enabled, changing only a property's state did not re-evaluate inland flood standing, so cached eligibility could keep an ineligible Inland Flood Coverage line item attached. BriteCore now treats a state change as an address change and refreshes inland flood coverage when the state is edited.

Duplicate County Prevention in Business Locations Settings (BC-24402)

The Business Locations settings screen and the county reload path allowed a state's county list to save with duplicate counties, colliding codes, or malformed identifiers, with no uniqueness validation, causing downstream data-integrity problems. BriteCore added validation, so counties save with unique names, codes, and identifiers, and stopped the tools that could create duplicate county records.

Location Numbers Renumber When a Building Group Is Removed (BC-24743)

With property grouping enabled, deleting the only building at a Location removed the group but left the higher Locations at their original numbers, leaving a permanent gap that carried into every later revision. BriteCore now renumbers the remaining Locations when a building group is removed, matching the behavior of the location-level delete.

A Stalled Renewal No Longer Halts the Nightly Renewal Batch (BC-24724)

During nightly renewal processing, a single policy whose eligibility check never returned could consume the entire time budget and abort the whole batch. BriteCore now isolates a stalled eligibility check and continues processing the remaining renewals, so one policy cannot stop the nightly run.

Cancellation Retry Recognizes the Term Where the Cancellation Landed (BC-24692)

When an immediate cancellation's effective date fell outside the requested term, the cancellation was recorded on the term containing that date, but a retry looked for the existing cancellation on the originally requested term and missed it, producing a user-facing error. BriteCore now checks for the canceled revision on the term where the cancellation actually landed, so retries are recognized.

Final Cancellation Completes for Policies in Cancellation Pending (BC-24685)

When a policy already had a committed Cancellation Pending revision with the same date and reason, a final cancellation treated the policy as already canceled and did nothing, leaving it stuck in Cancellation Pending with no canceled revision. BriteCore no longer treats a Cancellation Pending revision as proof of cancellation, so the final cancellation completes.

Reliable Default Primary Property Assignment Under Concurrent Edits (BC-24544)

When a revision had no primary property set, two simultaneous edits could each find the slot empty and both write to it, with the second overwriting the first while both reported success. BriteCore now fills the default primary property with a guarded update, so concurrent edits no longer conflict.

Location Deletion Works After Import When Property Grouping Is Disabled (BC-24551)

On accounts with property grouping disabled, importing a revision copied each property's group reference but did not recreate the matching group record on the new revision, leaving property references pointing at an older revision and causing location deletion to fail. BriteCore now remaps property groups on import, so location deletion works on the imported revision.

Payment Method Import Records the Correct Processing Integration (BC-24675)

When importing a stored payment method, BriteCore recorded the payment processor integration from the most recent unrestricted response rather than the one that owns the method, which could tie a payment method to the wrong processor. The import now records the owning integration, keeping stored payment methods bound to the processor that manages them.

Fallback Charges Blocked on Processor-Owned Payment Methods (BC-24674)

When no payment processor integration was connected, a charge could fall back to a default path that bypassed the ownership check, allowing a payment method tied to one processor to be charged through another. BriteCore now refuses that fallback charge for processor-owned payment methods, so charges run only through the processor that owns the method.

Pending Payment Approvals Bound to the Owning Integration (BC-24669)

The endpoints that approve or decline a pending payment validated the calling integration but did not confirm that it owned the payment being acted on, so one payment integration could approve or decline a payment belonging to another. BriteCore now binds each approval and decline to the integration that owns the payment.

Named Insureds With an Agency Role Can Select Their Own Payment Method (BC-24491)

When a contact both held an agency role and was the named insured on a policy, their own payment methods did not appear in the recurring and automatic payment options, because the contact was treated only as agency-billed. BriteCore now includes the contact's own payment methods in that case, so they can be selected for recurring and automatic payments.

Reinstatement From Cancellation Pending Updates Policy Status (BC-24272)

A policy that fully paid off a Cancellation Pending, Non-Payment balance could remain shown in that status even though the system logged that it had been reinstated, because the status was written to the account history without being saved to the policy. BriteCore restructured the reinstatement so the policy status is set to Active when the balance is cleared.

Pending Payment Settlement Listing Scoped to the Calling Integration (BC-24711)

The endpoint that lists pending payments for settlement validated the calling integration but then returned every pending payment on the account, so one payment processor could see another processor's pending payments. BriteCore now scopes the listing to the integration that made the request.

Committing a Due Cancellation Pending Revision No Longer Reactivates the Policy (BC-24697)

Committing an open revision on a policy in Cancellation Pending, Non-Payment whose cancellation date had already passed could silently return the policy to Active, clear its cancellation date, and re-bill it as an endorsement. BriteCore now keeps such a revision in its cancellation-pending status instead of reactivating and re-billing the policy.

Stored Payment Method Charges Restricted to the Owning Processor (BC-24671)

When two payment processors were connected, charging a stored payment method was delivered to every connected processor rather than only the one that owns the method, risking a double charge. BriteCore now restricts each charge to the processor that owns the payment method.

Correct Prorated Refund When Canceling Off a Pending Revision (BC-24656)

When a policy was canceled mid-term while its in-force revision was still in a pending state with no committed baseline, the cancellation rated with zero written premium and refunded the entire annual premium instead of the prorated unearned amount. BriteCore now includes the pending revision in rating history, so the cancellation returns only the correct prorated amount.

Billing Step No Longer Errors on an Unresolvable Payment Method (BC-24727)

The quote wizard billing step returned an application error when a billing contact had a saved payment method identifier that no longer pointed to a valid record. BriteCore now handles a missing payment method gracefully, so the billing step loads instead of erroring.

Payment Times Recorded for Third-Party Portal Payments (BC-24707)

Payments received through the third-party payment portal were recorded with a date but no time and defaulted to midnight, so on a day with a full cancellation, the payment could sort ahead of same-day cancellation entries in the account ledger. BriteCore now records the actual payment time, so these entries sort in the correct order.

Correct Due Date When Changing From Monthly to Escrow Billing (BC-24681)

Changing a term's billing schedule from Monthly to Escrow could generate a catch-up installment whose due date was copied from the last unpaid monthly invoice, placing it nearly a year out. BriteCore now uses the nearest upcoming unpaid due date for that catch-up invoice, so the due date is correct.

Payment Storage Failures Surface After an Integration Charge (BC-24668)

On the payment processor integration path, a charge that succeeded at the vendor still reported overall success even when saving the payment locally failed, so a completed charge could go unrecorded without any error. BriteCore now surfaces the storage failure after the charge, so the discrepancy is reported.

Convenience Fee Charged Once on Multi-Term Payments (BC-24461)

When a single card payment from a legacy processor was applied across two or more policy terms, the payment receipt stamped the convenience fee on each term and summed them, overstating the convenience fee total and the grand total. BriteCore now charges the convenience fee once per payment on these receipts, so the totals are correct.

Claim Note Alert Dates Saved to the Correct Calendar Day (BC-24313)

In the Add Alert and Edit Alert dialog under Claims Notes, the selected date was converted to universal time before saving, so a user working in the evening in a time zone behind universal time could store an alert dated one day later than the date shown. BriteCore now saves the alert using the local calendar day shown in the picker.

Correct Values When Editing a Claim Note Alert (BC-24312)

In the Claims Notes Edit Alert dialog, the field that loads an existing alert was tied to a shared value rather than to the alert being edited, which could cause it to populate from the wrong source. BriteCore bound the dialog to the specific alert being edited, so it now shows the correct existing values.

Claim Payment Dates Stored on the Correct Day to Keep Reserves Editable (BC-24141)

Claim payment and recovery dates were stored one calendar day ahead of the local entry date, so after an evening payment the claim could reject reserve and exposure edits with a date-ordering error until the clock caught up. BriteCore now stores claim payment dates on the local calendar day, so reserves and exposures remain editable.

Declaration Generation Handles Encrypted Policy Form Documents (BC-24352)

Declaration package generation could fail while processing certain policy form documents because it did not decrypt encrypted form files before merging them. BriteCore now decrypts policy form documents before merging them, so declaration packages generate successfully.

Preserved Credit Score Applied on Endorsement Rating (BC-24703)

On an effective-date endorsement, rating could fall back to a default credit tier even when the policy term already held a valid credit score, because one rating path read a separate first-revision credit lookup that found no report. BriteCore now falls back to the preserved term credit score on that path, so endorsements rate with the credit score already on the term.

Quote Rate Cleared Correctly When Re-Rating Is Needed (BC-24643)

A quote with an annual premium but no written premium wasn't cleared when its rate should have reset, so it kept appearing as rated in the quote wizard. BriteCore aligned the reset to the same premium value the wizard uses to determine rated status, so quotes reset and re-rate as expected.

Readable Audit Notes for Integration Policy Type Changes (BC-24611)

When an integration instance's assigned policy types changed, the Settings audit note listed the entire before and after sets as raw identifiers, often thousands of characters, without naming the instance or showing what actually changed. BriteCore rewrote the note to identify the instance and show only the policy types added and removed, making the change easy to read.

Calculated Selection No Longer Flags a Term Credit Score as Manual (BC-24564)

Choosing the calculated option in the Term Credit Score prompt still marked the term's credit score as manually updated, which pinned the score and prevented it from recalculating. BriteCore now clears the manual flag when the calculated option is chosen, so the term uses its calculated credit score.

Automatic Credit Refetch Restored in the Auto Quote Wizard (BC-24641)

In the Auto Quote Wizard, the automatic credit-score refetch that should run after a named insured is edited had stopped firing because it read a field name that was no longer provided. BriteCore corrected the field name, so the credit score refetches automatically after a named insured change.

Commercial Flood Eligibility Handles Multiple Locations in One Request (BC-24598)

Commercial flood eligibility checks batch properties into groups, and when a single request returned more than one location, an indexing error stopped the check. BriteCore corrected how it matches responses to properties, so eligibility completes when multiple locations are returned together.

Flood Eligibility Cache Refreshes a Stale Property Record (BC-24575)

When a property qualified to carry forward previously retrieved flood eligibility but already had a stored eligibility record whose address key no longer matched, the stale record was left in place, so every later check missed the cache and repeated the lookup. BriteCore now updates the stored eligibility record in that case, so the cached result is reused.

Flood Vendor Reauthorizes After an Expired Token (BC-24574)

When the flood eligibility vendor rejected an expired or invalid authorization token, the logic meant to refresh the token and retry never executed, so the request simply failed. BriteCore made the token refresh and retry reachable, so an expired vendor token is renewed and the request retried automatically.

Credit Tier Lookup No Longer Overwrites a Historical Term's Score (BC-24563)

A credit tier lookup meant only to read data could, under certain conditions, save a credit score onto a policy term, and for a committed revision on an older term it could overwrite that term's historical credit score with a later term's value. BriteCore changed the lookup so it no longer persists credit scores, leaving historical term scores intact.

Agency Validated Before a Credit Report Is Ordered (BC-24702)

On the unified quote path, a billable credit report could be ordered before the quote's agency was validated, so the wrong agency could be billed for the credit pull. BriteCore now resolves and validates the agency before ordering the credit report, so the correct agency is billed.

City Selection for Multi-City ZIP Codes Across Contact Screens (BC-24296)

For a ZIP code that maps to more than one city, the city selection list appeared only on the quote New Contact screen, while adding an additional interest or editing an existing contact card offered no usable city choice. BriteCore now presents the full city list wherever such an address is entered or edited, so the correct city can be chosen consistently.

Primary and Non-Primary Property Rules Re-Evaluate When the Primary Changes (BC-24184)

On an endorsement, changing which property is primary, including when deleting the primary property promoted another, did not re-run rules scoped to primary or non-primary properties, so line items from the previous primary remained. BriteCore now re-evaluates property-scoped rules whenever the primary property changes, so added and removed line items reflect the current primary.

Motor Vehicle Report Prefill No Longer Drops a Driver's Violations (BC-24925)

When several drivers' Motor Vehicle Reports returned at nearly the same time during prefill, one driver's result could be dropped while that driver was still marked complete, causing an empty report with no violations to be saved and then reused for the driver on later quotes for the full validity window. As a result, violations the vendor actually returned could be missing from rating. BriteCore corrected the prefill so every driver's result is captured before the reports are stored, so returned violations are recorded and used in rating.

Property Details Step Loads in All Quote Wizard Configurations (BC-24929)

A recent addition of the property rail to the Property Details step could leave that step blank in quote wizard configurations that use a customized property section, because the customization replaced the shared section without the new bindings and stopped the page from rendering. BriteCore moved the shared Property Details behavior into a common component that every configuration loads, so the Property Details step renders correctly everywhere.

Original source

New Features and Enhancements

Claim Payments Require a Payee Address (BC-21819)

Adding a payment on the Exposures tab of a claim now requires that the claim payee has an address, enforced both in the payment dialog and on the server. Payment options can also be configured directly in Settings under Claims instead of through advanced settings.

Premium Records Rebuilt as a Live Premium History (BC-22798)

The Premium Records view on the Accounts Receivable page is rebuilt as an event-based premium history per policy term, opened as an in-page modal like the Installment Schedule. The view now reads live data, resolving an issue where earned premium was not displaying, and no longer requires navigating to a separate page.

PGP Encryption for SFTP Report Exports (BC-22894)

Report exports delivered by SFTP can now be encrypted with PGP before transmission. Carriers enable encryption on an SFTP export configuration and provide the recipient's public key, which BriteCore validates; the recipient's private key is never requested or stored. When encryption is enabled, only the encrypted file is sent, and if encryption fails the report is not transmitted unencrypted. This allows report deliveries to meet recipient security requirements without any manual encryption step.

Speed Limit and Actual Speed Captured From Motor Vehicle Reports (BC-23040)

Motor vehicle report violations now capture the posted speed limit and the driver's actual speed, in addition to the existing excess speed value. These fields are available to the rating engine for custom evaluations, supporting state point calculations that key off exact speeds.

Commission Adjustments Without a Source Transaction (BC-23072)

The commission adjustment API endpoint now accepts adjustments that are not tied to a source accounting transaction. Callers can supply the agency, agent, amount, statement period, and an optional reason code directly, which supports chargebacks, corrections, and bonuses that are not tied to an existing commission row.

Non-Policy Adjustments on Commission Statement PDFs (BC-23074)

Commission statement PDFs now include a dedicated section for adjustments that are not tied to a specific policy, such as chargebacks, corrections, and bonuses. The entries are grouped by reason code so agencies can see every adjustment on the statement they already receive.

Administrator Queue View With Task Lifecycle Buckets (BC-23218)

The underwriting task queue now has an administrator view with Active, On Hold, and Archived buckets. The bucket selector is visible to the administrator role only, giving managers a lifecycle view of the queue while underwriters keep their focused view.

Bulk Task Selection and Updates in the Task Queue (BC-23219)

The underwriting task queue now supports bulk operations. Users can select every task under a policy with one checkbox in By Policy mode, and can mark tasks for review or archive them in bulk. Each affected task still emits its own event so downstream tracking stays accurate.

Task Queue Export Downloads the Current View (BC-23220)

The task queue's Export action now downloads a CSV of exactly what the user is viewing. The file reflects the active tab, status chips, search term, filters, and sort order, and includes every matching task rather than only the current page.

Multi-Driver Vehicle Assignment (BC-23595)

The fixed two-driver model on vehicles is replaced with support for one primary driver plus any number of additional drivers, and zero-driver vehicles are now valid for policy types that allow them. Driver position, experience, and count are exposed to the rate chain and rules so carriers can apply position-based rating factors.

Suspensions Handle Policy Types With Effective-Date Gaps (BC-23673)

When setting up a Suspension, the list of offered policy types now respects the selected start date for policy types whose definitions have gaps between effective-date versions. Enforcement uses the same logic, so the correct policies are suspended.

SQL Report Runs Resume From Completed Sheets on Retry (BC-23937)

Multi-sheet SQL reports are now more reliable on retry. Previously, a transient failure on a later sheet restarted the entire report from the first sheet, repeating hours of finished work and sometimes exceeding the run time limit. Completed sheets are now checkpointed, so a retry resumes with only the sheets that have not finished.

Company Letterhead Data for Custom Deliverables (BC-24279)

Custom document templates can now pull a shared company letterhead block from the revision data. Templates draw the carrier's name, letterhead lines, address, phone, and email from one consistent source, along with a revision-scoped list of Notice deliverables.

Bug Fixes

Quote Wizard Rating for Lines Without Top-Level Exposure Items (BC-21937)

In the quote wizard, lines whose primary exposure items all live under sub-lines showed Premium Not Applicable on the Risks step and offered no Rate Location option. Locations on these lines can now be rated in the wizard.

Declaration Generation Reliability During Straight-Through Processing (BC-22828)

Declaration generation during Straight-Through Processing (STP) issuance was hardened. Database contention during inline document generation could previously leave a zero-size document. The generation step now retries safely and rolls back cleanly, preventing empty Declarations.

Shared Deductible Updates Apply to All Related Deductibles (BC-23550)

In the quote wizard, updating the main shared deductible did not update the other related deductibles, and those deductibles could not be changed manually either. Related deductibles now stay in sync when the shared deductible changes.

Faster Agency Resolution for Motor Vehicle Report Requests (BC-23642)

The driving-records prefill integration resolved a quote's agency information with a redundant and expensive contact lookup that ran on every quote. That lookup was removed, and test coverage was added around this path to protect the behavior going forward.

Address Suggestions Without Entering a ZIP Code First (BC-23764)

The Smarty address pre-fill behavior is now consistent across quote flows. On the Homeowners agent flow, address suggestions previously appeared only after the ZIP code was entered, while the Auto flow suggested addresses immediately. Suggestions now appear consistently without requiring the ZIP code first.

Faster Policy List Loading and Agency Saves (BC-23793)

Two policy operations were slow: the policy list page could take up to 48 seconds to load its filter options, and saving an agency or contact on a policy could take up to 12 seconds. Both were reworked to avoid the underlying expensive queries, so the policy list and agency assignment now respond in seconds.

Duplicate Address Dialogs in the Multi-Property Quote Wizard (BC-23824)

In the Multi-Property Quote Wizard, the Edit button on a property's address gave no loading feedback while the property details loaded, so any extra clicks during that wait each opened another stacked dialog. The button now shows when it is working and opens a single dialog per click.

Repeated Field-Review Warning in the Multi-Property Quote Wizard (BC-23825)

On the Questions page of the Multi-Property Quote Wizard, the prompt asking users to double-check a field appeared once for every property on the quote. It now appears a single time, removing the duplicate messages.

Billing Details Withheld for Non-Payable Policies (BC-23940)

Privacy controls on policyholder-facing billing endpoints were strengthened. Policies that are not currently payable no longer return account balance, payoff amount, or billing schedule details through the public payment gateway.

Declaration Generation for Additional Insured Items With Multiple Supplemental Groups (BC-24041)

Declaration generation failed for policies containing Additional Insured line items with three or more supplemental question groups. The document build aborted with an internal error and left an empty Declaration folder on the policy. These Declarations now render correctly.

Excel Report Runs No Longer Fail on Legacy Sheet Names (BC-24042)

Reports saved before sheet-name validation was introduced could fail every Excel run because a stored sheet name was too long or contained characters Excel does not allow. Invalid legacy sheet names are now sanitized at run time so these reports generate successfully.

Commission Adjustment Retries No Longer Create Duplicates (BC-24044)

A commission adjustment could report failure to the caller after the adjustment row had already been saved, because a later step such as PDF statement generation failed, and a retry then silently created a duplicate adjustment. The save sequence was corrected so the reported result matches what was actually recorded.

Catastrophe Assignment With Automatic Loss Cause Fill (BC-24046)

Assigning a catastrophe to a claim could fail when the automatic loss cause fill counted duplicate loss causes toward the maximum allowed per claim, and a misleading success note was written even though the catastrophe was never saved. Duplicates are now removed before the limit check, a true overflow returns a clear error, and the update note is written only after the save succeeds.

Return Premium Export Endpoint Enforces Export Guards (BC-24101)

The return premium export API endpoint bypassed the safeguards enforced elsewhere in the export path. It now checks whether a return premium was already exported and honors voided status, preventing repeat exports and duplicate check numbers.

Return Premium Generation Covers Every Credit-Bearing Term (BC-24103)

When a policy had multiple terms carrying credit balances, the automated return premium process could consider only one arbitrary term per policy on each run. Every eligible term is now handled, so return premiums are generated without waiting for additional runs.

Return Premium Reconciliation Detects Missing Markers (BC-24104)

The return premium reconciliation check silently skipped policies with no export markers at all, so a completely missing accounting marker was reported as an all-clear instead of a discrepancy. The check now detects these policies.

Concurrent Return Premium Runs No Longer Duplicate Credits (BC-24105)

Two overlapping automated runs could each generate a return premium for the same credit balance, producing duplicates. Return premium creation is now protected against concurrent runs.

Return Premium Batch Authorization Is Now All-or-Nothing (BC-24108)

Authorizing a batch of return premiums could partially apply and then report total failure, leaving some records authorized while the caller was told nothing happened. Authorization is now all-or-nothing: either every eligible record in the batch is applied or none are.

Umbrella Policy Data Sync on First-Revision Imports (BC-24114)

The sync that copies underlying policy data for umbrella policies silently failed when a revision had no prior revision, which is common during bulk revision imports. The sync now runs correctly for first revisions.

Excess Speed Preserved When Reusing a Valid Motor Vehicle Report (BC-24122)

Copying a driver's still-valid motor vehicle report onto a new quote silently dropped the excess speed value from each violation. The copied violations now carry excess speed, so rating factors that depend on it evaluate correctly.

Export Date Stamped on Return Premium Exports (BC-24126)

The return premium export marked records as exported and wrote the accounting marker but never stamped the export date. The date is now recorded, keeping export tracking consistent.

First Category in a Rate Chain Step Now Rates Correctly (BC-24131)

The first category in a rate-chain categories step silently lost its line item reference, causing any quote for that policy type to fail rating with an unclear error. The reference is now preserved regardless of the category's position.

Generate Last Month's Report Button Reliability (BC-24140)

Two issues affected the Generate Last Month's Report button in the Mutual Boiler Reinsurance section of Policies and Processing: a stale background job record could block the button permanently, and no confirmation appeared when a report was queued. The stale guard is now cleared correctly, and users see a message confirming the report is running in the background with an email to follow.

Date Functions in Advanced Rule Triggers (BC-24152)

Advanced trigger and Advanced effect code that called common date functions failed with an internal error that aborted the entire rules run for the quote or revision. Rules using these date functions now evaluate correctly.

All Violation Fields Preserved When Reusing a Motor Vehicle Report (BC-24158)

Following the earlier excess speed fix, the remaining nine violation fields that were silently dropped when a driver's still-valid motor vehicle report was copied onto a new quote have been corrected. Copied violations now carry the complete set of fields returned by the original report.

Empty Sidebar Row Removed From the Mobile Menu (BC-24159)

The desktop sub-navigation toggle appeared in the mobile slide-out sidebar as a blank row that did nothing. The control is now hidden on small screens, where the mobile sub-navigation already provides its own toggle.

Sub-Line Underwriting Rule Triggers Evaluate All Conditions (BC-24212)

Underwriting rules with triggers on a sub-line silently dropped a failing trigger condition instead of blocking the rule, effectively turning AND conditions into OR conditions, so a rule could fire even when one of its conditions was not met. All trigger conditions are now enforced.

ImageRight Uploads Continue Past Rejected Files (BC-24255)

A single file rejected by the ImageRight vendor aborted the rest of the nightly upload, and the same permanent error was retried every night. A rejected file is now recorded and skipped so the remaining files upload, and permanent rejections are no longer endlessly retried.

Orbipay Upload Failures Now Raise an Alert (BC-24256)

A failure in the nightly Orbipay file upload was silently swallowed, allowing the export to fail repeatedly without any notification. Upload failures now raise an alert so they can be investigated promptly.

Return Premium Records Returned Newest First (BC-24277)

The policy export API endpoint returned a policy's return premium records in an arbitrary order, so integrations reading the first record could pick up an old refund amount. The records are now returned newest first, giving integrators a reliable ordering.

Installment Statement Print Dates After Reinstatement With a Fee (BC-24287)

Reinstating a policy with a reinstatement fee stamped every future installment billing statement with the reinstatement date instead of each statement's scheduled print date, and could create duplicates. Future installment statements now keep their scheduled dates.

Editing Additional Interests Created Before the Unified Save Path (BC-24288)

Editing and saving an existing policy-level Additional Interest was blocked by an address-type validation error on the linked contact, even though the contact showed no missing data. Additional Interests created before the unified save path can now be edited and saved normally.

Refunds Reflected When Re-Rating a Term (BC-24303)

A refund issued through the Refund Support Tool was invisible when the term was later re-rated, leaving future installments under-billed by exactly the refunded amount with no invoice behind it. The refunded amount is now billed back so installments cover the full balance.

Payment Amount Precision for Authorize.net Transactions (BC-24311)

Payments submitted with an existing payment method could be sent to Authorize.net with excessive decimal precision, causing the processor to reject the transaction. Payment amounts are now rounded to standard currency precision before being sent.

Commission Adjustment Performance at Scale (BC-24333)

Creating a commission adjustment recalculated commissions for the entire book of business, which could exhaust memory and fail on sites with large books. Adjustments now calculate only what they need, so they complete reliably regardless of book size.

Agency-Scoped Commission Statement Runs Stay Scoped (BC-24334)

A commission statement run scoped to a single agency also produced statements for unrelated agencies, because the current and future month projection calculated across the whole book of business instead of the requested agency. Scoped runs now generate statements only for that agency.

Erroneous Policy Notes From Underwriting Rules (BC-24356)

Underwriting rules wrote notes to a policy stating that an agent added or deleted coverages when the agent had only navigated between tabs. These system-generated notes no longer appear when no actual change was made.

Billing State History Link Styling (BC-24360)

The Billing State History link in the policy header now matches the Show Revision History link, using the same typography, color, hover, and focus treatment. Its permissions and behavior are unchanged.

Faster Response for Missing Policy Attachments (BC-24381)

Requesting a policy attachment whose stored file was missing took over 30 seconds to return a not-found response because the lookup retried with exponential backoff. Missing files now fail fast, so the interface responds promptly.

Original source

New Features and Enhancements

SQL Editor Terms of Service Sign Off (BC-17418)

Every SQL Editor user is prompted to accept a Terms of Service acknowledgment before running queries. Acceptance is recorded per user so the prompt does not reappear on subsequent sessions until the Terms of Service is updated.

State Field on the Policy Search Screen (BC-20666)

The policy and claims search screen now includes State as a filter, allowing staff to narrow results by the policy’s geographic U.S. state without exporting or scripting the query.

Commission Adjustment Reason Codes (BC-23071)

The commission accounting data now includes a reason-code column, and a new Commission Adjustment Reasons quick code was seeded with Correction, Bonus, and Chargeback so adjustments can be categorized consistently for reporting.

ICD Per Injury Diagnosis Code Persistence (BC-23161)

Injury diagnosis codes selected on a claim exposure are now persisted per injury rather than only at the claim level, enabling more precise medical coding on multi-injury claims. Available in Vendor Integrations.

Grouped Location and Building Display on Legacy Property Screens (BC-23388)

BriteCore now groups Locations and Buildings on the legacy property screen, matching the agent experience to maintain parity between both screens.

Group aware Add and delete functions on Location and Buildings on Legacy Property Screens (BC-23389)/(BC-23390)

Users on the legacy Property tab and Risks step can now add or delete a Location or add a Building directly, with group-aware controls that maintain parity between the screens.

Duplicate Address Detection Across Locations (BC-23391)

The legart that supports quick correction while still allowing intentional duplicates when needed.

Validation Error Rule Applied to Every Vehicle and Property (BC-23650)

A Validation Error rule effect now applies to every vehicle or property on a quote, rather than only the last one processed, so multi-risk quotes surface every applicable validation error at once.

Secured Online Payment Guard for Unsubmitted Policies (BC-23771)

The Secured Online Payment page now rejects payment attempts on Unsubmitted policies, closing a gap where a payment could be applied before the policy was in a state to accept it.

Get Policy Type Forms Now Traverses Sublines (BC-23854)

The get_policy_type_forms endpoint now returns forms attached to line items nested under sublines, matching the visible form layout in the administrative interface.

XactAnalysis Missing Information and Cross Dataset Rules (BC-23756)

The XactAnalysis integration now sends missing information updates back to the vendor and applies rules across the vendor's other datasets, keeping records synchronized when a claim is updated after the initial send.

Expanded Lifecycle Notice Configuration for Underwriting Cancellations and Non-Renewals (BC-23888)

Lifecycle notice settings now support configurable periods of up to 180 days for underwriting-related cancellations and non-renewals.

Improved Non STP Quote Submission Performance (BC-23706)

Quote submissions that fall out of straight-through processing now dispatch to the background worker queue, improving submission response time on complex quotes that require review.

Bug Fixes

Property Valuation Review Workflow Reset on Revaluation (BC-23914)

When a property is revalued after underwriting approval, the review workflow state is now reset so that the revised valuation goes through review rather than binding on the previously approved verdict.

Rejected and Ineligible Policies Included in Contact Policy Lookup (BC-23723)

The policies lookup now includes Rejected and Ineligible policies attached to a contact, so downstream integrations no longer see empty results for a contact whose only policy was declined.

Property Grouping Structural Improvements Across Legacy screens (BC-23890)

The Suspensions map now loads on the legacy property screens alongside the grouped Location and Building presentation, closing a gap where the map did not appear on affected policies.

360Value RCV Update Rating and STP State Refresh (BC-23711)

A 360Value replacement cost update now refreshes the rating and STP state on the associated policy, resolving the second half of the earlier fix so downstream review and rating reflect the returned replacement cost.

Retrieve Tasks Sort Stability and Filter Correctness (BC-22723)

The retrieve_tasks endpoint now uses a stable sort order and correctly applies the due-date filter, fixing pagination inconsistencies and preventing rows from being silently dropped.

Quote Wizard TigerCQ Rating Errors (BC-22626)

Errors surfaced by the TigerCQ integration inside the Quote Wizard were resolved, so quotes involving the affected integration can complete without the previous vendor error interrupting the wizard.

Policy Term ERP Item Display (BC-22684)

Extended Reporting Period items on a policy term are now displayed correctly, restoring visibility on carriers that offer ERP coverage on affected lines.

Legal Entity Type Selection for Organization Contacts (BC-22876)

Organization contacts now support a Legal Entity Type selector including LLC, S Corp, C Corp, Sole Proprietor, Trust, and Estate, replacing the free-form entry that previously required cleanup for reporting.

Attachment Preview After Upload (BC-22919)

Uploaded attachments now render in the preview panel immediately after upload, resolving cases where users had to refresh the page to see a document they had just added.

Guard Against Time Based SQL Functions in Query Validation (BC-23624)

The validate_and_execute_query path now rejects time-based SQL functions such as SLEEP and BENCHMARK, removing a read pattern that could negatively impact reporting performance.

Claim Status Change Configuration Loading (BC-23635)

A configuration lookup failure that prevented claim status changes on certain claims was resolved. The workflow service now initializes with the expected configuration and status changes complete as expected.

Claims Processing Page Item Amounts (BC-23636)

The Claims Processing page no longer raises a type error when a claim has no item amounts. The page now renders and remains usable in that state.

Retrieve Tasks Pagination Lower Bound Validation (BC-23681)

The retrieve_tasks endpoint now validates that page size is greater than zero, preventing an unbounded response when a caller passes zero for the page size.

Policy Wizard Organization Lookup by Tax ID (BC-23718)

The policy wizard organization contact lookup now searches by Tax ID or FEIN, and no longer incorrectly searches by Social Security Number or restricts matches to individual contacts. Organization duplicate detection now works as expected.

Additional Interests Save on the Classic Policy Information Tab (BC-23987)

BriteCore resolved a regression that prevented saving a mandatory Additional Interest from the classic Policy Information tab because of a hidden validation list. The save flow now succeeds as expected.

Report Status Export Column Display (BC-23790)

The Export column on the Report Status page now displays the correct export state instead of a placeholder, so users can identify at a glance which report runs have exports available.

ADP Report Company Code Update (BC-23745)

A carrier-specific Automatic Data Processing (ADP) report was updated to use the correct Company Code required by ADP, restoring successful ingestion of the report by the vendor.

EZLynx and BriteQuote Intake Phone Number Handling for Co Applicants (BC-23794)

The intake path from the EZLynx and BriteQuote integrations was rejecting quotes when a co-applicant had no phone number, because of an ungated validation change. Phone-number validation is now gated correctly and the intake accepts these quotes.

InsVista S3 Prefix Directory Creation (BC-23768)

InsVista vendor writes now succeed when their S3 prefix does not yet exist. The prefixes for InsVista uploads and deliverable zip files are now created on demand.

Unified Quote Engine Performance (BC-23769)

New write-free quote pipeline and the generate_quote and get_quote_schema API endpoints are now available. Legacy quote endpoints are flag-gated and routed to the unified engine, producing consistently faster quote generation and reducing database write load.

Payment Eligibility Pending Status Match Precision (BC-23831)

Payment eligibility logic that checked for a Pending status no longer also matches Pending E-Signature. The two statuses are now distinguished, so payment eligibility is only granted when the payment itself is pending.

Public Save Billing Schedule Validation and Secure Checkout Visibility (BC-23868)

The public saveBillingSchedule endpoint now validates the schedule it accepts, and Secure Checkout no longer displays unpaid invoices to visitors who are not eligible to pay. Both paths now enforce their respective access rules.

Closed County Quote and Policy Suspension on the Rating Path (BC-23872)

Suspensions for closed counties are now enforced on the rating path, closing a gap where a quote or policy could still rate successfully in a county that had been closed for new business.

Payment Transfers from the Payment Log Now Work Reliably (BC-23893)

We've resolved a bug that could cause payment transfers to fail. When using the Transfer button in the Payment Log to move a payment to another policy, the action could return an error and leave the payment on the original policy. Transfers now complete as expected and are recorded on both policies.

Get Claim Photos and Coverages by Claim Number (BC-23907)

Calling get_claim by claim number now returns the correct photos and coverages, resolving a case where the response was built from an empty claim ID and produced unrelated data.

Reinsurance LAE Amounts on the Recoveries Summary (BC-23910)

The Recoveries Summary on the merged Accounting tab now includes reinsurance Loss Adjustment Expense recovered and expected amounts, closing a gap where those figures were absent from the summary.

Refused New Business Signature Type Persistence (BC-23938)

A new business bind that is refused no longer persists a signature type on the revision. Refused binds now leave the signature-type field clean, so downstream re-quotes do not carry a stale value.

Payment Transfer Duplicate Key on Integration Instance (BC-23915)

Payment transfers that carry an integrationInstanceId no longer fail with a duplicate-key error. The transfer now proceeds and the integration reference is recorded once.

SQL Copilot Copy to Editor Button Availability (BC-23941)

The Copy to Editor button in SQL Copilot now appears on generated SQL responses, restoring the one-click path from a copilot suggestion into the SQL Editor.

BriteQuote Risk Builder Read Only Field Icon Alignment (BC-23983)

The information icon on read-only rating fields in the BriteQuote risk builder no longer overlaps the field label. Read-only fields now render with correct spacing.

Report Copilot Britedata Translation Openpyxl Error (BC-23800)

The openpyxl engine error that could interrupt a Report Copilot Britedata translation was resolved, so translations complete successfully.

Nightly Settle Batch Vendor TSR Failures (BC-23767)

Three distinct per-vendor Transaction Settlement Report failures that caused the nightly settle-batch cron to fail on certain configurations were resolved. The nightly job now completes without the SafetyNet retries that previously masked the underlying issues.

NOT INCLUDED - INTERNAL

Mock Credit Report Organization Save Error (BC-23500)

Saving an Organization while the End-to-End Mock Credit Report flow was active no longer fails, restoring the ability to create organizations during a mock-credit-report review.

Billing Engine Core and Billing State History Viewer (BC-22417)

BriteCore addressed the initial rollout gaps in the Billing Engine core and the Billing State History viewer, along with follow-up hardening identified in code review, so the engine now produces the state history expected by billing reviewers.

Concurrent Policy Creation Deadlock on Revisions Contacts (BC-23678)

Concurrent policy creation no longer deadlocks on the placeholder row in the internal revisions contacts table. Simultaneous new-business creates now proceed without blocking each other.

NOT INCLUDED - AI

MCP Test Identity Selection Across Permission Scopes (BC-23560)

The BriteCore MCP now supports testing as identities other than the Okta-authenticated administrator, so reviewers can exercise the MCP under different permission scopes.

Rules Copilot Simulation of a Newly Created Rule (BC-21195)

After creating a rule in Rules Copilot, users can now simulate the rule against representative policies from the same session, confirming behavior before publishing.

Underwriting Workbench Tasks Module (BC-22855)

A new Underwriting module was introduced with a dedicated Tasks tab, giving underwriters a purpose-built workspace to triage and act on assigned work rather than mixing tasks into general dashboards.

Templates Copilot Resolves Allowed Item Names on Context Change (BC-23119)

Templates Copilot now re-resolves the list of allowed item names when the policy, policy type, or location changes mid-session, so suggestions match the currently selected context.

MCP Tool Descriptions Clarified for Routing and Error Behavior (BC-23408)

Tool descriptions on the public MCP surface were revised to document error behavior, defaults, and routing distinctions across all tools, so external integrators can select the right tool without trial and error.

Lines Copilot Subline Duplication on New Item Creation (BC-22991)

When Lines Copilot creates new line items under a specific subline, the resulting build no longer contains duplicate sublines. A single subline now holds all items created against it.

Lines Copilot Policy Wide Lookup on Line Items (BC-22995)

Copilot-created line items that reference a policy-wide or property-wide line (for example, Inflation Guard) now correctly apply that lookup during rating, resolving cases where the reference silently did not take effect.

Report Copilot Out of Token Fallback Message (BC-23871)

Report Copilot now shows a clearer fallback message when a response is truncated because of a token limit, so users understand why the reply stopped and what to try next.

Policy Copilot Credit Score Category Only (BC-23444)

The Policy Copilot summary now displays only the credit score category rather than the raw score, aligning the summary with underwriting privacy requirements.

Claims Copilot Line of Business and Party Scoped Insights (BC-23449)

Claims Copilot insights are now scoped to the relevant line of business and to the parties involved in the claim, so insights no longer fire for unrelated lines or for non-parties on the claim.

Claims Copilot Summary User Interface Refinement (BC-23526)

The Claims Copilot summary was cleaned up to remove a redundant heading area, giving the AI-generated summary more room and reducing visual clutter on the claim overview.

SQL Editor Plan Only Query Analysis (BC-23544)

A new preview_sql_plan API endpoint returns a plan-only analysis of a SQL Editor report, allowing users to inspect the query plan without executing the query. This is useful for spotting expensive scans before running a long report.

Quote Copilot Number Input Categories and User Input Rate Tables (BC-23626)

Quote Copilot now supports Number Input categories and User Input factor and rate tables, enabling copilot-authored quotes on more of BriteCore's rating primitives.

Remove Automatic Generation of Claims and Policy Copilot Summaries (BC-23795)

Claims and Policy Copilot summaries and insights are no longer generated automatically. Users now trigger generation on demand, reducing background AI cost and giving users control over when a summary is refreshed.

MCP Boundary Error Handling and JSON RPC Compliance (BC-23400)

Error responses on the MCP boundary now use consistent, typed envelopes that conform to JSON-RPC and no longer leak validation internals, giving integrated tools a stable error contract.

Public MCP Quote Wizard Tools (BC-23826)

The public MCP surface now exposes Quote Wizard tools, allowing external tooling and integrations to progress a quote through the Quote Wizard flow programmatically.

Promote Subjectivity Definitions (BC-22393)

BriteCore resolved an issue that prevented promoting Subjectivity definitions between environments, allowing subjectivities to move through the standard promotion flow with other configuration.

Original source

New Features and Enhancements

Claim Vehicle and Party Details in Custom Claim Documents (BC-22897)

Claims staff can now generate custom claim correspondence with vehicle and party details filled in automatically. Full claim detail vehicle year, make, model and VIN, location of loss, owner and driver, lien holder, and whether the vehicle is first- or third-party is now available to claim document templates, alongside a unified view of everyone involved in the claim. A document can now prompt the adjuster for the specifics it needs at the moment of generation: a dropdown lets them select which vehicle or party the letter concerns, populated live from the actual claim file, and free-text fields capture anything that varies letter to letter. The adjuster selects once, and the finished document reflects their selection throughout. Templates without inputs generate immediately as before, and carriers configure all of this in Dynamic Document Studio with a preview that shows the finished result before the template goes live.

SOV API Integration for Commercial Property Quoting (BC-21471)

Carriers writing commercial property can now send Statement of Values submissions from their external SOV system directly into BriteCore, where they arrive as fully-formed quotes with locations and buildings intact. This removes the need to manually re-key spreadsheets into the system. Because SOV is the source of truth for commercial property, this eliminates the single biggest bottleneck in commercial quoting: submissions that used to require hours of manual entry with real risk of transcription errors now land in BriteCore in one step. The integration handles large schedules without timing out, preserves the property grouping structure defined in the SOV so buildings stay organized as intended, and can optionally apply underwriting rules as the quote is created so the resulting quote is clean and consistent. Agency lookup is more forgiving as well, resolving the correct agency from a partial agency number. Every new capability is opt-in and backward compatible, so carriers already using the quote API see no change until they choose to adopt it.

Claim Numbers Removed From LexisNexis Results (BC-23676)

BriteCore updated how results from the LexisNexis integration are displayed so that claim numbers are no longer viewable to agents. Previously, these identifiers were surfaced unnecessarily. Limiting the returned data keeps vendor results to only what is needed.

Revision Dropdown Selector for Faster Navigation (BC-20876)

Navigating between policy revisions previously required moving one revision at a time with the arrow controls, and each step triggered a full page load that could take many seconds on large policies. A dropdown jump menu was added between the navigation arrows, grouped by policy term and with deep-link support and a Go to Current Revision option. Underwriters can now jump directly to any revision, making review of policies with many revisions much faster.

Report Export and Import API Endpoints (BC-20905)

Reports previously could not be moved programmatically between environments. New API endpoints allow reports to be exported and imported while preserving their format and data integrity. This streamlines the management and migration of reports across environments.

Dynamic Dropdown, Text, and HTML Fields for Custom Policy Deliverables (BC-23713)

BriteCore added support for dynamic dropdown, text, and HTML fields in custom policy deliverables. Previously, these deliverables offered a more limited set of configurable field types. Template authors now have greater flexibility when building custom policy documents.

Agency Sweep Processing Enhancements (BC-23641)

Performance has been improved for the Agency Sweep Queue and Agent Payments screens. Agencies with larger sweep queues will now experience significantly faster loading and refresh times when viewing queued payments, adding payments, or submitting a sweep. This enhancement reduces delays and provides a smoother, more responsive workflow without requiring any configuration changes.

Uploading Loss-History Files in Test Environments (BC-23622)

BriteCore now allows loss-history (Comprehensive Loss Underwriting Exchange) files to be uploaded in test environments, which originally prevented validation of the LexisNexis integration outside of production. Support for these uploads in test environments was added. Carriers can now validate the integration before enabling it in production.

Collapsible Forms and Documents Section in Lines Configuration (BC-23597)

The Forms and Documents section in Lines configuration is now collapsible and collapsed by default, reducing clutter on the configuration screen.

Disclosure and Proof-of-Authorization Capture for Saved Payment Methods (BC-16104)

When using Stripe, BriteCore now captures a provable record of authorization whenever an agent saves a policyholder's payment method for future use, alongside the carrier's configurable disclosure. Previously, the disclosure was displayed, but no auditable proof of consent was retained. Carriers now have a queryable authorization trail covering the disclosure text shown, timestamp, policyholder, and attesting agent.

Rename payment "Receipt" to "Payment Confirmation" and make receipt actions non-conditional (BC-23463)

Payment receipts have been renamed to Payment Confirmation to more accurately reflect what the document represents. Because the document is generated immediately after a payment is authorized, before funds have settled, and because ACH payments can later be returned, it now confirms the policyholder's payment authorization rather than receipt of settled funds. To align with this change, Download and Email actions are now available immediately after authorization instead of only after completed payments. The internal Daily Cash Receipt report is unaffected, and documents that were generated previously retain their original title.

Bug Fixes

Policy Type Item API Preserves Rate Configuration on Partial Updates (BC-23542)

BriteCore identified and resolved an issue where partial updates through the modify policy type item API endpoint wiped rate-chain references and factor-table limits that were not part of the request. Integrations making targeted updates could unintentionally clear rate configuration. Partial updates now preserve all untouched rate-chain and factor-table settings.

Accurate Payment Status on the Electronic Payment Report (BC-23602)

BriteCore resolved an issue where the Electronic Payment Report displayed a spurious status for bank-transfer (ACH) payments processed through the payment processor. The status shown did not reflect the payment's actual state. The report now derives and displays accurate payment status.

Payments and Voids Blocked on Closed Claims (BC-18581)

BriteCore identified and resolved an issue where a closed claim still showed misleading messages when a user attempted to make or void a payment: a void appeared to succeed, and a payment returned a Failed to Fetch Payment Methods error. Payment and void actions are now correctly blocked on closed claims. This prevents invalid financial actions and confusing messaging on claims that are already closed.

Supplemental Question Answers Save Correctly in Quote Wizard (BC-23509)

BriteCore resolved an issue in Quote Wizard where a supplemental question answer appeared selected in the interface but was saved as empty, which blocked application submission. Answer selections now persist correctly. Applications that include supplemental questions can now be submitted without interruption.

Policy Overview Sub-Navigation Menu Toggles Correctly (BC-23601)

BriteCore resolved an issue where the menu control on the Policy Overview sub-navigation bar did not open or close when selected. The toggle now works as expected. Users can once again expand and collapse the sub-navigation menu.

Support Ticket Submission Restored (BC-23553)

BriteCore identified and resolved an issue that prevented users from submitting a request through the Submit a Support Ticket flow. The flow now works as expected. Users can submit support tickets successfully.

Month End Close Package Report No Longer Duplicates Rows (BC-22739)

BriteCore identified and resolved an issue where duplicate agent entries on a policy revision caused duplicate rows across all sheets of the Month End Close Package report. The underlying agent assignment was made idempotent, existing duplicate entries were removed, and the report queries now de-duplicate defensively. Month-end reporting no longer double-counts affected policies.

SQL Editor Parameter Defaults Save and Preview Correctly (BC-23366)

BriteCore resolved an issue in the SQL Editor where static enumeration and string parameter default values were stored already quoted, causing them to be double-quoted on save and breaking preview and save. Parameter default handling was corrected. Enumeration and string parameter defaults now save and preview correctly.

SQL Editor Run Query Handles Failed and Timed-Out Queries Cleanly (BC-23473)

BriteCore resolved an issue in the SQL Editor where the Run Query spinner would never stop if a preview request failed, and where a query that reached the time limit was retried unnecessarily, doubling the wait. Failure handling and retry logic were corrected. The editor now stops cleanly on failure and avoids redundant retries.

Scheduled Report File Transfers Restored (BC-23516, BC-23620)

BriteCore identified and resolved an issue where scheduled report deliveries over secure file transfer failed for all affected carriers because an outdated transfer library could not negotiate the required host-key algorithm. The transfer library and its negotiation were upgraded. Scheduled secure file transfers now complete successfully.

Correct Value in the Report Status Export Column (BC-23790)

BriteCore resolved an issue where the Status column in a report's exported output showed an incorrect value. The export now reflects the correct status. Exported report data now matches what is shown in the application.

Return Premium Processing Handles a Missing Underwriting Contact (BC-23638)

Users can now edit and process Return Premiums without encountering a generic application error when a policy contains incomplete underwriter contact information. The Mail To list has also been improved to automatically exclude blank or invalid contacts, resulting in a cleaner and more reliable user experience. No configuration changes or user action are required.

Correct Premium Reported on Non-Renewal Ivans Downloads (BC-23709)

BriteCore identified and resolved an issue where non-renewal transactions reported the full-term premium as the premium change amount in agency-management downloads, causing downstream systems to double-count premium. The premium-change calculation for non-renewals was corrected. Downstream agency-management systems now record the correct premium.

Original source

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