> 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/view/options/end-of-day.md).

# End of Day

### **End of Day**

**Automatic End Of Day**

Enable this option for the Back-Office to attempt closing the day at the time programmed in the Time For End Of Day option below. If no time is set, nothing will be done.

**Display End Of Day Result**

Enable this option to show a confirmation window after the End Of Day to confirm if it has completed successfully or not.

**Time for End Of Day**

This is the time when End Of Day is processed. If the system was not able to run the End Of Day, a warning message displays. If you enter 00:00, the system will not check for end of daytime. Time enter must be between midnight and noon.

**POS Reboot Time**

This is the time that the workstation will reboot automatically. If you enter 00:00, the system will not check to reboot workstations.

**Days Kept Summary**

This is the number of days that you want the computer to keep for the daily report. Enter your input in this field. The maximum is 9999 days.


---

# 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/view/options/end-of-day.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.