Enhancements
Create a Save/Restore method for Dashboard Customization (BC-14672)
BriteCore’s persona-based dashboards have a significant level of customization possible, with sorting, filtering, and the ability to create a personalized view for each user.
Now these personalizations can be saved. To save a customized dashboard, click on the gear icon in the upper right corner of any dashboard and give the saved setting a name. This dialog also allows for the deletion of saved settings and the setting of a default mode for that dashboard screen.
Now all of your personalized setups can be protected and carried forward.
Enhance Dashboards with Underwriter and Adjuster information (BC-16513, BC-16512)
BriteCore’s Underwriting Management and Claims Manager dashboards have been enhanced with data and filters for Underwriters and Adjusters on a per policy or claim basis.
New Claims Import Endpoint (BC-15543)
In this latest release, BriteCore has added a new ability to import claims into BriteCore. To import claims data, first, define the correct file format by exporting an example .csv file as a model, then that .csv file is replaced with a .csv file containing the actual claims data to be imported and uploaded. Note that the claims data is carefully checked and the import is canceled if errors are encountered.
Enable carrier control around publications of commissions on the dashboard (BC-16224)
The Agent Production Dashboard previously included a commission table that many clients prefer to keep hidden from their agents. This enhancement moves the commissions table onto its own separate dashboard, so carrier administrators can control access.
Enhanced Flexibility for Reversing Waived Premium Write-Offs with Invoice Cloud (BC-13390)
For carriers using InvoiceCloud as their payment provider, BriteCore now allows carriers to reverse premium write-offs in certain situations. This premium reversal addresses the requirement to reinstate policies when the insured decides to pay the waived premium. Previously, the "Delete" button for reversing waived premium write-offs was disabled due to InvoiceCloud's constraints.
With this update:
- BriteCore performs a check based on the carrier's setup with InvoiceCloud and the Accounts Receivable (AR) record type.
- Carriers using InvoiceCloud will see the "Delete" button enabled for AR entries marked as waived, allowing reversal of these write-offs as needed.
Manual Reinstatement Fee Support (BC-14544)
BriteCore now supports enhanced flexibility for policy reinstatement fees, allowing underwriters to manually adjust fees. Previously, only fixed reinstatement fees, configured within the Policy Lifecycle settings, could be applied uniformly. With this update, underwriters now have the option to override the default fee and enter a custom amount as needed.
New Reinstatement Fee Options When reinstating a policy, underwriters will see the following options:
-
Assess Fee or Waive Fee:
- If Waive is selected, no reinstatement fee will be charged.
-
If Assess Fee is selected, underwriters can choose:
- To apply the default reinstatement fee or specify a custom fee.
- For custom fees, enter a value greater than 0.
This update provides greater control over reinstatement charges, accommodating client needs for variable fees based on payment history.
Net Commission Billing for Agency Payments (BC-14434)
BriteCore now supports Net Commission billing for direct agency billing, where carriers deduct commissions directly from invoices instead of issuing month-end refunds.
To enable Net Commission billing, the policy type must be marked for net commission, and the policy term’s bill recipient must be set to Agent/Agency. This status is locked at the first revision commit to prevent mid-term changes.
For invoice display, if a policy is on Net Commission with the bill recipient as the Agency, the first installment will show a calculated net amount after deducting the commission from the total installment amount. For example, if the premium total is $499 with a net commission of 15%, it will display $424.15 due and $74.85 as the net commission, with a breakdown showing how it was calculated.
To account for Net Commission billing, month-end commission processing is bypassed for policies with Net Commission status, and associated reports adjust to reflect these mid-month commission changes.
Defects
Match Up Persistent Builder Query When Selecting Distinct Sublines (BC-15274)
The logic for selecting distinct sublines has been updated to ensure consistency with the Persistent Builder (PB) query:
- When PB is active: BriteCore now displays all line items, regardless of their visibility settings, as the previous filter for showing specific items has been removed. This resolves an issue where empty-looking sublines were displayed twice in the builder, despite containing hidden calculation items.
- When PB is not active: The system will follow the original rules for displaying property items, showing items based on specific visibility conditions.
Removal of Deductible Category and Update to Persistent Builder Mapping (BC-15906)
A Deductible category had been removed from a line item upon renewal, this triggered a persistent builder. As a result, configuring a Persistent Builder (PB) mapping to an explicit None will not work, because the Deductible category is treated as a "dependency" of the item.
To resolve this issue, a new setting has been introduced to instruct PB to drop the dependency check:
Steps to Configure:
- Go to Advanced Settings and ensure the new setting PBexcludeDependencies is set to True.
- Go to Support Tools and make sure to add a Persistent Builder Mapping to align with the updated configuration.
This change ensures the proper handling of dependencies in PB and allows the configuration of line items without the Deductible category.
Incorrect value for numeric custom field in Month End Close Package (BC-16351)
When adding an IM Premium custom field for a canceled policy to the Month End Close Package (MECP), the value of the field could be double the proper value. This release fixes this behavior so these premiums will be correctly reported.
Fix in CEO dashboard for mapping of certain counties (BC-16441)
The CEO dashboard contains inforce change by county maps which in edge cases were data was being incorrectly placed in the wrong counties. This is rectified in this release.