Recent topics
Role-based security map
Role Role type Log in with assigned credentials? BriteCore access Function Function Limitation Additional Insured Individual/Organization No N/A Add information
Access the Document Generation dashboard
ubleshoot BriteDocs issues related to document and packet generation. The dashboard lists all documents generated via BriteDocs and their generation status.
Billing – Automated NSF with Stripe integration
Clients using Stripe as a payment vendor will be able to automatically decline payments that are marked Non-Sufficient Funds (NSFs). Automating NSFs reduces the time spent manually processing NSFs and mitigates human error within the process.
BriteClaims event:`bc.claims.claim_assignment_created`
The s.exposure_assignment_created event emits when a claim is assigned to a party, such as Primary Adjuster, Claim Supervisor, Claim Manager, and Claim Assistant.
BriteClaims event:`bc.claims.exposure_assignment_created`
The bc.claims.exposure_assignment_created event emits when an exposure is assigned to a claim.
BriteClaims event:`bc.claims.payment_unapproved`
The bc.claims.payment_unapproved event emits when an approved payment against a claim is unapproved.
BriteClaims event:`bc.claims.payment_posted`
The bc.claims.payment_posted event emits when an approved payment against a claim is posted or deemed final.
BriteClaims event:`bc.claims.payment_approved`
The bc.claims.payment_approved event emits when a draft payment against a claim is approved.
BriteClaims event:`bc.claims.payment_drafted`
The bc.claims.payment_drafted event emits when a new payment is posted against a claim payment.
BriteClaims event:`bc.claims.exposure_status_changed`
The bc.claims.exposure_tag_changed emits when a claim exposure status is changed.
BriteClaims event:`bc.claims.exposure_tag_changed`
The bc.claims.exposure_tag_changed emits when a claim exposure tag is changed.
BriteClaims event:`bc.claims.risk_fault_updated`
The bc.claims.risk_fault_updated emits when a fault in a claim file is updated.
BriteClaims event:`bc.claims.risk_fault_added`
The bc.claims.risk_fault_added emits when a fault is added to the claim file.
BriteClaims event:`bc.claims.claim_tag_changed`
The s.claim_tag_changed event emits when any tags assigned to a claim change.
BriteClaims event:`bc.claims.risk_updated`
The bc.claims.risk_updated event emits when a risk is updated.
BriteClaims event:`bc.claims.claim_status_changed`
The bc.claims.claim_status_changed event emits when the claim’s status changes.
BriteClaims event:`bc.claims.risk_relation_added`
The bc.claims.risk_relation_added event emits when a new party is added to a risk.
BriteClaims event:`bc.claims.risk_added`
The bc.claims.risk_added event emits when a new risk is added to the claim.
BriteClaims event:`bc.claims.policy_holder_added`
The bc.claims.policy_holder_added event emits when a policyholder is added to the claim.
BriteClaims event:`bc.claims.claim_party_relation_added`
The bc.claims.claim_party_relation_added event emits when a new party is added to the claim.
BriteClaims event: `bc.claims.policy_revision_added`
The bc.claims.policy_revision_added event emits when the policy attached to a claim is revised.
BriteClaims event:`bc.claims.fnol_submitted`
The bc.claims.fnol_submitted event is emitted when the first notice of loss (FNOL) for a claim is submitted.
Course and quiz guidelines on the Help site
The course and quiz guidelines are now on the Help site. These are basic parameters to help us remain consistent when creating courses and quizzes.
Automatic 300 series redirects and 404 logs
The Help site now automatically performs two operations that improve each user’s experience and the site’s linking structure and SEO: 300 series redirects and 404 logs.
Import/Export custom access configurations
This tutorial explains how to use the Import/Export feature in BriteAccess.
Cross-site migration guide
This guide walks you through manually migrating configurations from one BriteCore site to another.
New agent Schedule Sweep screen design
BriteCore’s Design team is redesigning the Schedule Sweep screen for agents. While the Schedule Sweep screen’s appearance will change, its functionality will remain the same.
Policy workflow and status
This post outlines how quotes are submitted and when they’re ready to become bound, in-force policies. In BriteCore, a policy’s status depends on where it is in the policy lifecycle.
Client’s role in enabling LexisNexis product integrations
This guide walks you through the LexisNexis implementation process.
BriteAccess: Import/export custom access configurations
Set a temporary password for the user is a new feature that enables users to log in to the system if there are issues with the invitation process.
Integrations: Data mapping web UI manager
The data mapping web UI allows users to add, edit, and delete data mappings.
BriteAccess: Set a temporary password
The ability to set a temporary password for a user is a new feature that enables users to log in to the system even if there are issues with the invitation process.
Billing: Factor installments by payment method
Billing schedule installment factors can be configured differently based on a policy’s payment method setup, which is beneficial for carriers that want to incentivize specific forms of payment or payment methods.
Factor installments by payment method
Billing schedule installment factors can be configured differently based on a policy’s payment method setup, which is beneficial for carriers that want to incentivize specific forms of payment or payment methods.
Set a temporary password for invited users
You can set temporary passwords for users. This enables users to log in to the system if there are issues with the invitation process.
e2Value XML integration for classic BriteCore
Replacement cost estimation is a key component of most carriers’ underwriting process, particularly for habitational risks, such as homeowners and dwelling fire. Replacement cost estimation is used to determine how much dwelling coverage should be required on a policy to fully replace the structure in the event of a total loss.
Invoice Cloud integration
In BriteCore, clients can now use Invoice Cloud as a payment processor and bill presentment solution for their administrators, agents, and customers.
BriteApps: New settings and text messaging feature
Details changes to BriteApps, including new settings and a text messaging feature.
Plugins architecture and slots
Learn more about BriteCore’s UI plugins architecture, key concepts, plugin slots, and functionality.
Rules Execution Logs
We have improved BriteRules by making it easier to track the rules that are being executed, adding additional information to the logs, and providing more ways to search for logs, which makes troubleshooting easier.
Submit Zendesk Support Tickets from the Help site
Zendesk is now integrated with the Help site, allowing users to submit a Zendesk Support Ticket from any screen on the Help site.
BriteApps: Text messaging feature
A new text message feature is being released in BriteApps.
Integrations: Plugins UI Manager
Release note for the Plugins UI, which allows you to manage plugins.
Integrations: Root-level plugin slot
The web UI root-level plugin slot called britecore:root:markup is a hidden plugin that allows more advanced users to run javascript on any page.
Billing – Void return premium replaces delete return premium
Currently, you can delete exported return premiums from the Accounts Receivable screen in BriteCore. However, we’re removing the option to delete an exported return premium and adding the option to void an exported return premium.
Plugin manager web UI
The plugin manager web UI allows users to manage plugins. The web UI allows users to add, edit, and delete plugins.
Classic Policies: Delay cancellation per policy
Delay Cancellation is a new feature in classic Policies that allows additional time for an insured to pay a policy without extending the cancellation effective date. A delay can now be placed on a per-policy basis.
BriteClaims screen flow
This tutorial provides an overview of the BriteClaims screen flow with screenshots.
BritePolicies screen flow overview
This tutorial provides an overview of the BritePolicies screen flow, including screenshots.
BriteQuote screen flow
This tutorial provides a high-level overview of the quote screen flow with screenshots.
Show agency commission and premium separately
show_agency_commission_and_premium_separately is a global setting that will display the commission due to the agent but doesn’t remove it from the invoices.
Set up rejected return premiums
When generating return premiums, administrators can opt to reject return premiums, regardless of the return premium generation process (manual or automatic).
Underwriter Workbench improvements
Since it can be time-consuming going back and forth between BriteQuote and the Underwriter Review Summary to review a quote, added tools to make the process quicker and easier.
Configure BriteDocs in BriteSuite
This tutorial walks you through setting up BriteDocs in the Britesuite platform.
Silvervine is now payCloud.io
Silvervine (Primoris) is now payCloud.io. All references to Silvervine or Primoris on the Help site have been changed to payCloud.io.
Example tutorial: Add a plugin slot to the Policy Overview screen
BriteCore provides a beta JavaScript library that you can use to build your plugins. A plugin can help you extend the functionality of the Overview screen. This tutorial walks you through adding a plugin slot to the Overview screen.
Issue return premium to contact not on the policy
If an insured dies and the cancellation of the policy results in a return premium, the return premium may need to be issued to a contact not listed on the policy.
There are two methods you can use to issue the return premium to a contact not listed on the policy.
Policy limits
Policy limits measure the loss incurred on an exposure or claim and define the maximum amount the insurer will pay.
Add or change loss date on a claim
Claims can exist without a loss date entered in BriteClaims. There are instances when the exact loss date is unknown without further investigation. BriteClaims is designed to allow users to create an FNOL and submit a claim without a loss date. If the loss date on a claim isn’t correct, then you can still change the loss date if the claim’s status is New.
Associate a deliverable with BriteDocs support tool moved from BriteCore to BriteDocs
The existing Associate a Deliverable With BriteDocs support tool in BriteCore will be removed from BriteCore and added to the Documents Manager in Django Admin.
BriteDocs: Document Template Version by Product
Classic BriteCore supports the ability to deliver documents by state. We extended this functionality in BriteDocs for users to create templates based on products in Lines. This feature will allow users to create a template at the parent product level with the option to create variations for each child product or using the same template for all child products.
Process payment prior to bind
With the new advanced setting process-payment-at-bind, carriers can require an initial payment during the quoting process before a policy is bound and issued.
Process payment at bind
With the advanced setting process-payment-at-bind, you can choose whether to require an initial payment during the quoting process before a policy can be bound and issued.
BriteQuote – Setting time zones for quoting release notes
In BriteCore, you can now set the time zones for an individual product. The time zones set will be used to determine the quoting restrictions allowed for effective date tolerances.
Map a document from BriteDocs to BriteCore
When you create a new or customized template using BriteDocs, you must associate it with the existing deliverable it replaces. This tutorial walks you through document mapping.
BriteLines event: bc.lines.version_deleted
The bc.lines.version_deleted event is emitted when a product version is deleted.
Policy overview plugin slots
Previously, integration UI plugin slots were only available in the quote flow. Now, plugins are available on the Policy Overview screen.
Delete a product version
While working with lines, you may create draft product versions for experimentation, which you plan to delete when you’re finished. In BriteLines, you can delete draft non-initial product versions via BriteCore’s UI.
BriteLines – Delete product versions
Currently, there is no way to delete an unwanted product version. We created a way for you to delete all draft non-initial product versions.
BriteLines events emitted for product versions
BriteLines will now emit two new events when a product version is created or updated: bc.lines.version_created and bc.lines.version_updated.
Select how to print commission reports
You can select how to print commission reports for your company. To select how to print commission reports: Navigate to
Rename a product
A product is a classification within a LOB an insurer can rate on, such as countrywide, state, or jurisdiction. You can name a product when you create it, or you can go back and rename it at any time.
Rename a line of business
A line of business (LOB) is a classification of insurance business, such as auto, property, or liability. You can name a LOB when you create it, or you can go back and rename it at any time.
Renew Non-renewed Expired BritePolicies
Previously, when a policy was non-renewed or expired, if the risk was reapproved, the policy would need to be written as a new policy. We have made some changes that allow clients to renew an expired policy.
New learning course module
We added a new learning course module to the Help site. The learning module will allow us to expand and test the knowledge of BriteCore staff.
BriteSuite high-level data models
BriteSuite comprises a set of RESTful services that enable specific modules that are deployed as serverless lambda functions. Each BriteCore service endpoint is associated with a respective lambda function—modules developed in Python.
This document outlines a high-level description of the BriteSuite data models within each of the main modules.
BriteLines event: bc.lines.version_updated
The bc.lines.version_updated event is emitted when a product version is updated.
BriteLines event: bc.lines.version_created
The bc.lines.version_created event is emitted when a product version is created.
Delete return premium
You can delete a return premium from the Return Premium queue.
Configuration FAQ
Answers to frequently asked questions that arise when configuring a site.
Event Subscription UI
The Event Subscription web UI allows users to manage and troubleshoot event subscriptions.
BriteApps: Custom pages and telephone number field updates
BriteApps’ newest release is rolling out: Custom Pages.
Billing – Delete return premium is going away
Currently, you can delete exported return premiums from the Accounts Receivable screen in BriteCore. However, the ability to delete return premiums is going away.
Void return premium
You can void exported return premiums from the Accounts Receivable screen in BriteCore.
Enable void return premium
If you want the option to void return premiums instead of deleting them, you can switch now. To turn on the functionality to void a return premium from the Accounts Receivable screen, enable the Display Void Option for Exported Return Premium Rows setting.
Event Subscription UI
The Event Subscription web UI allows users to add and delete event subscriptions. Changes aren’t allowed by the API; any change requires a new subscription and deletion of the previous subscription.
Premium records
Explanation of how premium is calculated and/or tracked throughout various scenarios.
Set up credit scoring
Discussion of features and settings that impact how a client sets up credit scoring.
Set up and customize the Declaration
Discusses several features and settings used to modify declarations.
Reinstate policies
In BriteCore, you can reinstate policies with the following policy statuses: Cancellation Pending Non-Payment of Premium, Cancelled Policies, or Expired Policies.
Commit rule changes to a project
BriteSuite’s rule deployment process has changed: Rule deployment is now a one-step process. In the top-right corner of the screen,
BriteRules – One-step rule deployment
The existing rule deployment process is complex, making it difficult to know which new rules or changes have been committed to a site, so we improved the process by condensing it to one step.
Navigate quote wizard by URL
You can navigate to various screens within the quote wizard by changing the URL.
Data conversion configuration
This tutorial describes BriteCore’s data conversion process and guidelines.
Test credit scores locked to policy terms
Instructions on how to test the setting that allows users to lock a credit score to a policy for a specified number of policy terms.
ISO Protection Class lookup overview
When Building Code Effectiveness Grading Schedule (BCEGS) is enabled in BriteCore, users will be asked for the construction year when adding the location’s address. The specific construction year allows ISO to determine a protection class and BCEGS value for clients.
Set up Agent policy workflow with BCEGS and construction year
Both classic BriteCore and the policy wizard follow the same workflow when creating a new policy.
Building Code Effectiveness Grading Schedule (BCEGS)
Building Code Effectiveness Grading (BCEGS) emphasizes building code requirements designed to mitigate losses from natural hazards. BCEGS develops a relative Building Code Effectiveness Classification (or grade) for each community for insurance rating and underwriting purposes.
Set default as prior protection class
ISO Protection Class lookup failures trigger a user warning that halts the rating process by having the user choose a new protection class and rate before committing the policy manually.
Disable user accounts
Administrators can disable a user account regardless of the user’s status. When a user is disabled, the user’s login will be revoked within one minute. Their email, phone number, and status will display in light gray in the Users and Groups table.
Invite a new user
As an administrator, you must invite a user to BriteCore before the user can log in. When an Administrator invites a new user, BriteCore will link the user to an existing contact or create a new contact and then send the user an email with a temporary password that enables the user to log in for the first time. As an administrator, you can customize the email invitation new users will receive.
LexisNexis Auto Data Prefill overview
The LexisNexis Auto Data Prefill (ADP) integration allows carriers to retrieve driver, vehicle, and policy information based on minimal information collected from the insurance applicant at the point of contact.
ISO Verisk – 360Value validation
To use Verisk’s 360Value validation, administrators must enable it in BriteCore.
ISO Verisk – 360Value reports
For 360Value reports, you can choose whether or not a named insured is required to pull a report and preview a report during quoting without having to submit the application.
ISO Verisk – 360Value overview
Verisk’s 360Value integration provides component-based replacement cost estimates for the full range of residential, commercial, and agricultural properties.
ISO Prefill Services overview
Prefill Services uses the 360Value API call to get data for use in preliminary quoting and rate categories.
Renewal Queue overview
Policies set to renew should automatically renew on their renewal date. It’s possible for a policy scheduled for renewal to fail to renew automatically. When a policy fails to renew automatically, it will appear in the Renewal Queue.
Underwriter Review Summary tabs
The Underwriter Review Summary breaks the quote/application information into various tabs that the underwriter can review.
New business notices
When quoting new business, notices can be automatically generated and sent or manually sent to the agent on the new business quote or application.
Delete a policy
A policy may need to be deleted due to processing errors. To delete a policy, you must delete it from both the Policies side using BriteCore Shell and the Quote side using Django Admin.
Allow notes to be placed on the policy when an STP rule is triggered
The stp-make-detailed-note-on-failure advanced setting allows notes to be placed on the policy when an STP rule is triggered. These notes help administrators understand the reason the quote was referred for underwriting review.
Rules – Generate a note when an STP rule is triggered
Currently, when an STP rule is triggered, only the agent is provided details on which rules caused the quote to be referred from the Agent Wizard.
Straight-through processing (STP)
Straight-through processing (STP) allows agents to automate the submission and review process for applications that meet underwriting requirements and conditions. When business rules are established in the system, the applications that meet these requirements are automatically committed and their policy status is set to Active. Applications that don’t meet these requirements are set to Submitted, pending underwriter review and approval.
Edit party information
You can update a party’s information by selecting their name link from anywhere in the claim file.
Set up cancellation and reinstatement notices
Summarizes BriteCore’s cancellation notices and their uses, with examples.
Policy renewal overview
BriteCore will automatically renew policies. Policy renewals will reflect changes to the policy, such as new mandatory coverages and inflation guards. BriteCore will also update values like claim history and the age of a property.
Transfer prior term debits and credits to a renewal term
When BriteCore automatically renews policies, it won’t transfer outstanding debits to the renewal term, but it will transfer outstanding credits to the renewal term on the renewal effective date.
Retrieve and display claims and statuses and update claim status
BriteClaims enables organizations to manage the full life cycle of property and casualty (P&C) insurance claims from first notice of
Update exposure reserves, process exposure payouts, and set/submit recovery reserves
BriteClaims comprises different configurable pieces of data. From the first notice of loss (FNOL) to final payment and settlement, an
LexisNexis Motor Vehicle Records overview
The LexisNexis Motor Vehicle Records (MVR) integration is a fully-compliant, consumer-reporting agency solution that provides access to motor vehicle records from all 50 states.
LexisNexis Advanced Linking Initiative overview
The LexisNexis Advanced Linking Initiative integration uses LexID® to unify the way insurance data and public records information are included in an auto insurance customer’s file.
ISO VINMASTER overview
Verisk’s VINMASTER integration allows you to locate a vehicle’s current ISO Vehicle Series Rating Symbol and accurately determine premiums without the vehicle identification number (VIN).
Update age-related items on renewal
With the advanced setting enforce-yearbuilt-cross-terms enabled, when a policy is renewed or even rewritten, any items including values pertaining to age (age of roof, age of home, etc.) will automatically update to match the prior term’s values.
Plum Voice overview
Plum Voice is a cloud-based solution that offers secure, PCI-compliant, modern interactive voice response (IVR) and text payment processing and reporting.
Authorize.Net overview
Authorize.Net provides payment solutions for small to medium-sized businesses and organizations, enabling merchants to authorize, settle, and manage credit card and electronic check transactions.
Reports: Policy management
BriteCore includes several policy management reports that can be accessed in the Reports module.
Reports: Premium
BriteCore includes several premium reports. You can access these reports in the Reports module.
Policy dialog box in BriteClaims
The policy dialog box contains important policy information that is pulled into any claim filed on the policy.
Create and submit a first notice of loss using BriteClaims
This tutorial will guide you through creating and submitting an FNOL with BriteClaims APIs.
Archive or delete a revision
Clients can archive or delete revisions from the interface. To archive or delete a revision, the policy must have at least one active effective date revision. The revision date can’t already be archived or deleted.
Edit a revision date
When making changes to an existing policy, you can edit the effective date before you commit the revision by selecting Edit Revision Date.
Set up the stock declaration
Clients can use BriteCore’s stock declaration or build a custom declaration.
Set up and use mortgagee extensions
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 will still process the policy on the original cancel date as if there is no extension. The extension is reported to the mortgagee through InsVista only.
Set up a rating worksheet
To set up a rating worksheet, you must add the Rating Worksheet tag and then build the Rating Worksheet report.
Set up contact fields
You can set up and configure fields to display in classic BriteCore services and in the Policy Wizard.
View a property location
You can view the location of a property by its geographic coordinates or on a map.
Set up cancellation and non-renewal reasons
Clients can define their list of cancellation and non-renewal reasons by state and policy type.
Rewrite a policy
You may choose to rewrite a policy for a number of reasons. For example, you may need to change the policy type, in which case you would need to rewrite the policy.
Manage late-term endorsements
If an endorsement occurs after the renewal has been issued, BriteCore will attempt to carry forward any changes.
Generate Payoff Balance Summary
You can generate a deliverable for an insured that displays the remaining balance owed on a policy before a policy enters Cancellation Pending for non-payment.
Set up effective date behavior in the quote wizard
You can change the effective date of a policy while quoting. You can also add new lines effective dates. If you add a new lines effective date, change the effective date of a policy in a quote, and the policy’s new effective date falls after the new lines effective date, then BriteCore will automatically move the quote to the new lines effective date.
Orbipay setup
Provides instructions for both vendor and BriteCore setup of Orbipay.
Orbipay overview
Orbipay is a cloud-native platform that powers a comprehensive set of unified digital money movement and faster payment-related services for banks, credit unions, and insurance companies.
Test Invoice Cloud
BriteCore staff can access the Invoice Cloud testing sheet to test the integration.
Test iCheckGateway payments
After setting up the iCheckGateway integration, BriteCore staff can test the credit card and ACH payments.
Retrieve and display claims and statuses and update claim status
BriteClaims enables organizations to manage the full life cycle of property and casualty (P&C) insurance claims from first notice of
Block quoting in the Agent Wizard
In classic BriteCore, you can now configure underwriting rules that will block a user from continuing past a quote’s Risk screen in the Agent Wizard when the rule criteria are met. This functionality is similar to the validation rules that are triggered for clients using BriteSuite.
Rules – Block quotes in the Agent Wizard
In classic BriteCore, you can now configure underwriting rules that will block a user from continuing past a quote’s Risk screen in the Agent Wizard when the rule criteria are met. This functionality is similar to the validation rules that are triggered for clients using BriteSuite.
iCheckGateway overview
iCheckGateway combines ACH and credit card processing into a unified approach. Integrating iCheckGateway with BriteCore enables merchants to authorize, settle, and manage credit card and electronic check transactions.
OFAC Financial Anti-Terrorism Cross-Reference overview
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.
Hartford Steam Boiler (HSB) overview
The Hartford Steam Boiler Inspection and Insurance Company (HSB) is a specialty reinsurer for several coverages.
BriteLines – New bc.age utility parameter
Currently, the bc.age function uses the rating date, bc.transactionEffectiveDate, as the base date to calculate age, but now, the bc.age utility can specify a different base date when calculating age.
Configure LexisNexis FIRSt in BriteSuite
This tutorial walks you through the steps to implement LexisNexis FIRSt in BriteSuite.
Disable FEIN SSN for active policy
With the disable_fein_ssn_for_active_policy advanced setting, you can disable the ability to edit the FEIN/SSN once a policy is set to Active.
Manage unwanted quote or application
You can manage unwanted quotes or applications by changing the status from Unsubmitted or Submitted to Rejected.
Set up premium and fee display
Advanced settings allow you to choose how to display premiums and fees while quoting a policy.
Keep the agent on the same screen while quoting
When new business is quoted in the policy wizard, users are directed to separate screens to add and rate property and policy coverages. Advanced settings allow users to stay on the same screen while adding coverages by changing the additional screens to dialog boxes.
Lifecycle Parameters
Lifecycle Parameters in the Policy Lifecycle section are set by BriteCore configuration analysts during configuration and implementation.
Set up processing error notifications
Clients can receive notifications for processing errors.
Set up a threshold limit
Clients can define a threshold of applicable limits against which either an email is sent and/or an approval code is necessary for quoting to continue.
Set up effective date parameters while quoting
Clients can set parameters for how far into the past and/or future that the effective dates for a policy can be set when quoting.
Manage cancellations for converted policies
When a client transitions to 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.
Redirect to wizard policy status
With the advanced setting redirect-to-wizard-policy-status you can designate the policy status(es) that will redirect the user to the policy wizard when the user selects a policy from the Policy Search screen.
Default contact type
With the advanced setting default-contact-type, clients can set the default contact type in the policy wizard to individual or organization.
Notes overview – BriteClaims
Within BriteClaims, you can access Notes from multiple areas. The ability to view, access, and make changes in the Notes section depends on your role and the claim’s status.
Parties overview
The Parties screen manages parties entered throughout the lifecycle of a claim.
Filter the Transactions table in Accounting screen
In the Accounting screen of the claim file and exposure file, you can filter the Transactions table to easily locate specific transactions.
Delay assigning 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.
Manage Cancellation Pending for policies with future effective dates
Discusses how to move a committed policy with a future effective date to cancellation pending and how to carry the Cancellation Pending status to a future (renewal) term.
BriteSuite platform setup guide
Purpose This guide walks administrators through setting up the BriteSuite platform. The BriteSuite platform is built to be as configurable
Add an external adjuster
In BriteClaims, you can add external adjusters to a claim file.
Delete Persistent Builder mapping using Support Tools
When you create a new effective date, you may introduce changes incompatible with your older Lines versions, such as altered category options, different names, etc. This can cause your policies to fail to renew. With Create Persistent Builder Mapping, you can explicitly map the changes in the system.
NxTech Initial Load for Agency using Support Tools
Sometimes, you may need to send an initial load of policies to an agency for download. NxTech Initial Load for Agency is a support tool that helps to automate the process and generates a NxTech file that contains the current state of all policies for a given agency with all transaction codes set to SYN.
Get recent sweep payment/daily cash receipts using Support Tools
With View Recent Receipts, you can generate receipts, such as daily cash, sweep payments, etc.
Set expected recoveries
In personal auto claims, you can set the amount for expected recoveries. Expected recoveries are configurable and can consist of Reinsurance, Subrogation, and Salvage.
Loss run reports
BriteCore now includes loss run report functionality so an agent or agency can create a loss run report for an insured. A loss run is a summary of all the claims that have occurred on a policy over a period of time.
LexisNexis FIRSt
The LexisNexis® Financial Institution Reporting System (FIRSt) solution provides loss payee notification distribution services, helping clients conduct important business processes that support compliance requirements, such as notifying automobile finance companies, auto leasing companies, and mortgage lenders about changes to insurance policies.
Correct IVANS Claim Reports using Support Tools
Occasionally, the IVANS data exports may miss some transactions in the automated XML export. With the Correct IVANS Claim Reports tool you can regenerate a claim report based on the claim and cursor date.
IVANS eDocs Upload tool
Clients can create new file folder names in IVANS by enabling the IVANS eDoc Build Tool. The support tool allows clients to generate new XML files by specifying a date cursor, policy number, and documents to generate and export to IVANS.
Copy underwriting rules using Support Tools
When setting up a new instance of BriteCore, you can expedite the process by using the Copy Underwriting Rules feature to copy underwriting rules to a new effective date, state, and policy type. This saves you time when configuring your insurance products.
Correct a NxTech Report using Support Tools
Occasionally, NxTech reports exports may miss some transactions in the automated XML export. With the Correct a NxTech Report tool, you can regenerate a report based on the date, policy information, and transaction code.
Copy policy types using Support Tools
When setting up a new instance of BriteCore, you can expedite the process by using the Copy Policy Types feature to copy line items from one effective date and state to another effective date, state, and policy type. This saves you time when configuring your insurance products.
Copy line items using Support Tools
When setting up a new instance of BriteCore, you can expedite the process by using the Copy Line Items feature to copy line items from one effective date, state, and policy type to another. This saves you time when configuring your insurance products.
Import a line of business using Support Tools
When setting up a new instance of BriteCore, you can expedite the process by using the Import Line feature to import active policy types and lines of business from one instance of BriteCore to another. This allows you to promote defined insurance products to other environments.
Create Persistent Builder mapping using Support Tools
When you create a new effective date, you may introduce changes incompatible with your older Lines versions, such as altered category options, different names, etc. This can cause your policies to fail to renew. With the Create Persistent Builder support tool, you can explicitly map the changes in the system. This saves you time when configuring your insurance products.
Add a location to a ZIP code using Support Tools
You can use Support Tools to adds a city or county to a ZIP code, which links them in BriteCore.
Borrow coverage
If an insured is involved in an accident in a rented or borrowed vehicle, carriers need to borrow coverage to pay the owner of the rented or borrowed vehicle and to pay associated medical expenses. In BriteClaims, you can follow a series of steps to borrow coverage.
Medical Expense stackable coverage
Some states require stacking, or the combination of coverage limits, for auto insurance. BriteCore offers the ability to stack the Medical Expense coverage, so users can combine the Medical Expense coverage limits for up to four motorized vehicles on an insured’s policy.
Run the nightly auto pay policies process using Support Tools
You can use Support Tools to run the nightly auto pay process and apply automatic payments to eligible policies.
Set up underwriting cancellation times
In accordance with state regulations and business policies, clients can define the number of days a policy is in underwriting cancellation prior to the policy canceling.
Update search results using Support Tools
You can use Support Tools to update a policy’s status if the search results don’t match the policy status of the policy. This tool can also be used with claims, contacts, and properties if needed.
Run the nightly non-pay processes using Support Tools
You can use Support Tools to run the nightly process to place a policy into Cancellation Pending for Non-Payment of Premium, evaluate whether the policy should cancel for Non-Payment of Premium, cancel when appropriate, and generate the corresponding deliverables.
Run the nightly cancel and non-renew policies processes using Support Tools
You can use Support Tools to run the nightly process to finalize cancellation and non-renew policies.
Run the nightly auto renew policies process using Support Tools
You can use Support Tools to run the nightly auto-renew process so you can automatically renew several policies at one time.
Submitted Applications report
The Submitted Applications report is a custom report that displays the Policy Number, Policy Type, Agent/Agency, Agency Number, Effective Date, and Date Submitted for the submitted applications in one day.
Generate documents in the Attachments screen
In both the claim file Attachments screen and the exposure file Attachments screen you can generate documents.
Enable the new UI and BriteSuite navigation
With the global dvanced setting use-bc-ui-nav, you can enable the new UI and BriteSuite navigation.
Search and filter the Claims Activity log
You can search for or filter by criteria to locate and view specific claim activity within the Claims Activity log.
BriteApps: New email confirmation settings
BriteApps email confirmation settings release note.
Damaged Property Details overview
The Damaged Property Details screen consists of the Damaged Property Information section. On the Damaged Property Details screen, you can view detailed information about the damaged property and edit the damaged property information.
Injury Details overview
The Injury Details screen contains information related to an involved party’s injuries.
Configure ISO VINMASTER in BriteSuite
This tutorial walks you through implementing VINMASTER in BriteCore if you wish to write your own plugin. It can also serve as a reference to understand how VINMASTER integrates with BriteSuite.
Edit billing dates
You can edit billing dates for a policy’s current invoice in the Balance Details section of the Billing Overview tab on the Accounts Receivable screen.
BriteLines – Include used_in_rating in Risk Type State
The used_in_rating field, which is now included in both minimal and full risk type states for each field, can be useful for downstream services such as BriteQuote for deciding when a quote must be re-rated.
Set up email notifications for new business
Certain policy activities will trigger email notifications. Clients can designate email recipients using administrative alerts and settings within the Contacts module. Clients can further customize emails with advanced settings.
Google Maps (Onix) overview
BriteSuites is integrated with Google Maps mapping solution. BriteSuites uses Google Maps as a geocoding service. Geocoding refers to locations in terms of geographic latitude and longitude coordinates, which is more accurate than describing a location’s address in terms of street names.
Google Maps setup
BriteSuites is integrated with Google Maps, a mapping solution. BriteSuites uses Google Maps as a geocoding service. Geocoding refers to locations in terms of geographic latitude and longitude coordinates, which is more accurate than describing a location’s address in terms of street names.
SmartyStreets setup
SmartyStreets, an address validation integration, is available with BriteSuites. BriteSuites uses SmartyStreets as a geocoding service.
SmartyStreets overview
BriteSuites is integrated with SmartyStreets, an address validation solution. BriteSuites uses SmartyStreets as a geocoding service. Geocoding refers to locations in terms of geographic latitude and longitude coordinates, which is more accurate than describing a location’s address in terms of street names.
Quoting Template formulas
When defining a Quoting Template rule’s tigger(s) and action(s), there are times you will need to add formulas.
Define a Quoting template rule
In BriteRules, after you create and configure a Quoting Template rule, you need to define the rule’s trigger(s) and action(s).
Configure a Quoting Template rule
In BriteRules, after you create a Quoting Template rule, you need to configure it.
Create a Quoting Template rule
In BriteRules, you can use the Quoting Template to create, configure, and define rules for the quoting process. The first step is to create a rule.
BriteQuote event: bc.quote.renewal_failed
This event is emitted when an asynchronous renewal processing fails.
Risk default naming
With the risk_default_naming advanced setting, clients can choose if the name of the risk will default to Property or Location on the Risks tab of the quote wizard.
Default to application mode on quoting
With the advanced setting default-to-application-mode-on-quoting, users can choose to hide or display the quote/application toggle button that appears in the quote wizard (V2).
Delay cancellation per policy
With the Delay cancellation per policy feature, carriers can provide insureds additional time to pay an outstanding balance without extending the length of coverage.
BriteQuote event: bc.quote.renewal_created
This event is emitted when an asynchronous renewal is processed successfully.
Convert policies at renewal
Clients can manually convert policies from a legacy system to BriteCore when a policy is due for renewal. Only users with the Administrator role have the ability to manually convert policies at renewal.
Show primary property
With the show-primary-property advanced setting, clients can designate a primary property on a multi-property policy.
Set up timeline for Notice of Non-Renewal
In accordance with state regulations, clients can define the number of days prior to policy expiration that a Notice of Non-Renewal must be sent.
Content protection 101
This is an example post with protected content. Public-facing content The Lines module provides a dynamic interface for administrators to set up
Set up Claims email correspondence
Emails are sent by BriteCore or a user. BriteCore can send emails to agents/agencies, claims adjusters, claims supervisors, and staff. Users can send emails to any recipient.
Set up notifications for renewal failures
If a policy doesn’t automatically renew due to a processing error, BriteCore will send an email to designated recipients regarding the failed processing.
Set up renewal business notices
Explains how to set up renewal business notices
Auto renewal
By default, policies renew automatically in daycron based on a client’s renewal timeline configuration. With the advanced setting, auto_renewal, you can disable auto-renewals in daycron.
Endorsements overview
An endorsement is an amendment or change to a policy. Within BriteCore, endorsements are also referred to as revisions.
Step 5 – Add a claimant in the Claims module
A claimant is either a first-party (named insured) claimant or a third-party claimant. When a claim is linked to a policy, the named insured on the policy is considered to be one of the claimants. The named insured will appear on the Contacts tab of the claim under Named Insured. If there are additional claimants associated with the claim, you can add them in the Claimant(s) section of a claim’s Contacts tab.
Set up endorsement summary deliverable
An Endorsement Summary provides an itemized list of changes made during an endorsement or revision.
Reopen an exposure
Exposures closed by mistake can be reopened. Litigation and requests for additional payments may also necessitate reopening an exposure.
Assign claims adjuster to the exposure
In addition to assigning a primary claims adjuster to a claim, you can assign (and re-assign) claims adjusters to the exposure.
Edit Exposure Loss Description
On the Details screen of an exposure file, you can add and edit the Exposure Loss Description.
Prevent creation of multiple open revisions simultaneously
With the prevent-creation-of-multiple-open-revisions-simultaneously advanced setting, you can prevent users from creating duplicate endorsements (revisions).
Add recovery payment from exposure file’s Accounting screen
When a recovery payment is received for an exposure, the payment information can be documented and tracked by creating a recovery receipt within the Exposure Accounting Summary screen.
Generate endorsement summary
With the generate_endorsement_summary advanced setting, you can enable or disable the automatic generation of the Endorsement Summary when an endorsement is committed.
Personally Identifiable Information removed from Aged Accounts Receivable reports
To keep information secure, the Social Security Number (SSN) and Date of Birth columns have been removed from the Aged Accounts Receivable report.
Policy Attachments screen overview
The Attachments screen allows you to locate and manage files for a specific policy. The Attachments screen contains system- and user-generated folders and files.
Manage quoting suspensions
In BriteCore, administrators can add temporary suspensions on an agent’s or agency’s ability to bind a quote, submit an application, quote specific lines of business, or use straight-through processing. Administrators can also edit existing suspensions and delete suspensions.
BriteAPI Tutorial: Create and bind a quote
BriteQuote allows insurers to configure customized quoting and application workflows for targeted user experiences. BriteQuote is the API backend that stores quotes, risks, field answers, coverages, and premiums.
Review and next steps
You should have a solid understanding of the different parts of BriteLines and how they work together. To review what you have learned, you can go through the training again or revisit any of the topics.
Reinstate a policy
With BriteCore, you can reinstate a policy that has been canceled or has the status Cancellation Pending.
Start BriteLines training
In the BriteLines training, you will learn about each part of BriteLines and how they work together. The training pages contain links to documentation for specific tasks.
Initiate FNOL from a policy’s Overview screen
You can initiate an FNOL from a policy’s Overview screen.
Email policy information
You can email policy information to designated recipients from the policy header on a policy’s Overview screen.
View Declaration
You can access and view a policy’s declaration from the policy header on the Overview screen.
Configure LexisNexis Auto Data Prefill in BriteSuite
This tutorial walks you through implementing LexisNexis ADP in BriteCore if you want to write your own plugin. It can also help you understand how LexisNexis ADP integrates with BriteSuite.
Rate Preview
In Rate Preview, you can create scenarios to test, validate, and preview rates directly in BriteLines.
Items
Items are the coverages, fees, and endorsement forms attached to risks. You can add three types of items: Coverages, fees, and endorsements.
Calculations
Calculations are single-line statements that return a numeric result.
Product versioning
In BriteLines, you can version products by effective date, allowing you to make changes to a product without affecting in-force policies. You can publish product versions into production based on a specific effective date.
Rating risks
BriteCore’s rating engine combines risk type details (fields, items, rate tables, and calculations) with quote details (risks, field answers, chosen items) to determine each item’s premium, limits, and deductible.
Data fields
Data fields (fields) define the data that may be collected to rate a risk. The provided values are used for collecting data; creating underwriting rules; and determining the premium, limit, and deductible values.
Rate tables
Rate tables store the data used to map inputs (data fields, other rate tables, or calculations) to outputs (a rate, factor, or anything else).
Lines of Business screen
In BriteLines, you can create new lines of business or edit existing lines. A line of business (LOB) is a classification of insurance business, such as auto, property, or liability. The Lines of Business screen contains all of the existing LOBs.
Products
In BriteLines, products are set up in a product hierarchy based on parent-child relationships, meaning the child inherits data and properties from the parent.
Risk Types
Risk Types are similar to primary exposure line items in classic Lines and contain data fields, rate tables, calculations, and items.
Policy Information
The Policy Information section displays the line’s Risk Types, which include data fields, rate tables, calculations, and items.
Line Overview screen
The Line Overview screen contains the Products and Policy information sections.
Underwriting rule effects added to the Agent Wizard’s Questions screen
We added underwriting rule effects functionality to the Questions screen of V2 Agent Wizard.
Configure LexisNexis C.L.U.E. in BriteSuite
This tutorial walks you through implementing LexisNexis C.L.U.E.in BriteCore if you want to write your own plugin. It also helps you understand how LexisNexis C.L.U.E.integrates with BriteSuite.
Cancel a policy
You can manually cancel a policy from the policy header of a policy’s Overview screen.
Add policy to a claim
Claims can exist without an associated policy in BriteClaims. When an FNOL is submitted without a policy, the resulting claim is tagged with the No Policy tag and the New claim status. The status of a claim without an associated policy can’t be changed from New to Open unless a policy is added to the claim.
Configure LexisNexis National Credit File in BriteSuite
This tutorial walks you through implementing LexisNexis Credit in BriteCore if you want to write your own plugin. It can also help you understand how LexisNexis Credit integrates with BriteSuite.
Assign BriteClaims access permissions
BriteClaims permissions are managed by two systems: BriteRules and BriteAccess. With BriteRules, permissions are based on user role and claim/exposure status. With BriteAccess, permissions are based only on user role. You can assign BriteClaims specific access permissions to a role in BriteAccess.
BriteClaims email notifications
In BriteClaims, specific events can trigger email notifications. When an event occurs, BriteClaims posts that event in BriteEvents. BriteEvents and BriteRules communicate and BriteRules determines if the event triggers an email notification. The email notification will be sent if the event triggers a notification.
Manage contacts: Agents, agencies, and insureds
Insurance companies require a contact management system that stores and updates information about any entity, business, or individual associated with
Rewrite a policy
You can rewrite a policy from the policy header of a policy’s Overview screen. When you rewrite a policy, you can choose to only rewrite the policy, or you can choose to cancel and then rewrite the policy. A new policy ID is assigned to the rewritten policy.
Quote flow overview
The quote flow is a series of steps that a user walks through to quote a policy for potential new business. In BritePolicies and BriteQuote, the quote flow can be customized for each carrier to meet the needs of its organization. In general, the quote flow will consist of screens that gather basic information about the policy and policy type, the named insured(s), additional interests, the risk(s), and the coverages included in the policy. Based on this information, a rate is calculated.
Add and manage claim assignments on the Parties screen
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 Assistant. The Claim Assignments section is the third and final section on the Parties screen.
BriteAPI Tutorial: Add and process payments in BriteCore
Important note on PCI DSS compliance: The Payment Card Industry Data Security Standard (PCI DSS) requires all companies that process,
Property integration vendors
BriteCore supports several property integrations, allowing you to add a variety of functionality.
Change policy’s renewal status to Non-Renew
You can change a policy’s renewal status to Non-Renew from the policy header of the policy’s Overview screen.
Renew a policy manually
You can renew a policy from the policy header of a policy’s Overview screen. You can choose to renew a policy with or without changes.
Commercial integration vendors
BriteCore supports several commercial integrations, allowing you to add a variety of functionality.
Policy History tab
The Policy History tab is the second tab on a policy’s Overview screen. The Policy History tab displays the history of transactions on a policy and a detailed list of changes that occur in each transaction.
Auto integration vendors
BriteCore supports several auto integrations, allowing you to add a variety of functionality.
Policy’s Overview tab
The first tab of a policy’s Overview screen is the Overview tab. The Overview tab provides a summary of the policy, including information about the insureds, the agency, billing, and premium.
Policy header overview
The policy header provides a snapshot of the policy and provides a list of actions you can initiate from the policy header. With the policy header, end users can quickly see which policy they are in.
Delay cancellation per policy
With the Delay cancellation per policy feature, users can delay the policy cancellation date to provide additional time to pay an outstanding balance without extending the effective date of cancellation. A balance must be billed before the user can delay the cancellation date, and the selected cancellation date must be both greater than the original cancellation date and greater than today’s date. When a user delays cancellation, the policy will cancel on the new cancellation date (unless payment is issued) but will use the original cancellation date as the effective cancellation date.
New settings and Documents screen web redesign
New settings and Documents screen web redesign details for BriteApps’s latest release.
Changes to Pending Commissions Payments screen
The Changes to Pending Commissions Payments screen feature impacts manual commission payments, manual adjustments, the Commission Payment Queue, and Agent Commission report(s).
Vehicle Details overview
The Vehicle Details screen contains additional information about the involved vehicle. Each involved vehicle will have a Vehicle Details screen. On this screen, you can manage vehicle information, occupants, damage information, fault information, and, for third-party vehicles, insurance information.
Add an injury
On the Injuries screen of a claim file, you can add additional injuries. When you add an injury, you must be able to add the injury to a party already associated with the claim. If the party isn’t associated with the claim, add the party first.
Underwriting screen
In the Provider Administrator portal, the Underwriting screen in the Quote wizard resembles the Underwriter screen in the Agent portal Quote wizard. Configuration of the Quote wizard and settings will determine if the Underwriting screen appears.
Configure LexisNexis MVR in BriteSuite
You can integrate BriteSuite policies with LexisNexis Motor Vehicle Records (MVR) to automate the method of requesting driving records from all 50 states and the District of Columbia, with additional service for several Canadian provinces and Puerto Rico.
LexisNexis MVR integration allows you to validate the motor vehicle history of potential customers during the quote flow. Automotive insurance providers, agents and underwriters can use the records to determine eligibility.
BritePolicies screen flow
The BritePolicies screen flow is a YAML configuration that provides clients with the ability to customize the policy information tabs and content. The screen flow reduces the need for scrolling and is designed to present information in a clean, read-only view. To edit any information within the policy screen flow, you must create an endorsement.
Configure SmartyStreets in BriteSuite
You can integrate BriteSuite policies with SmartyStreets to validate addresses and standardize them to USPS specifications. This also provides geocoding; geocoding refers to locations using latitude and longitude, which is more accurate than describing a location’s address with street names.
Policy status and revision state overview
Throughout the policy lifecycle, a policy’s status will change, as will a policy’s revision states. The policy status indicates the current phase of the lifecycle a policy is in, and the revision state indicates the phase of revision a policy is in.
Append policy term suffix to quote numbers
When enabled, the append-policy-term-suffix-to-quote-numbers advanced setting adds a policy term suffix to a policy number. The suffix indicates the term of the policy, beginning with -00 and increasing incrementally.
Stripe integration overview
Stripe is a third-party payment processing vendor. With the Stripe integration, you can use Stripe as a payment processing option in BriteCore.
Enable the clue file prefix advanced setting
By default, BriteCore gives all claim data files the same filename: clup_history_T_. The clue_file_prefix advanced setting allows clients to customize the filename of their claim data files.
Generate monthly claims reports
With the LexisNexis C.L.U.E. integration, you can generate monthly claims reports.
Add LexisNexis system tags
In BriteCore, you can tag line items with system tags. Then, you can use tagged line items in conjunction with BriteData to produce clean, powerful reports.
Step 6 – Submit
On the Submit screen, you can review all information entered for the policy and save or submit the policy.
Step 5 – Billing
On the Billing screen, you can determine if the first and future bills are paid separately, add payment information, and select the payment or billing schedule.
Step 4 – Rating
On the Rating screen, you can identify the coverages, items, limits, and deductibles that will be included in the policy, as well as provide additional information about the risk/property. The rate is determined by this information.
Step 3 – Risks
On the Risks screen, you can add property detail information, such as the physical location of the risk/property, images of the risk/property, loss history of the risk/property, and the risk/property mortgagee. The information provided can impact rating or the decision to approve the policy.
Step 2 – Contacts
On the Contacts screen, you can add contacts related to the policy, such as the named insured, agency, and additional interests. Depending on settings, additional contacts can be added.
Step 1 – Policy Setup
In the Quote wizard, you can create quotes for new business and you can migrate policies from a legacy system. The first screen you will complete in the Quote wizard is the Policy Setup screen. The following instructions apply to the default view of the Policy Setup screen. Depending on settings and configuration, your Policy Setup screen’s appearance may vary.
LexisNexis credit scoring integration overview
The LexisNexis National Credit File (NCF) integration provides online consumer credit reports to insurance carriers. An applicant’s financial history can be considered as part of assessing risk for quoting and underwriting purposes.
LexisNexis C.L.U.E. integration overview
The LexisNexis C.L.U.E. (Comprehensive Loss Underwriting Exchange) integration provides property and casualty underwriters with valuable information.
Vehicles overview
Vehicles can be added and managed within the Vehicles screen of a claim. Vehicles added during the FNOL automatically populate the Vehicles screen. You can also add additional insured vehicles, unlisted vehicles of the insured, and claimant vehicles.
Step 8 – Submit claim
When you’re finished adding information in the Injuries screen, you have completed the FNOL workflow. If you’re satisfied with the entries you made throughout the FNOL workflow, navigate to the bottom of the Injuries screen and select Submit.
Step 4 – Vehicles
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.
Invoice Cloud setup
Invoice Cloud is a payment portal that integrates with BriteCore to offer electronic payments, AutoPay, bill presentment, and billing details.
Step 3 – Loss Details
The next step in the FNOL process is to complete the Loss Details screen. On the Loss Details screen, you can add information about the loss description, type of loss, loss location, and onsite services. This step is specific to the line of business or product.
Step 1 – Policy Search
The first step in the FNOL process is to identify the policy the loss event is being filed against. If you don’t have policy information, you can continue the FNOL workflow without attaching a policy to the FNOL. To access the Policy Search screen of the FNOL process, select + New FNOL on the FNOL Drafts screen or select + New Claim on the Claims Home screen.
Configure Google Maps in BriteSuite
This tutorial walks you through implementing GoogleMaps in BriteCore if you wish to write your own plugin. It can also serve as a reference to understand how GoogleMaps integrates with BriteSuites.
BriteCore Support
BriteCore standard support hours are 8:00 a.m. through 5:00 p.m. Central Time. You can reach support the Help button in the BriteCore application, Zendesk tickets, email, phone, and community forum messaging.
Our critical defect line is available 24/7.
Additionally, BriteCore customers receive an escalation chart with direct email addresses and cell phone numbers for the support team and senior leaders.
Configuration questionnaires for implementation
Configuration questionnaires for implementation.
Classic Quotes overview
The Quote wizard provides a dynamic interface for agents and internal staff 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. The Quote wizard can be accessed from the Agent portal and the Provider Administrator portal.
BriteAPI Tutorial: Create and bind a quote – New
BriteQuote allows insurers to configure customized quoting and application workflows for targeted user experiences. BriteQuote is the API backend that stores quotes, risks, field answers, coverages, and premiums.
Remove underwriting questions
If you no longer want an underwriting question for an effective date or specific policy type, you can remove it.
Add underwriting questions to a policy type
In classic Lines, you can add Yes/No underwriting questions to a specific policy type.
Void refund payments
With the void_refund_payments advanced setting, you can display or hide the Void button on return premium entries in the Account History table on the Accounts Receivable screen.
Manage adjuster groups and user roles
When you assign an adjuster, you must search for an adjuster or select an adjuster from a menu of names. BriteClaims users who belong to the Adjuster group are available to be assigned as an adjuster.
Add underwriting questions to an effective date
In classic Lines, you can add Yes/No underwriting questions to an effective date. Adding an underwriting question to an effective date applies it to all of the policy types with that effective date.
How quotes are set up in BriteCore
An overview on how quotes are set up in BriteCore.
Enable LexisNexis credit score reports for international addresses
BriteCore sends LexisNexis conditional data based upon whether the contact is a person or business and if the contact is within the United States. The allow-credit-score-report-for-international-address advanced setting allows you to retrieve credit scores for international addresses.
Send conditional credit scoring data to LexisNexis
BriteCore sends LexisNexis conditional data based upon whether the contact is a person or business and if the contact is within the United States. The required fields Name, Risk Address, and DOB are sent to LexisNexis.
LexisNexis FIRSt setup
In BriteSuite, LexisNexis® Financial Institution Reporting System (FIRSt) sends updated personal auto policy information to the appropriate lienholder(s). FIRSt sends updated policy data from BriteCore to LexisNexis, where it is distributed to the lienholders.
LexisNexis credit scoring setup
LexisNexis’s National Credit File (NCF) provides online consumer credit reports to insurance carriers. An applicant’s financial history 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.
LexisNexis FIRSt integration overview
The LexisNexis® Financial Institution Reporting System (FIRSt) solution provides loss payee notification distribution services, helping clients conduct important business processes that support compliance requirements, such as notifying automobile finance companies, auto leasing companies, and mortgage lenders about changes to insurance policies.
Enable the optional SSN setting for LexisNexis
BriteCore sends LexisNexis conditional data based upon whether the contact is a person or business and if the contact is within the United States. The lexis-nexis-credit-score-report-requires-ssn advanced setting allows you to determine if the SSN is necessary to retrieve a credit score from LexisNexis.
Set up and generate an Adverse Action Letter (Insurance Scoring Notification)
The Fair Credit Reporting Act requires an Adverse Action Letter be sent to insureds whose insurance coverage is adversely affected as a result of the information in their credit report.
Data fields overview
Data fields define the data that may be collected to rate a risk. The provided values are used for collecting data; creating underwriting rules; and determining the premium, limit, and deductible values.
BriteSuite permissions by product line
Classic BriteCore allows you to control which agencies can write each line of business (LOB) or product that is active on their site. We extended this capability to BriteLines products and classic Lines LOBs for clients using classic BriteCore, BriteSuite, or a combination of both.
Product settings
Product settings are configurable settings that apply across all of the products within a given hierarchy.
BriteLines – Product Export improvements
The product template download process now runs asynchronously, reducing the time it takes to export a product template. Since product exports won’t time out, users can initiate an export, leave the page, and return later. The new Product Exports page displays exported products.
Classic quote wizard configuration guide
This guide walks you through the classic quote wizard configuration.
Data field validators
BriteLines provides field validators that you can define when creating a field. Field validators ensure that data entered while creating a quote matches the expected pattern.
Pro-rata premium calculations
When a premium-bearing change is made to a policy mid-term, affected items must prorate the premium against the term.
Calculation variables
BriteCore’s rating engine provides several variables you can use in your calculations.
Write calculations
In BriteLines, you can write calculations, which are single-line statements that return a numeric result.
Commission reports
BriteCore offers four out-of-the-box reports pertaining to commissions as summarized in the table below. Reports are accessed in the Reports module.
Calculation functions
BriteCore’s rating engine provides several functions you can use in your calculations.
Classic BriteCore environment setup guide
This guide walks SI partners through setting up the classic BriteCore platform. The classic BriteCore platform is built to be highly configurable out of the box. However, there are some limitations for SI partners. In this guide, we will discuss the limitations and identify ways to work around them to bolster the partnership experience.
Access payments in the Payment Log
On the Payment Log screen, you can use the filters to view payments received for either all policies within a specific date range or a named insured within a specific date range.
Introducing LexisNexis FIRSt integration with BriteSuites services
Introducing the LexisNexis Financial Institution Report System (FIRSt) integration. Carriers using BriteCore’s BriteSuite services can now integrate LexisNexis FIRSt for Personal Auto policies.
Set up barcodes on invoices
Invoice barcodes can increase efficiency for clients creating batch payment entries. When a barcode is on an invoice and the invoice is returned with payment to the client, then the invoice barcode can be scanned and can automatically create a batch payment entry.
Make a payment to rescind a policy pending cancellation
You can rescind a policy with the Cancellation Pending Non-Payment of Premium status by making a payment to bring the account current.
Changes to Pending Commissions Payments screen
With this feature, you will be able to make manual commission adjustments on all commissionable policies per agent or agency for the most recent month, until the Commissions Payment Queue is cleared or processed. You will be able to make multiple adjustments, positive or negative, per agent or agency at one time. If manual commission adjustments are made, you will be able to regenerate an Agent Commission Report from the Pending Commissions Payments screen, and the Agent Commission Report will reflect the manual adjustment change.
Don’t allow PO Box as risk address
With the feature Don’t allow PO Box as risk address, you can’t add a PO box as a risk address or change a risk address to a PO box.
Transfer return premium
You can transfer return premium from one policy to another.
Edit return premium
From the return premium queue, you can edit who the return premium will be issued to.
Upload CSV to Commission Payment Queue
If commission payments aren’t automatically pulled into the Commission Payment Queue, you will need to upload a .csv of commission payments before you can process the commission payments.
Access Electronic Payment Report
The Electronic Payment Report contains all electronic payments made on a specified date.
View policy information from the Payment Log
In the Payment Log, you can view details about payments made within a specified date range. You can also view information about the policies that payments are issued on.
Search and filter the Payment Log
You can locate specific payments or narrow the Payment Log results by using the search and/or filter functions. The Filter From and Filter To boxes must be filled in, but entering search criteria is optional.
Payment Log overview
The Payment Log, accessed in the Provider Administrator portal, contains information about payments made on premium.
Access Sweep Report
You can access the Sweep Report from the Schedule Sweep screen of the Payments module. The Sweep Report can contain information about all sweep payments made within a designated date range by agents or agencies associated with the insurance carrier. The Sweep Report can also be configured to provide more limited information by allowing the agent or agency running the sweep report to view only the sweep payments made by that agent or agency.
Access Detailed Transaction Report
You can access the Detailed Transaction Report from the Schedule Sweep screen of the Payments module.
Manage the Sweep Queue
In the Sweep Queue of the Payments module, you can remove and submit payments.
Submit a sweep payment
In the Agent portal, you can submit manual payments through Agent Sweep. Depending on settings, Agent Sweep allows you to add single or multiple payments to the Sweep Queue.
Accounts Receivable overview – Agent portal
The Accounts Receivable screen in the Agent portal displays the policy header, the Billing Overview tab, and the Billing Setup tab. Information for a specific policy is organized between the two tabs: Billing Overview and Billing Setup.
Manage convenience fees with Invoice Cloud
With the Invoice Cloud integration, you can add a convenience fee for ACH and credit card payments. You can add, edit, or remove the fees at any time.
Change payment methods on an existing policy
Policyholders can pay their premium manually or automatically.
Make a down payment with a credit card
Agents can make a down payment with a credit card on the initial invoice in the Policies module.
Make an ACH down payment
Agents can make an ACH down payment on the initial invoice in the Policies module.
Invoice Cloud integration functionality
In BriteCore, the Invoice Cloud integration provides functionality for making and managing payments.
Enable Invoice Cloud
After setting up the Invoice Cloud integration on the Vendors screen, you need to enable the use-v2 advanced setting for the integration to function.
Invoice Cloud overview
Invoice Cloud is a secure electronic bill presentment and payment solution that administrators, agents, and customers can use. Administrators and agents will use Invoice Cloud only as a payment processor, but customers will use it for the entire electronic billing experience.
Updates to the Policyholder and Provider Administrator portals and web redesign
Latest release notes for BriteApps.
Don’t allow null Loss Date
With the Don’t allow null Loss Date feature, users in the Provider Administrator portal won’t be able to change a claim’s status to Open if the Loss Date isn’t entered for the claim.
Make an ACH payment
In the Policies module, agents can make an ACH payment on a policy.
Make a credit card payment
In the Policies module, agents can use a credit card to make a payment on a policy.
Manage the Daily Cash Receipt deposit list
When manual payments are made on a policy and you add these payments on the Daily Cash Receipt screen, the payments populate in the deposit list. From the deposit list, you can view policy information, access a policy’s Accounts Receivable screen, remove a payment, and process the deposit receipt.
Submit a manual payment
In the Provider Administrator portal, you can submit manual payments on the Daily Cash Receipt screen.
Make a payment
You can initiate payments on single policies or on policy groups from the Accounts Receivable screen in both the Provider Administrator and Agent portals.
Edit the initial bill contact
By default, the Initial Bill Contact section populates with the information selected in the Recurring Billing Section. You can’t edit the Initial Bill Contact section unless you choose to send the initial bill to a different contact.
Set up the recurring billing contact
You can set up recurring billing for a policy on the Billing Setup tab of the Accounts Receivable screen.
View future invoices
By default, you can view current and previous invoices, but not future invoices, in the Account History table of the Accounts Receivable screen. BriteCore provides functionality so you can view future invoices in the Account History table.
View revision history
You can view the revision history of a policy from the Accounts Receivable screen in both the Provider Administrator portal and Agent portals.
Write off custom fee
On the Accounts Receivable screen, you can write off custom fees billed to a policy.
View installment schedule
You can view and open the installment schedule from two separate locations on the Billing Overview tab of the Accounts Receivable screen. The Installment Schedule link appears in the Balance Details section and the Account History section.
View and access claim information from Accounts Receivable screen
You can view the total number of claims filed against a policy, view an overview of claim information, and access a claim from the policy’s Accounts Receivable screen. The Claims field can be found in the Policy Details section of the Billing Overview tab.
Manage non-pays
The Total Non-Pay(s) field captures the total number of non-pays on a policy. You can find the Total Non-Pays field in the Policy Details section of the Billing Overview tab on the Accounts Receivable screen. The number included in the Total Non-Pay(s) field includes any legacy non-pays manually added.
Access linked policies
When you link policies together to form a policy group, you can access a linked policy in the policy group from another linked policy in the same policy group. You can access linked policies from the policy header on the Overview screens or from the policy header on the Accounts Receivable screen.
View contact information from the Accounts Receivable screen
In the Provider Administrator portal, you can view and access contact information from a policy’s Accounts Receivable screen.
Supported AWS services
BriteCore’s cloud-native platform is designed for easy access from any internet-capable device, efficient management and support, excellent performance and scalability, and resilience in the face of business disruptions.
FNOL Drafts overview
The FNOL Drafts screen provides the ability to create a new FNOL and filter the FNOL Drafts list to easily locate the draft you want to access. The FNOL Drafts screen also displays a list of all FNOL drafts with details about each loss.
Policy Lifecycle – Expiration settings
Once you select your state and Lifecycle Parameters, you can configure the Reinstatement settings.
Policy Lifecycle – Reinstatement settings
Once you select your state and Lifecycle Parameters, you can configure the Reinstatement settings.
Policy Lifecycle – Continuation setting
Once you select your state and Lifecycle Parameters, you can configure the Continuation setting.
Policy Lifecycle – Non-Renew settings
Once you select your state and Lifecycle Parameters, you can configure the Non-Renew settings.
Policies Contacts settings
Configure Contacts in the Policies module settings.
Policies options setting: Disable Notes Edit
With the Disable Notes Edit setting, you can establish a time limit for editing a note after it’s created.
Policy Lifecycle – Cancellation settings
Once you select your state and Lifecycle Parameters, you can configure the Cancellation settings.
Vendor integration GitHub resources
The links on this page are internal-only resources. You must have the proper login credentials to access the links on this page.
Show previous credits and debits
A setting allows staff (Provider Administrator portal) and agents (Agent portal) to view a previous term’s credit or debit in the Account History table of a policy’s Accounts Receivable screen.
Display revision history ar agent
With the advanced setting display_revision_history_ar_agent, you can display or hide the Show Revision History link in the Agent portal.
Display revision history ar
With the advanced setting display_revision_history_ar, you can display or hide the Show Revision History link in the Provider Administrator portal.
Policy Lifecycle – Non-pay settings
Once you select your state and Lifecycle Parameters, you can configure the Non-Pay settings.
Remove namespaces and tags
After you add namespaces or tags to a rule, you can remove them.
Policy Lifecycle – Payment settings
Once you select your state and Lifecycle Parameters, you can configure the Payment settings.
Add or edit a rule description
Each rule needs to have a description to articulate the rule’s purpose and function. If a rule doesn’t have a description, you can add one. If you need to change an existing rule description, you can edit it.
View STP templates
In BriteRules, a template is a predefined rule with a set of arguments that can be configured. If you want to see if any of the available STP templates fit your needs, you can view them in the Quoting Form Behavior project.
Enable Straight Through Processing (STP)
After you set up your STP rules, you need to enable the straight-through-processing advanced setting to turn on STP functionality.
Import a project
In BriteRules, you can export a project and then import it into another environment.
Export a project
In BriteRules, you can export a project with or without dependencies.
Manage rules effective dates
You can manage existing rules effective dates with the following actions: Edit, Publish, Revert to Draft (available only for published effective dates), and Create Deployable.
Deploy a rule to the master branch
Once you create a rule, you can deploy it to BriteCore’s master branch.
Create classic STP rules
In classic BriteCore, you have to write STP rules in Python code in the code repository. In BriteRules, you can create STP rules directly from the user interface.
Deploy project versions
In BriteRules, you can deploy an existing product package to a production site or a test site.
Create a deployable project version from an effective date
In BriteRules, deployable project versions are set up by effective dates and labeled by tags. If you want to deploy a project version based on a new effective date, you need to create a deployable project version based on the new effective date.
BriteRules overview
BriteRules integrates with multiple BriteCore products to create rules which automate system decisions. All rules use data from other products received via API calls.
Classic quoting templates
When creating a classic quoting rule in BriteRules, you will need to choose a template, which includes scope formula items and formula syntax.
Add a namespace to a rule
A namespace is a hierarchical definition that defines the context in which a rule is applied.
Assign a rule to a line of business
In BriteRules, you can assign a rule to a line of business by adding the line of business as a namespace.
Processing settings
You can set up Processing options under the Policies settings.
Attachments settings
You can select the Attachments options under Policies settings.
Set up policy lifecycle numbering
Policy numbering allows you to link a policy to a unique ID.
Accounts Receivable options
You can define policies term lengths by state and policy type.
Send billing invoice outside of a policy term
BriteCore’s default billing behavior is to bill for the current premium due on a policy within the policy’s current policy term. There are cases when you must bill outside the current policy term for the current premium due.
Add new contact as a party – Individual
The Add
Make a payment from exposure file’s Accounting screen
You can issue payments on a claim from the exposure file’s Accounting screen. To issue a payment, reserves must first be set. See Set reserves from exposure. The amount of payment can’t exceed the remaining reserve amount.
Commit revisions
When BriteCore users finish modifying a policy revision, they can commit the revision and finalize the changes to the policy.
Policy Lifecycle – Billing Options settings
Once you have selected your state and Lifecycle Parameters, you can configure the Billing Options settings.
Set up voided return premium
Clients can display a Void button on return premiums that have been exported from BriteCore.
Set up minimum return premium threshold
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.
Manually issue a return premium on a policy with a credit
You can manually issue return premiums on a policy with a credit.
DayCron/Nightly processing
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.
Asynchronous revisions
With the new Asynchronous revisions feature, users who process renewal revisions can process a manual renewal revision as a background job, and agents can process new business as a background job.
Policy Lifecycle – Billing Schedules settings
Once you have configured the Billing Options settings, you can set up your billing schedules.
Policy Lifecycle – Get started
When setting up the Policy Lifecycle, you will need to configure the settings in the following sections: Choose a State, Lifecycle Parameters, Billing, Payment, Non-Pay, Cancellation, Non-Renew, Continuation, Reinstatement, and Expiration.
Policy Lifecycle – Write-Off Reasons
Once you set up your billing schedules, you can add the write-off reasons you want to provide as options.
Choose a State and Lifecycle Parameters
To begin setting up the Policy Lifecycle, you need to configure the following sections: Choose a State and Lifecycle Parameters.
Issue a return premium on a policy without a credit
You can issue a return premium on a policy without a credit using Support Tools.
Export return premiums
Return premiums are exported from a central queue and can be exported to any vendor of a client’s choosing, including QuickBooks and Intaact.
BriteRules Projects overview
In BriteRules, Projects are groups of rules for a particular process.
Create a rules effective date
Effective dates for rules serve as historical records of changes over time. An effective date ties a rule to a particular date in time.
Manage negative commissions
Negative commissions occur when the sum of all monthly transactions for an agency net to less than $0.
Google Maps and SmartyStreets integrations
Currently, BriteSuite isn’t integrated with geocoding services. To change that, we have added two new vendor integration services: GoogleMaps and SmartyStreets.
Resend a commission report (statement)
You can resend commission reports (statements) after they have been emailed or mailed.
Pay monthly and contingent commissions electronically
Monthly and contingent commissions can be paid electronically or manually.
Policies settings – CAT Data
In BriteCore, Policies has the following module-specific setting: CAT Data Model.
BriteCore design system
Our Design team ensures BriteCore’s complex workflows are easy to understand and use. The BriteCore design system site provides an in-depth look at what goes into designing BritreCore’s products.
Issue a Negative Commission Report (statement)
When an agency has a negative commission balance, the agency will need to be informed so the negative balance can be addressed. An agency is informed about the negative commission balance through the Negative Commission Report (statement).
Enter manual adjustments
Manual adjustments are for entering a payment received from an agency against a negative balance.
Display revision history on the Accounts Receivable screen
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.
Show change of address all invoices
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).
Cancel invoice bill for
The cancel_invoice_bill_for advanced setting allows you to configure the type of premium you want the Cancellation Billing Statement to bill for: adjusted, earned, or unearned.
Commissions overview
Commission is the compensation due to an agent or agency in exchange for the development of new business or maintenance of existing business. A commission can be paid in one of two ways: paid on written premium or paid on paid premium.
Use wizard
With the Billing advanced setting use-wizard, you can use the new policy wizard in BriteCore.
Gen3 agent accounts receivable page
With the Billing advanced setting gen3-agent-accounts-receivable-page, you can display the new Accounts Receivable screen if this setting is enabled.
Agent portal setup overview
To set up the Agent portal, complete the following processes: enable the BriteQuote Policy Wizard, configure the Agent portal settings, add Agent Dashboard text, and turn on the Agency Dashboard.
Turn on the Agency Dashboard
Once you have enabled the BriteQuote Policy Wizard and configured the Agent portal, you need to turn on the Agency Dashboard.
Enable the BriteQuote Policy Wizard
Before you can configure the Agent portal, you must enable the BriteQuote Policy Wizard through the use-wizard advanced setting.
Un/Underinsured Motorist policy limits
If a third-party claimant is uninsured or underinsured, you can set reserves and manage payments based on the established uninsured/underinsured coverages.
Allow agents to make agency payments
With the advanced setting allow-agents-to-make-agency-payments, clients can enable all agents associated with an agency to make payments using the agency’s sweep account, whether or not an agency is listed as an agent’s primary agency.
Agent portal module-specific settings overview
In BriteCore, the Agent portal has the following module-specific settings sections: Payment, Binding Authority, Options, Terms, BriteQuote Suspensions, and Agent Dashboard Text.
Agent portal – Options settings
In BriteCore’s settings, you can configure the Agent portal to suit your needs. In the Options settings section, you can select a variety of settings to customize the Agent portal setup.
Agent portal – Terms and BriteQuote Suspensions
In BriteCore’s settings, you can configure the Agent portal to suit your needs. In the Terms settings section, you can select policy term lengths. In the BriteQuote Suspensions settings section, you can set up BriteQuote suspensions.
Agent portal – Binding Authority settings
In BriteCore’s settings, you can configure the Agent portal to suit your needs. In the Binding Authority settings section, you can select how you want to handle unbound applications.
Agent portal – Payment settings
In BriteCore’s settings, you can configure the Agent portal to suit your needs. In the Payment settings section, you can select what an agent must include when submitting a policy and any exclusions that apply.
Policies module-specific settings overview
In BriteCore, the Policies module has the following categories of module-specific settings: Policy Lifecycle, Options, Contacts, Policy Numbers, Terms, CAT Data, Fees, Accounts Receivable, Processing, and Attachments.
Agent portal: New Accounts Receivable screen
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.
Renewal line item utility
In quotes, the renewal line item utility removes the manual process required to add or change a coverage that is applicable to all policies during renewal. The utility reduces efforts to manually locate and update all of the policies from requesting agencies.
Turn off Protection Class lookup at renewal
Currently, the fire protection class lookup is based only on whether or not the vendor is enabled. We created an advanced setting that allows you to turn off Protection Class calls at renewal.
Add an underwriting rule for renewal only
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.
BriteCore’s release schedule and processes
A description of BriteCore’s release schedules and processes.
Enable new policy search
With the Policies advanced setting policy-go-to, you can set access to policy at the agent or agency level.
Policy go to
With the Policies advanced setting policy-go-to, you can set access to policy at the agent or agency level.
Manage Cancellation Billing Statements
Several settings impact billing statements. Many settings directly impact the Cancellation Billing Statement.
Set up new business payments
Payment and billing requirements for policy applications are managed within Settings > Modules > Agent Portal.
Set up billing statements (invoices)
Throughout the course of business, you can use various billing statement types. You can set up and customize your billing statements with BriteCore.
Send commission reports (statements)
Commission reports are generated at the beginning of each month and capture the commission earned for the previous month’s business. Commission reports can be sent electronically or by mail.
Account information overview
Overview of the account information screen.
Allow commit revision at old led
With the Policies advanced setting allow-commit-revision-at-old-led, you can choose to allow old lines effective date policy revisions.
Lines settings – Policy Annual Premium Rounding
In BriteCore, Lines has the following module-specific settings under Policy Annual Premium Rounding: None, Round Policy Annual Premium to the Nearest Dollar, and Round Policy Annual Premium Up to the Nearest Dollar.
Lines settings – Persistent Builder Options
In BriteCore, Lines has the following module-specific settings under Persistent Builder Options: Exclude Supplemental Questions and Derive deductible selection when previous selection is removed.
Lines module-specific settings overview
In BriteCore, the Lines module has the following categories of module-specific settings: Options, Persistent Builder Options, and Policy Annual Premium Rounding.
Lines settings – Options
In BriteCore, Lines has the following module-specific setting: Blank Category Default.
Module-specific settings overview
In BriteCore’s Settings module, you can access module-specific settings for the following modules: Contacts, Lines, Policies, Claims, and Agent portal.
Revert to Inherited
All entities with an Overridden inheritance status can re-establish the inheritance connection with the parent product, meaning the data will be updated to be the same as the parent product.
Product inheritance overview
Models can share common definition ancestors through product inheritance.
Product versioning overview
In BriteLines, you can version products by effective date, allowing you to make changes to a product without affecting in-force policies.
View archived product versions
Once you archive a product version, it no longer displays in the version dropdown list, but you can still view it.
Enable carrying a payment method across policy terms
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.
Agency portal: Application submission status
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
BriteApps: Web version redesign and Provider Administrator and Policyholder Portal updates.
Risk name templates overview
You can use risk name templates to give a risk an easier-to-read name.
Supported web browsers
BriteCore supports the following web browsers: Chrome, Firefox, and Safari.
Use unbound options
The use-unbound-options advanced setting can be used to display multiple unbound options on the Submit screen of an application/quote in the Quote wizard.
Risk querying
Sometimes, in calculations, we need to perform some complex operations, such as making decisions by looking into all child risks, returning the sum of bodilyInjury premium across all child risks, or finding out how many child risks exist for a given risk.
Risk type hierarchy
Risk type hierarchy is based on nested parent-child relationships.
Allow auto-payments on any amount
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.
Track check numbers
Return Premium check numbers can be counted incrementally starting from 0.
Rate table sorting
You can sort rate table columns in ascending or descending order.
Rate tables overview
Rate tables store the data used to map inputs (data fields, other rate tables, or calculations) to outputs (a rate, factor, or anything else).