Master Data Field Reference

The information below describes how to define fields in Master Data set for both raw and derived data elements. Any field that you plan to use in any form in a bordereau or data management project must have a field in the Master Data set. The settings made when creating master data fields comprise the data dictionary definitions for your project's data set. Settings made in master data fields trigger filters within Bordereaux.

Guide to Establishing and Identifying Data Fields

The field definitions and descriptions below can help when creating data fields in the Master Data Set as well as provide a reference to existing fields.

Field
(Metadata)

Definition | Description

Field Code

required

Field name that will be used to store values to a database.

Important: Do not include spaces or special characters.

The underscore ( _ ) symbol is accepted.

Maximum length is 55 characters.

Application restricts creation of field nodes with system keywords such as ID, PolicyStatus, Rownumber.

Duplicate values are disallowed.

Field Name

required

This name displays on reports or other outputs as a label.

The underscore ( _ ) symbol is accepted.

The maximum length is 255 characters

Application restricts creation of field nodes with system keywords such as ID, PolicyStatus, Rownumber.

Duplicate values are disallowed.

Help Text

Provides information to help define the field for users and indicate how it is used.

The maximum length is 255 characters.

Data Type

required

Identify the data storage format of the master data field.

The following options are available when creating master data fields and will be used to validated incoming data fields.:

Integer
Decimal
String
Date
Boolean

Minimum Characters

Identifies the minimum number of required characters accepted when the data type selection is String.

Maximum Characters

Identifies the maximum number of allowed characters when the data type selection is String

Format

Identifies the format appropriate for the field's data type.

Select the Raw option when you are creating a field to accept unaltered data. (Inbound field)
Select the Derived option when you are creating a field which will be used to derive a value using a combination of one or more Raw fields and/or business rules.

Note: Output Data sets can be built using both Raw and Derived Data sets. Labels for output data fields can also be revised.

Encrypted

Selecting the Encrypted checkbox to will cause values in the field to be encrypted while in transit.

Minimum Value

The lowest numeric value accepted when you choose Integer or Decimal as your data type.

Maximum Value

The largest numeric value accepted when you choose Integer or Decimal as your data type.

Default Value

The value populated in a field by default. (Available to all data types with the exception of the Date data type.) This value will be applied when there is a null value for the field within incoming data.

Output Value

The value used as results or outgoing data.

Field Type

required

Choose one:

Select the Raw option when you are creating a field to accept unaltered data. (Inbound field)
Select the Derived option when you are creating a field for data outgoing into a data output set in the template (Outgoing field)

Defined Field Type

Field Name	Data Type	Import Type
Accounting Period
Acquisition Cost
Acquisition Cost
Acquisition Cost
Admin TPA Fee
Billing Due Date
Billing From Date
Billing To Date
Cash Received Functional Currency
Cash Received Original Currency
Cash Received Translated Currency
Claim Reserves Original Currency
Claim Status
Claim TPA Fee
Claims Paid Functional Currency
Claims Paid Original Currency
Claims Paid Translated Currency
Claims Reserves Functional Currency
Claims Reserves Translated Currency
Commission Amount
Commission Amount
Currency Type
Date of Loss Payment Plan
Effective Date
Endorsement/Net Change Amount
Endorsement/Net Change Amount
Expiry Date
Fees Amount
Functional Currency
Gross Premium	Decimal	Premium and Cash Imports are selected to create the field and Data Type selected (should be Decimal)
GWP Functional Currency
GWP Original Currency
GWP Translated Currency
Net Premium	Decimal	Premium and Cash Imports are selected to create the field and Data Type selected should be Decimal
Net Premium Paid	Decimal	Type - Cash Import Type
Original Currency
Paid To Date Fee
Paid To Date Loss
Pay Type
Payment Plan
Policy Effective Date	Date	All Import Types or Combination
Policy Endorsement
Policy Endorsement
Policy Endorsement Effective Date
Policy Endorsement Expiry Date
Policy Expiry Date	Date	All Import Types or Combination
Process Year	Integer	Any Import type or By selecting Combination of import types
Reporting Period
Select
State	String	All Import Types or Combination
Tax/Surcharge Amount
Total Incurred
Total Insured Value
Transaction Type	Integer	All Import Types or Combination
Translated Currency
Underwriter Year	Integer	Any Import type or By selecting Combination of import types
YOA GWP - Functional Currency
YOA GWP - Original Currency
YOA GWP - Translated Currency

ETL
(Extract, Transform, Load)

This is a toggle switch. Allows field to be used for non-BDX data translations. Reduces Field Definition Requirements. Left turned off (untoggled) the field being defined will be used for Bordereaux (non ETL) meaning there will be more fields available for tagging data according to insurance import types of premium, cash and claims. If the switch is toggled on (will turn green), you are not preparing a Bordereaux output file and intend to use more of the data manipulation features.

Import Type

The import type designation is designed for data used in Bordereaux. Each selection used for non ETL data, aka Bordereaux, identifies the information as pertaining to one of the three insurance-related data types available. Options are as follows:

Premium - Select this option when importing premium transaction data.
Cash - Select this option when importing cash transaction data for policies.
Claims - Select this option when you are working with policy claims data.
Others - this is the only choice for ETL import types and will be the only option to appear (pre-selected) if the ETL toggle is turned on

Key
Required when the FieldType is Derived.

The choices in this section define database keys and designate the transaction type where the data is a key field.

Policy Key - Available only when premium, cash, or claims import types are selected.
Risk Key - Available when any one import type is selected or when all import types are selected.
Coverage Key - Available when any one import type is selected or when all import types are selected.
None (default option)
Claims Key - Available only when the claims import type is selected.
Cash Reconciliation Key - Used to reconcile cash transactions against premium. Available only when premium and cash import types are selected.

Reference Type

required

Reference ID and Reference name is used throughout the system to identify individual records in grids.

For Premium and Cash transactions the Reference ID is typically a Policy Number.
For Claims transactions the Reference ID is typically a Claim Number.
Reference Names are typically the Insured Name and used when you have selected both Cash and Premium import types and selected the Reference ID option, then an order of priority must be established where the system recognizes or references them in order.

For example:

In the Premium line, choose whether this type of data will take priority over cash.
In the Cash line, choose whether this type of data will take priority over premium.

Additional Rules:

It is possible to define Reference names and Reference IDs as either Raw or Derived fields.
Can only create one Reference name and Reference ID for per customer/party.
Can only create one primary and one secondary Reference ID per import type.

Field Level

required

Use to identify if the field you are defining is available in ALL templates being configured or should only be available to templates being configured to handle a specific line of business. For example Policy Number is usually defined as a Policy Level Field, whereas Vehicle ID Number (VIN) is usually a Coverage or LOB-level field only applicable to Personal or Commercial Auto policies.

Choose one of the three field-level options available:

Retain the None (default) setting when there is no relevance to placing your data field to policy or coverage level in your data hierarchy.
Select the Policy option when the data is relevant at the policy level in your data hierarchy.
Select the Coverage option when the data is relevant to the coverage level in your data hierarchy with subcategories to further define the field.
- When you select Coverage, the definition of subcategories is required and the field level subcategory dialog opens.
  Use the dialog to define one or more classes of business where the data field belongs, is found or can be utilized. In the example below, the field belongs at the coverage level to a commercial property class of business.
  
  Checking the Select box limits the visibility of this data field to when the class of business of a template is Commercial Property. When Mandatory is selected, the data field would always have to have a value present. You can select a class of business without requiring a value in the field.

Field Mandatory

When you select the Field Mandatory checkbox, the system puts the record in error status when data is missing for the field during validation.