Missing employee data is any required employee-level field that hasn't been reported yet - a case field that needs a value before Ason can calculate a correct result. Ason tracks this continuously, per employee.
- A Task is created automatically pointing at the missing field
- The missing-data view lists everything outstanding for an employee, so nothing gets lost between individual tasks
- Employees can complete their own missing data directly via ESS, without HR involvement
- A payroll period cannot be closed while relevant data is missing - surfacing gaps early is what keeps results always up to date without manual intervention
FAQ
Who resolves missing employee data - HR or the employee?
Either - via the regular case-change flow, or directly by the employee via ESS.
Does missing data block closing a period?
Yes - a payroll period cannot be closed while relevant data is missing.
How is a field reported once it's no longer missing?
The same way as any other case field - see New CaseChanges.
Why do these tasks exist - where do they come from?
A required employee-level case field doesn't have a value yet; Ason flags it automatically because it needs that value to calculate a correct result.
Do employees see their own missing data in ESS too?
Yes - an employee sees exactly their own outstanding missing-data items via ESS, and can complete them directly.
Can a period be closed while employee data is still missing?
No - it blocks closing, same as missing company data.
API Endpoints
| What | Call |
|---|---|
| List missing employee data | GET /tenants/{orgId}/payrolls/{payrollId}/missingdata/employees |