> 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-app-punch-register.md).

# Employee App Punch Register

Logic ERP has introduced a new **Employee App Punch Register**. It lists every punch made from the attendance app — when and where it was made, whether it was inside the site, the manager's review and what happened in attendance — and marks the punches that need a look.

***

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

* Navigate to **Payroll Reports** and open the **Employee App Punch Register**.
* Enter **Date From** and **Date To**. The report lists the punches whose attendance day falls on these dates.
* Select branches or employees if needed.
* Tick **Exceptions Only** in the report settings to see only the punches that need a look.

***

### **Step 2: Read the report**

* **PUNCH** and **PUNCH TIME** show IN or OUT and the date and time of the punch in the branch's local time. **SHIFT DATE** is the attendance day: a punch after midnight that belongs to yesterday's night shift shows yesterday's date.
* **SITE**, **DISTANCE (M)** and **ACCURACY (M)** show the nearest site, how far the phone was from it, and how accurate the phone's position was. **LAT, LONG** shows the position, which can be pasted into any map.
* **GEOFENCE** shows **INSIDE**, **OUTSIDE - ALLOWED**, **OUTSIDE - FLAGGED** (sent to the manager to review) or **BLOCKED**. A punch with a faked location always shows **OUTSIDE - FLAGGED**. When the branch has no site, punches show **INSIDE**.
* **FAKE LOCATION** shows **YES** when the phone reported a faked position. **SELFIE** shows **YES** when a selfie was taken.
* **REVIEW**, **REVIEWED BY** and **REVIEWED ON** show the manager's decision on a flagged punch. **HR (DESK)** means HR decided it in Logic ERP.
* **ATTENDANCE** shows whether the punch reached attendance: **UPDATED**, **LEFT FOR HR**, **FAILED**, **NOT IMPORTED** or **RESOLVED BY HR**, with the reason in **ATTENDANCE MESSAGE**.

***

### **Step 3: Exceptions**

* **EXCEPTION** shows **YES** for a punch that was outside the site and flagged, blocked, made with a faked position, waiting for or rejected in review, or not updated in attendance.
* An IN punch stays **NOT IMPORTED**, and counts as an exception, until the OUT for that day is made.
* The total row shows the number of punches and how many of them are exceptions.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-reports/employee-app-punch-register.md)


---

# 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-app-punch-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.
