> 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-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-register-month-wise.md). # Attendance Register Month Wise **Available on:** Desktop · Web · Phone Navigate to **Payroll Entry** and click on "Attendance Register Month Wise". **Attendance Register Month Wise** shows every employee against every day of a month, so a block of employees and days can be marked in one go. Absent days and leaves show in red. The **web** page adds faster ways to choose a block and a right-click menu that marks attendance straight away — see **On the web** below. ## Load the month 1. Pick the **Year** and the **Month**. To show particular employees only, tick **Employee** and pick them. 2. Press **Refresh**. For rostered employees, empty days that are a week-off, a holiday or a half-day off show a grey **W/O**, **HOL** or **H/O**. They are shown only; nothing is saved from them. **Other Options** holds the screen's settings — the order of employees, which employee code is shown, **Use Payroll Year For Attendance** (the Month list then shows payroll periods), **Use Double Click For Attendance Entry**, **Don't Allow Modification if Payroll Exist** and others. **Configuration** holds the register's working days and rules. ## On the desktop ### **Step 1: Select the days** * Drag across a block of days and employees in the grid. Clicking an employee's **S.No.** selects their row. ### **Step 2: Set the attendance** * Press **F6** (or right-click the block) to open the panel for the block. * Choose **Present** or **Absent** and the kind of day — **Others** lists your own attendance statuses (Present) or leave types (Absent). Overtime hours typed in switch the day to **Full Day + Overtime Hrs**. Then press **OK**. * Comp-off is under **Absent** > **Others**, as **COMP OFF** and **HALF DAY - COMP OFF**. Once the month is loaded, a full day shows as **A(CO)** and a half day as **P(HCO)**. * **Delete** on the panel removes the block's attendance; it needs delete rights and asks first. * **F2**, or **View Leave Balances** on the panel, shows the leave balances of the selected employees. With **Use Double Click For Attendance Entry** ticked, a double-click opens the panel for one day. Days before an employee joined, or after they left, are not marked. If a day fails its checks — for example not enough leave — the marking stops there; the days already marked stay. > **Example —** Five employees were on a training course from 10 to 14 November. HR drags from the first employee's 10 November cell to the fifth employee's 14 November cell, presses **F6**, chooses **Present** and **Full Day**, and presses **OK**: 25 days are marked at once. ## On the web The web page does everything the desktop does, with faster ways to choose a block and a menu that marks attendance directly. ### **Choose a block** * **Drag** across days and employees. A block is always one rectangle. * Click an employee's **S.No.** to take their whole month — drag down the S.No. column to take several employees one after another. **Select all** takes every employee and every day. * The count above the grid shows what is chosen, for example *Selected: 3 employee(s) x 5 day(s) = 15*. ### **Mark it** * **Right-click** the block and pick straight from the menu: **Present** or **Absent**, each with its kinds of day and your own statuses. The block is marked at once, with the same checks and messages as the panel. * The menu also has **Set Attendance...** (opens the panel), **View Leave Balance**, **Delete Attendance** and **Block from here**. * A right-click inside a selected block works on the whole block; a right-click on any other cell works on that cell alone. * **Double-click** a day to open the panel for that one day. * **Full Day + Overtime Hrs** needs the hours typed in, so it is only on the panel, not on the menu. ### **On a phone** * **Month and options** folds the year, month and buttons away to give the grid room; tap it again to bring them back. The **Select all** / **Block from here** bar stays in view. * To choose a block, tap one corner day, press **Block from here**, then tap the other corner. * **Press and hold** a day for the menu. It opens in two steps: tap **Present** or **Absent**, then the kind of day (**Back** returns to the first list). * A swipe scrolls the grid; it does not open the menu. > **Example —** Meena and Arjun, listed one after the other, were on unpaid leave all November. On the web, HR clicks Meena's **S.No.** and drags down to Arjun's, right-clicks inside the selection and picks **Absent → Leave Without Pay**: both employees' whole month is marked in one step. ## Messages you may see | Message | Why | What to do | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | | Invalid Year / Invalid Month | **Refresh** without a valid year and month | Pick them | | Please Select the Month. / Select Month For Creating Report | **Employee** ticked before a month is picked | Pick the month first | | Please Set Configuration | No register settings for the year | Set them with **Configuration** | | No Working Days in the Month | The month's working days are not set | Set them with **Configuration** | | Cannot Generate PayRoll. Date Locked | The month is locked for payroll | Choose another month | | Please Specify Overtime Hours | **Full Day + Overtime Hrs** with no hours | Enter the hours | | Are You Sure To Delete Attendance | The delete question | **Yes** to delete | | Deletion Rights Are Not Allow\........... | Your user may not delete attendance | Ask for delete rights on the screen | | Payroll Exist For Following Employees Attendance Can Not be Marked (desktop list) / The Following Attendance Couldn't be Marked: Payroll already exists (attendance not changed) for: … (web) | Payroll is already made for the employees named, with **Don't Allow Modification if Payroll Exist** and **Use Payroll Year For Attendance** ticked | Leave them, or untick the option if they must change | | The Following Attendance Couldn't be Marked: Payroll Year Not Defined For Date … | No payroll year covers that date | Set up the payroll year | | Modification Rights Not Available | **OK** on **Other Options** without the right to change them | Ask for the rights in User Access | | Select the days (cells) first. | Web: nothing is selected | Select a block first | | Select day cells, or the S.No. column for whole employees. | Web: only name or code cells are selected | Select days, or click S.No. | | Load the month first (Refresh). | Web: the grid is empty | Pick the year and month and press **Refresh** | | Tap a day cell first, then press Block from here. | Web: **Block from here** with no day picked | Tap a day first | --- # 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-learning-hub-tutorials-and-best-practices/payroll/payroll-entry/attendance-register-month-wise.md?ask=&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.