Enhancements
STP Enhancements
BriteCore continues to expand Straight-Through Processing (STP), giving carriers full control to configure and manage their own rules directly in the existing underwriting rules user interface. With these updates, you can now create UI-based STP rules for New Business and Renewals, define more precise conditions with advanced triggers tied directly to rating variables, and see clear error messaging with severity levels when rules fail. All STP results are stored in a unified location for reporting and traceability, and errors are scoped by policy vs. risk so underwriters can quickly identify where action is needed. Together, these changes make it easier to configure automation yourself, without custom code, while giving underwriters greater clarity when handling exceptions.
These enhancements benefit carriers by aligning rules with the same logic that drives pricing and reduces reliance on engineering teams for rule changes. They also make underwriting reviews faster and easier by providing actionable error details, ensuring results are fully traceable, and helping underwriters quickly resolve issues across multiple risks.
Visit our Help Site article for step-by-step guidance on configuring STP rules and reviewing results.
LexisNexis NCF reason codes stored for scoring and letters (BC-18910)
BriteCore added structured support for capturing up to five reason codes from the National Credit File integration, preserving their order of significance. This enhancement ensures consistent storage of codes and descriptions for audit purposes and letter generation, and is particularly important for communicating adverse action decisions.
SSH Key Support for Vendor Integrations (BC-18693)
The Vendor Integrations uploader has been enhanced to support SSH key authentication for SFTP connections, replacing the previous username/password-only approach. A new Uploader via Vendor Integrations option is available under Settings, allowing carriers to configure secure file transfers with SSH keys. In addition, the system can now POST to a designated URL with file details, streamlining integration workflows. This enhancement strengthens security and flexibility across all vendor integrations that rely on SFTP.
Allow updating a rating grid (BC-17667)
BriteCore now permits replacing an existing rating grid by uploading a newer version that shares the same effective dates (LED). During interpolation, the newer grid version will be used so rating outcomes reflect the most up-to-date factors without changing LEDs. This improvement streamlines rating updates by avoiding one-off date adjustments when only minor factor values are changed. It also reduces friction for operational teams who manage grids iteratively.
Defects
Correcting alignment of report list option to hide reports (BC-19301)
BriteCore corrected the alignment of the “hide this report” eyeball symbol to improve visibility and maintain consistency with established UI standards within the BriteCore Platform. The “Hidden Reports” capability supports systematic cleanup of reports by allowing teams to hide reports that are no longer needed. When a hidden report is not needed moving forward, please submit a ticket to BriteCore in order to delete the unneeded report(s).
Hidden reports filter not working when set to yes (BC-18949)
BriteCore corrected an issue where the “Hidden Reports” filter on the report list page option did not consistently display and hide reports in the report list. The fix replaces the previous filter with a clear include/exclude control that better reflects carrier intent. As the control is a toggle, no counts are provided anymore. The hidden reports feature is designed to support the systematic cleanup of reports. Carriers can initially hide reports that they suspect are unnecessary, and when those reports go unused over time, they can be permanently removed with confidence.
Documents not rendering properly in deliverables (BC-19421)
Document previews and PDFs (Quote Summary, Policy Application, Declaration) sometimes failed to generate and the related administrative alert emails didn’t go out. This occurred when changing the effective date triggered an upgrade to a newer quote version, which hid certain underwriting questions. As a result, downstream processes encountered missing data they were expecting in the original structure. Britecore has updated the process to always include defaults for hidden or not-applicable sections and to handle missing answers gracefully. With this change, documents should generate reliably again and the administrative alert emails should be sent as expected.
Property Inspection Request for Bees360 Added to Issuance Flow Rules (BC-19360)
A rule action for requesting property inspection via Bees360 was not available in the issuance portion of the rules engine UI. When setting up the rule, administrators can now select Event Type as the module scope, and the Request Property Inspection option will correctly appear as an available effect. This update ensures that property inspections can be properly triggered within underwriting rules, improving compliance and workflow accuracy.
Policy renewals report failures rectified (BC-19135)
BriteCore resolved a failure that caused job errors and incomplete output in the policy renewals report. The issue was traced to a naming conflict between a worksheet and a generated cover sheet, which disrupted report assembly in certain conditions. BriteCore renamed the conflicting artifacts and added collision handling so customized names no longer break report generation. The fix does not change report content or filtering logic, only the way the workbook is built.
Melissa not populating rating fields in Quote Wizard (BC-19123)
Melissa returned valid results but the Quote Wizard did not reflect the values in rating fields. BriteCore corrected the mapping so returned fields were properly stored and surfaced on the user interface without requiring a page refresh. The change removes a gap that could affect automated decision-making and related validations.
Post-issue subjectivity could not be satisfied (BC-18894)
BriteCore fixed a defect that prevented post-issue subjectivities from being updated after commitment. The fix allowed authorized users to mark subjectivities as satisfied, waived, or unsatisfied regardless of the revision’s committed state. We added a confirmation warning when changing an already satisfied or waived item back to unsatisfied to prevent unintended policy impacts. This improves administrative flexibility while ensuring users are made aware of the consequences of reversing prior decisions.
Losses incurred report showed incorrect negative totals (BC-18862)
BriteCore corrected an issue where the “Losses Incurred” report could display incorrect negative totals in rare timing conditions. Investigation identified a race in claim reserve updates when multiple changes occurred on the same claim in rapid succession. The fix required a per-claim request serialization for reserve updates so each computation used the most recent committed values. Users now see accurate incurred totals.
Eliminate effective date deletion error (BC-19050)
BriteCore resolved an issue that previously prevented users from successfully deleting the latest effective date. The fix introduces stronger validations and improved sequencing to ensure dependent configurations are handled gracefully, avoiding system errors. To enhance the user experience, a clear success message is now displayed upon deletion, reducing ambiguity and providing confirmation of the action.
Correct commission calculation for non‑commissionable items (BC-19044)
BriteCore addressed a defect where commission calculations incorrectly included items that were configured to be excluded, such as certain taxes and fees. The correction aligned the commission engine with account receivable calculations so non‑commissionable amounts no longer inflated commission totals. This change ensures that percentage‑based commissions apply only to the intended premium base, improving billing accuracy.
Renewal processing retried after an anticipated MVR error (BC-18641)
The renewal process has been updated to handle invalid driver’s license scenarios correctly. Previously, when an MVR (Motor Vehicle Report) failed due to a rejected license, the system would continue retrying the renewal on subsequent days. With this fix, the renewal now fails immediately after the first MVR error, preventing repeated unsuccessful attempts. In such cases, the policy must be manually renewed once the license information is corrected, ensuring accuracy and reducing unnecessary processing.
Write-off premium default amount was incorrect (BC-18597)
For some clients, the Write Off Premium pop-up for policies has been corrected to display the proper trailing balance in the Amount to Write Off field. Previously, this field showed incorrect values, leading to confusion and incorrect write-off amounts. With this fix, the system now consistently populates the field with the accurate trailing balance, ensuring write-offs are calculated and applied correctly.
The transfer payment tool did not execute and surfaced no actionable feedback (BC-18352)
The Transfer button within the Return Premium screen has been updated to properly handle scenarios where a payment is transferred to a policy without a named insured. Previously, initiating this action provided no feedback, leaving the user uncertain about the outcome. With this fix, the system now clearly displays an error message when such a transfer is attempted, ensuring transparency and preventing incomplete payment transfers. .
Fix SQL Editor confirmation on empty editor (BC-19055)
BriteCore removed an unnecessary navigation warning from the SQL Editor when no content was present. Previously, users were prompted to confirm leaving the page even in the absence of edits. The enhancement improves clean/dirty state detection so that prompts only appear when unsaved changes exist.