Reports
The question finds its report
Headcount by department, leave liability, overtime by site: the recurring questions exist in the library already, scoped to what the asker is allowed to see.
The situation
The organisation, asked about constantly.
By department
Sales316
Engineering483
Operations402
Around every workforce stands a ring of people who need numbers about it: a board asking for headcount and cost, a finance partner reconciling payroll, an auditor sampling compliance, a department head tracking absence. In most companies each request triggers the same ritual: export, filter, pivot, format, email, and hope nobody asks how the number was reached, because the answer is a chain of manual steps that no one can replay.
Where it breaks
The problems that live in this world.
Not generic HR pains: the specific ways this environment grinds people teams down, one honest description at a time.
Every report is rebuilt from scratch.
The monthly headcount pack is assembled by hand from exports, every month, by someone whose actual job is waiting. The same questions produce the same work forever.
Numbers arrive without their working.
Two reports disagree about headcount because they silently counted differently. Without the derivation on the page, every figure is an assertion, and reconciliation meetings are where the time goes.
Sensitive data rides in attachments.
Salary reports travel as spreadsheets in email, forwarded past the audience they were built for. Once exported, nobody controls, or even knows, who saw what.
Nobody logs the asking.
Who ran the compensation report, who exported the compliance list, and when? For a regulated business, the absence of that log is itself a finding.
Day to day
Three operational realities, handled.
Attendance, pay and compliance are where this world gets judged. Here is how each one runs on a connected record.
01
The recurring questions, pre-answered.
The asks that return every cycle, headcount by department, absence by site, cost by country, already exist as ready-made definitions in Reports, which comes with every module you run, so answering means running something, not rebuilding it.
02
Shaped once, kept forever.
Narrow any definition by department, country, status, type or date range, then keep the shaped view under its own name. Next month the same question is one click, and the answer travels into CSV or a branded PDF with the basis of every figure printed alongside it.
03
Safe to hand to the checker.
Visibility follows the role of the person asking, pay data demands a one-time email code on top of a signed-in session, and tenant admins can open a log of who ran and exported what. The evidence chain includes the asking itself.
The modules that fit
Take what fits, leave the rest.
HarmoniHRM is modular. These are the pieces that earn their keep in this world, each reading and writing the same connected record.
Reports→
The product this job runs on. See the full Reports product page for the library, saved views, exports and the run log.
Employee Management→
The connected record the reports read, so every figure comes from live data, not an export of an export.
Payroll→
Payroll and cost reporting from the same runs that paid people, behind step-up protection.
Analytics→
The companion product for trends and exploration, where Reports delivers the tabular answers.
Compliance watch→
The compliance position that reports export as auditor-ready evidence.
A working day, connected
How the day actually runs.
Follow one realistic cycle through HarmoniHRM, step by step, from the first event of the day to the numbers that close it.
01
The question finds its report
Headcount by department, leave liability, overtime by site: the recurring questions exist in the library already, scoped to what the asker is allowed to see.
02
Filters shape it to the ask
Department, country, status, type and date filters narrow it to exactly the population in question, without touching a formula.
03
The saved view ends the ritual
The monthly pack becomes a set of saved views run on demand, so the same question stops producing the same work.
04
Export carries the working
CSV for the analyst, a branded PDF for the board, and on both, the line naming how each figure was reached goes along for the ride.
05
Sensitive reports demand more
Anything pay-bearing asks for a one-time code sent to the runner before a figure appears, so permissions are never the last line of defence.
06
The log closes the loop
Who ran what, exported what, and when sits in a record tenant admins can open, so the trail behind the evidence is itself evidence.
Who lives this
The people inside this playbook.
Employee Management
Filters shape it to the ask
Department, country, status, type and date filters narrow it to exactly the population in question, without touching a formula.
Payroll
The saved view ends the ritual
The monthly pack becomes a set of saved views run on demand, so the same question stops producing the same work.
Analytics
Export carries the working
CSV for the analyst, a branded PDF for the board, and on both, the line naming how each figure was reached goes along for the ride.
Asked before buying
The questions that come up every time.
Do we need Employee Management for Reports?
No. Reports is its own product with its own surface, and it comes with every module you run at no extra charge. This page is about the reporting job; the Reports product page covers the product itself in full, from the library to the run log.
What does a report actually contain?
A tabular answer to one question, shaped by the filters you set, with a line stating how each number was reached. That line survives into the CSV and the branded PDF, so the recipient can trace a figure instead of taking it on trust.
Who can run which reports?
Whatever a person’s role permits, and nothing more. Pay-bearing reports add a second gate, a one-time code sent by email before anything is shown, so a borrowed session never opens salary data.
Is there a record of report usage?
Yes. Runs and exports are written to a log tenant admins can read, which is exactly what an auditor wants: not just the number, but who produced it and when.
Run it on your own organisation.
Modular pricing, no long contracts. Start with the modules this world actually needs and add the rest when you are ready.