InsVista setup – BriteCore Support

InsVista electronically notifies mortgagees and lienholders of changes to applicable policies. BriteCore sends homeowners (HO) and billing (BG) files to InsVista so InsVista can notify policy stakeholders. When a qualifying transaction occurs, BriteCore will compile the information in the InsVista table in the Policies module on the Processing screen during nightly processing. If there are no transactions from the previous day, the InsVista table will be empty.

Considerations

If the nightly-processing advanced setting is set to manual, you will need to build and send the InsVista file manually. See the Using the integration section below for more information.

Prerequisites

Contact InsVista to sign up for their service. You can begin the implementation once you receive a client code, client number, FTP host server, username, and password from InsVista.

Implementation

The implementation section includes steps you must take to implement InsVista.

Step 1: Add your company as the primary carrier in BriteCore

BriteCore will automatically pull Remit Payments To information from the primary carrier contact in BriteCore. The Remit Payments To information is included in InsVista notifications to mortgagees, so mortgagees know to whom and to what addresses to send payments. To add a primary carrier contact to BriteCore, see Add a New Organization contact overview and Add a primary carrier for more information.

Step 2: Set up InsVista

To set up the InsVista vendor in BriteCore:

Select Settings.
Select Vendors.
By InsVista, select the checkbox.
Select the pencil icon.
Type the Client Code and Client Number you received from InsVista.
Verify the Remit Payments To information is correct.
Type the Host Server, Username, and Password you received from InsVista.
Select Done.

BriteCore employees will also need to add the FTP credentials you received from InsVista to your company's britecore.cfg file.

Step 3: Set up the Escrow Billing billing schedule

BriteCore will send billing information to InsVista if the policy uses the Escrow Billing billing schedule. To set up the Escrow Billing billing schedule,

Select Settings.
Select Modules.
From the dropdown list, select Policies.
Under Policy Lifecycle, select Edit.
Select Yes.
Select a state.
Select Lifecycle Parameters Are the Same for All Business or Lifecycle Parameters Are Defined Per Policy Type.
1. If the parameters are defined per policy type, select the policy type.
On the Billing tab, under Billing Schedules beside New Billing Schedule, select the green plus (+).
In the Name of Billing Schedule box, type Escrow Billing.
Complete the other fields to set up the Escrow Billing billing schedule.
Select Save and Exit to close the Edit Billing Schedule dialog box.
Select Save and Exit to close the Policy Lifecycle dialog box.
Select Yes.

Step 4: Set up system tags

Please see Set up system tags for InsVista for more information.

Step 5: Set up Lines

You will need to complete the following steps to set up loss payees for InsVista if a loss payee is attached to coverage on a policy. BriteCore will report the limit, deductible, and legal description of the loss payee to InsVista, so InsVista can notify the mortgagee. To add a Description Supplemental Question for loss payees:

For coverages with loss payees, follow the steps to add a question from Set up supplemental questions.
In the Question Label box, type Description.
From Question Input(s) Type, select Single Line.

Step 6: Test the integration

BriteCore will send test files to InsVista. InsVista should be notified that the integration is going live one week before the go-live date.

Use the integration

BriteCore will compile changes to policies. Please see InsVista transaction types for more information. You can review the policy changes, build and review the files, and send the files to InsVista.

View policy changes

Select Policies.
Select Processing.
Beside InsVista, select the gray arrow to expand the table.

Build HO and BG Files

Select Policies.
Select Processing.
Beside InsVista, select the gray arrow to expand the table.
From the Unsent File dropdown list, select the HO or BG file.
Select Build File. If BriteCore builds the file successfully, it will display a message stating the file has been built and can now be viewed or sent to InsVista.

If you want to remove a specific policy change, unselect the checkbox beside the change and build the file again.

Send HO and BG Files

Select Policies.
Select Processing.
Beside InsVista, select the gray arrow to expand the table.
From the Unsent File dropdown list, select the HO or BG file.
Select Send File.

Related BriteCore tools and settings

Validate non-review date log with lifecycle
- The advanced setting, validate-non-renew-date-log-with-life-cycle, sync a policy's non-renewal status with the Policy Life Cycle timeline. When enabled, the non-renewal status aligns with the generation or print dates of the Non-Renewal Notice deliverable. If the change occurs outside the timeline, the date defaults to the action date.
  By default, the setting is disabled, so the date always reflects the action date. Enabling it ensures InsVista HO reports and non-renewal transactions align with the Policy Life Cycle timeline, preventing premature reporting.
Render auto-assign as printed