# 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. {#die-stunden-sind-erfasst-aber-was-sagen-sie-mreport-macht-aus-deiner-bexio-stundenerfassung-eine-echte-zeitauswertung-mit-soll-ist-vergleich-uberzeit-und-ferien src=324a0d8f} ## Recording is not analysing {#erfassen-ist-nicht-auswerten src=cdb15b8c} ^^ The actual problem 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? ## Time tracking, hour recording, time analysis {#zeiterfassung-stundenerfassung-zeitauswertung src=9238cae1} ^^ Briefly placed 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. ## From a time entry to a time analysis {#vom-zeiteintrag-zur-zeitauswertung src=3c51a7fd} ^^ How the analysis is built 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](/en/employee-reports/). ## What is answered afterwards {#was-danach-beantwortet-ist src=e9c76a2c} ^^ Concretely ### 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](/en/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](/en/work-report/).