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.