The Core Narrative

Arrears are the 'Time Machine' of payroll. They occur when a salary change is effective from a past date but processed in the current month. The most common trigger is the annual salary revision—decided in April but often approved in June, meaning the payroll team must 'Go back in time' and calculate the difference for April and May.

The math involves comparing what was actually paid and what should have been paid, and then adding that difference to the current month's payout. But the complexity multiplies when you consider statutory implications. The PF, ESI, and TDS for each of those past months must also be recalculated. The employer may owe additional PF contributions to the government. The employee's tax liability might change because the arrears push their annual income into a higher slab.

If the arrears span a financial year boundary (e.g., a revision effective from March but processed in April), the tax treatment becomes even more intricate. In a well-configured payroll system, arrears calculation is automated—the system stores the 'effective date' of every change and processes the differential automatically. In a manual setup, it is a spreadsheet nightmare that routinely results in errors, employee grievances, and compliance gaps.

4.3.2

Key Takeaways

Arrears are taxable in the month of payment, but employees can claim relief under Section 89(1) if the arrears relate to a previous financial year—HR should proactively inform employees about filing Form 10E.

PF Arrears: If the Basic Pay revision is backdated, the employer must deposit the differential PF contribution with interest for each delayed month.

ESI Impact: If arrears push an employee's gross above ₹21,000, they may exit ESI coverage retroactively—creating a complex 'Contribution Period' adjustment.

The 'Effective Date' is king: Every salary revision letter must clearly state the effective date, and the HRMS must capture it precisely to trigger accurate arrears computation.

4.3.3

Practical Scenarios

"A government PSU processing an annual DA revision for 10,000 employees effective from January but announced in July—the payroll team processed 6 months of arrears, additional PF contributions, and revised TDS projections in a single cycle."

"A private company discovering that its manual arrears calculation had under-deducted TDS for 200 employees by an average of ₹3,000 each, resulting in a collective ₹6 Lakh shortfall that had to be recovered in the next payroll run."

Academy Pro-Tips

Minimize arrears by processing salary revisions as close to their effective date as possible—every month of delay adds a month of complex recalculation.

Always run arrears as a separate line item on the payslip (e.g., 'Basic Arrears - Apr to Jun') so employees can verify the computation and the audit trail is clear.

Before processing bulk arrears (like annual increments), run a 'Dry Run' report showing the total financial impact—get Finance approval before committing the payout.

Points to Remember

Under the new Labor Codes, if an employer delays implementing a government-mandated wage revision, they may be liable for interest on the arrears amount in addition to the principal.
Arrears processing is the #1 reason payroll teams request a 'Re-run' of a closed month—having a robust month-end lock with a controlled re-open process is essential.

4.3.1