> 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-installation-configuration-and-troubleshooting-solutions/faqs/payroll/attendance-app-logic-workforce-faqs.md).

# Attendance App (Logic Workforce) - FAQs

Common questions from HR about the **Logic Workforce** attendance app and the Payroll screens that set it up. Each answer points to the screen's full guide in the Learning Hub.

***

### How do I set an employee as HR?

* Navigate to **Payroll Setups** and open **Setup Attendance App Users**.
* Load the employee with **Select Employees** (or **All Working** / **App Users Only**).
* Set the **HR** column to **Yes**. This also switches **App Enabled** to **Yes** - an HR user works through the app.
* Choose the **HR Branch**: one branch, or **ALL BRANCHES** (where it starts when HR is ticked). The HR user acts only for employees of that branch.
* Press **Save** and confirm.

To make several people HR at once, tick them in **Select**, choose **HR: YES** and the **HR Branch** in the bar above the grid ("Set for ticked"), press **Apply to Ticked**, then **Save**.

An HR user approves requests at an **HR** approval level and reviews punches. In the app, an **HR** section appears under **More**, with **Punches left for HR**, **Auto-absent days** and **Reset a phone**. An HR user never acts on their own requests or their own phone - another HR user does. Switching **App Enabled** off removes HR as well.

Full guide: [Setup Attendance App Users](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-users.md)

***

### How do I give an employee the attendance app?

* First set up the branch's sites in **Setup Attendance App Branches**.
* In **Setup Attendance App Users**, load the employee and set **App Enabled** to **Yes**.
* The employee logs in with the **Employee Phone** from Setup Employees. To use another number, type it in **Login Mobile**. The number needs at least 10 digits, and two app users cannot share one.
* Press **Save**. The employee can now log in to the app with the company code and the one-time password (OTP) sent to that number.

The app can only be switched on for a working employee. Once an employee leaves, they can no longer log in.

Full guide: [Setup Attendance App Users](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-users.md)

***

### An employee has a new phone and cannot log in. What do I do?

The app is linked to the phone the employee first logged in on. On any other phone the app says *Your account is linked to another phone. Ask HR to reset it.* An HR user releases the old phone:

* In the app, the HR user opens **More** and taps **Reset a phone**.
* They type the employee's **Employee code** (for example *EMP0010*), tap **Reset phone** and confirm. The app shows *Phone of … released.*
* The employee then logs in on the new phone with an OTP.

Only HR for the employee's branch can reset a phone; a manager cannot. Phones are reset from the app only.

***

### How do I stop punches made outside the store from counting?

* In **Setup Attendance App Branches**, add the store as a **site**: its position and a **Radius M** (how far from the spot a punch still counts).
* In **Setup Attendance App Users**, set the employee's **Geofence**:
  * **ALLOW** - a punch outside the site counts as normal.
  * **FLAG FOR MANAGER** - it counts, but waits for review (this is where new app users start).
  * **BLOCK** - it is recorded but **not counted**; the app tells the employee how far away they were.

A branch with no active site counts every punch as inside. A punch from a faked location is always flagged.

> **Example - a store and its car park**
>
> A store's entrance and its car park are about 80 m apart. HR sets the site at the entrance with **Radius M** 150, so a punch from the car park still counts, and sets the store's staff to **BLOCK**. A punch made from home is then recorded but not counted.

Full guides: [Setup Attendance App Branches](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-branches.md) · [Setup Attendance App Users](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-users.md)

***

### Where do I review punches made away from the store?

* Navigate to **Payroll Entry** and open **Attendance App HR Review**.
* The **Flagged Punches** list shows punches made away from the branch's sites (for employees set to **FLAG FOR MANAGER**) and punches with a faked location.
* Tick the rows, add a remark if needed, and press **Accept** to keep the punch or **Reject** to remove it. Rejecting rebuilds the day from the punches left, unless the day was entered by hand.

This list is not limited by the dates at the top. The employee's direct manager can also review these punches in the app, under **Approvals**.

Full guide: [Attendance App HR Review](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-app-hr-review.md)

***

### An employee punched in the app but the Attendance Register does not show it. Why?

The app does not overwrite a day someone has already entered or changed by hand, or a day whose payroll is processed. Such days - and days the app's punches could not be written for another reason - are listed in **Attendance App HR Review**, under **Punches Left for HR**, with the app's times and the reason in **Why**.

* Press **Use App Punches** to replace the day with the app's IN and OUT (only when the app has both, and payroll is not processed), or
* fix the day yourself in the **Attendance Register**, then press **Mark Resolved**. Mark Resolved changes nothing on the day; it only takes it off the list.

Full guide: [Attendance App HR Review](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-app-hr-review.md)

***

### Who approves leave requests made from the app?

Leave, missed-punch, short-leave and comp-off requests follow **Setup Attendance Approval Rules** (Payroll Setups). When no active rule fits, a request goes to the employee's **reporting manager**, then to **HR**. Profile-change requests always go straight to HR.

A rule can be limited to a request type, branch, department or grade, and has up to 9 levels: **REPORTING MANAGER**, **MANAGER'S MANAGER**, a **NAMED EMPLOYEE** or **HR**. Choose the request type (for example **TRY: LEAVE**) and press **Try for Employee...** to see whom a real employee's request would go to, even before you save.

Full guide: [Setup Attendance Approval Rules](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-approval-rules.md)

***

### A request is waiting with a manager who is away. Can someone else decide it?

Only if the approval rule allows it. Tick **Can Override** on a later level of the rule in **Setup Attendance Approval Rules** (not on level 1). That level may then approve or reject in the app while the earlier levels are still waiting; the earlier levels then show as **Passed over**.

**Attendance App HR Review** on the desktop and web acts only on requests that have reached the HR level. An HR level with **Can Override** decides early from the app.

Changing a rule does not change requests already waiting - they keep the approvers they started with.

Full guide: [Setup Attendance Approval Rules](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-approval-rules.md)

***

### How do I change an employee's manager?

* Navigate to **Payroll Setups** and open **Setup Employee Tree**.
* Select the new manager and press **Add Team Members...**, or select the employee and press **Move Under...**.
* Press **Save**.

Changes show in blue until you save. Requests already waiting stay with the old manager. When there are any, the screen lists them after **Save** under **Requests Still Waiting**, for information only. The employee's next request goes to the new manager.

Full guide: [Setup Employee Tree](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-employee-tree.md)

***

### Why was an employee marked absent automatically?

The branch has **Auto Absent** on in **Setup Attendance App Branches**. An app user with **nothing** for a working day - no attendance, no punch, no leave, missed-punch or comp-off request - is marked absent (**LP**) once their shift has ended and the branch's **After Minutes** have passed. A short-leave request does not stop the mark. Week-offs, holidays and days whose payroll is processed are skipped, and only today and the two days before are checked. If a punch arrives later, the absent mark is replaced.

To correct a day, open **Attendance App HR Review**, go to **Auto-absent Days**, pick a **New Status** and press **Save Status**.

Full guides: [Setup Attendance App Branches](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-branches.md) · [Attendance App HR Review](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-app-hr-review.md)

***

### How do I track an employee's location while they are on duty?

* In **Setup Attendance App Users**, set **Tracking** to **PINGS** and choose **Ping Minutes** (5 to 240).
* In **Setup Location Sharing Notice**, fill in and save the notice the app shows the employee.
* The employee reads the notice in the app and agrees.

Location is then shared every **Ping Minutes**, only while the employee is on duty (punched in and not yet out); the phone shows *Location sharing is on* meanwhile. Only the employee's manager and HR for their branch can see the trail, and every view is recorded. Pings are kept for 90 days.

Full guides: [Setup Attendance App Users](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-users.md) · [Setup Location Sharing Notice](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-location-sharing-notice.md)

***

### Tracking is set to PINGS but no location is recorded. Why?

Check, in this order:

* **The notice** - until it is filled in and saved in **Setup Location Sharing Notice**, the app tells the employee *The location sharing notice has not been set up yet. Ask HR.*
* **The employee's answer** - the list on that screen shows each one as **Agreed (version …)**, **Agreed to version … - asked again**, **Withdrawn** or **Not answered yet**. Location is shared only after they agree to the current version. Changing a notice someone has already answered makes a new version, and everyone is asked again.
* **On duty** - pings are taken only between the employee's IN and OUT punches.

Full guide: [Setup Location Sharing Notice](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-location-sharing-notice.md)

***

### A branch is in another time zone. Do I need to do anything?

Yes. In **Setup Attendance App Branches**, choose the branch's **Time Zone**. A punch time is converted to it, which decides the attendance day and the times attendance is judged on, late marks included. **(SERVER TIME ZONE)** uses the server's own time.

Full guide: [Setup Attendance App Branches](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-attendance-app-branches.md)

***

### Can HR use these screens on the web or a phone?

Yes. Every attendance app setup and review screen has a web page with the same steps, laid out for a phone on a narrow screen.

Full guide: [Using These Screens on the Web and Phone](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/shift-roster/using-these-screens-on-the-web-and-phone.md)

***

### Staff have Saturday off one week and a fixed weekday off the next, and Sunday is always off. How do I set this up?

Use a two-week cycle.

* In **Setup Week-off Patterns** (Payroll Setups), make a pattern with Pattern Type **ROTATING CYCLE** and **Cycle Days 14**. Count the days from a Monday: 1-7 is the week with Saturday off, 8-14 is the week with the weekday off.
* Enter the off-days **6** (Saturday), **7** and **14** (both Sundays), plus the weekday in week 2: **9** for Tuesday, **10** for Wednesday, **11** for Thursday, **12** for Friday.
* Make one pattern per weekday, for example *SAT + WED ALTERNATE* = 6, 7, 10, 14.
* In **Allocate Roster** (Payroll Entry), give each person a roster line with their shift, their pattern and an **Anchor Date** on a **Monday of a week in which they have Saturday off**. Save, and generate the roster.

> **Example**
>
> Ramesh works 10:00 AM to 7:00 PM. His pattern is SAT + WED ALTERNATE and his Anchor Date is Monday 2 November. He is off on Saturday 7 and Sunday 8 November, then on Wednesday 11 and Sunday 15 November, and works on Saturday 14 November. The cycle then repeats.

Full guide, with a table of the day numbers: [Setup Week-off Patterns](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-week-off-patterns.md)

***

### Half the staff have Saturday off this week, the other half next week. Do I need two patterns?

No. They share the same pattern; only the **Anchor Date** on their roster lines in **Allocate Roster** differs. Give each person a Monday of their own Saturday-off week. The two groups' Mondays are one week apart, for example 2 November and 9 November.

Full guide: [Allocate Roster](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/allocate-roster.md)

***

### Everyone works the same hours but has different week-offs. Do I need a shift for each?

No. Make **one shift** in **Setup Payroll Shifts**, for example 10:00 AM to 7:00 PM. Make a week-off pattern for each set of off days in **Setup Week-off Patterns**. Then pick each person's pattern in the **Week-off Pattern** column of their roster line in **Allocate Roster**; it replaces the shift's own pattern for that person.

If the shift's pattern is **(NONE)**, a roster line left on **(SHIFT'S OWN)** gives no week-offs, so pick a pattern on every line.

Full guide: [Setup Payroll Shifts](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-payroll-shifts.md)

***

### What is the difference between "2nd and 4th Saturday off" and "every other Saturday off"?

* **2nd and 4th Saturday** follows the month: use **NTH WEEKDAY OF MONTH** with SATURDAY / 2ND and SATURDAY / 4TH. In a month with five Saturdays, two Saturdays in a row are worked.
* **Every other Saturday** keeps alternating whatever the month: use **ROTATING CYCLE**, Cycle Days 14, off-days 6, 7, 14 (Saturday plus both Sundays), with the Anchor Date on a Monday of a Saturday-off week.

Full guide: [Setup Week-off Patterns](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-week-off-patterns.md)

***

### I changed a week-off pattern or a roster line, but the old week-offs still show. Why?

Days already generated do not change by themselves. Generate the roster again for those employees, or for **All Rostered Employees**, in **Generate Roster** (Payroll Entry). After saving a changed pattern, **Setup Week-off Patterns** tells you how many rostered employees use it. When you save **Allocate Roster**, it offers to generate straight away.

Full guide: [Generate Roster](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/generate-roster.md)

***

### Our new roster starts on 1 November. What Anchor Date do I enter?

**Date From** is 1 November for everyone. The **Anchor Date** is day 1 of the pattern's cycle. For patterns counted from a Monday, enter a **Monday of the person's Saturday-off week**, for example 2 November for those off on Saturday 7 November and 9 November for those off on 14 November. Do not leave it blank: Date From, a Sunday, would then be day 1, and every off-day would move by one.

Check one person from each group in **Roster Calendar** before the roster starts. Generating again does not change days that have already passed.

Full guide: [Allocate Roster](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/allocate-roster.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-installation-configuration-and-troubleshooting-solutions/faqs/payroll/attendance-app-logic-workforce-faqs.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.
