Start by selecting the period you want to review. General working time, hours logged against tasks and service requests, absences, quantities and costs in euros represent different things. Check the contents and units of the view as well as the period.
Required features and permissions
Tracking general working time requires the working time feature to be enabled in your environment. You can review hours related to a task or service request even without general working time tracking. You can only see entries and jobs that you have permission to view. Viewing other users' hours and editing entries require separately granted permissions.
Daily and weekly hours on mobile
On Android, tap the clock icon at the top of the home screen, to the left of the search icon. On iOS, tap the working time icon at the top of the home screen, next to the search button. The view shows the current status of general working time and the day's and week's time entries.
Select the day you want to review from the days of the week. Use the arrows in the week selector to change weeks. A week runs from Monday to Sunday. Open the day's entries by tapping an entry type row or its duration. On iOS, the detailed views for working time, lunch, sick leave, vacation and travel expenses are available only when the general working time feature is enabled.
General worktime on Android and General Worktime on iOS represent general working time tracking. Task and service request times represent time allocated to those jobs. The same time may be included in both general working time and an entry for a job. Android's On items breakdown helps distinguish time allocated to jobs from general working time.
The day's Total adds together general working time, task and service request times, lunch, sick leave and vacation. Overlapping time is not removed, and lunch is not deducted from this total. The weekly total adds up the durations of the week's entries in the same way. These figures therefore do not, on their own, indicate hours worked, approved hours or billable hours.
For example, 8 hours of general working time, 2 task hours worked within that time and a 30-minute lunch entry produce a total of 10:30. This does not mean a 10.5-hour working day.
For travel expenses, the number shown on mobile is the number of entries, rather than euros, kilometres or hours. Open the travel expense row to check the entries. Quantities for entry types measured in pieces are also separate from hours; do not add them to working time.
Mobile date filtering and ongoing entries
Daily and weekly searches on mobile are based on the entry's start time. An entry that continues overnight is not split between days. For example, an entry that starts at 22:00 on Monday and ends at 06:00 on Tuesday appears in Monday's information with a duration of eight hours. An entry that started in the previous week is not included in the new week's total just because it ended this week.
Mobile summaries are not limited to approved or completed entries. They may also include ongoing and processed entries. The duration of an ongoing entry is based on the time between its start and the moment the data is retrieved. The running timer for general working time also appears as a separate status; do not add it to the total again.
Reviewing entries in the browser
In the browser's main menu, select Working time monitoring and open its Working time main tab. It contains the following separate views:
- Log entries shows individual entries of all types. Use it to check start and end times, the user, the connection to a job, status, approval and unit. The open icon on a table row opens the entry's details; a task or service request link opens the related job.
- Working time groups general working time, lunch and absence entries by user and start date. Task and service request entries are not included in this view.
- Log entry sums separates general working time, lunch, sick leave, vacation and time allocated to tasks and service requests by user. Quantities measured in pieces are broken down by entry type.
Set the date filter using the selector above the table. For a precise comparison, select Filter by specific time range and fill in Date range. Filter the results to yourself using the search field in the table's user column. Also check the column filters and any filters in a saved view.
The default period is not the same in every view: the one-month selection in Log entries means one month back from the current time, while Log entry sums uses a calendar month. Previously used filters or a saved view may be restored.
The date selector in Log entries is titled Log entry create time, but the search is based on whether the entry overlaps the selected period. A time entry that started before the period may therefore also appear. The row's Duration shows the full duration of the entry, rather than just the portion within the selected period. For an ongoing entry, it shows the time elapsed so far.
Absences and limitations when comparing totals
In Log entry sums, vacation is calculated as 7.5 hours for each calendar day covered by the entry. For sick leave entirely within the selected date range, the entry's duration is used, up to a maximum of 7.5 hours per calendar day. Calendar days include weekends. When only the portion of an absence overlapping a boundary of the date range is calculated, the view uses 7.5 hours for each calendar day included in that portion. These are calculation rules for this totals view, rather than rules shared by mobile and all reports.
The totals view also has a limitation for entries that cross the boundaries of the date range: the overlapping portion may replace other minutes already totalled for the same user and entry type. If the start or end of the period falls within an entry, verify the result using the individual entries and Worktime Report.
For a daily comparison, open Working time monitoring → Worktime Report. It splits a time entry that continues overnight between calendar days in the environment's time zone and includes the portion within the selected period. Quantities measured in pieces are allocated to the start date. Open a daily total cell in the report to see the underlying entries. The same overnight entry may appear in the underlying lists for several days, but it is still a single entry. See also checking Worktime Report and processing entries.
Why can the number of minutes differ?
On mobile, the duration of an individual entry is rounded down to whole minutes. The stored duration of an ended entry is rounded up. Log entries uses this stored duration. Log entry sums, in turn, rounds the difference between the timestamps to the nearest minute.
For example, a 61-second entry gives one minute on mobile, two minutes as the stored duration and one minute in the summed calculation. Multiple short entries can therefore increase the difference between views.
Worktime Report uses the stored minutes for an ended entry within a single day. The daily portions of an overnight or ongoing entry are calculated from the difference between timestamps. The report's daily breakdown does not change the original entry.
A working time rule may also affect the duration of general working time. The automatic calculation deducts lunch already logged for the same day before applying the rule's own lunch deduction. If lunch has not been logged and automatic lunch deduction is enabled, the calculation deducts the amount specified by the rule and creates a lunch entry. It is therefore helpful to review general working time and lunch separately. See working time rules and entry types.
Hours and costs in euros for a specific job
Open the task or service request details in the browser. On the form, select Logged work hours to check the job's entries and Work costs to check its cost rows. These are separate tabs on the browser form; the mobile daily summary is not a cost calculation for the job.
Work costs can include working time, products, travel expenses, daily allowances and other costs added separately. Saving an hour entry alone does not create an automatic cost row. Automatic creation starts when the task or service request is marked as completed. At the same time, any open timers for the job are ended at the time completion is processed.
Automatic rows are created if the job has products or travel expenses, or if it has a positive number of hours and Users work will be calculated as a cost? is enabled in the user details of at least one person who logged time. When any of these conditions is met, working time cost rows are created from all hour entries for the job. The setting therefore does not, on its own, limit cost rows to that user's entries.
The cost of a working time row is entry minutes ÷ 60 × the user's hourly value. The user's This user's average hourly price takes priority; if it is not set, This users hourly price is used. An average hourly price set to zero also overrides the hourly price. If no pricing information is available for the user, the cost is zero. For example, 90 minutes at €40/h produces a cost of €60.
The travel expense amount is entered on the travel cost row, and the daily allowance amount is entered on a separate daily allowance row if it is not zero. The product cost depends on the pricing method used; see inventory value and product cost price. Adding a separate expense is described in adding another work cost.
Cost is a different value from the product's selling price, the amount transferred to invoicing or the job's planning estimate. Check the cost and sales revenue columns separately.
The value of an existing cost row does not change automatically when only an hour entry is corrected. The displayed unit price for a working time cost is derived from the stored cost in euros and the entry's current duration: the duration may therefore change while the cost stays the same. After a correction, check both the hours and the cost row and, if necessary, ask a user with permission to manage costs to look into the correction. See correcting an hour entry.
Verify the result and export the data
Compare the same users, exactly the same date range, and the same entry types, units, statuses and approvals. A completed time entry does not mean that the entry is approved or that the related job is completed. End or check open timers before making the final comparison.
Retrieve the data again after making changes. Open the entries underlying an unclear total, check their start and end dates, and compare work costs only with entries related to that job. Working time monitoring has a separate Traveling allowance main tab for reviewing travel expenses.
Export view to Excel above the table exports the data from that view to Excel. Wait for the data to load and check the filters before exporting. Durations in Log entry sums are exported in minutes, although the table displays them in hours and minutes. For example, 1:30 corresponds to a value of 90 in the export. Exporting does not approve entries or mark them as processed.