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.