> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chapt-13-time-and-attendance/view/options/tmx-configuration.md).

# TMx Configuration

**Settings**

**Path**

Type in the path used when import/exporting schedule and payroll files to TimeManagement. Use the folder icon to browse to your preferred directory.

**POS Sales Data**

Enable this option to export the sales data of POS employees even if they are not linked to Time & Attendance employees.

**Log**

**Level**

Select the log level you want to keep information. Make your selection between Standard, Detail and Debug or None to deactivate the Time Management log file.

![Button - View Log](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-ViewLog.gif)

Use the View key to access to log file. The file name is TMxexp.txt and is located under C:\POSERA\MaitreD\DATA\LOG directory.

<br>


---

# 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.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-complete-online-documentation/chapt-13-time-and-attendance/view/options/tmx-configuration.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.
