> 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/employee-register.md).

# Employee Register

Logic ERP has added thirteen new columns to the **Employee Register** for the organisation structure, the attendance app, rosters and official contacts. This release also makes sure every employee is listed.

***

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

* Navigate to **Payroll Reports** and open the **Employee Register**.

***

### **Step 2: New columns**

Add the columns from the report's column settings, then tick them:

* **ORG UNIT** — the unit the employee is placed in, with the units above it.
* **ORG DESIGNATION** — the designation from **Setup Designations**.
* **REPORTING AUTHORITY** — the employee's reporting authority.
* **MANAGER** — the employee's manager, worked out the same way as for approvals: the reporting authority, or else the head of the employee's unit or a unit above it.
* **APP ENABLED**, **APP ENABLED ON** and **APP LOGIN MOBILE** — from **Setup Attendance App Users**.
* **LAST APP PUNCH** — the date and time of the employee's latest punch from the app.
* **ROSTER** — the employee's current roster, for example **SHIFT: GENERAL** or **ROTATION: DAY NIGHT WEEKLY**.
* **WEEK-OFF PATTERN** — the week-off pattern of that roster.
* **EMP-WISE HOLIDAYS** — **Yes** when the employee's holidays are set employee-wise.
* **OFFICIAL PHONE** and **OFFICIAL EMAIL** — the employee's official contacts from **Setup Employees**.

***

### **What's corrected**

* Every employee is now listed. Earlier an employee was left out when, for example, their shift, bank, grade, department, branch or payroll configuration had been removed. Such details are now shown blank.
* The **(NIL)** entry is not listed.


---

# 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/employee-register.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.
