> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/timesheets/set-up-hour-types-and-rates.md).

# Set up hour types and rates

Hour types determine how registered time is processed.

You use them for post-calculation, reporting, and invoicing.

### Common hour types

* **Working time**
* **Travel time**
* **Evening hours**
* **Weekend hours**

You can link one or more rates to each hour type.

{% hint style="info" %}
Separate hour types make reports clearer. They also help with correct charge-through.
{% endhint %}

{% stepper %}
{% step %}

### Open the hour types

Go to **Settings → Hour types**.
{% endstep %}

{% step %}

### Add a new hour type

Click **Add**.
{% endstep %}

{% step %}

### Fill in the settings

Give the hour type a clear name.

Then link the correct rate or rates.
{% endstep %}

{% step %}

### Create separate types for work time and travel time

A common base setup is:

* **Travel time work week**
* **Working hours work week**
  {% endstep %}

{% step %}

### Check the overview

After saving, your hour types appear in the overview.
{% endstep %}
{% endstepper %}

### Recommended setup

Start small. First create the hour types you actually use.

This is often enough:

* working time within the work week
* travel time within the work week
* overtime or evening hours
* weekend hours


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/timesheets/set-up-hour-types-and-rates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.