The Agent portal now displays a new version of the Accounts Receivable screen. The Agent portal Accounts Receivable screen update is consistent with recent Accounts Receivable updates in the Provider Administrator portal. The new Accounts Receivable screen provides additional features, enhanced usability, and a modern look.

The Changes to due dates, non-pay notices, and cancellation dates feature consists of changing the core functionalities of non-pay notification and calculation of cancellation dates and creating the advanced setting, offset-invoice-dates-for-non-business-days.

The Stripe integration now captures the successful and failed payments and shows the correct Payment Status in the BriteCore UI.

Updates include new features in the E-Delivery dashboard and redesigned Payments functionality for the web version of BriteApps.

You can add a specific due date for the month within the billing schedule so insureds who are paid once per month or receive subsidized income can select the billing date that works best for them. You can choose a due date for a policy and you can generate the chosen due date for selected linked policies.

BriteCore clients using Stripe can now use the Stripe Connect Platform Account, allowing them to have a centralized list of customers and leverage the destination charges feature to transfer charges to connected accounts.

BriteCore now provides logic to prevent duplicate claim entry in the Agent portal. Previously, duplicate claims could be created if a policyholder reported a claim through BriteApps and an agent created a claim for the same loss. With the Potential Duplicate Claim feature, when a potential duplicate claim is entered, the Potential Duplicate Claim dialog box will display this warning message: Please check to see if the loss you are attempting to report is a duplicate of one of these previously reported claims.

In Classic Rules clients, you can create underwriting rules with the trigger in the Property section and the effect in the Policy Wide section of the quote. When you create rules with this new scope, they’re applied to the underwriter enforcer (automatic renewals), the admin builder, and both versions of the quoting wizard.

Replacement cost estimation is a key component of most carriers’ underwriting process, particularly for habitational risks, such as homeowners and dwelling fire. It’s used to determine how much dwelling coverage (typically Coverage A) is required to fully replace the structure in the event of a total loss. e2Value provides web-based property valuation services.

Currently, the credit score in the builder is a combined credit score relying on the Multiple Credit Scores setting. Since No Hit and No Score are non-numeric, you can’t use them when combining any of the stored tiers. In such cases, the system would automatically use the default credit score, which is numeric. You can find the default credit score in Vendor settings.

We established logic to differentiate between the No Hit and No Score factors because, in some rating schemes, they use a factor not used on any numeric credit score, which leads to an incorrect rating when using the default score.

The Policyholder portal includes a new setting to display a View Declaration link. The Provider Administrator portal has updated columns and graphs in the Enrolled Users and Charts and Graphs dashboards. BriteCore has a new variable with the keyword {portal_code} to include in deliverables.

Stripe is a third-party payment processing vendor that is now available as a payment processing option in BriteCore. With Stripe, you can add customer profiles; add/update payment methods; process one-time payments; start/stop automatic payments; and delete, void, or reverse payments.

With the Historical Submitted Application report, you can get details of all submitted applications that occurred over a date range, regardless of the current status of the policy or if the policy was accepted/rejected by underwriting.

BriteCore has implemented changes to prevent users from adding blank or null notes to the Notes list. When you add a note in any BriteCore module, it must have a title and you must select Add Note.

Your IVANS integration can be configured to deliver all of the information captured in BriteCore’s Supplemental Questions to agency management systems.

For canceled policies, using the remove-endorsements-on-reinstatement advanced setting, administrators can determine if these endorsements remain archived when a policy is reinstated or if BriteCore unarchives and reapplies these endorsements to the policy.

Reports reference different data sources. Going forward, instead of all reports directly referencing your database, they will reference data extracted from your database via a standardized process. The result is a standardized data set referred to as a dataframe. This will eliminate potential discrepancies when comparing reports.

With the display-unbound-message advanced setting, administrators can create a custom message that will display on the Submit tab of the legacy quoting engine when agents submit a quote unbound for underwriter review so agents are aware that the quote is being submitted unbound.

With the Additional Drivers feature, you can now add additional drivers as contacts on specific policy types. When you add contacts with the role Additional Driver to a policy, you can pull MVRs for any driver listed on the policy, even if the additional driver isn’t the named insured.