IWS Release Notes - September 2014
We strive to keep our products above the industry standard so that your systems remain current and flexible. For that reason, we make continuous improvements to BriteCore's code base. We've been experimenting with a continuous release process, and we'll be shifting to this to better reflect our daily improvements. Rather than waiting for the all-clear of many items to go out in one weekly release, you'll receive continuous updates for code changes going out in the daily release. Items that require full release notes for this month can be found in this section of the BriteWiki.
- 1 September 23, 2014
- 2 September 22, 2014
- 3 September 17, 2014
- 4 September 9, 2014
- 5 September 3, 2014
September 23, 2014
Always Bill Auto Pay
A new setting has been added to Settings > Modules > Policies > Policy Lifecycle > Billing > Options > Always Bill Auto Pay that allows carriers to pull Auto Pays for policies regardless of the amount due. This new setting will ignore the threshold set for ‘Do Not Issue a Bill If the Amount Due is Less Than’ for Auto Pays only.
Example: The threshold for ‘Do Not Issue a Bill If the Amount Due is Less Than’ is set at $25. Policy ABC123 is setup as an Auto Pay on a Monthly ACH billing schedule with a monthly premium of $20. Since this amount is less than the $25 threshold, the auto pay will currently only pull every other month (when the amount due exceeds $25). With this new setting, BriteCore will force the Auto Pay to pull each month even though it is under the threshold.
This setting is not editable via the interface. If you are interested in using this setting, please submit an OOPS! ticket requesting this change.
September 22, 2014
New Underwriting Enforcement for BriteQuote
If you allow bound application submission, a new Lines setting is available that allows you to define the limit above which an application must be submitted unbound. In the setup of a line item, you have the ability to define a limit using an on/off setting entitled Disallow “Submit Bound” if limit exceeds and is located in Lines > Effective Date > Policy Type > Line Item > Setup > Options. Once enabled, this enforcement applies to quotes and applications in BriteQuote - this enforcement does apply to the builder in BriteCore.
When an agent enters a limit, or the system calculates a limit, that is above the defined threshold a popup message will generate on the Rating tab after a user clicks Rate and Save. The popup will indicate to which line item the limit threshold applies.
If a limit threshold is set on more than one item, the popup will list each applicable item. In the example below, the limit for both Coverages A and B have exceeded the defined limit.
Columns Added to Item Detail Report
IWS has added County and Zip Code as new columns to the existing Item Detail Report located in Reports > Report List > Data Extracts. These new columns will assist in providing needed information for clients when filling out various reports for vendors.
September 17, 2014
Policies & Claims Search Updates
Funded by Farmers Mutual of TN, Eastern, and Baldwin
Policies and Claims searches have been updated to include new columns and also display more intuitive results.
In BriteCore and BriteQuote the search results previously displayed a Claimant column. Starting tomorrow, the Claimant column will be replaced with Named Insured(s) in BriteCore and with Adjuster in BriteQuote.
Updated Search Results
Search results have also been improved to assist BriteCore and BriteQuote users. When blank searches are performed the results will be sorted by the date they were created in descending order. This means the most recently created Policy or Claim will be listed at the top of the results.
In Addition, for Claims searches, a blank search will hide claims with a 'Closed, Data Conversion' status. These claims can still be found by searching specifically for them, however, hiding them from blank searches allows users to view more relevant results.
Note: If parameters are entered into the search field, searches will continue to list the most relevant results in regard to the parameters given.
Automated Reserve Totals
Summary fields are now visible in Claims > Individual Claim > Accounting > Overview. These new fields provide easy, at-a-glance viewing of Reserve Totals. The Total Reserve field is calculated by summing the Reserve and Paid To Date columns and the Remaining Reserve field is calculated by summing the Reserve columns.
Deductible Field for Claim Payments
A new field has been added to Claims that allows carriers to track deductibles that have been applied to a specific Claim Payment. This new field is viewable in Claims > Individual Claim > Accounting > Transactions > Add an Entry.
The data entered in this field is then stored with the individual payment in the Payments table on the Transactions menu and can be viewed by expanding the individual payment row.
Currently the data entered in this field is for informational purposes only and does not impact payment amounts, reserve amounts or report totals. However, since this data is now being captured, it will allow for future use in reports.
Note: This field can also be left empty ($0.00) and all references will show $0.00.
September 9, 2014
New Columns Added to Claims Reports
IWS has added new columns to BriteCore’s Claims Reports for Policy Type, Subline Name, and Subline Type . Users view these columns by running any of the following reports located in BriteCore > Reports > Report List > Claims:
- Claims Payments
- Claims by Loss or Close Date
- Losses Incurred
- Uncommitted Claims
- Open Loss Report
Automating Additional Insured Supplemental Question
This feature will reduce the amount of data entry required for Supplemental Questions of the type Contact > Additional Insured. If clients have supplemental questions that are set up as the Input Type of Contact > Additional Insured, this new functionality will be applied.
To reduce duplicate data entry, the Additional Insured Supplemental Questions will automatically pull in the contact information that has been added to the Information tab during policy setup. The contact(s) will now be selectable from a drop down menu and a new link to ‘Copy Property Address’ has been added for increased efficiency.
In addition to the above automation, IWS has added a new setting that allows clients to pre-define the available options for the type of Interest the contact has with the policy. This new setting is located in Settings > Modules > Policies > Contacts >Suggested Interests and each entry in this field is selectable from the Interest field on the policy’s Information tab.
A user can also manually type values on the policy's Information tab that do not appear in the pre-defined list. Please note that a manually typed value not already in the list does not automatically add that value to the list.
September 3, 2014
Option to Use Inception Date for Line Item Setting
Currently clients have the option to use a policy’s effective date when determining whether or not a line item applies based on past claims data. Starting tomorrow, clients will also have the ability to reference the policy’s inception date for these line items.
A new setting has been added to Lines > Effective Date > Policy Type > Line Item > Options that allows the inception date of policies to be used. When this new setting is selected, the code will reference the policy’s inception date to determine if the line item should apply instead of referencing its effective date.
When the inception date of a policy is being referenced, BC will look at the inception date until the point that (Today - X years > inception date). Once this occurs, the logic will ignore the inception date and only consider (Today - X years).
NOTE: X is determined by the number selected for that particular line item in Lines > Effective Date > Policy Type > Line Item > Options
ISO APlus Code Added to Perils
For clients who report claims data to ISO APlus there is a new option for Peril codes that allows clients to assign an ISO APlus code for each Peril.
This new ISO APlus Code will be used to determine the claim type (Property or Liability).
New Claims Designation
Claims can now be designated as Property or Liability from the interface. By default BriteCore will automatically determine the type of claim based on the Coverage(s) Filed Against and Peril(s) added to the claim. Unless the Coverage(s) Filed Against or the assigned Peril(s) are designated as Liability, BriteCore will assign the designation of Property to the claim, otherwise Liability will be the claim’s designation.
The new designation has a manual override that allows user to manually set the claim type if needed. This option is located in the Edit Claim Status popup on individual claims.
NOTE: Once the type of the claim is set manually, BriteCore will not attempt to automatically set the claim type, regardless of new Coverage(s) Filed Against or Peril(s) added to the claim.
For clients who report claims data to ISO APlus, this new claim type will used in the ISO APlus file.