> 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/report-center/report/report-t-and-a/punches-summary.md).
# Punches Summary
Maitre'D punches summary report gives information on all the punches that were done for a specific period of time. This report is sorted by employee name. This report shows detailed information such as the real date and time the punches were recorder at, as well as the date and time that was used for payroll calculation. If there is a difference between these columns, the adjustment reason also appears. From the report filter window, select the dates and employees to be included in the report.
#### The following is a sample of the punches summary report:
**Task:**
Time & Attendance employee name.> Time In:
**Time Real:**
The employee actual clock in date and time
**Time used:**
Clock in date and time used for Maitre'D reports. This time is affected by your round up setup programmed under your Time & Attendance options and is also affected by an adjustment made by an authorized employee.
**Code:**
Reason for employee clock in adjustment
\>Time Out:
**Time Real:**
The employee actual clock out date and time
**Time used:**
Clock out date and time used for Maitre'D reports. This time is affected by your round up setup programmed under your Time & Attendance options and is also affected by an adjustment made by an authorized employee.
**Code:**
Reason for employee clock out adjustment
---
# 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/report-center/report/report-t-and-a/punches-summary.md?ask=&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.