Step 1 - Navigate to the Penalty Logs page
Log in to Asanify as an Admin.
Click on Attendance in the left navigation bar.
Select the Penalty Logs tab from the top navigation.
You will now see the Penalty Logs table listing all attendance penalty records for your organisation.
Step 2 - Understand the Penalty Logs table
The table shows the following columns for each penalty record:
Employee Name – The name of the penalised employee. Hover over the name to see their Employee ID, Designation, and Department.
Deduction Date – The date on which the penalty deduction was applied.
Penalty Type – The type of deduction applied:
Loss of Pay (LOP) – A pay deduction.
Loss of Leave (LOL) – A leave balance deduction.
Deduction (Days) – The number of days deducted. If an employee has multiple penalty types in the same record, this shows the combined total.
Violation – An icon indicating the type of attendance violation that triggered the penalty. Hover over the icon to read the violation label:
Late Arrival – The employee was late too many times within the defined period.
Work Hour Shortage – The employee worked fewer hours than the required minimum.
Step 3 - Filter penalty records (optional)
You can narrow down the records using the filters at the top of the table:
Penalised Between – Select a date range to view penalties applied within that period.
Penalty Type – Choose Loss of Pay, Loss of Leave, or both.
Apply or clear filters as needed. The table updates automatically.
Step 4 - View the penalty reason and details
To see the full reason behind any penalty, click the eye icon (View Details) in the Actions column for that record.
A Penalty Details dialog opens, showing:
Penalisation
The deduction breakdown — for example, "1.0 Day(s) of Loss of Pay". If the penalty was split across multiple leave policies or pay components, each line is numbered separately.
If a buffer was configured in the attendance policy, you will also see the date on which the penalty was applied and the buffer period that was accounted for.
Violation(s)
The specific attendance violation that caused the penalty:
For Work Hour Shortage – shows the total hours the employee was short, along with the period (start and end dates) during which the shortage occurred.
For Late Arrival – shows the number of late arrivals counted, along with the individual dates on which the employee was late.
Triggered Rule
The exact attendance policy rule that fired the penalty. Examples:
"For shortage of work hours between 1.0 to 4.0 hour(s), deduct 0.5 day(s) of pay."
"For every 3.0 day(s) of late arrival in a month, deduct 1.0 day(s) of leave."
This is the clearest explanation of why the penalty was applied.
Attendance Policy
The name and version of the attendance policy that was active when the penalty was calculated. Click the View button to open the full policy details in a new tab and review the rules configured under it.
Additional Information
What are the two violation types?
Violation | What it means |
Late Arrival | The employee exceeded the allowed number of late clock-ins within a weekly or monthly period as defined in their attendance policy. |
Work Hour Shortage | The employee worked fewer hours than the minimum required for the period, triggering a slab-based deduction. |
Why can't I see some employees in the list?
The Penalty Logs table includes employees with Active, Resigned, and Terminated statuses, so all historical records are accessible. If you still cannot find a record, try clearing the filters or widening the date range.
How are penalty rules configured?
Penalty rules are defined within attendance policies. Each policy version can have separate rules for late arrivals and work hour shortages, along with buffer days and penalty types (LOP or LOL). To check which policy is assigned to a specific employee, go to People, select the employee, and open their Attendance tab.
What does "Synced Payroll" mean in the details dialog?
If the penalty has already been included in a payroll run, the Synced Payroll field will show the payroll month it was synced to. This lets you confirm whether the deduction has been processed for payment.