18 February 2019

Links in BriteCore Redirect to BriteWiki

  • Any links in BriteCore that used to redirect to the support site will now redirect to the BriteWiki.

Restrict Users From Editing Agency Contact Names

  • Within the Administrative Portal, you may not want some of your staff changing the names of agents, agencies and agency groups. The britecore/contacts/storeContactName permission allows you to control who can edit agent, agency and agency group names.

Cross-Term Previous Balances Note

  • Cross-Term previous debits and credits are displayed on the Renewal Billing Statement under Previous Balance.

Determine Line Item Sort Order on the Declaration

  • You can choose the sort order of line items on the Declaration via the use_only_LED_rate_item_sort_order_in_dec advanced setting. This setting only applies to the Optional Items section of the Declaration.
    • False (Default): BriteCore sorts the items in the declaration twice.
      • First, the system sorts by Line Item Type, which will group them by those types.
      • After Line Items are grouped by type, the system sorts them by the line item's sort order defined for each specific line in the Lines area.
    • True: The system ignores the first sorting step and only sorts items by the sort order defined in the Lines area.

Review Number Prior to Application Submission Advanced Setting

  • The review_number_prior_to_application_submission allows you to determine whether the quote number is change to a policy number before or after submission.
    • True: The quote number won't be changed until submission.
    • False: The quote number will be changed to the policy number during quoting, prior to submission.

Omit Automatically-Generated Signature Date

  • By default, when an application for new business is created, the date the application was generated shows on the signature line. Having BriteCore automatically set the signature date can be problematic because the automatically created date is often prior to when the insured and agent legally signs the document. The omit-automatic-signature-date advanced setting prevents the system from pre-filling the date on the policy application.
    • False (Default): The date the application was generated automatically prefills.
    • True: The enabled signature blocks in any deliverable will no longer show the automatic populated signature date.

11 February 2019

Set a Default SLP for Primary Contact

  • Administrators can set a default Surplus Lines Producer (SLP) for a Primary Carrier contact. Configuring the default will enable users to use the SLP agencies in BriteCore as a primary contact.

Add All Agencies to (or Remove From) a Contact

  • The allow-add-all-active-agencies advanced setting adds the options to Add all Active Agencies to this Contact and Remove all Agencies from this Contact in the Role > Agencies section within a contact.
  • Adding all active agencies to a contact is useful in situations where a carrier has a third-party provider, such as a Claims Provider, who needs to be associated with all agencies in order to provide services within the Agent Portal.

Hide Calculation Line Items from IVANS XML Vendor Report

  • Calculation line items are typically used to facilitate complex calculations. As such, calculation line items do not need to appear in the XML of the IVANS report. Calculation line items can be filtered out of the report via the ivans-downloads-export-calculation-items advanced setting.

MVR Reports Attachment

  • The ISO Motor Vehicle Reports (MVRs) are used to write auto property damage lines of business. The MVRs provide information about Drivers, such as license status, incidents they have participated in, and age.
  • When created, the report is attached to the insured’s contact within the Contacts module as a PDF. Having the full MVR report attached to the contact, rather than the policy, is helpful when writing umbrella policies, for example.

Determine If The Policy Is In Force Before Canceling for Non-Pay

  • When a policy has never been issued, BriteCore will not attempt to cancel the policy when a payment is NSFed.
  • While processing the NSF, you can adjust the Due Date and Cancel Date so the policy will not immediately cancel when/if issued.

4 February 2019

Assess Reinstatement Fee for Expired Policy

  • Clients may charge a fee when reinstating expired policies by setting a value in the Dollar amount accessed when an expired policy is reinstated box on the Reinstatement tab in the Policy Lifecycle screen. By default, the fee is $0.00 for reinstatement.

Return Premium Check Number Available in Reports

  • To improve reporting, Return Premium Check Number has been added as an option in the BriteData Report Builder. Return Premium Check Number works well alongside Return Premium Policy Number and Return Premium Amount.

APO Addresses Available in the State Dropdown Menu for Electronic Billing

  • Army Post Office (APO) addresses are available in the State dropdown menu for electronic payments. The APO addresses are:
    • AE for Europe, Middle East, Africa, and Canada
    • AP for Pacific
    • AA for Americas excluding Canada

Print Application Permission Rule

  • Previously, the Print Application and Submit Application buttons were tied to the same permission rule, agent/policies/submitQuote. If a user did not have permission to submit a quote, the user could not print an application.
  • The agent/policies/printApplication permission rule has been added to separate these functions. Now, a user can have permission to print an application without also having permission to submit a quote.

28 January 2019

Add a Catastrophe (CAT)

  • Two advanced settings control attaching a Catastrophe (CAT) to a claim:
    • allow-cat-auto-assign, default False
    • automatically-fill-loss-cause, default True
  • If the values are in default, Britecore will prompt a CAT suggestion and, if that CAT is selected, the loss causes will be filled with the CAT related loss causes.
    • If the allow-cat-auto-assign is set to True, Britecore will assign the CAT to that Claim without any prompt.
    • If automatically-fill-loss-cause is set to False, Britecore will not fill loss causes related to the CAT.

Added Due Date to Accounting DataFrame and Accounting Details Report

  • Due Date (Invoice Due Date) has been added to the BriteData Report Builder in the Accounting Data Report to assist with accounts billed but not collected (Premium In Course of Collection that is past due).

21 January 2019

Decimal and Integer Validation Parameters

  • A Lines Administrator may require additional validation parameters when setting up modifications (such as Schedule Mod, Experience Mod, and Anniversary Rating Mod) to get the exact values necessary without using workarounds. To meet this need, Positive or Negative Decimal Number and Positive or Negative Integer (less or greater than 0) have been added as validation parameters.
    • For Positive or Negative Decimal Number, users must include a leading zero. For example, an entry of 0.987 works correctly but .987 does not.
    • For Positive or Negative Integer (less or greater than 0), a user must enter a positive or negative number other than zero.

Set Up ISO Verisk - 360Value: Select Home Type

  • For 360Valuations, users select the home type to receive a more targeted valuation for underwriting.
  • Users must select among 1-4 Families, Condo IU and Manufactured/Mobile.

Do Not Trigger Persistent Builder for Newly-Added Category Object

  • The Do not trigger Persistent Builder for newly-added Category object setting available during Line Item setup allows users to prevent trigger Persist Builder for cases, such as:
    • Lines setup where in one effective date there exists a line item (A. Residence) on a policy type (Dwelling) that has categories in its rate chain.
    • Within an effective date, a line item (e.g., Coverage A) does not have categories. A new effective date is created and categories are added to the Coverage A line item.

Edit Line Item - Save without Exiting

  • The Line Item screen of a policy has been updated with a Save button instead of the Save and Exit button.
    • Rather than being redirected to the Policy Type screen when users click Save, they will remain on the Edit Line Item Screen. The warnings and popups remain unchanged.
    • When users click the Cancel button, they will be redirected back to the Policy Type screen.

Claim Payment Check Number in Reports

  • Claim Number and Claim Payment Check Number have been added to the BriteData Report Builder to improve accounting and record keeping for Claims transactions.

14 January 2018

Create Custom Quoting Limit Threshold Error Message

  • The limit-threshold-submission-error advanced setting allows users to create a custom error message that will be displayed if an agent tries to submit an application that exceeds the quoting limit threshold.

Use Comma Separated List for Underwriting Rules

  • When creating an underwriting rule, users can now enter either a range (i.e. 0-50000) or comma separated values (i.e. 20000,30000,40000,50000) for the limit under Trigger.

How to Access BriteCore's Data Dictionary

  • Data frames (data dictionaries) contain data from one or more database tables. At present, BriteCore produces two categories of data: data frames and prepared data frames (data dictionaries). These are stored as CSV files to allow manipulation via other tools, such as Excel and Jupyter.
  • To access the Data Dictionary,
    1. Log in as an administrator
    2. Navigate to Reports
    3. Click Data Dictionary

Customize Processed FNOL or Claims Email Body

  • Users can customize the body of a FNOL email or claim email that is sent to the Agent when a claim has been processed.
  • Variables, such as {reserve} and {cause_of_loss}, will be replaced with the actual values from each processed claim. The Help link gives users more info on adding variables to the email.

Link to Payment Methods

  • In the Administrative Portal, users can click on the Payment Details link on the Accounts Receivable screen to quickly navigate to the Bill Whom's payment method.

7 January 2019

Insured Name Requirement Option for 360 Value Reports

  • The Require Insured Name checkbox on Settings > Vendors > 360 Value controls whether or not a Named Insured is required to pull a 360Value report on a policy. If the checkbox is checked, a Named Insured must be included in the request report.

Private Folder Upload Notes Setting

  • The private_folder_upload_notes advanced setting determines whether or not notes will be created when a file is uploaded to a private folder.
    • False (Default): Notes will not be created when a file is uploaded to a private folder.
    • True: A note will be created when a file is uploaded to a private folder.

31 December 2018

Display the Agency Sweep Account on the Accounts Receivable Screen

  • The allow-sweep-payments-in-billing-setup advanced setting allows clients to determine whether or not to include the agency sweep account in the Payment Method section of the Accounts Receivable screen of the Administrative Portal.
  • This setting is False by default. When this setting is False the agency sweep account is not included in the Payment Method section, which ensures insurance staff do not inadvertently select the agency's sweep account for auto payment on future invoices.

Show/Hide Duplicate Addresses on Inspection Due Report

  • Clients may choose to show or hide duplicate addresses for the same policy on the Inspections Due report. When the inspections-due-omit-addr-dupes-by-policy advanced setting is set to:
    • True: Only duplicated addresses on the same policy are hidden on the Inspections Due report. Addresses that are duplicated on different properties will show on the report.
    • False (Default): All duplicated addresses will be hidden on the Inspections Due report.

24 December 2018

Prevent Multiple Open Revisions

  • The prevent-creation-of-multiple-open-revisions-simultaneously advanced setting prevents users from creating duplicate endorsements. With the setting enabled, users cannot create more than one open revision at a time.
  • By default, this setting is False, and BriteCore allows users to independently initiate revisions (endorsements) on different dates without issuing them.

Postpone Past Outstanding Debits for an NSF Payment

  • In the NSF Payment popup, Postpone past outstanding invoices to: allows the user to apply the postpone date only to past outstanding debits. When the NSF is processed, a past invoice that has not been paid in full will have the new postpone date and cancel date.

Enforce Underwriting and Non-Pay Cancel Dates

  • The Enforce Cancel Date IFF NonPay Cancel is Later Than UW checkbox on the Policy Lifecycle page allows clients to enforce underwriting and non-pay cancel dates. When a policy is set to cancel for non-pay and underwriting, this setting will place a higher priority on the underwriting cancellation if and only if the non-pay cancel date surpasses the underwriting cancel date.
  • The Notice of Cancellation Non-Payment of Premium and Continuation of Coverage - NonPay notices will state:
    • Payment of premium does not override the UW scheduled cancellation. If the Underwriting cancellation gets resolved, the system will revert the cancel date back to the original Non-Pay date.
    • Which case the Continuation of Coverage notice will specify reinstatement of underwriting cancellation does not override the scheduled Non-Pay cancellation

Allow/Disallow Agents to Remove Default Line Items

  • When editing a line item, administrators can determine whether a line item is Default or Mandatory for a policy type using the Line item is <Mandatory/Default> for this policy type checkbox and drop-down menu.
  • In the Agent Portal Policy Builder, line items that are set to Default will display a removal option (red X) and can be removed from the policy. Line items that are Mandatory cannot be removed from the policy.

Show Detailed Information About Insureds

  • The show_detailed_information_about_insureds advanced setting allows users to display detailed information on the Policy setup page and the Information tab for a policy, including address, FEIN Tax ID, and Legal Entity Type.

17 December 2018

Show Policy Wide Premium During Rating

  • The show_policy_wide_premium advanced setting allows clients to display each portion of a policy's premium to agents so they can explain policy premium to insureds during the quoting process.
  • By default, BriteCore shows property coverage and entire policy premiums. With this setting enabled, agents can view each portion of a policy's premium, including the premium for property coverages, policy-wide coverages and entire policy premium.

Import Batch Payments: Enable the CSV File Upload

  • The enable-batch-payments advanced setting uploads a CSV file to populate the batch payments table, rather than requiring the values to be entered manually.
  • If any data corrections have to be made, users can edit values in the table on the Batch Payments page, rather than editing the CSV file and uploading it again.

Premium Write-Off: Option to Add a Reason

  • To improve the audit trail, users can type a Reason for premium write off in the Write-Off Premium popup. The reason is stored in the policy's Notes section.

IVANS Email Notifications

  • When setting up NxTech eDocs and NxTech Downloads services, clients can add email addresses that will be sent notifications when files are built and exported to IVANS servers during nightly export processes.
  • For the policy download notification, a CSV file will be attached to the email.
  • For the eDocs notification, the email will show the file names uploaded and appended transaction codes.

Set Up Custom Claim Status

  • The claim-custom-status advanced setting allows users to add custom claim status codes in BriteCore. The custom status values display on the following BriteCore pages:
    • BriteCore Claim Search status drop-down menu
    • BriteCore Admin Claim Status menu
    • BriteCore reports

14 December 2018

New BriteWiki

We are elated to open the new BriteWiki to our clients. At BriteCon2018, we communicated we would open BriteWiki access to you by the end of 2018. Since BriteCon, our newly-formed technical writing team has conducted user tests with some clients to verify our content is discoverable, our design usable, and our permissions accurate. We feel the BriteWiki is now ready for use.

Starting now, all clients have access to the next-generation BriteWiki. You can access the BriteWiki via direct URL https://britecore.atlassian.net/wiki/spaces/BSHP/overview or by typing britecore.support into your browser. Note that neither http:// nor www is needed when typing britecore.support. You will be directed to the client homepage where a five minute overview video is available. Once accessed, we recommend you bookmark the BriteWiki’s homepage.

We will keep the current support site available, as well as BriteCore links to it, through January to provide time to transition your staff.

Within the new BriteWiki, you will experience a more powerful search and better overall organization. We hope you find this a helpful reference resource on BriteCore functionality and features.


The Education Team at BriteCore

10 December 2018

Contact Permissions

  • Contact permissions are used to determine which users have the ability to view and edit contact roles and login information:
    • Edit and display login information: /britecore/contacts/information/loginInformation
    • Save role data: /britecore/contacts/storeRoles
    • Prevent adding roles: /britecore/contacts/information/retrieveRoles
  • Each role has a custom permission rule that can be added to any Permission Level Group. Permissions for specific roles override the storeRoles rule.
  • If role permissions are set to None, contacts with the role will be hidden from the Contacts search screen.

Non-Pay Cancellations of Agency Billed Policies

  • The nonpay_cancellation_for_agency_billed_policies advanced setting allows both agency and directly billed policies to be canceled for non-pay. This prevents agents from having manually generate deliverables on policies that should have been canceled.

Enforce Min/Max Payment Amount for Sweep Payments

  • This feature prevents sweep payments outside of the current amount due (minimum) and payoff amount (maximum).
  • To enable,
    1. Navigate to Settings > Modules
    2. Click Policies
    3. Under the Policy Lifecycle click the Edit button (confirm the pop-up message, click Yes to save your data)
    4. Confirm the Policy Type
    5. Check the box for Enforce minimum (currently due) and maximum (payoff amount) payment amounts when making agent sweep payments
    6. Scroll to the bottom of the page and click Save

Release Version Added to the Footer

  • In the Administrative Portal, check the footer to see which code base release version the current BriteCore site is running from and when it was last updated:
    • Specific custom code bases are identified by a string of numbers
    • The most recent code base is called "master"

Change the Mailing Date to the Endorsement (Revision) Commit Date

  • When a new revision is created on a policy, the Declaration’s default mailing date is the revision effective date. The use-revision-commit-date-as-dec-mailing-date advanced setting changes the mailing date to be the revision commit date.

14 November 2018

Allow Duplicate FEIN/SSN

  • The allow-duplicate-fein advanced setting allows duplicate FEIN/Tax IDs to be created when set to True.
  • The setting is set to False by default to enforce Risk Clearance. When the setting is set to False and a duplicate FEIN/Tax ID is entered, an alert message is displayed.

Acord AL3

  • BriteCore supports AL3 files, which handle the transmission of insurance information. Currently, BriteCore's Acord AL3 integration needs to be setup in the database, rather than the user interface.

Lexis Nexis Credit Score Testing

  • Lexis Nexis Credit Scoring automatically defaults to Production. However, a radio button under Settings > Vendors > Lexis Nexis Credit Scoring allows clients to toggle between production and test servers so clients aren’t charged for pulling credit scores during the testing process.

8 November 2018

BriteApps Features

Combined Billing

  • The combined billing feature is available in both the mobile and web versions, and this feature is not controlled by a setting. If multiple policies have amounts due, the user will have two options from the dashboard. They can see View Payments on each policy or Pay my Bill on the combined amounts:
    • When users choose View Payments, they can complete the workflow that exists currently.
    • When users choose Pay my Bill, they are directed to the Make Payment screen for making combined payments. From there, they can choose to pay the current due or the entire term.
combined billing briteapps.jpg

Pay the Future Term

  • Making a Future Term Payment is now available in both the mobile and web versions, and this feature is not controlled by a setting. If a policy has the current term paid in full and the next term is available, the policyholder will have the ability to pay that future term.
future term briteapps.jpg

Alert When Property Photos Are Uploaded

  • The ability to be notified when the policyholder uploads a property photo is now available for both the mobile and web versions.
  • The Additional email address to notify when insured uploads a property photo setting allows users to enter email addresses for those who should receive this notification in Settings under Notification.

Enrollment Without a Policy Number

  • Searching for an account during the enrollment process by using Last Name and Date of Birth is now a feature that is available in both the mobile and web versions.
  • You will need to enable the Use user-based search during enrollment setting in order to use this feature in Settings under Enrollment.

Verify Password Field

  • The ability to re-enter a password upon creating an account is now available for both the mobile and web versions.
  • You will need to enable the Use Additional Verification Password Field setting in order to use this feature in Settings under Enrollment.

Administrative Field Update

  • A number of changes have been made to the administrative pages:
    1. Reworked the left Navigation Menu
    2. Renamed some of the pages so that they align with what they are used for
    3. Changed the view for all pages to be in a column view where possible

29 October 2018

Default ISO on Protection Class (PC) Fail

  • The default-pc-lookup-to-prior advanced setting replaces the User Warning for ISO Protection Class Lookup failures with an Admin Processing Error alert email. Then, the setting defaults PC to the prior ISO manual rating.

BCEG Construction Year Setting to Communicate with ISO for Protection Class

  • When the BCEG (Building Code Effectiveness Grading) is enabled, the location address interface will ask to collect the construction year to communicate with ISO. This determines a Protection Class and BCEG Code value for clients.
  • The require-construction-year advanced setting requires users to enter the construction year for the location/risk address model.
  • The show-bcegs-code advanced setting displays the BCEG code retrieved from ISO.

ISO Protection Class Service: Add Configurable URL

  • serviceURL has been added as an optional field to the vendor in the database. A URL set in the database through that field has higher precedence over default URLs that are hardcoded in the application code.

22 October 2018

Set Up Risk Numbering and Naming

  • The complex_risk_naming advanced setting allows users to create a naming convention when adding risks to a policy which automates risk naming. This setting allows users to add one auto incrementing count to the naming convention which can be useful for policies with multiple risks.

Set Up Agency Downloads (IVANS)

  • IVANS is an interface for the exchange of insurance information between property and casualty insurers, agents, and trading partners. Using the ACORD Automation Level 3 (AL-3) standard, industry partners are able to electronically exchange information such as policy/submission, claims, and accounting data.
  • Several changes and additions were made to the IVANS integration:
    • BriteCore added an additional transaction trigger:
      • Primary insured name/address changed
    • BriteCore can now send PDFs to IVANS (edocs) and has a tool to support it
    • BriteCore can now send commissions and claims data to IVANS

Display Coverage Limit on Declaration

  • When enabled, the display-coverage-zero-limit advanced setting displays the coverage limit on deliverables as a number, even if that limit is $0 (zero). Previously, coverage limits of zero were displayed as ***.

8 October 2018

Display the Deductible Value and Percentage

  • Some deductibles are a percentage of coverage rather than a flat dollar amount. The display-adjustable-deductible advanced setting and Display deductible for adjustments in Declarations checkbox allow clients to display the deductible as a percentage and dollar amount on the declaration.

Billing for Unearned/Earned Premium

  • The cancel_invoice_bill_for advanced setting allows clients to determine whether the Cancellation Billing Statement shows unearned or earned premium as the Total Amount Due.
  • Setting cancel_invoice_bill_for to Earned is recommended for clients who use BriteCore's policy administration system.

Print Billing Schedule

  • Agents can print the billing schedule:
    1. Navigate to Billing
    2. Click View Schedule
    3. Click Print Schedule in the pop up window
    4. For optimal formatting, check Background graphics

Allow Payments on Submitted Applications

  • The allow_pay_submitted_policies advanced setting allows users to apply payments to submitted policies using either the lockbox or DCR screen.

Search for Policies on Claims Page

  • Users can search for a policy by policy number or insured's name when filing a claim.

1 October 2018

Disallow Users from Deleting a Contact

  • Two permission level rules enable clients to disallow users from deleting a contact from the Contacts module:
    • The britecore/contacts/removeContact permission level rule controls the ability to delete contacts from the Contacts List screen. When this permission is enabled the red X icon used to delete contacts is hidden.
    • The britecore/contacts/removeContactRole permission level rule controls the ability to delete roles from specific contacts. When this setting is enabled, Delete This Role X (found in the Role section under Contacts > Information) is hidden.

24 September 2018

Customize Sender Email

  • Emails sent from BriteCore come from admin@britecore.com. The primary-sender advanced setting allows clients to customize the sender, for example clientname@clientname.com.

Assign an Underwriter Contact from the Administrative Portal

  • Underwriter revision contacts can now be assigned via the Agent and Administrative Portals.
  • In the Administrative Portal, the field appears under Policies > Information.

Customize C.L.U.E. Filename

  • By default, BriteCore names claim data files sent to LexisNexis using the prefix clup_history_T. The clue_file_prefix advanced setting allows users to customize the filename prefix.

17 September 2018

Label Agents as Agency Administrators

  • An Agency Administrators section has been added to organization contacts, which allows clients to assign administrators to agencies.
  • Contacts assigned as agency administrators
    • Have the agent role
    • Do not have special permissions in BriteCore
    • Are designated by a system tag, Contact Administrator, which makes them easy to identify and contact
  • Within the client's office, agency administrators are responsible for assigning agents to agencies.
  • To add an agency administrator to an organization, complete the following steps:
    1. Navigate to Contacts
    2. Edit an organization or click New Organization
    3. Click Edit beside Agency Administrators
    4. Select the contacts to designate as agency administrators
    5. Click Done

Disable Revisions on Policies No Longer In-Force (Canceled)

  • The following behavior is now the BriteCore default. That is, no setting presently exists to alter the behavior.
  • When a policy is not in-force (canceled), revisions cannot be committed and endorsements cannot be processed.
  • To commit a revision on a canceled policy, the policy must be reinstated.

ISO Prefill Services

  • Prefill Services uses the 360Value API call to get data use in preliminary quoting and rate categories.
  • Prefill Services can populate several fields in the Policy Builder:
    • Exterior Wall Construction Type
    • Percent Wood Framing
    • Exterior Wall Finish
    • Foundation Type
    • Number of Full Bathrooms
    • Number of Half Bathrooms
    • Number of Bedrooms
    • Number of Stories
    • Roof Cover (Type)
    • Roof Shape
    • Use or Number of Families
    • Year Built

Insvista: Non-Renewal Change Log

  • The validate-non-renew-date-log-with-life-cycle advanced setting allows clients to send non-renewable notices to Invista according to the non-renewal configured timeline, rather than when the policy is set to non-renew.
  • For example, if a policy is set to non-renew 90 days before expiration and insureds need to be contacted 60 days prior to expiration, the non-renewable notice will be sent 60 days prior to expiration.

Additions to the Payments Received Report

  • On the Payments Per Policy tab, the Payment Made By column was added.
  • A new tab, Payments Per Payment Type, was added that groups payments by payment time, such as credit card payments.

Printing the Declaration Across Terms

  • The print-deliverable-if-propagation-crosses-term advanced setting ensures that the new renewal Declaration will print if a late term endorsement is processed after the renewal has been issued.
  • Previously, BriteCore would not print the new renewal Declaration.

Resending Missed Files

  • If OnBase fails to receive files for an extended period of time (a day or more), developers can use bin/onbase_tools.py to process files for a specific date range.