Employee reports
One clear hours report per person, built from your bexio time – with overtime and undertime, vacation, public holidays and an expected-versus-actual comparison, calculated for you.
Per person
This is how plain bexio time tracking becomes a real working-time analysis: every person gets their own hours report, laying out the time recorded in bexio in a form anyone can follow – day by day, and summed across the whole period. You can analyse employee hours straight out of bexio, without recording them again anywhere. Managers and employees then look at the same traceable figures instead of holding two versions of a spreadsheet against each other.
What is in every report:
This fits you if
The employee hours report is meant for companies already recording their time in bexio who need a clean working-time analysis per person – typically SMEs, agencies and service providers with several employees. If you keep a spreadsheet template per employee today, this replaces exactly that file.
It earns its place wherever employee hours have to be reviewed regularly: before an annual review, for payroll, in a discussion about overtime and remaining vacation, or when management wants to know how the team stands against its expected hours. If what you mainly need is billing towards clients, the work report is the better place to start.
Counted automatically
An hour balance is only correct if vacation and public holidays are handled correctly. mReport takes both from your central base data: the public holidays come from the company holiday calendar kept for that year, and where the day before a holiday counts as shortened in your company, that reduced expectation goes into the calculation too.
Vacation taken is measured against the recorded vacation entitlement in the same pass – remaining vacation and the hour balance come from one source and cannot drift apart. You maintain these rules once a year, not once per report and not once per person. Your time in bexio is left unchanged; mReport only reads it, as the privacy policy describes.
Balance
Rather than arguing about numbers, the report shows how the balance came about. A real example from the demo report for July 2026:
The arithmetic goes through step by step: 171.50 h worked against 184.00 h expected gives −12.50 h. From that come the 8.00 h paid out as overtime on 23 July – hours already compensated must not show up again in the open balance. What is left is the reported balance of −20.50 h.
That replaces the spreadsheet otherwise kept per person – including the formulas that have to be adjusted every time the year turns. Every one of these figures can be traced back to the individual day, and the same expected-versus-actual comparison carries on across the whole year and across year boundaries. The report states the vacation in the same breath – in this example 97.50 h taken and 102.50 h available. How many employee reports your plan includes is on the pricing page.
Ready to hand over
Every report exports as a PDF – in the same layout you see here: with the company logo, the recipient, the period, the working-time and vacation figures and the overtime paid out. The document is ready to send, print or file; there is nothing to rework.
That takes the employee report straight into the annual review, into payroll or into the personnel file. How the export works for every report type is on the PDF export page.
Real working years
A year rarely runs cleanly from January to December. These are the points where the hand corrections in a spreadsheet come from – and exactly what mReport takes off you.
If somebody moves from 100 to 80 percent in June, that must not distort the yearly balance. For changes like this you record a further dataset with its own validity period: every month is calculated under the rules that applied at the time.
Overtime that has been paid out can be recorded as a payment. It is counted in the balance, so the overtime reported still matches what is genuinely still open.
Overtime does not disappear on 31 December. Balances, vacation entitlement and vacation taken can be analysed across year boundaries – including the comparison with the previous year.
Answers to a few common questions.
mReport compares the actual hours recorded in bexio with the expected working time configured for each employee (weekday hours, shortened days before a public holiday) and reports overtime and undertime as a balance – across several years if you want.
Both go into the calculation automatically: the public holidays come from the company holiday calendar kept for that year, and vacation taken from the recorded entitlement. Expected and actual hours are compared correctly without you deducting individual days by hand.
If somebody changes their workload or their working days mid-year, you record a further dataset with its own validity period. Every month is calculated under the rules that applied at the time – the yearly balance stays correct.
Overtime that has been paid out can be recorded as a payment. It is counted in the balance, so the overtime reported still matches what is genuinely still open.
You choose the period for each report: a single month for the running overview, or the whole year for an annual review and your records. Both views export as PDFs.
The working-time settings are configurable per year – weekday hours, the choice of public holidays and the vacation entitlement included – optionally carrying the previous year over as a starting point.