Considerations for Payroll Data Validation

Before you run payroll or any other statutory processes or reports, it's essential that the requisite HR and payroll data setup is verified, validated, and complete for all your workers. Missing or noncompliant data can impact legal processes or reports.

Consider the following to ensure that your payroll and HR data is compliant and error free.

Payroll Data Validation Report

After you set up your HR and payroll data, and before you run the payroll process or any other report, run the Payroll Data Validation Report. The Payroll Data Validation Report provides details of missing or statutorily noncompliant data at the worker and organization level. You can then take corrective action as necessary to complete the data setup and correct noncompliant data.

Validation Rules

Apart from the predefined country-specific validations that's included in the application, add business rules and validation messages at the enterprise or legislative data group level. Add these rules during the implementation phase.

Use the delivered formula 'Global Attribute Mandatory Check' to set up validations to identify missing data. You add the validations to the Data Validation Report extract definition.

Validation Levels

The data group you select when adding validation rules to the Data Validation Report determines the level of validation. For example, you might have a validation rule at the tax reporting unit level or at the person details level. When adding a validation, you must ensure a database item exists for the attribute for which you're adding the validation.

Control the Rules for Data Validation Reports

Use the delivered ORA_HRX_GLB_VALIDATION_OBJECTS lookup type to set up a lookup code that you can use to control the validation. For example, you can use this lookup code to add multiple country tags to a validation. Alternately, if the validation is no more valid for the country, remove the previously added country tag from the lookup code.

Validation Types

The validations can be simple or complex.

The application triggers simple validations if you haven't provided a value for an attribute required for a report or a process. For example, the Tax Reporting Registration Number is missing at the organization level or the National Identifier value is missing for a worker. You can create a simple validation by using the delivered formula 'Global Attribute Mandatory Check' and the appropriate database item group.

The application triggers complex validations when there's more than one attribute included in the validation. For example, a value is missing for a National Identifier Type pertaining to a worker.

For coding complex validations, Oracle recommends that you use data elements of type Rule with a user-defined Rule Formula to perform the validation. You must deliver these data elements in a record of type Formula.

User-Defined Rule Formula

For coding complex validations, Oracle recommends that you use extract attributes of type Rule with a user-defined Rule Formula to perform the validation.

Data Security

By default the report is submitted through an elevated user that has full data access and is secured through the list of values on the report parameters. However, you can configure the Data Validation Report to run based on the profile of the user who submits the report. For example, if a user has access to only employees within a specific payroll or department, you can configure the report to check data only for those employees.