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.
