Data Validation Rules

Understand the data validation rules that are applied to data being processed in Tide

During Transformation, Tide applies a series of data validation rules to submitted data. ‍Visit the Data Validation Overview article to understand the ‍stages and process of data validation. Visit the Transformation Overview‍ to understand how validation fits within the Transformation stage of processing.

The following articles cover data validation checks which are over and above the core validation rules set out below:

Core Validation Rules

These rules are applied to all data processing. The Error Name is the title of the error screen where any validation errors are presented.

Rule Name

Rule Definition

Error Name

Validate Year of Account values

Check that all Year of Account values are valid years

Invalid Year of Account values identified

Validate Reference Data values

Validate that there is an exact match, or previously assigned mapping, between supplied values and the relevant Tide reference data values.

Reference data Translation Required

Validate Boolean values

Check that Boolean values are valid

Invalid boolean values identified

Validate Date values

Check that date values are valid

Invalid date values identified

Validate Financial values

Check that financial values are valid

Invalid financial value translation required

Validate Decimal values

Check that decimal values are valid

Invalid decimal value translation required

Validate Integer values

Check that integer values are valid

Invalid integer values identified

Validate Percentage values

Check that percentage values are valid

Invalid percentage values identified

Validate mandatory field populated

Validate that a data field that has been set as mandatory has been populated.

Mandatory data field not populated

Validate Risk Postal/Zip Code is populated

If the Risk Country is either ‘United States of America’ or ‘Canada’ and at least one Aggregate Limit is associated with at least one Section of the Reporting Channel of the submission, then validate that Risk Postal/Zip Code is populated.

Mandatory data field not populated

Validate initial premium is positive

Check that the first reporting of a risk has positive premium reported.

First reporting of risk with negative premium

Validate Consistent Currency Reporting

Check that all currency fields report the same currency in subsequent reporting of a Risk, Premium, or Claim.

Inconsistent Currency value identified

Identify Contract based on Year of Account field

Identify the correct Contract in Tide that the record should be allocated to, based on the value in the Year of Account field.

Cannot identify Contract in Tide based on Year of Account

Identify Contract based on Risk Inception Date field

Identify the correct Contract in Tide that the record should be allocated to, based on the value in the Risk Inception Date field.

Cannot identify Contract in Tide based on Risk Inception Date

 

Was this article helpful?

Can't find what you're looking for?

Contact Support