> For the complete documentation index, see [llms.txt](https://gitbook.clockin.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.clockin.de/english/getting-started-with-clockin/einrichtung-fuer-admins/enter-starting-hour-balance.md).

# Enter Starting Hour Balance

If the employee has already accumulated overtime or minus hours before starting with clockin, you can enter this balance in the Hour Overview.

**Here’s how:**

1. Go to the employee’s profile and open the **Hour Overview** tab.
2. Click the **pencil icon** in the “Previous Month” column to enter the overtime or minus hours.
3. If the employee already had overtime, simply enter the number — for example, 10 for 10 overtime hours. For minus hours, add a minus sign in front — for example, 10 for 10 minus hours. (☝️ *Decimal values are also supported. If an employee has 35.5 overtime hours, you can enter it exactly like that.)*

✅ Click the **floppy disk icon** to save your entry.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.clockin.de/english/getting-started-with-clockin/einrichtung-fuer-admins/enter-starting-hour-balance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.