Work cost and income shows costs and income recorded for tasks and service requests over the selected period. Use it to compare monetary amounts for work. The report does not recalculate the cost of working hours or indicate that income has been invoiced or paid.

Open the report and select the data

In the browser's main menu, open Dashboard → Report pages and select a report page using the name selector at the top of the page. If the report is not on the page, an administrator can select Add new report, find the Work cost and income report and drag it onto the page. Adding reports and permanently saving settings require administrator permissions. See also adding and arranging reports.

Open Settings in the report's title bar. All filters contains two source options: Data based on task work costs and income and Data based on service request work costs and income. Both are selected in a new report. Clear one option to view only one type of work. If you clear both, the report has no work data to display.

Work expenses recorded on Android and iOS can also be included in the same data. The entry must first be saved to the service; a form merely filled in on a mobile device is not a data source for the report.

A spot's own device costs are not included in this report, even if the work relates to the same spot. A separate Device costs report is available for these in the report selection.

The period and permissions determine which rows are included

Tme period for the data at the top of the settings filters cost rows by their creation time. This does not generally mean the date the work was performed, the working date of a time entry, the invoice date or the payment date. For example, a cost row created in February for work performed in January belongs to the February data.

Time grouping for data divides the data into days, weeks, months or years. A new report defaults to monthly grouping and a calendar-based year view extending one year back: it includes the previous and current calendar years. For example, in 2026 this means 1 January 2025–31 December 2026. Always check the saved report's own settings. The year view cannot be combined with daily grouping; select another suitable period to examine individual days.

When reconciling a specific period, enter the start and end dates yourself. Without specified limits, work creation times are also used to determine the report's time boundaries, so this selection does not guarantee coverage of all cost rows created later. Fixed and relative time options are described in report periods and filters.

There is no general completion or billability filter for an administrator's data: saved cost rows for unfinished work may also appear. A supervisor's data includes only rows from completed tasks and service requests that they have permission to read. The work's completion time must also fall strictly between the start and end of the report period. For supervisors, both the cost row's creation time and the work's completion time must therefore meet the time limits. Being able to see a report page does not grant access to all its data.

The period filter uses the user account's time zone, which defaults to Helsinki. It has not been verified that daily, weekly, monthly and yearly groups align with that same local time zone. Before reconciling daily figures, pay particular attention to rows created near midnight or a change of period.

When are cost rows created and updated?

Working time, products and travel expenses

Saving a time entry alone does not create an automatic cost row. Automatic creation starts when a task or service request is marked as completed. At the same time, any running timers for the work are stopped at the time completion is processed.

Automatic rows are created if the work has products or travel expenses, or if it has a positive number of hours and at least one person who recorded time has Users work will be calculated as a cost? enabled in their user details. When any of these conditions is met, working time cost rows are created from all time entries for the work. The option therefore does not limit creation to that user's entries.

The cost of a working time row is minutes recorded ÷ 60 × the user's hourly value. The user's average hourly price takes precedence; if it is missing, the user's hourly price is used. An average hourly price set to zero also overrides the hourly price. If pricing information is missing, the cost is zero. The minutes of a finished time entry are rounded up to whole minutes. For example, 90 minutes at €40/h produces a cost of €60.

Correcting a time entry alone does not recalculate the monetary value of an existing cost row. After a correction, check both the hours and the saved cost. Differences between hours and costs are described in more detail in viewing hours and work costs.

The travel expense amount creates its own cost row. A daily allowance creates a separate row if its amount is not zero. A cost and a sales amount are saved separately for a product. The product cost depends on the pricing settings in use and the product row's source data; the report does not recalculate it using the product's current prices.

With FIFO/LIFO calculation, the product cost may initially be provisional. Later inventory processing updates a cost row awaiting calculation using the prices of the batches used and, if necessary, a fallback price. It does not change the row's creation time or recalculate the sales amount. As a result, the cost and the difference between cost and income for a previously reviewed period may change later.

Check the product cost and the actual inventory transactions separately. The disappearance of the pending indicator alone does not prove that batch-based calculation succeeded, as the indicator can also be removed in an error situation. Pricing rules, their order of precedence and fallback prices are described in inventory value and product cost price.

Other work costs and rounding on mobile devices

An individually added other work cost is saved as a cost row even before the work is completed. Its undiscounted value is quantity × unit price. The valid discount for other costs for the work's first customer changes the value to quantity × unit price × (1 − discount percentage / 100). Without an applicable discount, the original unit price is used.

The discount is checked when the expense is saved and again when the work is completed. A change to or expiry of the discount alone does not update an earlier row, but saving later or completing the work may change its amount. Because the row retains its original creation time, the change may appear in the figures for an earlier report period. Normal addition, editing and deletion of other costs are blocked for completed, cancelled or forwarded work.

When creating a new other cost on Android, the quantity and unit price are each rounded separately to the nearest whole number before being sent; halves round up. iOS sends the numbers as decimals. For example, without a discount, a quantity of 1.5 and a unit price of 10.50 produce 2 × 11 = €22 on Android and 1.5 × 10.50 = €15.75 on iOS. This difference arises before the report's own rounding of totals.

Therefore, check the saved values instead of the preview. Entry, permissions and checking mobile saves are described in adding another work cost.

What makes up cost and income?

The report totals saved work cost rows. These can include working time, products, travel expenses, daily allowances and other expenses. The report does not limit the data to working time or final product rows. The work's billability is not a filter in this report.

Row classificationIncluded in costIncluded in income
The row's value is a costThe saved row valueThe saved sales amount; a missing sales amount is treated as zero
The row's value is incomeNothingThe saved row value

The report does not add discounts, margins or taxes as a separate calculation step. It uses the values already saved on the row. In particular, income from a row classified as income comes from its value, even if a separate sales amount also appears in the work's cost view. A similarly named income column in different views therefore does not, by itself, guarantee the same calculation basis.

For example, a row classified as a cost with a value of €80 and a sales amount of €100 contributes €80 in cost and €100 in income to the report. If a €30 row classified as income is also included, the total cost is €80 and income is €130. The difference is €50. The combined cost and income of €210 is not profit, nor does the difference indicate the company's overall profit: the report contains only the saved rows included in its data.

Without grouping by entity, task and service request costs appear as separate series, but Income combines income from the selected work sources. The default chart is Stacked bar. The full height of a bar may therefore include both cost and income; use the legend to interpret the series.

Totals are rounded to two decimal places. Without grouping by entity, the cost total for each work source is rounded separately, and the combined income is rounded only after the sources have been combined. When grouping by entity, each work source's group totals are first rounded separately, and the combined group result is rounded again. This can cause a one-cent difference between grouped and ungrouped views.

Filter the work and select grouping

Settings → All filters contains folder, spot and customer filters. These filter data from both work sources through the work's current spot. The folder filter also includes subfolders of the selected folder. The customer filter is based on folders linked to the customer and their subfolders, rather than a separate billing customer for the work.

In the same section, service requests can be filtered by service request type, supervisor role and selected service requests. Tasks can be filtered by the user who performed them, the responsible party and the work order. Service request-specific filters do not filter task rows, and task-specific filters do not filter service request rows. The filter for the user who performed the task refers to that user, rather than the person who created an individual cost or time entry. Filters in different fields narrow the data together.

Note this filtering exception: if the folder selection contains no folders you can read, or the customer selection contains no customer-linked folders you can read, that filter alone does not empty the data. Other data may remain visible. Verify the result using a known spot; the presence of a customer selection alone does not prove that the data has been restricted to that customer.

In the Group by section of the settings, you can select By folder, By spot or By customer. A group's cost and income combine the selected task and service request sources. Grouping is based on current links:

  • By folder: the work must be linked to an existing spot and its folder. Other rows are excluded from the groups. The amount belongs to the spot's own folder, rather than automatically to its parent folder's group.
  • By spot: the work must be linked to an existing spot. Work without a spot is excluded.
  • By customer: the customer comes from the customer link on the work's spot folder. Rows without this link do not form a named customer group.

Grouped totals therefore do not necessarily match the ungrouped total. A group whose cost and income are both zero throughout the period does not receive a visible series.

The 25-spot limit when grouping by spot

When you select By spot and no actual data filters are applied, the report uses a maximum of 25 spots. Spots are selected from work in the data that has at least one cost row with a positive value. They are selected in order of the spot's latest update time, newest first. This is not a list of the 25 highest costs or incomes. A zero-value row containing only a sales amount does not meet the positive-value requirement for selection.

Rows from both tasks and service requests are used to select the spots, even if one work source is deselected. Rows from the disabled source are not included in the displayed totals, but they can affect the set of 25 spots and displace spots from the visible source.

Changing only the period or selecting a work source does not remove this default limit. An actual data filter, such as selecting specific spots, removes the default limit of 25 spots. For reconciliation, use an explicit spot filter and also check your own read permissions.

How does deleting work affect the report?

When a completed task or service request is deleted, its cost rows can be retained. Retained rows may remain in an administrator's ungrouped report in their original creation period, even though the work itself can no longer be opened. If costs are not retained, they are deleted along with the completed work.

Retained rows are no longer linked to the deleted work's current spot, folder or customer. Filters and grouping based on these links may therefore exclude them. They are also excluded from a supervisor's data, because inclusion requires existing, readable and completed work.

Deleting work therefore does not always reduce the report in the same way as deleting a cost row. If an administrator's overall report differs from a report grouped by entity, also check retained costs from deleted work.

Check the result

  1. Select a known spot and clear start and end dates. First view only tasks or only service requests without grouping by entity. Wait for the new data retrieval to finish.
  2. Open the Work costs tab on the form for the task or service request being compared. Check the saved row values, cost or income classification and sales amounts. Compare the cost rows' creation times with the report period. As a supervisor, also check the completion time and your permission to read the work.
  3. If a working time cost is missing, check that the work is completed, the conditions for automatic creation and the pricing information of the users who recorded time. For product costs, check for any later batch-based calculation. For other expenses, check the saved quantity, unit price and discount.
  4. Calculate cost and income using the rules described above. Only then add the other work source and grouping. If the totals change, check links, filters, rounding, the default limit when grouping by spot and retained rows from deleted work.
  5. If necessary, open the three-dot menu in the report's title bar and select Export to Excel. The export contains the series and periods generated for the report, rather than a breakdown of the original cost rows.

Save the shared report's settings

An updated chart does not mean that the selections have been saved. Changes made by users other than administrators are temporary viewing changes.

  • An individual saved report: an administrator sees Save Settings in the report's title bar when the settings are open. It saves that report's settings.
  • A new report or the whole page: at the top of the page, select Control report page → Save the page. This saves all reports on the page with their settings, order and sizes. Therefore, also check the selections in the other panels. A separate Save the page button may also appear at the top when changes are made.

Saving changes the configuration of the shared report page: other users also open the report with the saved selections. Their own read permissions still restrict the data.

Wait for the save success notification. Reload the report page and verify that the report and the desired settings were retained. Simply switching pages and returning may show unsaved selections from the same session. If saving the whole page returns an error, check the situation again: some reports may already have been saved.

Filtering, grouping and saving report settings do not change the work's cost rows, status or invoicing. Saving also does not freeze the report's figures. Changes to and deletion of cost rows, later calculation of product costs, changes to the work's current links and the progression of a relative period can change results retrieved later.