> 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/troubleshooting-and-known-issues/q-and-a-per-diem.md).

# Q\&A (Per Diem)

Per Diem setup in JobManager.

Create a new IPC category "Per Diem"

In this category you create 3 new triggers (for each Per Diem), for use in registration.

Examples could be:

* LodgingMealsDay(Daily)
* LodgingMealsStart(Start)
* LodgingMealsStop(Stop)

Create a new Registration add-on "Lodging and Meals"

and fill in the triggers Start, Stop and Day in the new section Automation.

Min/max duration is for the system to se how far the calculation can be back and forth in time.

### Calculation options <a href="#calculation-options" id="calculation-options"></a>

*1. Per Diem every day - uses Start/Stop and Daily trigger*

*2. Per Diem last day - uses Start/Stop trigger*

to be set up at Allocation, nothing (times is calculatid last day), Daily (time is calculated each day) *Job (for projects) allocates the time for each job during the day*

It is also possible to set up a Pay type to payment in salary.

## See also

## Reference

[Registration add-on](https://docs.dynalogic.com/birds-jobmanager-product-overview/integrations-and-technical-reference/tables/registration-add-on-6182339.md)

\
\\


---

# 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/troubleshooting-and-known-issues/q-and-a-per-diem.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.
