> 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-complete-online-documentation/chapt-13-time-and-attendance/time-and-attendance-reports.md). # Time and Attendance Reports ## Time and Attendance Reports Icon - Time & Attendance


Activity	Labor by Employee Code	Schedule per Days with Salary	Tips Transfer
Coffee Break by employee code	Labor by Employee Name	Schedule per Tasks	Weekly Detail by Employee Code
Coffee Break by employee name	Labor Cost	Schedule per Task with Salary	Weekly Detail by Employee Code with Salary
Combined Report for Payroll Data Entry	Labor Department Summary	Schedule with Salary	Weekly Detail by Employee Name
Employees Availability	Labor Task Summary	TEFRA by Department	Weekly Detail by Employee Name with Salary
Employees by Code	Labor Department Summary	TEFRA by Employee Code	Weekly Summary
Employees by Name	Labor Task Summary	TEFRA by Employee Name	Weekly Summary with Salary
Employees per Task	Punches by Employee Code	TEFRA Summary
Employees Task List by Code	Punches by Employee Name	Time Card by Date
Employees Task List by Name	Punches Summary	Time Card by Employee Code
Employees Weekly Work Schedule	Schedule	Time Card by Employee Name
Employee Weekly Work Schedule with Salary	Schedule per Days	Tips Declaration
Employees with Tips Performances

--- # 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-complete-online-documentation/chapt-13-time-and-attendance/time-and-attendance-reports.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.