The answer, without building a sheet
One registry drives both the screen and the export, so what you look at and what you send are always the same numbers.
Dashboard & Analytics
Attendance Register & Summary
Daily and monthly, by entity, department, branch or period.
Leave Ledger & Balances
Every credit, every debit, and the balance that produced them.
Payroll Register
The full run, line by line, with statutory columns.
Headcount & Attrition
From actual joining and exit dates, not a manual count.
Expense Claims
Claimed, approved and settled, by person and category.
CSV On Demand
A preview on screen and a streamed export for anything larger.
One registry behind the screen and the file
The familiar problem with reporting is not that reports are missing. It is that the number on screen and the number in the exported file are produced by different code, and eventually they disagree — usually in front of an auditor.
One registry defines each register, and both the screen and the exporter read it. What you looked at and what you sent are the same figures by construction rather than by testing.
Registers, not just dashboards
A dashboard tells you attrition is fourteen percent. An inspection asks for the attendance register for March, in a specified form, for a specified establishment. Klok produces both, and the second is the one that carries a deadline.
Attendance register and summary, leave ledger and balances, payroll register, headcount and attrition, expense claims — each as a screen and as a file.
Exporting personal data is an event
Any export covering personal data is recorded: who ran it, when, and over whom. That is not friction for its own sake. When somebody eventually asks how salary data left the system, the answer needs to be a record rather than a recollection.
From a question to a file
Pick the register
Attendance, leave, payroll, headcount, expenses — defined once in the registry.
Scope it
Entity, workplace, period, grade. The same filters the screen uses.
Read it
On screen first, so the shape is checked before anything is sent anywhere.
Export it
The identical figures as a file — and the export itself recorded against your name.
Questions about reports & registers
Can we filter by branch or department?
Yes — period, entity, department and branch, with the same filters applied to the export.
Are these acceptable as statutory registers?
They are produced from captured timestamps and approved runs rather than reconstructed, which is what makes them defensible. Whether a specific format satisfies a specific authority is a question for your advisor.
Can we build custom reports?
A report builder and dashboards are on the roadmap. Today you get the core registers plus CSV, which covers what most inspections and reviews ask for.
Are the numbers on the dashboard the same as the registers?
They are derived from the same records rather than maintained separately, which is why a dashboard figure can always be traced to the register behind it. Two sources that disagree is the failure this design avoids.
Can we export a register for an inspection?
Yes, as CSV or XLSX, in the shape a register is expected to take. Every export is recorded in the audit trail, because who took a copy of payroll data is itself worth knowing.
Can managers see only their own team?
Yes — scope follows role. A manager seeing the whole company's salaries because reporting was not scoped is a common and avoidable breach.
Can we switch this module off if we do not need it?
Yes. Modules are switched on per company and what is off is not billed. There is no bundle you have to buy through to reach the part you actually want.
Who can see this data inside our company?
Access follows the role you assign, and every company's data is isolated from every other company's by a boundary enforced in the software and covered by automated tests. Nobody at another company can reach yours.
See it on your own data
Fourteen days, no card, no consultant. Import your Excel and watch the first record draft itself.