Salary Arrears in Payroll: Processing and Recovery

Salary arrears in payroll are the amounts an organisation owes an employee for a past period because the correct pay was not processed at the time. They arise from an increment approved in July but effective from April, a promotion whose paperwork reached payroll a month late, a minimum wage revision notified after the cut-off, or an attendance correction that reverses a loss-of-pay deduction. Arrears processing is the discipline of computing that gap accurately, month by month and component by component, applying the right statutory treatment, and showing it clearly on the payslip.

Most teams treat arrears as an afterthought — a single lump-sum line added at the end of the run. That works until someone asks a hard question: why is PF on arrears only partly deducted, why did TDS jump so sharply this month, why does the arrear differ from what the employee calculated on a notepad. This guide covers why arrears arise, how to calculate them properly, how to handle negative arrears and salary recovery, what statutory treatment applies, and how an HRMS turns a monthly firefight into a controlled process.

What salary arrears actually are

An arrear is a timing difference, not a new entitlement. The employee earned the money in an earlier month; payroll simply did not know about it when that month was processed. Once the correct information arrives, payroll must reconstruct what should have been paid and settle the difference.

That reconstruction matters more than people assume. An arrear is not "new salary minus old salary, times number of months". It is the sum of month-wise recomputations, each respecting the attendance, loss of pay, statutory ceilings and component rules that applied in that specific month.

Arrears, advances and bonuses are not the same thing

An arrear is payment for work already performed under a revised or corrected entitlement. An advance is payment ahead of entitlement, recovered later. A bonus or incentive is discretionary or performance-linked and does not relate to a past pay rate.

Keeping these distinct on the payslip and in the ledger matters for tax treatment, statutory computation and employee understanding. Lumping a retention bonus into an "Arrears" line because it is convenient creates avoidable disputes and audit questions.

Positive and negative arrears

Positive arrears are the common case: the employee is owed money. Negative arrears — overpayment recovery — occur when the recomputation shows the employee was paid more than entitled for a past period.

Negative arrears are far more sensitive. Paying someone extra rarely triggers a grievance; recovering from someone almost always does.

Why arrears arise

Understanding root causes is not academic. Each cause has a different fix, and organisations that classify arrears by cause usually find two or three sources account for most of the volume.

Delayed appraisal cycles. The cycle is effective 1 April, but moderation, budget approval and letter issuance run into June or July. Three or four months of increment arrears accumulate. This is predictable and therefore plannable — finance can provision the outflow and payroll can earmark a specific run for retrospective processing.

Backdated confirmations. Probation-to-confirmation transitions often carry a salary change or eligibility for components probationers do not receive. Confirmation arrears are small in value but high in volume, and tend to affect junior employees for whom the amount matters proportionally more.

Promotions and role changes. Promotion arrears usually involve more than a percentage increase. A grade change may alter the whole structure — a different basic-to-CTC ratio, new allowances, a shift from fixed to fixed-plus-variable, sometimes a change in statutory applicability. Because the structure changes, these need component-level recomputation rather than a delta on gross.

Revised minimum wages. State minimum wage revisions are notified periodically and frequently apply from a date earlier than the notification. The resulting arrear is not discretionary. Verify the applicable schedule, category and zone against the current state notification, since these vary considerably.

Late attendance regularisation. An employee is marked absent because a regularisation request sat with a manager past the cut-off. Reversing that loss of pay is an arrear. This category flows in both directions — a late-approved leave without pay creates negative arrears just as easily.

Wrong master data. Incorrect date of joining, a wrong grade mapped at onboarding, a location code pulling the wrong HRA percentage, a missing PF opt-in. These are the most damaging category because they are silent: nobody knows the number is wrong until someone checks.

Retrospective shift and overtime claims. Night shift, hazard, on-call and overtime payments depend on roster data that often arrives after the cut-off. In manufacturing, healthcare and logistics this produces a steady monthly stream of small arrears. The fix is usually process design — move the cut-off, or accept a formal one-cycle lag and say so.

Reimbursement and flexible benefit corrections. Declaration changes, late bills, rejected and re-approved claims, and mid-year restructuring all cause retrospective adjustments. Because these components often carry specific tax treatment, corrections flow through to taxable income and TDS.

The anatomy of an arrear calculation

Accurate arrear calculation in India depends on five inputs. Miss any one and the number will be defensible only until somebody checks it.

The revision effective date determines which months are in scope. It should come from an approved document — an increment or promotion letter, a confirmation, or a statutory notification — and be stored as a dated attribute on the compensation record, not overwritten onto the current salary. Storing only the current salary with a "last modified" timestamp destroys history and forces manual spreadsheet work every time.

The affected months run from the effective date up to the month in which the revision is applied. A revision effective 1 April applied in the August run has an arrear period of April to July, with August paid at the new rate normally. Watch mid-month effective dates: that month splits between old and new rates.

Component-wise delta must be computed per component, never on gross. Basic, HRA, special allowance, shift allowances and employer contributions behave differently under tax and statutory rules, and downstream systems need the split. Computing on gross and back-allocating breaks the moment a structure changes.

Proration rules must match between the arrear calculation and the original month. If payroll uses calendar days, arrear months must use calendar days. Mixing a 31-day calendar basis with a fixed 30-day divisor produces small differences nobody can trace.

Loss of pay interaction means LOP must be re-applied at the revised rate for each affected month. If an employee had three LOP days in May, the May arrear is the delta on earned days only. This is the most common arithmetic error in manual arrear sheets.

Expressed per component per month: Arrear = (Revised monthly component × earned days ÷ payable days) − (Original monthly component × earned days ÷ payable days).

A fully worked arrear calculation example

The figures below are illustrative, chosen to make the arithmetic clear. They are not benchmarks.

An employee's increment is approved in August 2025 with a revision effective date of 1 April 2025. The August payroll is the first run at the revised salary, so April to July are the arrear months.

Attendance during the arrear period, on a calendar-day proration basis: April 30 payable days with no LOP; May 31 payable days with 3 LOP days (28 earned); June 30 payable days with no LOP; July 31 payable days with no LOP.

The gross arrear payable in August is roughly INR 31,226, of which INR 17,565 is basic arrear.

A quick mental calculation gives INR 8,000 × 4 = INR 32,000. The correct figure is about INR 774 lower because of the three LOP days in May — exactly the kind of gap that generates a helpdesk ticket. The payslip should therefore show the month-wise breakup, not a single line.

Adding the statutory layer

Suppose the organisation restricts PF to the statutory wage ceiling and the employee's basic already exceeds it under both structures. The basic arrear may then produce no incremental PF at all, because PF wages were already capped.

Change one assumption — the basic was below the ceiling before the revision and above it after — and PF on arrears increases, but only up to the ceiling and only for the months in question. Because ceilings, rates and applicability rules change, confirm the current position with your payroll advisor rather than hard-coding an assumption.

A second example: mid-month promotion arrears

A promotion is effective 16 May 2025 and processed in the July payroll. Gross moves from INR 48,000 to INR 60,000, with a structure change: special allowance shrinks and a new site allowance of INR 3,000 appears.

May is a split month. On a calendar-day basis with 31 days, the old rate applies for 15 days and the new rate for 16.

June was paid entirely at the old rate, so the June arrear is the full delta of INR 12,000. Total arrear in July is about INR 18,194, and each component must be computed separately because the structure changed — the site allowance arrear is a new line, and the special allowance arrear may be negative even though the total is positive.

That last point deserves emphasis. Within a single positive arrear, individual components can be negative. A payroll engine that silently floors component arrears at zero will overstate the payout.

Negative arrears and salary recovery

Negative arrears arise when a recomputation shows the employee was overpaid. The commercial instinct is to net it off the next payslip. That instinct is often wrong, and sometimes unlawful.

Common causes of overpayment

• Loss of pay approved after payroll was processed, so the deduction never applied.
• Notice period shortfall not captured before the final run.
• A revision processed with the wrong effective date, applying an increase too early.
• Duplicate payment of a reimbursement or incentive.
• An advance or loan instalment that failed to deduct due to a schedule error.
• Excess leave encashment against a balance later corrected.
• A component paid to an employee never eligible for it under their grade.

Lawful recovery principles

Indian wage legislation limits what may be deducted from wages, in what circumstances, and how much in any single wage period. The general framework is that the deduction must fall within a permitted category, must be documented, and is subject to an aggregate cap per wage period.

Do not attempt to determine the precise permitted categories or percentage caps from memory. They sit in wage legislation and associated rules, have been affected by the labour code consolidation, and can differ by employee category. Confirm the current position with your legal or payroll advisor before designing a recovery policy.

Beyond the legal limits, five practical principles reduce disputes considerably.

1. Establish the overpayment before acting. Recompute, document the cause, and be able to show the month-wise working. A recovery that cannot be explained will not be accepted.
2. Communicate before deducting. The employee should learn about it from a conversation or letter, not from a shrunken payslip. This is the single highest-leverage practice in the whole area.
3. Offer proportionate instalments. A few hundred rupees can be netted in one go; a month's salary must be spread across cycles.
4. Document consent where the recovery is not clearly a permitted statutory deduction — a signed acknowledgement of the amount, cause and schedule protects both sides.
5. Fix the root cause first. If a wrong allowance is still in the master, correct it before recovery starts, or the balance keeps growing.

A recovery letter should state plainly what happened, which months are affected, the month-wise amounts, the total, the instalment schedule, the effect on take-home, the treatment of tax already deducted on the excess, and a named contact. Avoid legalistic phrasing and avoid implying fault where there is none — most overpayments are employer administrative errors, and saying so makes the conversation far easier.

Worked example: instalment-based salary recovery

An employee was overpaid INR 24,000 across three months because an allowance of INR 8,000 per month was wrongly mapped to their grade. Normal monthly net pay is INR 52,000.

There is a second consideration here. Because the excess allowance was taxed when paid, reversing it reduces taxable income for the year, so payroll should recompute the year-to-date tax position rather than simply deducting the gross overpayment.

Recovery at full and final settlement

When an employee resigns with an outstanding balance, it is normally adjusted against final dues — pending salary, leave encashment and reimbursements. Two cautions apply. Some settlement components, notably gratuity, have their own protective treatment and should not be assumed freely adjustable; take advice. And if final dues are insufficient, chasing the balance after separation is expensive and rarely successful.

The practical control is to run an overpayment exception report at the point a resignation is accepted, not on the last working day. If an overpayment surfaces only after separation, options narrow to a written repayment request and, in significant cases, a formal legal process — which is why most organisations write off small post-exit balances and focus on prevention.

Statutory treatment: PF, ESI, PT and TDS on arrears

This section is directional. Rates, ceilings and thresholds change, and several elements have been affected by the labour code consolidation. Treat it as a framework for asking the right questions, and confirm specifics with a qualified professional.

PF on arrears

The general principle is that PF is payable on arrears of PF-qualifying wages, and is typically accounted in the month of payment rather than allocated back to the original months. The arrear increases the PF wage base for that month, subject to the ceiling and inclusion rules the organisation applies.

Three questions decide any specific case: which arrear components fall within PF-qualifying wages under your definition, whether PF is restricted to the statutory ceiling or computed on actual wages, and whether the employee is an excluded employee or an international worker. Where PF is computed on actual wages, an arrear generally increases both contributions in the month of payment; where the ceiling applies and the employee is already above it, an arrear on basic may produce no incremental PF. Report arrear PF correctly in the monthly electronic return — some formats provide a separate arrear wage field.

ESI on arrears

ESI applicability depends on a wage threshold, and the contribution period structure generally means an employee covered at the start of a contribution period remains covered for that period even if wages rise mid-period.

This creates a specific question: if an increment pushes an employee above the threshold with retrospective effect, contributions for the intervening months are usually still due under the contribution period rule, and the arrear itself may attract contribution. This is frequently misunderstood — verify before excluding arrear wages.

Professional tax on arrears

Professional tax is a state levy with slab structures that vary by state. Because slabs are usually applied to monthly earnings, a large arrear can push an employee into a higher slab for that month. Whether that is correct depends on the state's rules; some organisations apply the slab to arrear-inclusive monthly earnings, others treat arrears separately. Confirm your state's position and apply it consistently — inconsistency here is easy for an auditor to spot.

Labour welfare fund contributions, where applicable, are typically small fixed amounts at set intervals, so arrears rarely change them. Still, check whether any local levy in your states of operation is wage-linked.

TDS on arrears and Section 89 relief

Salary TDS is generally computed on projected annual income and recovered across the remaining months of the financial year. An arrear raises that projection, which raises the annual liability, which is then recovered over fewer remaining months.

Two effects catch employees by surprise. A large arrear can push projected income into a higher slab, increasing the rate on the top slice. And an arrear paid in February or March causes a far sharper monthly TDS spike than the same arrear paid in June. If large arrears are being paid late in the year, say so in advance.

Income tax law also provides relief where salary is received in arrears and the receipt creates a higher tax incidence than would have applied had the amount been taxed in the years to which it relates — commonly referred to as relief under Section 89, supported by a prescribed form. Some employers give effect to this through payroll on the basis of employee declarations; others require the employee to claim it on filing. Either way, payroll must provide a clear month-wise and year-wise breakup of the arrear, because a lump-sum statement makes the relief impossible to compute. Availability can depend on the tax regime the employee has opted for, so direct employees to a tax advisor rather than making blanket promises.

Downstream effects on gratuity, bonus and settlements

A retrospective revision to basic wages can affect gratuity accrual, statutory bonus computation, leave encashment rates and notice pay. Where an employee separates shortly after an arrear is processed, check whether their final settlement was computed on the revised or the old rate.

This is a genuine and frequently missed exposure: the exit was calculated in September on the old salary, the increment effective from April was processed in October, and the settlement is now understated.

Payslip presentation and employee communication

An arrear that is clearly presented generates a fraction of the queries of one that is not. This is not cosmetic — payslip clarity is the cheapest support cost reduction available to a payroll team.

Show arrears as separate, labelled earnings lines rather than merged into current-month components. "Basic Arrears" and "HRA Arrears" tell a far better story than a single "Arrears" line, and they let the employee tie the payslip to their increment letter.

State the arrear period explicitly — "Arrears for Apr 2025 to Jul 2025". Where LOP reduced an arrear month, flag it with a footnote such as "computed on earned days; 3 LOP days in May 2025". Show negative arrears as a clearly named deduction such as "Salary recovery", never as a reduction hidden inside an earnings line.

For any material arrear, issue a supporting statement alongside the payslip showing, per affected month, the payable days, earned days, old and revised amounts per component, and the arrear per component. That statement does triple duty: it answers queries, supports the employee's relief claim, and forms part of your audit evidence.

For organisation-wide events such as an appraisal cycle or a minimum wage revision, send a short note before the run, not after. Cover what is being paid, the period, the credit date, why the amount may differ from a simple multiplication, and the likely tax impact. That last paragraph is worth writing carefully — employees who see a large TDS alongside a large arrear often assume an error.

Reports and audit trail

Arrears attract audit attention because they involve retrospective changes to processed periods. The defence is a clean, reproducible trail.

A payroll arrears report should carry, at minimum: employee code and name, revision type, effective date, approval reference, arrear months, component-wise arrear per month, total arrear, statutory impact, and the payroll period in which it was paid. Produce it for every run containing arrears and retain it with that run's documentation. If it can only be reconstructed by re-running a calculation, it is not an audit trail.

Alongside it, maintain four registers:

• A revision register listing every retrospective compensation change with source document and approver.
• A recovery register listing every negative arrear, its cause, the instalment plan, amounts recovered and the balance outstanding.
• An exception log for arrears computed manually outside the standard engine, with reasons.
• A write-off log for recoveries abandoned, with the approval that authorised it.

The recovery register deserves particular attention. Multi-month recoveries are easy to lose track of when a payroll executive changes, and unrecovered balances quietly become write-offs by default.

Reconcile the total arrear paid to the sum of individual arrear records, the arrear-driven change in PF, ESI and TDS to the statutory registers, and the payroll cost posted to the general ledger including any provision release. Where arrears cross a financial year boundary, check whether accounting requires the cost to be recognised in the earlier year — payroll must supply the period-wise split for finance to answer that.

Month-end controls and sign-off

Arrears should not be the last thing done in a run. They must be computed, reviewed and frozen before the run is finalised, because they change statutory calculations downstream.

Step by step: processing arrears in a payroll cycle

1. Freeze inputs. Close attendance, leave regularisation and compensation approvals at the defined cut-off. Late arrivals go into next cycle's arrears rather than being force-fitted.
2. Extract retrospective changes. Pull every compensation record with an effective date before the current period that was not applied in a prior run.
3. Validate source documents. Confirm an approved letter or notification exists and that the system effective date matches it.
4. Recompute affected months with each month's actual attendance, LOP and structure.
5. Review component-level output. Check for negative components, zero-value arrears and outliers; anything above a defined threshold gets manual review.
6. Separate positives and negatives. Route negative arrears to the recovery process rather than netting them automatically.
7. Apply statutory recomputation for PF, ESI, PT and the annual tax projection with the arrear included.
8. Generate the payroll arrears report and per-employee statements before finalising.
9. Obtain sign-off. Payroll lead reviews the report, finance approves the incremental outflow, HR confirms the underlying approvals.
10. Process, communicate and archive. Run payroll, issue payslips with arrear statements, send the communication, archive the reports.

Step by step: handling a suspected overpayment

1. Isolate the case and deduct nothing while the position is unconfirmed.
2. Recompute the affected months and quantify the excess per component per month.
3. Identify and fix the root cause so the overpayment stops.
4. Check statutory consequences — excess PF or ESI contributed, excess tax deducted, PT slab impact.
5. Determine what may lawfully be recovered and the applicable cap, with advice where unclear.
6. Design an instalment plan proportionate to the amount and the employee's net pay.
7. Communicate in writing with the month-wise working, and hold a conversation for anything material.
8. Obtain acknowledgement of the amount and schedule.
9. Set up the deduction with an end date and a total-recovery cap so it cannot over-deduct.
10. Track to closure in the recovery register and confirm the final instalment clears the balance exactly.

Sign-off checklist

• Every arrear traces to an approved document with a matching effective date.
• The arrear period is correct and does not overlap an already-settled period.
• LOP has been re-applied at the revised rate for every affected month.
• Proration basis matches the basis used in the original months.
• Component-level arrears, including negatives, have been reviewed.
• Structure changes have been recomputed component-wise, not on gross.
• Statutory recomputation has been run and reconciled.
• Negative arrears went through the recovery process, not automatic netting.
• Recoveries respect the agreed plan and any applicable statutory cap.
• Employees separating this month have had settlements checked against the revised rate.
• The payroll arrears report has been generated and retained.
• Employee communication has been drafted and scheduled.

Common mistakes in arrears processing

Calculating on gross instead of component-wise. The most common shortcut and the most consequential. It breaks PF and ESI computation, misstates taxable components, corrupts the ledger split, and makes structure changes impossible to handle correctly.

Ignoring loss of pay in arrear months. Paying a flat monthly delta for a month with unpaid leave overstates the arrear and creates an inconsistency: LOP was applied at the old rate but never at the new one.

Mixing proration bases. Calendar days in the original run and a fixed divisor in the arrear calculation produces small differences that consume disproportionate time to investigate.

Treating a promotion as a percentage increase. When the structure changes, individual components can move in opposite directions, and a system computing only positive deltas will produce the wrong total.

Overwriting salary history. Storing only the current salary makes retrospective recomputation guesswork. Effective-dated records are the foundation of reliable arrears processing, and retrofitting them later is painful.

Netting negative arrears silently. Deducting without notice is the fastest way to convert an administrative error into a formal grievance, and may exceed permitted deduction limits.

Forgetting the tax projection. Adding an arrear without recomputing the annual projection understates TDS, which surfaces as a large catch-up deduction later — usually in February or March, when it hurts most.

Missing separated employees. People who left during the arrear period may still be entitled to arrears for their period of service. Excluding them because they are inactive is both a compliance and a reputational risk.

Applying arrears to the wrong cost centre. If the employee changed department or location during the arrear period, posting the whole arrear to the current cost centre distorts departmental costs.

Rounding inconsistently. Rounding each month's component arrear and then summing gives a different total from summing and then rounding. Pick one convention, document it, apply it everywhere.

Failing to provision. A known appraisal cycle with a known effective date and a known typical delay is a provisionable cost. Treating the outflow as a surprise every year is a planning failure, not a payroll one.

Arrears and wage-structure changes under the labour codes

India's consolidation of labour legislation introduces, among other things, a harmonised definition of wages with a structural relationship between the wage components and total remuneration. The practical effect widely discussed is that organisations with a low basic-to-CTC ratio may need to restructure so a larger share of remuneration falls within the defined wage base.

Implementation timelines and detailed rules have moved over time and can vary by state, so confirm the current applicable position with your legal advisor. What follows concerns the arrears implications of such a restructuring, not the underlying requirement.

If a structure change is applied with a retrospective effective date, every affected employee generates arrears — and because the change reallocates value between components rather than simply increasing pay, component-level arrears will include negatives even where the total is neutral.

Consider an employee on a gross of INR 60,000 with basic at INR 21,000, restructured so basic becomes INR 30,000 with the difference taken from special allowance. Gross is unchanged, so the gross arrear for any retrospective month is nil. But the PF wage base rises by INR 9,000 per month. If PF is computed on actual wages, both contributions increase, take-home falls, and employer cost rises — from a change that looks neutral on the payslip's gross line.

Plan for four things: prefer a prospective effective date where the law allows it, since retrospective restructuring multiplies the work; run statutory recomputation across affected months even where gross is unchanged; communicate the take-home impact with a worked example before implementation; and restate downstream accruals such as gratuity provisions, leave encashment rates and statutory bonus.

Automating arrears processing in an HRMS

Manual arrears processing does not scale. Beyond a few dozen cases a month, spreadsheets become both the bottleneck and the risk.

Effective-dated master data is the architectural prerequisite. Every compensation-relevant attribute — structure, grade, location, cost centre, statutory applicability — should carry a validity period rather than a single current value, so the system can answer "what was this employee's structure on 12 May" without guesswork.

A retro engine, not a delta formula. A proper engine re-runs the payroll calculation for each affected period using that period's inputs and compares the result to what was actually paid. That distinction is what lets it handle LOP correctly, apply the right proration basis, cope with structure changes, produce component-level results including negatives, and handle mid-month effective dates. It also needs versioned attendance and leave data, because overwritten attendance destroys retro accuracy.

Approval workflow scaled to the amount and the number of months involved. A one-month confirmation arrear needs different scrutiny from a nine-month backdated promotion. Capturing the source document, approver, timestamp and comments generates most of the audit trail automatically.

Recovery management needs an instalment schedule with a start date, per-month amount, total cap preventing over-recovery, automatic suspension if net pay would fall below a defined floor, and visibility to employee and payroll alike. Recoveries that continue after the balance clears, or stop silently and are never restarted, are common failures in systems that treat recovery as a plain recurring deduction.

Automatic exception reports should flag arrears above a value or percentage threshold, arrears spanning more than a set number of months, negative arrears of any size, arrears for separated employees, effective dates preceding the date of joining or falling in a locked period, recoveries with no movement for several cycles, and cases where a manual override replaced the engine's output.

Statutory recomputation and reporting. The system should recompute PF, ESI, PT and the annual tax projection automatically when an arrear is added, carry arrear wages into statutory returns in the correct field, and produce per-employee month-wise arrear statements. Making those statements, revision history and recovery schedules visible in employee self-service removes a large share of arrears queries, since most are simply requests for information the system already holds.

What automation cannot do is fix a broken approval process. If increment letters take three months to reach payroll, the HRMS will faithfully compute three months of arrears every year. Nor can it decide policy — proration basis, rounding convention, recovery limits and communication standards are organisational decisions that must be made before they can be configured.

Implementation checklist

Foundations. Compensation master is effective-dated with full history retained. Attendance and leave data is versioned, not overwritten. Proration basis and rounding convention are defined and documented. Salary structures are template-driven so grade changes apply cleanly.

Calculation. The retro engine recomputes affected periods rather than applying deltas. Component-level arrears, including negatives, are produced. LOP is re-applied at revised rates. Mid-month effective dates split correctly. Structure changes recompute all components. Cost centre allocation follows the employee's assignment in each affected month.

Statutory. PF, ESI and PT recomputation on arrears is configured to your verified policy. The annual tax projection is recomputed when an arrear is added. Arrear wages map to the correct fields in statutory returns. Month-wise arrear statements are generated. Gratuity, bonus and leave encashment accruals are restated where basic changes.

Recovery. Negative arrears route to a workflow, not automatic netting. Instalment plans support a total cap and end date. A net-pay floor prevents excessive deduction. Written communication and acknowledgement are part of the workflow. The recovery register tracks balances to closure. The exit checklist includes an overpayment check at resignation acceptance.

Controls and communication. Approval workflow is scaled to value and months. Exception reports run automatically each cycle. The payroll arrears report is generated and archived every run. Reconciliation to statutory registers and the ledger is completed. Manual overrides are logged with reasons. Payslips show arrears as separate labelled lines with the period stated, arrear statements are issued for material amounts, and tax impact is explained proactively for large or late-in-year arrears.

Frequently asked questions

What exactly are salary arrears in payroll?

Salary arrears are amounts payable to an employee for a past period because the correct salary was not processed at the time. They typically arise from a retrospective pay revision, a backdated promotion or confirmation, a statutory wage revision, or a correction to attendance or master data. The arrear is the difference between what should have been paid in each affected month and what was actually paid.

How is arrear calculation done in India?

For each affected month, recompute the salary under the revised structure using that month's actual attendance, loss of pay and proration basis, then subtract what was actually paid — component by component, not on gross. Summing the month-wise, component-wise differences gives the total. Multiplying a monthly delta by the number of months is a shortcut that gives the wrong answer whenever there was loss of pay, a mid-month effective date or a structure change.

Is PF deducted on arrears?

As a general principle, PF is payable on arrears of PF-qualifying wages and is usually accounted in the month of payment. Whether an arrear actually increases the contribution depends on which components qualify as PF wages in your organisation, whether wages are restricted to the statutory ceiling, and the employee's category. Confirm the current rules and ceiling with your payroll advisor rather than assuming, since these change.

Why is TDS so high in the month arrears are paid?

Salary TDS is generally computed on projected annual income and spread across the remaining months of the financial year. An arrear raises that projection, which raises the annual liability, which is then recovered over fewer remaining months. The effect is sharpest in the last quarter. Employees may also be eligible for relief on arrears of salary under the income tax law, which can reduce the overall burden — they should check their position with a tax advisor.

Can an employer recover salary paid in excess?

Recovery of overpaid salary is generally permissible, but wage legislation limits which deductions are allowed and how much may be deducted in a wage period, and the position can vary by employee category. Beyond legality, good practice is to establish and document the overpayment, communicate in writing before deducting, offer proportionate instalments, and obtain acknowledgement. Confirm the applicable limits with your legal advisor before setting a recovery policy.

What are negative arrears?

Negative arrears occur when a retrospective recomputation shows the employee was overpaid — for example when loss of pay is approved after payroll ran, or a wrong allowance was mapped to a grade. They should be routed through a documented recovery process with an instalment plan, not silently netted off the next payslip. Individual components can also be negative inside an overall positive arrear, which is common in promotions that change the salary structure.

How should arrears appear on a payslip?

As separate labelled earnings lines — "Basic Arrears", "HRA Arrears" — rather than merged into current-month components, with the arrear period stated explicitly. Flag any month where loss of pay reduced the arrear. For material amounts, issue a supporting statement showing payable days, earned days, and old and revised amounts per component for each affected month. Show recoveries as a clearly named deduction.

Do employees who have left still get arrears?

Generally yes, for the portion of the arrear period during which they were employed, subject to your policy and the nature of the revision. Excluding separated employees because they are inactive in the system creates compliance and reputational risk. Where a full and final settlement was already computed on the old salary, check whether leave encashment, notice pay and other wage-linked amounts need restating on the revised basic.

Closing thoughts

Arrears will never disappear from payroll. Appraisal cycles run late, letters arrive after cut-off, statutory notifications are retrospective, and managers approve regularisations a week too slowly. The realistic goal is not zero arrears but controlled arrears — computed accurately, treated correctly under statute, explained clearly, and evidenced properly for audit.

Organisations that handle this well share a few traits. They store compensation history with effective dates instead of overwriting it. They recompute affected months rather than applying delta formulas. They route negative arrears through a human conversation before a deduction. And they publish a month-wise arrear statement without waiting to be asked.

All of this is easier in a system built for it. If arrears processing in your organisation currently lives in a spreadsheet only one person understands, that is a good signal it is time to change the tooling.

CozyHR handles effective-dated compensation, retrospective recomputation across affected months, component-level arrears including negatives, statutory recomputation, and the reports auditors ask for — with recovery workflows that keep employees informed. If you would like to see how your next appraisal cycle would run, try CozyHR and put a real arrear scenario through it.

This article is general guidance for payroll and HR teams, not legal or tax advice. Statutory rates, ceilings, thresholds and deduction limits change and vary by state and employee category. Verify the current position with a qualified professional before applying any of it to your payroll.