Missing Data report
The Missing Data report lists employees with incomplete profiles, and which field is missing on each. It is the cheapest way to find problems that would otherwise surface during a pay run.
Where: My Team › Reports › Missing Data You need: the Reports (team) right
Run this before your first payroll
Most first-payroll problems are not payroll problems. They are a profile field nobody filled in — a missing tax number, no bank details, no hire date — and they surface at the worst possible moment, when a pay run fails or produces a wrong figure.
Finding them here costs minutes. Finding them mid-run costs a cut-off.
Worth running:
- Before every pay run, at least for the first few cycles
- After a bulk import, because imports are where gaps arrive in volume
- Monthly, once things are stable
What it shows
Each row is one employee and one missing field, with their placement so you can see whether the gaps cluster in one department or intake.
An employee missing several fields appears on several rows. A short list of people can therefore produce a long report — that is the report doing its job, not duplication.
Fixing what it finds
For a handful of employees, open each profile and fill the gap.
The report also offers one-click reminders to the employees themselves, which is the right move for anything only they can supply — bank details, emergency contacts, a government ID number. Chasing those by hand is wasted effort when the report can ask them directly.
For anything larger — a whole intake missing the same field, or a field introduced after people were added — use Profile Manager to edit many profiles at once rather than opening them one by one.
Reading the pattern
The pattern usually tells you the cause:
- One field missing across many people — that field was probably not in your import
file, or was added to KAMI after those people were created.
- Many fields missing on a few people — those profiles were created in a hurry, often
by hand while someone was mid-task.
- Gaps concentrated in one department or branch — whoever onboards for that area is
working from a different checklist.
The second and third are worth fixing at the source, not just in the data.