> 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/period-6182303.md).

# Period

Relevant periods must be created before operation. Below is an example of relevant periods:

| Period   | Description                      | Period length |
| -------- | -------------------------------- | ------------- |
| 20Y      | Infinite period                  | 20Y           |
| DAY      | Day                              | 1D            |
| WEEK     | Weekly                           | 1W            |
| YEAR     | Yearly                           | 1Y            |
| 14DAYSEW | 14 days, start equal week number | 14D           |

The example shows a set of typical periods needed. The period 20Å is used as an infinite period, and can be used to control a flex-balance in an undetermined amount of time. With this feature, it is not needed to transfer balances from one year to the next.

**Note! Periods are not allowed to be changed after operation of the system has started**

Created, but never used periods, can be deleted, however, any associations on time counting units/pay counting units must be deleted, before this can be done.

| Topic                     |
| ------------------------- |
| [Period](#field-1)        |
| [Period Length](#field-4) |
| [Description](#field-5)   |
| [First Date](#field-8)    |
| [Floating](#field-10)     |

## See also

## Reference

[Period Line](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/period-line-6182305.md)

\
\\

<details>

<summary>Period</summary>

ID for the period.

</details>

<details>

<summary>Period Length</summary>

Period length defines the length of the period

</details>

<details>

<summary>Description</summary>

Description of the record.

</details>

<details>

<summary>First Date</summary>

First date in the period

</details>

<details>

<summary>Floating</summary>

Indicate whether the Period is floating. This means always calculate period from the required date and backwards. The length of the period is still given by the [Period Length](#field-4) field.

Can be used in eg.:

* Calculation Warnings/Error
* Time Counters
* Pay Counters

No Periode Lines are created if Period is floating.

**Related topics**

* [Calculation Warnings/Errors](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/calculation-warnings-errors-6182409.md)
* [Time Counters](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/time-counters-6182411.md)
* [Agreement Pay Counters](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/agreement-pay-counters-6182511.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/period-6182303.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.
