Monthly and contingent commissions can be paid electronically or manually.
With the advanced setting show-change-of-address-all-invoices, you can choose to include the Change of Address form on installment, equity, amended, and cancellation statements (invoices) or you can include the Change of Address form on all statement types, including initial and renewal statements (invoices).
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.
You can create underwriting rules for renewal only that allow users to add new coverages and change existing coverage limits during the automatic renewal process. When the rule is triggered, the change will always be effective based on the effective date of the new term.
By default, changes made to a previous policy term’s payment method and/or billing schedule don’t carry over to the next policy term. To enable carrying forward the changes made to the payment method and/or billing schedule, use the store-pay-method-across-terms advanced setting.
The Application submission status feature allows clients to provide more than one unbound option for an agent to choose from when the agent submits an unbound application. The unbound options are customizable and can clarify why the application is submitted unbound and if payment is required.
BriteApps: Web version redesign and Provider Administrator and Policyholder Portal updates.
Clients may choose to use the billing threshold for policies that use manual or one-time electronic payments and not for policies set up on auto-pay. The Always Bill Auto Pay setting allows clients to override the Do Not Issue a Bill If the Amount Due is Less Than setting for policies set up on auto-pay.
Administrators can enable the days-to-delay-printing-auto-rp-deliverable advanced setting to delay printing the Return Premium Notice by a defined number of business days.
You can view a specific enrolled user’s policy information from the Enrolled Users dashboard.
With the default_tester_email advanced setting in the admin-alerts section, an administrator can set the default email address to which BriteCore will send emails and alerts. This setting affects test site behavior only; test sites don’t typically send emails or alerts.
The Financial Anti-Terrorism Cross-Reference allows clients to verify contact names in BriteCore against OFAC’s Specially Designated Nationals List of suspected terrorist names and aliases.
In the Pre-Processing tab of the Payment Processing screen, you can locate payments you want to add to a batch by filtering the payments list by specific criteria. In the future, you will also be able to search for payments.
Administrators can update the Provider Administrator portal dashboard in several ways.
If clients set up additional geographical boundaries, they can rate based upon geographical location.
Calculation line items are typically used to facilitate complex calculations, so they don’t need to appear in the XML of the IVANS report. Administrators can filter calculation line items out of the report using the ivans-downloads-export-calculation-items advanced setting.
The ability to add, edit, and archive notes depends on your user role and claim status. You can only add, edit, and archive a note when you access the Notes section from an FNOL, a claim file, or an exposure file. You can’t add, edit, or archive a note when you accessed the Notes section from the Claims Home screen.
This event emits when a risk type sequence is deleted.
This event emits when a risk type sequence is updated.
This event emits when a risk type sequence is created.
This event emits when a Product’s setting is updated.
The IVANS eDocs service is intended to build and upload generated XML files to the IVANS servers. When using eDocs, you receive a daily IVANS-eDocs file uploaded email, which includes a file with PDF details and a transaction code. We have added additional fields so the data is similar to the IVANS Policy Download file.
This event is emitted when the policy is no longer in cancellation pending, such as when a payment is made or the policy is manually reinstated.
This event is emitted when the policy is set to cancel, but not actually canceled, such as when there is a late payment.
This event is emitted when the policy is reinstated.
This event is emitted when the policy is moved out of a non-renewal state and back to a renewal state.
This event is emitted when the policy is set to non-renew.
BriteCore offers a fully headless policy administration system used to execute core processes such as rating, underwriting, binding, issuing, endorsing, canceling/rescinding cancelation, reinstating, and renewing policies.
This tutorial walks you through the Britecore Classic API endpoints handling policy transactional services to create your own policies dashboard.
In the Provider Administrator portal, you can use the BriteCore permissions framework to make the Claims Accounting screen is read-only for selected roles and to remove all Delete buttons from all Policies Accounts Receivable records.
Settings allow staff in the Provider Administrator portal and agents in the Agent portal to view the revision history on a policy to match endorsements to the policy’s billing history.
When a policy is on a billing schedule and either the payor pays the policy in full or a return premium transfer pays the policy in full, BriteCore will not waive all future installment fees. BriteCore’s default behavior can be changed with a setting.
The default behavior for Accounts Receivable always shows Total Paid to Date as a positive balance. In the rare event of a refund larger than what has been paid on the policy, BriteCore has a setting that will show the accurate Actual Paid to Date to reflect negative numbers.
Via settings, clients can set up billing scenarios that meet their business needs.
BriteCore allows clients to update the billing schedules on their policies. When a change is made to the billing schedule, the Preserve/Regenerate selection only occurs within the Provider Administrator portal. This means only client administration and not the insured or agent see the popup box.
When paying commissions on paid premium, the presence of a payment does not necessarily guarantee a commission payout. Because fees are not considered commissionable, the percentages of payments thought to be applied to fees can’t be considered commissionable either.
When a policy is canceled and the amount of the return premium is above the defined minimum threshold, the amount will be moved automatically to the Return Premium Queue. If the return premium is below the defined minimum threshold, the return premium will remain on the policy.
Clients can automate the transfer of a return premium when a policy is rewritten.
You can manually issue return premiums on a policy with a credit.
There are cases when a return premium must be issued to the carrier. For example, while transitioning onto BriteCore, money may have been applied to the incorrect processing system. In this case, issue the return premium to the carrier, rather than the insured, and apply money to the correct processing system.
You can issue a return premium on a policy without a credit, using support tools.
For personal auto, the next step in completing the FNOL is to complete the Vehicles screen. On the Vehicles screen, you can add the vehicle(s) involved in the loss event, the owners of the vehicles, the passengers of the vehicles, vehicle information, and damage information.
By default, when an agent adds a sweep payment to the Sweep Queue, the agent must select Submit Sweep to submit the sweep payment for processing. With the auto-submit-sweep-queue advanced setting, sweep payments added to the Sweep Queue will be processed automatically in overnight processing, without requiring agents to select the Submit Sweep button. With this advanced setting, you can also choose to set a grace period, which means a certain number of days, indicated by the grace period, must pass before the sweep payment will process in overnight processing.
With the agent-payment-amount-zeroed advanced setting, you can choose to zero the Amount field when an agent is entering a sweep payment on the Schedule Sweep screen. Changing the Amount field to zero forces the agent to enter the payment amount of the sweep payment.
Agents can make sweep payments from the Payments module of the Agent portal. In the Payments module, you can make sweep payments from the Schedule Sweep screen. Staff can also complete sweep payments from the Accounts Receivable screen of a policy within the Provider Administrator portal.
BriteCore now provides the ability to customize installment fees by payment method in a billing schedule via the customize installment fee by payment method feature. Setting different installment fees per payment method, such as ACH, credit card, or manual/cash, can be used to incentivize customer enrollment in auto-pay. Previously, this was accomplished by creating multiple billing schedules.
You need to set up the Willis Towers Watson/e2Value Structure Insurance Score integration before you can use it to retrieve insurance scores.
You can use the Willis Towers Watson/e2Value Structure Insurance Score integration to retrieve insurance scores.
The Willis Towers Watson’s Structure Insurance Score (SIS) integration provides a series of insurance scores. Administrators and agents who write homeowners insurance can use this integration to determine the score of an insured structure.
Latest BriteApps release notes on Payments redesign and Provider Administrator portal dashboard updates.
The Lexis Nexis’s National Credit File (NCF) provides online consumer credit reports to insurance carriers. The financial history of the applicant can be considered as part of assessing risk for quoting and underwriting purposes. NCF supports a common inquiry and results format for credit information obtained from the three major credit bureaus.
Credit tiers determine how credit scores in specific ranges should be reported. You can define credit tiers by effective date, state, and policy type. You can add labels to credit tiers that will appear in place of the credit score, such as Poor or Excellent, and you can restrict credit tiers.
The Lexis Nexis’s C.L.U.E. (Comprehensive Loss Underwriting Exchange) is a valuable information source for property and casualty underwriters. C.L.U.E. furnishes insurance companies’ property and liability claims data, which is utilized in the evaluation of underwriting of property/casualty insurance.
Through strategic alliances with leading credit information services, ISO Passport provides easy access to critical consumer-credit information by generating credit reports containing addresses, collections, employers, inquiries, public records, and trade accounts.
You can delete payments from three locations within BriteCore: Daily Cash Receipt screen, Payment Log screen, and Accounts Receivable screen of the policy. By default, when you delete a payment, BriteCore will treat the payment and policy like the payment never occurred, which could cause the policy to enter Cancellation Pending, Non-Payment of Premium or could automatically cancel the policy. Due to BriteCore’s default behavior, it is recommended that you only delete payments from within the Accounts Receivable screen of the individual policy.
AIR Worldwide, a Verisk Analytics company, provides software and catastrophe modeling to help companies manage risk from natural catastrophes, terrorism, cyber-attacks, and pandemics. BriteCore offers two integrations with AIR products: AIR Touchstone and AIR Hazard Service’s Flood Zone API.
While you can mark a payment as NSF from the Payment Log, it is recommended that you mark a payment as NSF from the Accounts Receivable screenwithin the individual policy. When you mark a payment as NSF, BriteCore will treat the payment as if it never occurred. BriteCore will use the Due Date and Cancel Date of the outstanding invoice to determine the course of action.
You can add payment methods in two ways: On the Payments screen of the Contacts module and on the Accounts Receivable screen of a policy.
With the reinstate_mortgagee_billed_non_paid_renewals_on_payment advanced setting, you can allow mortgagee billed canceled policies or non-pay renewals to be reinstated as long as payment that meets the payment threshold is made within a specified amount of time.
With the bypass-duplicate-payments-check advanced setting, you can allow the system to bypass the default behavior of checking for and declining duplicate electronic payments. In the event that you need to re-attempt an electronic payment due to a slow response time or system error, it can be helpful to bypass the duplicate payment check so you can accept a payment made on the same policy for the same amount within a 48-hour period.
When making a change to a policy on the same calendar day a revision (new or renewal) is generated and endorsed, you want the endorsement declaration to accompany the renewal declaration. Administrators can enable the always-print-endorsement-docs advanced setting to ensure both forms print.
When a client transitions onto BriteCore, renewals may be converted one month at a time. During that period, clients will have policies expiring in their legacy system and renewing into BriteCore. On occasion, clients may need to either cancel or issue a cancellation notice on a policy that is in the transition phase.
Underwriting questions can be defined and prompted within specific policy types. Underwriting questions can either be global or granular within a line of business.
Straight-through processing (STP) allows agents to automate the submission and review process for applications that meet underwriting requirements and conditions. When engineers code rules, applications that meet requirements are automatically committed and their policy status is set to Active. Otherwise, the policy status is set to Submitted, pending underwriter review and approval.
Munich Re has a personal lines policy endorsement, Munich Re Inland Flood Coverage, for insurance companies who want to help their policyholders manage their flood risk more economically. BriteCore’s policy management system integrates with Munich Re Inland Flood Coverage for personal lines including Homeowners and Dwelling Fire.
Munich Re has a personal lines policy endorsement, Munich Re Inland Flood Coverage, for insurance companies who want to help their policyholders manage their flood risk more economically. BriteCore’s policy management system integrates with Munich Re Inland Flood Coverage for Homeowners and Dwelling Fire lines.
When working with the Mutual Boiler Re (MBRe) integration, you might need to refer to the MBRe specifications documents and transaction codes.
The Hartford Steam Boiler Inspection and Insurance Company (HSB) is a specialty reinsurer for the following coverages: Home Systems Protection (Homeowners Equipment Breakdown), Service Line – Identity Recovery, Farmowners and Commercial Equipment Breakdown, Employment Practices Liability, Data Breach, and CyberOne.
Verisk’s analytics company, iiX, offers an ISO Motor Vehicle Reports (MVR) service. The MVR service allows users to obtain MVRs from all 50 states, the District of Columbia, and select Canadian provinces. BriteCore’s ISO Motor Vehicle Reports integration functions similarly to its integrations with ISO Loss History and ISO Credit Scoring.
Clients may choose to show or hide duplicate addresses for the same policy on the Inspections Due report.
By default, policies that are agency billed are not automatically canceled for non-payment. There are advanced settings that allow agency billed policies to automatically cancel due to non-payment.
Agency billing is used when the agency is responsible for billing the insured. This occurs when an agency is a wholesale agency or a surplus lines producer. BriteCore supports wholesale agencies, or agencies using agency billing, by sending invoices to the agency rather than the insured.
Plum Voice powers interactive voice response (IVR), which includes call routing, messaging, and voice communications for customers. With BriteCore, payors can check account balances and apply credit card or ACH payments to policies by calling a specific telephone number.
Clients can receive notifications for processing errors. Some of the errors are specific to, and therefore documented with, specific workflows. For example, notifications specific to the renewal workflow are documented with that page. This page documents notifications that apply to both new and renewal business workflows.
Britecore provides an advanced setting, append-policy-term-suffix-to-quote-numbers, that quickly shows you the number of times a policy has been renewed. The system identifies the number of renewals by adding a two-digit suffix—a term number—beginning with -00 to the end of policy numbers.
This enhanced policy numbering scheme allows you to search based on any part of the policy number.
In BriteCore, when an application is submitted, it’s immediately issued a policy number. This setting avoids assigning policy numbers until the application has been made an active policy. BriteCore will distinguish, via number format, between an application/quote and active policy.
This setting in the Policy Lifecycle area is only accessible during setup, before the site is live. BriteCore can enable this setting via the database, but it’s not something normally done after the site enters production. There may be unforeseen consequences of making this change and we recommend testing this change thoroughly in a test environment.
Provides various instructions for setting up new business workflow. Please note that the Generation 2 BriteCore Services new business workflow is no longer used with new clients.
By default, when new business is quoted in the policy wizard users are directed to separate screens to add and rate property and policy coverages. A setting allows users to stay on the same page while adding coverages by making those screens popups, or modals, rather than separate screens.
The redirect-to-wizard-policy-status setting allows clients to identify policy statuses that should open in the policy wizard by default. This setting only affects the Agent portal.
This articles details efforts related to per-client customization on the policy wizard. The audience for this document is anyone that needs to interact with these new mechanics at a code level and anyone interested in knowing the new capabilities in more details.
By default, agents can access but not create deliverables within the Agent portal. A setting allows clients to identify custom deliverables agents can create within the Agent portal.
By default, agents can’t see policy notes. You can allow agents to view all notes for a given policy within the policy’s Notes tab. The setting applies to the Policies module only and provides view-only privileges; agents can neither create note alerts nor add, edit or delete notes.
Within a claim, you can access to two different headers: the claim file header and the exposure file header. When inside a claim file, the menu on the left side of the screen provides additional claim details or exposure details.
BriteCore’s Solution Architecture team outlined the Pull Request (PR) for all partner and client PRs targeted towards the master branch in the BriteCore repository.
The goal is to provide partners developers, client developers, and other third-party developers with timely responses on their PRs with minimal disruption to the Product teams’ normal workflows.
When one-time or recurring electronic payments occur, notification of certain situations can be helpful, such as notification of underpaid policies, duplicate payments, and declined payments. You can set up notifications in the Provider Administrator portal for these instances and for others.
As insurance contracts are legally binding, it’s important that the entity with an insurable interest is correctly identified throughout the policy lifecycle. The setting disable_fein_ssn_for_active_policy disables the FEIN/SSN, which prevents those values from being changed once a policy is set to active (but not necessarily committed).
The new business workflow has undergone two major iterations. The first iteration led to what clients who went live prior to 2017 are using, known as legacy quoting or BriteQuote. The legacy quoting offered minimal customization and was difficult to change due to technology constraints. In 2017, work began on a custom UI that offered new clients the ability to easily customize the entire quoting process within the Agent portal. This transition to the custom UI spec project was research and development with implementation. As a result, customizing a client’s quoting experience is still a work in progress.
Manuscript endorsements refer to custom coverages, often with a custom name and rate. This type of custom insurance coverage is typically written from scratch for specific events or assets tailored to the insured, such as an annual training conference or annual county fair.
By default, BriteCore allows users to independently initiate revisions (endorsements) on different dates without issuing them. To prevent this behavior, use the prevent-creation-of-multiple-open-revisions-simultaneously setting. With the setting enabled, the system safeguards against users from inadvertently creating duplicate endorsements.
An endorsement is an amendment or change to a policy. Within BriteCore, endorsements are also referred to as revisions. While typical commercial insurance contains general coverage, BriteCore allows the flexibility for clients to build almost any endorsement they would like to offer, from Coverage A to custom coverages like manuscript endorsements.
A billing agent can generate an invoice (deliverable) for an insured with the remainder owed on a policy before it goes into cancellation pending for non-payment. The current system, Edit & Reprint, will generate the full invoice amount of the total premium, while Payoff Balance Summary will provide the remaining balance.
The validate_application_before_print advanced setting restricts application printing for incomplete quotes. When enabled, agents and agencies are required to complete all of the required fields on a policy prior to selecting Print Application on new policy applications.
BriteCore clients should have a plan for continued business operations during critical events or circumstances that may impact their standard operating procedures. To help our clients’ employees carry out their duties, we have outlined the printing options BriteCore offers. These options will help clients minimize business interruption, allowing their customers to receive their insurance documents as expected.
BriteCore is set up for billing operations to continue while working remotely. Billing setup, billing schedules, and billing invoices won’t be impacted by transitioning to remote work. Collaborate with named insureds on transitioning to remote payment methods: auto-pay, online pay, or mobile pay.
A BriteCore client can use SSN or address to obtain a credit score. If SSN is not collected, there are cases where prior address is required in order to obtain the credit score. For example, in the event that the insured has not been in a residence a requisite number of days, a trigger can require the prior address. The features in this document facilitate the gathering of prior address information.
Clients can add an extension to cancellations to accommodate mortgagees. When used, BriteCore will report a cancel date of X more days via InsVista to the mortgagee. BriteCore, however, will still process the policy on the original cancel date. In other words, BriteCore processes the policy as if there is no extension. The extension is reported to the mortgagee through InsVista only.
Written, earned, and unearned premiums are calculated on a daily basis. To determine the premium, divide the written premium by the number of days in the term. Premium record calculations display for each day the policy is in force. These calculations are accessed on the Accounts Receivable screen of every policy.
When a mortgagee or title company issues payment based on a submitted application before the application becomes a committed and active policy, the payment needs to be accepted. With the allow-pay-submitted-policies advanced setting, you can allow payments to be applied to submitted policies.
When you enter manual (check, money order, cash) payments on the Daily Cash Receipt screen, the payments will populate in a list below the Check, Money Order, and Cash sections. When you create a deposit receipt for these payments, BriteCore will automatically clear the list of payments and generate a deposit receipt document. When the deposit receipt is generated, BriteCore will also automatically generate payment receipts for each payment listed on the deposit receipt.
Rate Capping allows a carrier to cap a renewal rate change at each renewal until reaching the approved rate level. Carriers can cap a rate change at a maximum percent increase (or decrease) or a set dollar amount. The amount at which the renewal will be capped is calculated as a percentage of the previous term premium, minus any natural increases, new coverages, or properties manually added to the policy on renewal.
MassPrinting is a leading provider of document output solutions to the insurance industry. MassPrinting works closely with your internal team to provide a personalized outsourcing solution for the printing and mailing of your policyholder communications.
You can group inbound payments together to aid in more efficient processing. In BriteCore you can batch manual payments in the Provider Administrator portal. You can enter a batch by referencing the policy or invoice number, the system will pull information from the invoice.
BriteCore accepts manual and electronic payments. Manual payments are check, cash, or money order and electronic payments are ACH or credit card. Manual payments are entered by a user or through the File Transfer Protocol (FTP) upload method. Electronic payments are made through integration with third-party vendors.
Insureds may need to change the billing due date to better accommodate their needs. For example, if an insured is paid once per month, on the first day of the month, the insured may need to change the due date to the 1st of the month. If an insured receives Social Security on the 23rd of the month and has a fixed income, the insured may need to change the due date to the 23rd of the month.
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.
BriteCore provides agents with additional features, enhanced usability, and a modern look with the new Accounts Receivable screen in the Agent portal. The new Agent portal Accounts Receivable screen is consistent with recent Accounts Receivable screen changes in the Provider Administrator portal.
OBRIEN Insurance Solutions has 45 years of experience in managing policyholder communications for insurance companies. Outsourcing with OBRIEN will yield cost savings, increase capabilities and efficiencies, and automate processes, so you can focus on creating and delivering value for your customers.
If a client wants to use ImageRight and requires a different filename format for deliverables other than the default, the format can be made configurable via vendor settings. A setting will hold a JSON string that includes a Python string with named placeholders, allowing target_deliverables to define the individual types of files that can be sent for a client.
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.
Cron is a software utility in Unix-like computer operating systems that automatically schedules time-based jobs. BriteCore’s DayCron script is executed on every live site’s Leader node around midnight every day. This document provides a summary of the nightly processing details in BriteCore.
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’re attempting to report is a duplicate of one of these previously reported claims.
To prevent duplicate claim entries, BriteCore will search the system to identify potential duplicate claims when you create a claim in the Agent portal. After selecting the loss date and time in the first notice of loss (FNOL), BriteCore will automatically search for any additional claims filed on the same policy from one day before the entered loss date to one day after the entered loss date.
After you initiate the FNOL from the Claims or Policies modules, you can complete the FNOL. Complete the following sections to complete the FNOL. Policy
On the Parties screen of the claim file, you can add and manage claim assignments, such as Primary Adjuster, Claim Supervisor, Claim Manager, and Claim
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.
Using Classic Lines, you can create underwriting rules with the trigger in the Property section and the effect in the Policy Wide section of the
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.
In this tutorial, we will guide you through creating your own custom quoting application workflow using BriteAPIs for BriteCore Classic.
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.
BriteCore combines claims administration functionality and business process management (BPM) support for the entire claims process. From open to close, agents and adjusters work collaboratively
BriteCore offers a policy administration system used to execute core processes such as rating, underwriting, binding, issuing, endorsing, canceling/rescinding cancelation, reinstating, and renewing policies. It’s
The Quotes module provides a dynamic interface for agents and other stakeholders to generate policy estimates based on risk locations, rating details, product lines, and individual carrier risk tolerances. Carriers can configure each screen, from collecting contact details, answering initial questions, and completing rating information, to submitting an application, evaluating underwriting metrics, and completing final processing.
When a BriteCore site uses BriteLines, BritePolicies, BriteClaims, BriteDocs, BriteRules, BriteAccess, or BriteNotes, the enabled_gen3_modules advanced setting makes those modules available upon selecting the corresponding UI icon instead of the Classic BriteCore module counterparts (if applicable).