Who are these instructions for?
Administrators
Invoicers
Project managers
Content of the instructions
1. Where does the hourly rate come from?
In the system, the hourly rate can be determined on several different levels.
If a price is set for the same job in multiple locations, the system uses the price with the highest priority. The priorities for the different price levels are listed in step 3.
2. The most common ways to determine the price
We recommend that you primarily use the product register and customer-specific price lists to determine prices. In exceptional situations, other levels of the pricing hierarchy can also be used.
Product register (most common and recommended)
The product register is the lowest level of the hierarchy.
A separate price is set for each product.
If the price is not specified at a higher level, the shifts are priced according to the price that is defined in the product register.
Instructions for maintaining a product register: Product management
Customer- or project-specific price list
The price list can be used to determine a different price for a product on a customer- or project-specific basis.
The same price list can be attached to several customers.
You can set start and end dates for the price list.
Instructions for creating and updating a price list: Customer-specific product price lists in Koho: creating, editing and managing
This is the recommended method when separate pricing has been agreed for the customer.
3. Hourly rate priority
In Koho, the prices of hour entries can be defined on 12 different levels. This list can be used as a checklist when an incorrect price is generated for a shift or when the price is determined in an exceptional way.
In section 2, we go through the most commonly used and recommended options.
Price list if Price List priority is selected in the price list settings
Settings → Price List
The price list can be allocated to the customer or project level.
The price of a work order, ticket or plan phase
The price can be set for an individual work order template, ticket, or plan step.
Rarely used.
Cost per employee for the task
Assigned to a task at either the task group or project level.
Used when the same work is charged at a different price depending on the worker.
Note! In some situations, this can also be implemented with the user proficiency factor setting.
Project cost per employee
On the Project Setup tab of the project edit view, set up the Set prices per employee button.
Used when you want to assign a fixed price to a specific user for all jobs in a project.
Customer's price per employee
Works in a similar way to the price per employee in a project.
The task's own hourly rate
In certain situations, a task can be assigned its own hourly rate in a project or task group.
Task-level prices are difficult to update en masse.
The project's own hourly rate
Is set in edit mode for the project.
The customer's own hourly rate
Assigned to the client in edit mode.
Price list set for the project
Price lists are managed under Settings → Products → on the Price list tab.
The price list is pinned to the project from the project edit mode.
Price list set for the customer
The price list is managed as above, but the price list is attached to the customer in their edit mode.
Employee's default price
To be configured in the user settings.
Product list price
To be set up in Settings → Products.
This is the most commonly used method.
4. The most common mistakes and solutions
Problem | Solution |
|---|---|
The shift has the wrong price | Check the pricing priority and whether the price is set to a different tier. |
The price was not updated for the old service | By default, price changes don't affect retroactively. To update prices in the billing view, select shifts → Update prices. |
Tips and best practices
Use the prices in the product register by default.
If necessary, set customer-specific price lists.
Use other pricing tiers only when you actually need.