> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/october-2026/payroll/payroll-reports/attendance-summary-report.md).

# Attendance Summary Report

Logic ERP has corrected the **WEEKLY OFFS / HOLIDAYS** column of the **Attendance Summary Report**.

***

### **Step 1: Open the Report**

* Navigate to **Payroll Reports** and open the **Attendance Summary Report**.
* Tick the **WEEKLY OFFS / HOLIDAYS** column in the report's column settings.

***

### **What's corrected**

* **WEEKLY OFFS / HOLIDAYS** now shows the number of days the employee worked on their own week-offs. Earlier it always showed 0. A half day worked on a week-off counts as one day.
* Each employee's own week-offs are used: employee-wise week-offs (for example from their roster), or the week-offs of the employee's branch. Earlier every branch's week-off was applied to everyone.
* This column will now show figures where it showed 0 before. This is intended.

***

### **Comp-off**

* Comp-off days are counted in **DAYS WORKED** and **ABSENT DAYS**, as casual leave is. A half day of comp-off counts like a half day of casual leave in **DAYS WORKED**, **DAYS PRESENT** and **ABSENT DAYS**, and a half day of comp-off worked on a week-off counts in **WEEKLY OFFS / HOLIDAYS**.


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/october-2026/payroll/payroll-reports/attendance-summary-report.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.
