> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-counters-6182411.md).

# Time Counters

Create and edit relevant Counter Units, which collects time and absence. This information is used to post time in the various modules and is used to generate pay data.

| Topic                                     |
| ----------------------------------------- |
| [Calculation ID](#field-1)                |
| [Time Counter](#field-3)                  |
| [Description](#field-5)                   |
| [Period](#field-7)                        |
| [Highlight](#field-8)                     |
| [\*\*\*OBSOLETE\*\*\* Publish](#field-9)  |
| [Favorite](#field-10)                     |
| [Hide](#field-11)                         |
| [Presentation Unit of Measure](#field-13) |
| [Adjustment allowed](#field-21)           |
| [Report Favorite](#field-31)              |
| [Report primo/ultimo](#field-32)          |
| [Report details](#field-33)               |
| [Period Sum](#field-120)                  |
| [Date Sum](#field-121)                    |
| [Content Type](#field-130)                |
| [BI Group](#field-8000)                   |
| [BI Group (Caption)](#field-8001)         |

## See also

[Adjust Time Counter](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/adjust-time-counter-6182626.md)

## Reference

\
\\

<details>

<summary>Calculation ID</summary>

Related Calculation ID.

</details>

<details>

<summary>Time Counter</summary>

The ID of the Counter.

</details>

<details>

<summary>Description</summary>

Description of the record.

</details>

<details>

<summary>Period</summary>

The period for which this Time Counter should sum.

</details>

<details>

<summary>Highlight</summary>

Highlighted with red foreground color.

**Related topics**

* [Time Calculation and Approval](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/time-calculation-and-approval-6182701.md)
* [Registration Cockpit](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/registration-cockpit-6182710.md)
* [JobManager - Registration Client](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/jobmanager-registration-client-6182711.md)
* [JobManager - Time Sheet](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/jobmanager-time-sheet-6182712.md)
* [JobManager - Time Sheet (Week)](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/jobmanager-time-sheet-week-6182713.md)

</details>

<details>

<summary>***OBSOLETE*** Publish</summary>

This field is obsolete. Function moved [to this](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/balance-setup-6182373.md).

</details>

<details>

<summary>Favorite</summary>

When marked as *Favorite* this is visible for [Caluclation and Approveal](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/time-calculation-and-approval-6182701.md).

**Related topics**

* [Time Calculation and Approval](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/time-calculation-and-approval-6182701.md)

</details>

<details>

<summary>Hide</summary>

If this is marked, the *Time Counter* is hidden in the *Calculated lines*.

</details>

<details>

<summary>Presentation Unit of Measure</summary>

For the timecounter. (e.g. day, month etc.) It is presented in calculated lines, specification of Time and Payment. Blank = Hours

</details>

<details>

<summary>Adjustment allowed</summary>

Can the Counter Units be adjusted.

**Related topics**

* [Adjust Time Counter](https://docs.dynalogic.com/birds-jobmanager-product-overview/user-guide/general/adjust-time-counter-6182626.md)

</details>

<details>

<summary>Report Favorite</summary>

Must be checked to appear on the pay specification.

</details>

<details>

<summary>Report primo/ultimo</summary>

Show as primo/ultimo balances. *Typically used with Flex Balances.*

</details>

<details>

<summary>Report details</summary>

Show details on reports. *Can be used for vacation, where each day should be listed.*

</details>

<details>

<summary>Period Sum</summary>

Calculated time for the period summed from [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/calculated-lines-6182625.md).

</details>

<details>

<summary>Date Sum</summary>

Calculated time for the date summed from [this table](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/calculated-lines-6182625.md).

</details>

<details>

<summary>Content Type</summary>

Select

* Present
* Not Present
* Absence
* All

</details>

<details>

<summary>BI Group</summary>

Select a value from [JobManager BI Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-bi-group-6182367.md). Record with the same value is being summed up.

</details>

<details>

<summary>BI Group (Caption)</summary>

Displays *Caption* as found in [JobManager BI Group](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/jobmanager-bi-group-6182367.md).

</details>


---

# 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://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-counters-6182411.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.
