> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/server-control/tools/memoire-file-analysis.md).

# Memoire File Analysis

### Memoire Files Analysis

The Memoire Files Analysis option enables Payfacto programmers to locate any errors in case of Back-Office problems. This function is not meant to be used by end-users, and should only be performed under the supervision of a PayFacto Software Support Specialist.

**Data**

Enable this field to select the MEMOIRE.DAT file from the DATA directory.

**Rebuild**

Enable this field to select the MEMOIRE.DAT file from the REBUILD directory.

**Disk**

Select this option to export the selected MEMOIRE.DAT file to a TXT file. The file generated is named MEMOIRE.TXT.

**Printer**

Enable this option to display the selected MEMOIRE.DAT file on the screen to be subsequently printed.

**Current**

Enable this option to analyze the MEMOIRE.DAT file from current day.

**Previous Days**

Enable this option to analyze the MEMOIRE.DAT file from one of the last 31 days.

**Date Selection**

Enter here the month's day number of for which you want to analyze the MEMOIRE.DAT file.


---

# 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.maitredpos.com/maitred/maitred-online-help-contents-by-module/server-control/tools/memoire-file-analysis.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.