Validation Jobs
A validation job evaluates employee payroll data against approved rules from one or more contracts. Each job produces a set of findings.
Creating a validation job
Navigate to Validation → New validation run.
| Field | Required | Description |
|---|---|---|
| Contract(s) | Yes | One or more contracts with approved rules |
| Employee dataset | Yes | CSV file with employee payroll data |
| As-of date | Yes | The pay period being validated |
| Jurisdiction | Yes | Determines which statutory evaluators run alongside agreement rules |
How validation works
- The engine loads all approved rules from the selected contract(s)
- The jurisdiction's statutory evaluators are loaded (e.g., Ontario ESA overtime threshold)
- Each employee record is evaluated against every applicable rule
- The more favorable provision is applied (agreement rules cannot go below statutory minimums)
- Discrepancies between the data and the rules are logged as findings
Jurisdiction selection
The jurisdiction you select at validation time is immutable for that job — it determines which set of statutory evaluators run. This ensures that validation results are reproducible and auditable.
If your employees are covered by agreements in multiple jurisdictions, create separate validation runs for each jurisdiction.
See Jurisdictions for the full list of supported jurisdictions and their statutory evaluators.
Validation statuses
| Status | Description |
|---|---|
queued | Job is waiting to be processed |
running | Engine is evaluating records |
completed | All records evaluated — findings available |
failed | An error occurred — see error details |
Typical processing time: under 30 seconds for datasets up to 10,000 records.
What gets validated
The engine evaluates rules that can be tested against structured payroll data:
| Rule family | Requires |
|---|---|
| Overtime | Hours worked, hourly rate |
| Shift premiums | Shift start/end times |
| Vacation | Years of service, vacation hours/pay |
| Wages | Classification, step, hourly rate |
Rules that require context not present in payroll data (grievance timelines, termination notice periods) are included in the rule inventory but not in automated validation.
Column mapping
When you upload a CSV, the column-mapping engine attempts to automatically recognise fields. If automatic mapping fails, you'll be prompted to manually map columns.
The mapping is saved — subsequent uploads from the same HRIS format are mapped automatically.
Re-running validation
You can re-run a validation job at any time:
- After approving additional rule candidates
- After uploading a corrected dataset
- After changing the as-of date
- After making payroll corrections to verify remediation
Each run is a separate job with its own findings, preserving the audit trail.
Scheduling
Coming soon
Scheduled validation runs (weekly, bi-weekly, monthly) are on the product roadmap. Currently, validation runs must be triggered manually.