Drop file here
Accepts .xlsx or .xls only
or select from
Supports .XLSX & .XLS
● Split by date range● Priority date protection● Duplicate overlap guard● 100% secure processing
Upload your payroll sheet and get individual LOP date rows - ready for HRMS import.
Drop file here
Accepts .xlsx or .xls only
Supports .XLSX & .XLS
Loss of Pay - the salary deduction applied when an employee is absent without approved leave, or has exhausted their leave balance. The core formula is monthly gross ÷ days in month × LOP days.
Splits each employee's LOP period into individual, HRMS-ready date rows - the format most HR systems expect for bulk upload - rather than a single date-range entry most systems can't parse.
An employee on LOP from 28 March to 3 April splits into two HRMS-ready rows: 4 days in March, 3 days in April - each attributed to the correct payroll cycle, with no manual date-splitting.
Flags overlapping absence records instead of silently double-counting a day. If another row's start date falls mid-range, that row takes priority and the excess is logged for review.
Duplicate overlap guarding ensures the same date is never written twice for one employee across multiple rows - and your payroll sheet never leaves your browser.
Payroll runs on a calendar-month basis, so an absence spanning two months has to be split at the month boundary into two separate HRMS-ready rows - this tool does that split automatically from a single start and end date.
Employee ID, 28 Mar to 31 Mar (4 days), attributed to the March payroll cycle.
Employee ID, 1 Apr to 3 Apr (3 days), attributed to the April payroll cycle.
This tool outputs the split date rows only - it does not calculate the rupee deduction. Feed each row's day count into your payroll system or a salary proration calculator to get the actual LOP amount for that cycle.
Because payroll runs on a calendar-month basis, an absence that crosses a month boundary has to be split into separate entries, each using that month's own per-day rate (that month's gross divided by that month's actual number of days). An absence from 28 March to 3 April becomes two rows - one for the March days, one for the April days - rather than one entry spanning both.
If two overlapping LOP records exist for the same employee - for example, one entered manually and one imported from an HRMS export - a naive split could count the overlapping days twice, deducting pay twice for the same absence. Priority date protection detects the overlap, keeps only one record for those dates, and flags the conflict so you can review it rather than silently double-charging the employee.
Yes. Upload a single payroll sheet covering as many employees as you need, and the tool processes each employee's absence records independently, applying the same month-boundary splitting and overlap protection to every row.
An Excel file (.xlsx or .xls). Use the Generate Template button above to get a sheet with the exact column headers this tool expects, so your dates and employee details map correctly.
Your file never leaves your browser. All reading, date-splitting, and validation happens locally on your device using JavaScript - nothing is sent to, or stored on, any PayrollTool.in server.