Analysing time

Analysing bexio time tracking

The hours are recorded – but what do they say? mReport turns your bexio time tracking into a real time analysis, with expected against actual, overtime and vacation.

An analysis of the time recorded in bexio, with a yearly calendar heatmap and a weekly view comparing expected and actual hours

The actual problem

Recording is not analysing

Time tracking does one job very well: it collects time entries. What it does not do is answer the question asked at the end of the month – how much somebody actually worked, measured against what was agreed. That is where the handwork starts in a lot of companies: export from bexio, pivot table, subtract the public holidays by hand, go looking for vacation days, add up a balance.

Questions that time tracking alone leaves open:

  • How many hours should this person have worked in the period?
  • How much overtime or undertime is currently open?
  • Are public holidays and vacation taken counted correctly?
  • What does the balance look like across several years?
  • Where does effort arise that never gets billed?

Briefly placed

Time tracking, hour recording, time analysis

The terms get used interchangeably but describe different steps. Time tracking and hour recording are the collecting of entries – who worked on what, when. bexio does that reliably, and mReport changes nothing about it.

Time analysis is the step after: the same hours condensed and measured against rules – expected hours, public holidays, vacation – so that a list of entries becomes a statement. Put that analysis into a document you can hand on – to an employee, a client or management – and it becomes time reporting. This analysis layer is what many setups are missing, and it is exactly what mReport supplies, without you recording time a second time.

So anyone looking to analyse bexio time tracking is rarely looking for another recording tool, but for the analysis on top of it: expected hours, public holidays, vacation, and a balance that holds across months and years.

How the analysis is built

From a time entry to a time analysis

mReport reads the time recorded in bexio and sets it against the expected working time you define once a year: weekday hours, the holiday calendar, shortened days before a holiday, and the vacation entitlement. Out of that comes a day-by-day working-time analysis per person, with a calendar heatmap, a weekly view and an overtime or undertime balance.

Because the rules are kept centrally, the same arithmetic applies to everyone – and it stays correct even when a workload or a working pattern changes mid-year. The result is an hours report per person; the detail is on the employee reports page.

Concretely

What is answered afterwards

For HR administration

Overtime and undertime, vacation taken and remaining, and overtime paid out – derived traceably rather than maintained in a spreadsheet that grew.

For management

How much of the time worked is billable, where internal and non-billable effort arises, and how utilisation is spread across the team – see the company dashboard.

For talking to clients

Project hours measured against an hour budget and handed on as a report – without exposing internal entries. See the work report.

Frequently asked questions

Answers to a few common questions.

What is the difference between time tracking and time analysis?

Time tracking collects the entries – who worked on what, when. The analysis sets those hours against the working time agreed and counts in public holidays, vacation and overtime. bexio does the first part, mReport the second.

What is a time analysis?

A time analysis condenses the hours recorded and measures them against rules: expected hours per weekday, public holidays, vacation. A list of time entries becomes a statement – how much somebody worked, measured against what was agreed. mReport does that analysis for the time recorded in bexio; recording stays in bexio.

Do I have to record the time again in mReport?

No – recording stays entirely in bexio. mReport reads the entries and analyses them; nothing is written back.

How are public holidays and vacation counted?

Public holidays come from a company holiday calendar per year, vacation taken from the recorded entitlement. Both go into the expected working time automatically, including shortened days before a holiday.

Can I take overtime from several years into account?

Balances can be analysed across year boundaries, including the comparison with the previous year and overtime already paid out.

Do I need an additional time-tracking tool?

No. Recording stays entirely in bexio – only the analysis is added on top. If you already record time, nothing about your recording has to change.

How long does setting up take?

The bexio connection takes a few minutes. After that you define the working-time rules once per year – weekday hours, public holidays and the vacation entitlement – and the reports are ready.