> 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-status-report.md).

# Attendance Status Report

Logic ERP has improved the **Attendance Status Report** for employees whose week-offs and holidays are set employee-wise, for example by their roster.

***

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

* Navigate to **Payroll Reports** and open the **Attendance Status Report**.
* The change applies when **Attendance Status** is ticked under **Txn Type Selection** and **Display Attendance Status in Short** is ticked in the report settings.

***

### **What's changed**

* A paid leave on an employee's own week-off now shows **W** and is counted under **WEELK OFF**, even when **Pick Holdiays From Masters** is not ticked. Earlier only Sundays were treated as week-offs, so a Saturday week-off showed **L**.
* An employee whose employee-wise holidays have not been entered for the period still uses Sunday as the week-off, as before.
* For these employees, a leave on a Sunday that is not their week-off now shows **L** instead of **S**.
* Employees whose holidays are not set employee-wise are not affected.

***

### **Comp-off and half days**

With **Display Attendance Status in Short** ticked:

* A comp-off day is counted with the paid leaves. A half day of comp-off (**HCO**) counts half as worked and half as paid leave, like a half day of casual leave.
* **Corrected:** the leave half of a half day of casual or sick leave (**HC** / **HS**) is now counted in **PAID LEAVES**, and so in **TOTAL DAYS WORKED**. Earlier it was left out. These totals will go up for employees with such half days. This is intended.

Without it, a comp-off day shows as **A(CO)**.


---

# 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-status-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.
