The software offers flexible options for pricing transactions.

Most commonly, transactions are priced by defining different hour prices and pricing models in the software, based on which each individual transaction automatically receives its price. You can also simplify price maintenance by setting up predefined role‑based and user‑specific price lists and linking them to customers and matters. In addition to hour-based transaction types, the power user can also define specially priced transaction types.

Pricing can also be defined at the matter level. An entire matter can be set as periodic‑fee‑based or fixed‑price, or a price limit can be set - when the limit is approached, the user recording the transaction will receive a warning. Customers can also be given a discount on the final invoice amount.

Hour prices can be defined at several different levels:

• The power user can define default hour prices for transaction types, users, and employee roles at the business unit level in the settings, applying to all customers and matters.
• Default hour prices can be overridden with customer-level prices, which apply to all of the customer’s matters, or with matter‑level prices, which apply only to a specific matter.
• The price of an individual transaction is determined according to the software's hour price hierarchy.

At the business unit, customer, or matter level, a user‑based or role‑based pricing model can be enabled, which affects the hour price hierarchy by offering additional pricing options:

• User‑based pricing model takes into account the hour prices defined for users either in their user profiles or when adding them to a customer or matter team. This model fully overrides the rates set based on the user’s employee role.
• Role‑based pricing model considers the employee role rates set either in the user’s profile or at the customer or matter level. This model overrides all hour prices  defined directly for the user in their profile or as a member of a customer or matter team.

If neither pricing model is used, the price hierarchy considers both user‑specific and role‑specific prices according to the hierarchy.

Role‑based and user‑based price lists defined in the settings simplify pricing because price changes can be easily updated for all customers and matters:

• Role price lists are created by defining hour prices for different employee roles. These can be created, for example, for domestic and foreign customers, corporate and private customers, or other customer groups. They can be linked either to a customer or a matter.
• User price lists work similarly, but hour prices  are defined per user. User price lists can be linked to matters.
• Both types of price lists can be created in different currencies.

The power user can also define specially priced transaction types in the settings whose price is not based on hours worked:

• A fixed‑price transaction type always assigns a predetermined fixed amount that cannot be changed even at the invoicing stage.
• A standard‑price transaction type also assigns a predefined standard price, but it is taken into account during invoicing, for example when making price adjustments.
• A unit‑priced transaction type allows the transaction to be priced per unit instead of per hour, for example per item.