Findings
A finding is a discrepancy between an employee's payroll data and an approved rule. Each validation job produces zero or more findings.
Finding structure
Every finding includes:
| Field | Description | Example |
|---|---|---|
| Employee ref | Hashed employee identifier | a7f3b2... |
| Date / period | The pay period or shift date | 2025-01-15 |
| Rule | The approved rule that was violated | Overtime daily threshold (7.5h) |
| Source clause | Link to the agreement clause text | § 12.3, p. 47 |
| Expected | What the rule says should happen | 1.5× rate for hours beyond 7.5 |
| Actual | What the data shows | No premium applied for 9h shift |
| Delta | Estimated financial impact | $26.25 |
| Severity | Classification of the discrepancy | Error |
Severity levels
| Level | Meaning | Action |
|---|---|---|
| Error | Clear violation — the data contradicts the rule | Review and remediate |
| Warning | Possible violation — data is ambiguous or borderline | Investigate |
| Review needed | The engine cannot determine compliance — insufficient data | Provide additional data or manual review |
Reading the findings list
Navigate to Validation → select a completed job → Findings.
The findings list is sortable and filterable by:
- Employee: see all findings for a specific employee
- Rule: see all employees affected by a specific rule
- Rule family: see all overtime findings, all shift premium findings, etc.
- Severity: filter to errors only, or include warnings
- Financial impact: sort by estimated cost to prioritise remediation
Grouping
Findings can be grouped by:
- By employee — useful for individual remediation (e.g., back pay calculation)
- By rule — useful for identifying systematic misconfigurations
- By pay period — useful for time-bound analysis
Understanding the financial impact
The delta field shows the estimated financial impact of each finding:
Finding: Employee a7f3b2, 2025-01-15
Rule: Overtime daily threshold (7.5h)
Hours: 9.0 hours worked
Gap: 1.5 hours × $35.00 × 0.5 (overtime premium) = $26.25WARNING
Financial impact estimates are approximations based on the data provided. Actual remediation amounts may differ based on factors not captured in the dataset (e.g., retroactive rate changes, averaging agreements, or statutory holiday interactions). Always verify with qualified payroll professionals.
Aggregate statistics
The findings summary shows:
| Metric | Description |
|---|---|
| Total findings | Number of discrepancies found |
| Affected employees | Number of unique employees with findings |
| Affected rules | Number of rules with at least one finding |
| Total estimated impact | Sum of all financial deltas |
| By severity | Breakdown of errors, warnings, and review-needed |
Actions on findings
| Action | Description |
|---|---|
| Acknowledge | Mark as reviewed — finding remains visible |
| Dismiss | Mark as not applicable (with reason) |
| Export | Include in a report |
| Add note | Attach a note for your team or auditor |
All actions are logged in the audit trail.
Finding lifecycle
[Detected] → [Reviewed] → [Acknowledged / Dismissed]
↓
[Remediated] → [Re-validated] → [Resolved]After making payroll corrections, re-run the validation job to verify that findings are resolved. The system tracks the resolution status across runs.