Employee Directory
Employee Directory headcount and structure come from here.
Reporting that agrees with payroll, because it is payroll's data.
Kellith's insights are not a warehouse fed by exports. They are read from the same live records the modules maintain — so the number in the board pack is the number in the system.
What it does
One ledger, many questions
Headcount, attendance patterns, leave consumption — answered from the records themselves, not from a copy that was true last Tuesday.
Current and trended
See where the organisation stands today and how it has moved — absence creeping up, headcount by department, leave liability building.
Isolated to the foundation
Every query is tenant-isolated at the data layer. Your insight is computed from your records and nobody else's, structurally.
The end of the side spreadsheet
When reporting lives inside the system of record, the Friday-afternoon reconciliation meeting has nothing left to reconcile.
Part of one system
Reports & Insight doesn’t work alone.
Attendance & Time
Attendance & Time presence and absence patterns.
Leave Management
Leave Management consumption and balances.
Questions, answered
Where does the reporting data come from?
From the same live records the platform runs on — the directory, attendance days, leave decisions and payroll runs. There is no export pipeline to break or drift.
Can reports disagree with what the modules show?
No — and that is by design. Reports are computed from the module records themselves, so a figure in a report is the same figure the module would show you.
Is our reporting data isolated from other customers?
Yes. Tenant isolation is enforced at the data layer on every query, reporting included — not filtered afterwards in application code.
Begin the conversation
See Kellith with your organisation’s names in it.
A thirty-minute walkthrough with your org structure, your leave policies and your payroll calendar — not a canned demo.
Already run on Kellith? Sign in to your console.