> For the complete documentation index, see [llms.txt](https://docs.milientsoftware.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.milientsoftware.com/help/setup/travel-and-expense/t-and-e-configuration.md).
# T\&E configuration
To configure the various expense types navigate to the travel and expense configuration found under Setup and Travel & Expense.
Below are the most used expense types described on how to configure, to see more specific as to what values to use, find the correct year in the menu under Expense types.
## Expense types
### Daily allowance
The daily allowance section consists of fields to be used for each type of meal/compensation. These are activated/shown by select what should be available in the "Configuration" section, and the "Supported fields" box. Select those needed for the expense type.
### Car allowance
The car allowance section contains the fields used when filling out the travel taken place. In addition there are fields to be used to register rates to be used.
---
# 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://docs.milientsoftware.com/help/setup/travel-and-expense/t-and-e-configuration.md?ask=&goal=
```
`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.