Validation Exceptions

• Submission - Validations performed on the filing prior to loading it to the database. If any of these validations fail, the filing will not be loaded to the database. They consist of checks such as ensuring the data year is appropriate, the file name and other information provided by the company is valid.
• Form and Format - Validations that ensure the filing is submitted in the prescribed electronic format. Excessive form and format errors or form and format errors on critical tables would prevent the filing from loading to the database.
• Completeness - Validations performed on the data to ensure it is complete as required by the instructions and the specifications. If the filing does not contain critical tables or all required rows on critical tables, it will not be loaded to the database.
• Consistency - Validations performed on the financial data that ensure the data flows correctly through the filing. These are commonly referred to as "crosscheck" validations. 
• Textual - Validations performed on textual data in the filing to ensure it is not missing or invalid.

Validation Priorities:

• IRIS - Identifies crosschecks that must be passed in order for IRIS ratios to be calculated on a company filing.
• A priority - Identifies inter-table (inter-schedule) crosschecks that verify that data carries accurately from the schedules to the exhibits, to the balance sheet, and to the income sheet.
• No priority - No priority is assigned to the validation rule.
• RBC - Identifies crosschecks that must be passed in order for the Risk Based Capital calculations to be performed.
• Result status 6 identifies validation failures - Identifies a validation rule for which failures are identified by result status code 6. Validation failures identified by the result status code 6 are ignored by the Work Flow and Correspondence applications.

Validations are stored on multiple filing types, including:

• Original - Original will reflect the validation exceptions that existed on the originally submitted filing.  There will only be one original submission processed.
• Current - Current shows the user the validation exceptions that currently exist on the database.
• Vendor - Vendor will show the user validation exceptions identified by the company as existing in their filing that were not corrected prior to submission.
• Refile - Refile reflects validation exceptions associated with a complete refiling of the submission.  Refiles are filings made by companies whose original filings could not be loaded to the database.
• All Types - All Types reflects validation exceptions that exist for all of the above file types.

Filing Period Type allows the user to select validation exceptions for a particular filing deadline. 

Filing Set allows the user to select validation exceptions for a particular data set within a filing deadline.The user may sort the validation exceptions by filing period, filing set, or table name.  To access Validation Exceptions:

To View Validation Exception reports using the iSite+ Reports Page

3. Click on the Validation Exception Link located under the Compliance section.

4. Select the desired criteria for the report from the drop-down lists on the page. See above for definitions of the available selection criteria.

5. Click the Submit button to generate the report. The Validation Exceptions Report page will display based on the criteria selected.

6. To print the Validation Exceptions Report or to save it to your computer, select the appropriate command from the File menu at the top of the window.

7. To close the Validation Exceptions Report, click the close (X) button in the upper right corner of the report window or select the Close option from the File menu at the top of the window.

8. To perform another search or navigate to a different application within iSite+, select the appropriate link at the top of the iSite+ Reports page.