Payroll calculations · 3 MIN READ
Attendance cycles from the twenty first to the twentieth and salary payment dates
A business may collect attendance from the twenty-first of one month to the twentieth of the next so it has time to review inputs before salary processing. That collection window should not be confused with the salary earning period, the employee’s actual service dates or the applicable wage-payment deadline.
The payroll policy needs to explain how those dates connect. Without that explanation, two teams can use the same phrase September payroll while referring to different attendance or earnings periods.
Name each period explicitly
Record the attendance window, salary period, processing month and intended payment date separately. State whether the arrangement uses actual information, provisional assumptions for later dates or a controlled correction in the following cycle.
For example, attendance ending on 20 September may support a salary process covering September. The team still needs a defined treatment for the remaining dates. It should not silently treat them as worked, unpaid or belonging to October without an approved lawful policy.
Check joiners and leavers against service dates
An employee joining on 21 September should have their actual service and payment position reviewed. A system rule excluding everyone after the attendance cutoff is an operational setting, not by itself a legal reason to ignore wages earned.
Similarly, a departure after the twentieth needs a process for confirming the final dates and any provisional amount already included. Do not change the recorded last working date to fit the attendance window.
Keep payment law separate from cutoff design
The Code on Wages framework sets wage periods and payment timelines, including the general monthly and specified exit-wage requirements described in Ministry guidance. [1] A company’s internal collection cycle should be designed around the applicable obligation rather than treated as an exemption from it.
Where a proposed cycle raises timing or entitlement questions, review the relevant law and employment terms before configuration. A provider should not be left to infer the legal position from the name of a payroll month.
Design the correction route
If the employer uses provisional inputs, record the basis, affected dates and approval. When actual attendance arrives, compare it to the assumption and create an identifiable adjustment. Keep the original earning period attached to the correction.
Suppose the final week was provisionally treated as payable and a later authorised record identifies one relevant unpaid day. The next working should show that prior-period correction and its basis, rather than create an unexplained reduction to the current month’s attendance.
Test the calendar before going live
Test a joiner on the twentieth, a joiner on the twenty-first, an exit after cutoff, February, a long absence spanning two months and a retrospective approval. Confirm that no date is paid twice or omitted and that the payment route can meet applicable deadlines.
Payroll Advisor’s managed scope supports agreed calendars and attendance adjustments. [2] A clearly documented cycle allows the same service dates to remain consistent across HR, attendance, payroll and the employee’s payslip explanation.
Sources & further reading
- Ministry of Labour employer compliance handbook February 2026 Official guidance
- Payroll Advisor managed payroll scope Company source
This article is general information, not individual legal or tax advice. Applicable rules depend on the financial year, state, employment terms and your circumstances. Have a correction? Contact hello@payrolladvisor.in.