IWS Release Notes - March 2016

From BriteWiki
Jump to: navigation, search

March 28, 2016

Enhanced Payment Setting - PR3902 Clients now have greater control over electronic payments as the existing setting to restrict payments for policies in Cancellation Pending has been divided into two settings. With this release you may now separate payments against policies in Cancellation Pending for Non-Pay from policies in Cancellation Pending for Underwriting.

CP Payment Setting.png

By default, if the previous setting was enabled both new settings will be enabled. This will retain existing behavior but can be updated if needed. To update the setting, navigate to Settings > Modules > Policies > Policy Lifecycle > Non-Pay.

Show in Builder Setting Expanded - PR3555 There is now more flexibility for displaying lines items. The existing Show in Builder setting determines whether a line item shows in Builder for staff (BriteCore) and agents (BriteQuote). With the expansion, users may select whether to show the line item in both BriteCore/BriteQuote or just BriteCore. The new BriteCore only option keeps the line item from being available and visible in BriteQuote. If the item is added via BriteCore, it will not be visible in BriteQuote.

ShowInBuilder Setting.png

To honor current functionality, line items that currently have this setting selected will be converted to the Britecore & BriteQuote option.

As a final note, this contrasts with the Line item not available in BriteQuote setting. This setting keeps the line item from being selectable in BriteQuote and invisible in BriteQuote if added via BriteCore.

March 01, 2016

Support Tools - PR3767 BriteCore users now have access to new tools to correct data discrepancies. On the Dashboard footer, the previously labeled Utils has been renamed Support Tools.

SupportTools.png

Currently, there are two tools available for users, Add a Location to a Zipcode and Update Search Index. Clicking either tool will generate a form that requires various information from the user.

Add a Location to a Zipcode: This tool may be utilized if the City options for a specified zipcode do not contain the needed City. The user may add a City via this tool to make it available throughout BriteCore.

NOTE: Property locations are restricted by the pre-defined Business Locations in settings and cannot be overridden with this tool.

Update Search Index: This tool may be used to update a policy’s status if the search results do not match the policy status of the policy. This tool can also be used with claims, contacts, and properties, if needed.

Auto-Analyze Billing Schedule Upon Payment - PR3807 A new setting provides greater efficiency when applying payments at the beginning of a policy term. Billing schedules can now be automatically updated if the payment amount for an initial/renewal invoice is within a defined threshold. In Settings > Modules > Policies > Policy Lifecycle > Payment users build this setting.

  • First, enable the setting.
  • Second, select to which billing schedule the setting applies.
  • Third, set a threshold for each selected billing schedule.

BillingSchedule Updates.png

Example Using the above setup and assuming the Semi-Annual billing schedule is split 50/50, a policy is on an Annual billing schedule and has $1000 of written premium. If the insured makes an initial payment >= $495 and <= $505, the billing schedule of this policy will automatically update to Semi-Annual.

NOTES:

  • The payment amount is calculated against the invoice (premium + installment fee). Non-Payment fees, Reinstatement fees, etc. are not used to determine eligibility for updating the billing schedule.
  • Only Billing Schedules that are setup to show on the invoice, public gateway, or sweep payment will appear as options for this new setting.
  • If the payment amount matches the current billing schedule and also another billing schedule, the billing schedule will not be updated. e.g. Escrow Billing vs. Annual.

Updated Verification for Loss History - PR3473 An additional verification step has been added to the process of pulling loss histories for policies. Prior to sending the request to the vendor, the information that is being sent needs to be reviewed. Users will now see a popup window that shows how the first/last name are being sent to the vendor.

LossHistory Verification.png

Once the name(s) are verified/corrected, clicking Get Current Loss History will send the request to the vendor and any loss histories will be returned as expected.