Salary Arrears Calculation: A Payroll Processing Guide

Salary Arrears Calculation: A Payroll Processing Guide

Salary arrears calculation is one of those payroll tasks that looks trivial from the outside and turns out to be genuinely intricate once you open the spreadsheet. Someone gets an increment effective 1 April, but the appraisal letters only go out in July. Someone else is promoted with effect from an earlier quarter. A state notifies a minimum wage revision with retrospective effect. An attendance correction reverses three days of loss of pay from two months ago. In every one of these cases, you are not simply paying a person "some extra money this month" — you are rewriting history, and the rewrite has consequences for provident fund, ESI, professional tax, gratuity accrual, bonus eligibility, income tax deduction at source, and the numbers on your statutory returns.

This guide is written for payroll managers, HR operations leads, finance controllers and founders running payroll for Indian small and mid-sized businesses. It covers what arrears actually are, the triggers that create them, a disciplined month-wise computation method, component-wise splitting, the statutory knock-on effects, tax treatment and relief on arrears, payslip presentation, arrears for exited employees, recovery of overpayments, and the checks that keep an arrear run from turning into an audit finding.

A standing caution before we begin: statutory wage ceilings, contribution rates, tax slabs, professional tax schedules and the applicability thresholds for various labour statutes change over time and vary by state. Nothing in this article should be treated as a statement of current law or current rates. Every figure used here is an illustrative assumption for teaching the mechanics. Verify current rules with the relevant government portals, the applicable state notifications, and your own tax or legal advisor before you run a live payroll.

---

What Counts as Salary Arrears?

Arrears, in payroll terms, are amounts that an employee was contractually or statutorily entitled to receive in an earlier payroll period, but which were not paid in that period. The entitlement existed then. The payment happens now. That gap between entitlement date and payment date is the whole story.

This distinction matters more than people realise, because it separates arrears from three things that look similar:

• Arrears are retrospective. The entitlement arose in the past. Example: an increment effective 1 April, processed in July.
• Prospective revisions are not arrears. If you revise a salary effective from the current month, there is nothing to recompute.
• Deferred or contingent payments — a performance bonus declared and paid in one go, a retention payout that vests on a date — are usually not arrears, because entitlement crystallised only when the condition was met. They are current-period earnings, even if they relate to past performance.
• Corrections of payroll errors sit in a grey zone. If you underpaid HRA for two months because of a master data error, the amount owed is arrears in substance. If you overpaid, you have a recovery, which is arrears in reverse.

The reason this taxonomy matters is that arrears must be recomputed period by period, whereas current-period earnings are simply added to the current period. Recomputation is what drives PF, ESI, PT and tax outcomes.

The Common Triggers

In Indian SMB payroll, arrears show up for a fairly predictable set of reasons.

1. Appraisal cycle finalised late. Easily the most common. The company decides increments are effective 1 April, but budget approvals, manager calibration and letter generation run into June or July. Three or four months of arrears then hit a single payroll.

2. Promotion effective from an earlier date. A promotion approved in August but backdated to 1 June, often with a change in grade, allowance structure and sometimes a shift from a non-managerial to a managerial band.

3. Wage structure restructuring. The company changes its salary architecture — raising basic as a percentage of CTC, folding a conveyance allowance into special allowance, introducing a fixed statutory bonus component — and applies the new structure from an earlier date for consistency with the financial year.

4. Minimum wage revision notified retrospectively. State labour departments periodically revise minimum wages and variable dearness allowance, and notifications are sometimes published after the effective date. Employers covered by the applicable minimum wage schedules then have to top up past months for affected employees. Check the specific notification for your state, your scheduled employment and the relevant skill category, since these vary considerably.

5. Attendance or LOP correction. Loss of pay was applied for days that turn out to have been approved leave, comp-off or an on-duty travel day. The reversal creates arrears. The opposite — unrecorded absence discovered later — creates a recovery.

6. Missed overtime or shift allowance. Overtime registers or shift rosters reach payroll after cut-off, or an approval chain stalls. The overtime relates to a past wage period and must be paid at the rate applicable to that period.

7. Deferred joining formalities. A new joiner's bank details, PAN, or documentation are incomplete at cut-off, so their first month is held. When it is released, the earlier month's salary is arrears — and importantly, it is arrears of that earlier month for PF and ESI purposes, not fresh current-month wages.

8. Court, tribunal or settlement directed payments. An order directing payment of withheld wages, reinstatement with back wages, or settlement of a dispute. These often come with their own specifications about period, components and interest, and need careful reading before you compute anything.

9. Contract or vendor conversion. An employee moves from a contract engagement to direct employment with a backdated effective date, or a probation confirmation with a backdated confirmation-linked salary change.

10. Statutory bonus true-up. After the annual accounts close, the bonus percentage payable is finalised and a differential becomes due for the relevant accounting year. Applicability, calculation ceilings and eligibility limits under bonus law should be checked as they stand currently.

Arrears vs. Ad Hoc Payments: A Quick Test

Ask three questions:

1. When did the entitlement arise? If the answer is a past wage period, it is arrears.
2. Would the past payslip have been different if you had known then what you know now? If yes, it is arrears.
3. Does the amount depend on the past period's attendance, wage rate or structure? If yes, it must be recomputed month-wise, not estimated.

If all three point backwards, you have an arrear, and you owe the employee a recomputation, not an approximation.

---

The Golden Rules of Arrear Processing

Before any formula, internalise these principles. Most arrear disasters trace back to violating one of them.

Rule 1: Recompute the Past, Don't Just Add a Lump Sum

The wrong way: "Her salary went up by ₹8,000 a month, it's been four months, pay ₹32,000 as arrears."

The right way: rebuild each affected month's payslip at the new rate, compare against what was actually paid, and pay the difference — component by component, month by month.

Why the shortcut fails:

• One of those months may have had loss of pay, so the arrear for that month is proportionately less.
• One of those months may have had a partial-month structure (mid-month joining, mid-month grade change).
• The components do not all scale identically — a fixed conveyance component may not change while basic and HRA do.
• Statutory deductions on the arrear depend on the month to which the arrear relates, not the month of payment, for several purposes.
• Overtime paid in a past month may need recalculation because the base wage for the overtime rate has changed retrospectively.

Rule 2: Preserve the Original Payroll; Post the Difference

Never edit a finalised payroll period. Once a period is closed, filings have been made, payments have been disbursed, and the ledger has been posted. The correct approach is to compute a shadow recalculation of the closed period, derive the delta, and post that delta in the current open period as clearly identified arrear lines with a reference to the original period.

This keeps three things intact: your original payslips (which employees may have used for loan or visa purposes), your original statutory filings (which you may amend separately if required), and your audit trail.

Rule 3: Split Arrears by Component

An arrear line that just says "Arrears — ₹47,320" is a liability, not a payslip entry. Arrears must be broken into basic arrears, HRA arrears, special allowance arrears and so on, because:

• PF is computed on a defined set of wage components, not on gross.
• HRA exemption computation depends on the HRA amount attributable to each month and the rent paid in that month.
• Gratuity and bonus calculations reference specific components.
• Employees claiming house rent exemption or other deductions need the split for their own tax filing.

Rule 4: Tag Every Arrear to Its Source Period

Every arrear amount should carry a "for the month of" tag. This single field drives correct PF wage-month attribution, correct ESI contribution-period allocation, correct professional tax treatment in some states, and clean reconciliation.

Rule 5: Never Net Arrears Against Recoveries Silently

If an employee is owed ₹40,000 in arrears and owes ₹12,000 from an earlier overpayment, do not show a single net line of ₹28,000. Show both, gross. Netting hides information, creates disputes, and makes both the tax computation and the statutory base ambiguous.

Rule 6: Decide Your Policy Before the Run, Not During

Document — in writing, approved by whoever owns payroll policy — how your organisation handles:

• Whether arrears attract PF and at what wage attribution
• Whether arrears are included in the month of payment or month of entitlement for ESI
• Whether LOP months are excluded proportionately
• How arrears interact with notice pay, full-and-final, and exited employees
• The instalment policy for recoveries

Making these decisions in the middle of a run, under time pressure, is how inconsistency creeps in.

---

Step-by-Step: How to Calculate Salary Arrears

Here is a repeatable method. Follow it in order.

Step 1: Establish the Effective Date and the Arrear Window

Get the authoritative document — the increment letter, promotion letter, board or management approval, the state notification, the court order. Extract:

• Effective date of the revision
• Processing month in which arrears will be paid
• Arrear window: every wage period from the effective date up to (but not including) the first month paid at the new rate

Example: revision effective 1 April, first paid correctly in the August payroll. Arrear window = April, May, June, July. Four months.

Watch for mid-month effective dates. If the promotion is effective 15 June, June is a split month: fifteen days at the old structure, fifteen (or sixteen) at the new. Your proration basis — calendar days, fixed 30 days, or working days — must match the policy you use everywhere else. Inconsistent proration is a frequent source of employee complaints.

Step 2: Freeze the "Old" and "New" Salary Structures

For each affected employee, capture both structures at the component level.

Illustrative example only. Component names, ratios and amounts vary by employer; use your own structure.

Note the fixed conveyance did not change. This is exactly the sort of detail a flat "difference × months" calculation destroys.

Step 3: Pull Actual Paid Data for Each Arrear Month

For each month in the window, retrieve what was actually paid — not what should have been paid at the old rate, but the actual payslip: paid days, LOP days, gross earned, each component earned, PF deducted, ESI deducted, PT deducted, TDS deducted.

This matters because the arrear is a difference between two recomputations, and the "as paid" side must reflect reality including any LOP, mid-month changes or one-off adjustments.

Step 4: Recompute Each Month at the New Structure with the Same Attendance

Now rebuild each month's earnings using the new structure but the same attendance facts — unless the arrear is itself an attendance correction, in which case use the corrected attendance.

The general formula for a component in a month:

`` Component earned = Component monthly rate × (Paid days ÷ Total days in the proration base) ``

Apply this consistently for both the "as paid" and "as should be" sides.

Step 5: Derive the Component-Wise Delta per Month

Subtract as-paid from as-should-be, per component, per month. Negative deltas are possible (for example, if a restructuring reduced a component while increasing another) and should be shown, not suppressed.

Step 6: Aggregate into Arrear Lines

Sum each component's deltas across all arrear months to get:

• Basic arrears
• HRA arrears
• Special allowance arrears
• Any other component arrears
• Overtime arrears (where the OT rate changed retrospectively)

Keep the month-wise detail available as backing documentation even though the payslip shows the aggregate per component.

Step 7: Recompute Statutory Deductions on the Arrears

This is where most of the technical work lives, and it gets its own section below. Broadly:

• Recompute PF on the arrear wages, respecting whatever wage definition and ceiling policy your organisation applies, and attribute to the correct wage month if your policy and filing mechanism require it
• Determine ESI treatment based on the contribution period rules and the employee's coverage status
• Check whether professional tax changes because the month's gross in the payment month crosses a different slab
• Recompute income tax projection for the year and adjust TDS

Step 8: Recompute Annual Tax Projection and Adjust TDS

An arrear payment increases the year's taxable income. Your payroll system should re-run the annual projection including the arrear, recompute the full-year tax liability, subtract TDS already deducted, and spread the remaining liability over the remaining months — or deduct a larger amount in the arrear month if the employee prefers.

Step 9: Produce the Arrear Statement

Every employee receiving arrears should get a month-wise statement showing, for each month: the old earned amount, the new earned amount, the difference by component, and the total. This one document eliminates the overwhelming majority of arrear queries.

Step 10: Post, Reconcile and Archive

Post the arrear to payroll, reconcile the totals to your approval document, and archive the calculation workings with the approval, the effective-date evidence and the sign-off.

---

Worked Example 1: A Straightforward Backdated Increment

Illustrative scenario (all figures assumed, not real): Priya's increment is effective 1 April. It is processed in the August payroll. Her old gross was ₹60,000 per month; new gross ₹73,000. Proration basis: calendar days. She had 2 days of LOP in June.

Month-Wise Gross Arrear Computation

Illustrative example. June figures reflect 28 paid days of 30 (₹73,000 × 28 ÷ 30 = ₹68,133 rounded).

Notice the June arrear is ₹12,133, not ₹13,000. The naive "₹13,000 × 4 = ₹52,000" would have overpaid by ₹867. Small on one employee; meaningful across two hundred.

Component-Wise Split of the Same Arrear

Illustrative example. June components prorated at 28/30.

This second table is the one you attach to the payslip. It tells the employee exactly what changed, and it gives your PF, ESI and tax engines the inputs they need.

---

Component-Wise Arrears: Why Splitting Matters

It is tempting to treat arrears as a single sum. Resist it. Here is what the split actually drives.

Basic Salary Arrears

Basic is the load-bearing component of Indian payroll. It typically drives:

• Provident fund contributions (subject to the applicable wage definition and any ceiling policy)
• Gratuity accrual and eventual payout calculation
• Statutory bonus computation where applicable
• Leave encashment in many policies
• Notice pay and severance in many contracts
• HRA exemption computation, since the exemption formula references a percentage of salary

A retrospective increase in basic therefore ripples into all of the above. If your arrear posting does not identify how much of the arrear is basic, none of these downstream recalculations can be done correctly.

HRA Arrears

HRA arrears matter for the employee's rent-based exemption computation. The exemption is generally computed on a monthly basis using the HRA received in that month, the rent paid in that month, and salary for that month. When HRA for past months increases retrospectively, the exemption for those months may also increase — provided the rent evidence supports it.

Practically:

• Your payroll system should attribute HRA arrears to the correct months when running the exemption computation, not treat the entire arrear as HRA of the payment month.
• If the system cannot do month-wise attribution, at minimum flag it, and let the employee true up in their own return filing.
• Employees who did not pay rent in the arrear months get no additional exemption regardless of the arrear.

Special Allowance and Residual Components

Special allowance is usually the balancing figure in an Indian CTC structure. It absorbs whatever is left after basic, HRA and fixed allowances. Consequently:

• It moves the most in absolute terms during a restructuring
• It is typically fully taxable
• Its treatment under wage definitions for statutory purposes has been the subject of interpretation and should be checked against current guidance and your advisor's view

Fixed Allowances That Do Not Change

Conveyance, telephone reimbursement, fixed meal allowance and similar components often stay constant across an increment. Including them in a flat arrear multiplier is a common, silent overpayment.

Reimbursements and Expense Claims

These are not salary and should never be part of an arrear computation. If a reimbursement was delayed, pay it as a reimbursement, not as an arrear — the tax and statutory treatment is entirely different.

Overtime and Shift Arrears

Where the base wage used to compute overtime has increased retrospectively, past overtime hours may need re-rating. The mechanics:

1. Recompute the overtime hourly rate at the new base wage for each affected month
2. Multiply by the overtime hours actually worked in that month
3. Subtract the overtime already paid
4. The difference is overtime arrears for that month

The multiplier and the base for overtime are set by the applicable statute and rules for your establishment type and state — verify these rather than assuming a general figure.

---

Worked Example 2: A Mid-Month Promotion with Structure Change

Illustrative scenario: Rahul is promoted effective 16 June. Processed in the September payroll. His structure changes materially — not just a uniform increase. Proration basis: calendar days.

Old monthly structure (illustrative): Basic ₹24,000, HRA ₹12,000, Conveyance ₹1,600, Special allowance ₹7,400. Gross ₹45,000.

New monthly structure (illustrative): Basic ₹32,000, HRA ₹16,000, Conveyance ₹1,600, Special allowance ₹12,400, plus a new Site allowance ₹3,000. Gross ₹65,000.

Month-Wise Recomputation

Illustrative example only.

Component-Wise Arrear Split

Illustrative example only.

Two things to observe. First, the new Site allowance appears only from 16 June — it did not exist before, so there is no "old" figure to subtract; the entire amount is arrears. Second, conveyance remained flat, contributing zero. A flat differential approach (₹20,000 per month × 2.5 months) would have produced the same total here by coincidence, but the component split would have been wrong, and the PF, HRA-exemption and gratuity implications would all have been misstated.

---

Statutory Knock-On Effects of Arrears

This is where arrear processing stops being arithmetic and becomes compliance. Treat each of the following as a topic to verify against current rules — the mechanics described here are structural, not a statement of current rates or ceilings.

Provident Fund on Arrears

The general principle: provident fund contributions are payable on the wages that qualify under the applicable definition. If an arrear increases those qualifying wages for past months, contributions on the incremental amount generally become due.

Key considerations to work through with your advisor and against current rules:

1. Which components of the arrear are PF-qualifying? This depends on the statutory wage definition and on how your organisation has structured its components. The treatment of allowances that are universally, ordinarily and necessarily paid to all employees has been the subject of judicial interpretation, and organisations differ in their positions. Do not assume; confirm your position and apply it consistently to arrears exactly as you apply it to regular wages.

2. The wage ceiling question. PF law contemplates a statutory wage ceiling for mandatory coverage and for the employer's contribution obligation, and many employers contribute on wages above the ceiling as a matter of policy. Whether an arrear increases PF contributions therefore depends on:

• Whether the employee's wages were already at or above the applicable ceiling before the arrear — in which case a ceiling-limited employer may see no change
• Whether your organisation contributes on actual wages without restricting to the ceiling — in which case the arrear will increase contributions proportionately
• Whether the arrear pushes an employee from below the ceiling to above it, changing the calculation basis

Confirm the current ceiling amount and the current contribution rates from the official source before you compute anything.

3. Month attribution. PF returns are filed month-wise. An arrear relating to April but paid in August raises the question of which month's return it belongs to. Practice varies, and the filing mechanism itself constrains what is possible. Common approaches include reporting the arrear in the month of payment with a clear internal record of the source months, or filing supplementary/arrear entries where the mechanism supports it. Establish your approach, document it, and be consistent — inconsistency is what triggers queries.

4. Interest and damages exposure. Delayed remittance of contributions can attract interest and damages under the applicable provisions. Where arrears arise from an employer-side delay, factor this into your decision on how promptly to process and remit. This is a strong practical argument against letting appraisal arrears drift for six months.

5. Employee-side impact. An arrear increases the employee's own PF deduction in the payment month, sometimes noticeably. Communicate this. An employee expecting ₹51,000 of arrears and receiving substantially less after PF and tax will raise a ticket unless you have explained the deductions in advance.

ESI on Arrears

Employees' State Insurance operates on defined contribution periods and benefit periods, and on a wage threshold for coverage. Arrears interact with this structure in a few specific ways.

Coverage continuity within a contribution period. ESI rules are structured so that an employee covered at the start of a contribution period generally remains covered for the remainder of that period even if wages rise above the threshold mid-period. This means an arrear that pushes an employee's wages above the coverage threshold does not typically remove them from coverage immediately — contributions usually continue until the end of the contribution period. Verify the exact current rule and the current threshold before applying this.

Contributions on arrear amounts. Where an employee is covered, arrears paid to them generally form part of wages for contribution purposes. The practical question is which contribution period the arrear belongs to.

Timing sensitivity. Because ESI has fixed contribution periods, the timing of an arrear payment relative to period boundaries can affect the outcome. An arrear paid just before a period ends behaves differently from one paid just after.

Exited employees. Arrears paid to someone who has already left require care — coverage status, contribution period and the employer's reporting obligations all need checking.

Given how much of this depends on current thresholds and period definitions, treat ESI on arrears as a "check the current rules every time" item rather than something you configure once and forget.

Professional Tax

Professional tax is a state levy. Rates, slabs, deduction frequency and filing formats differ across states, and some states do not levy it at all. Arrears interact with PT in two ways:

1. Slab movement in the payment month. Most state PT schemes deduct based on the gross salary for the month. A large arrear inflates the payment month's gross, potentially pushing the employee into a higher slab for that month. Whether this is the correct treatment depends entirely on the state's rules — some states' schemes reference monthly gross as paid, others may be interpreted differently.

2. Annual caps. Some states cap annual PT. If an arrear pushes monthly PT higher, you may hit the annual cap earlier in the year and need to stop deducting.

Action: check the notification and the FAQ for each state in which you have employees. Configure your payroll to handle arrear months explicitly rather than letting a generic slab lookup produce whatever it produces.

Gratuity Impact

Gratuity is calculated on a defined wage base (typically referencing last drawn wages and a defined set of components) and on completed years of service. A retrospective increase in basic:

• Increases the gratuity accrual liability for accounting purposes
• Increases the eventual payout for anyone who separates after the revision
• May require your actuarial valuation inputs to be refreshed if the revision is material across a large population

For an employee who separated during the arrear window, and whose revision was effective before their exit date, the gratuity already paid may be understated. This is a real and frequently missed exposure — see the section on exited employees.

Bonus Impact

Where statutory bonus is applicable, both the eligibility threshold and the calculation ceiling are defined amounts that should be checked against current law. A retrospective wage revision can:

• Move an employee across the eligibility threshold, creating or extinguishing entitlement for the relevant accounting year
• Change the calculation base if the applicable wage is below the calculation ceiling
• Trigger a differential payable for a past accounting year

If your revision is effective from a date inside a previous accounting year for bonus purposes, flag it for a bonus recomputation. Do not assume the payroll system does this automatically.

Leave Encashment, Notice Pay and Other Derived Amounts

Any amount computed as a multiple of salary is affected by a retrospective revision:

• Leave encashment paid during the arrear window at the old rate
• Notice pay recovered or paid at the old rate
• Any salary-linked insurance cover or benefit sum assured
• Retention or variable pay expressed as a percentage of fixed pay

Build a checklist of every salary-derived amount in your organisation and run through it whenever a material retrospective revision lands.

Labour Code Wage-Definition Effects

India's labour codes introduce a consolidated definition of "wages" with a structural feature that matters enormously for arrears: a rule that excluded components, taken together, should not exceed a specified proportion of total remuneration, with the excess deemed to be wages.

The implication for arrear processing is significant. Under such a definition:

• A restructuring that shifts money into excluded allowances may not reduce the statutory wage base as intended
• A retrospective restructuring could change the deemed wage figure for past months, altering PF, gratuity and other calculations for those months
• The interaction between the deeming rule and arrear attribution needs to be worked out explicitly

The status, commencement and rules under the labour codes have evolved and continue to evolve, and state-level rules matter. Do not design a restructuring around an assumed position. Get current advice, and if you are contemplating a retrospective restructuring, get that advice before you set the effective date.

---

Income Tax and TDS on Salary Arrears

Arrears are salary income. The employer must deduct tax at source on them like any other salary payment, and the general position in Indian salary taxation is that salary is taxed on a due-or-receipt basis, whichever is earlier. In practical payroll terms, an arrear paid in the current financial year for months falling in the same financial year is simply part of that year's income. Arrears relating to an earlier financial year are more interesting, because they generally get taxed in the year of receipt even though they relate to an earlier year — which can push the employee into a higher effective rate than they would have faced had the money been paid on time.

How an Arrear Changes the TDS Projection

Employers compute monthly TDS on salary by projecting the employee's annual income, computing the estimated annual tax, and dividing the balance across remaining months. An arrear disturbs this in a specific sequence:

1. Add the arrear to the year's projected taxable income
2. Re-apply the employee's chosen tax regime, standard deduction and declared eligible deductions
3. Recompute the estimated annual tax liability including applicable cess
4. Subtract the TDS already deducted in the year to date
5. Divide the balance over the remaining months of the financial year (including the current one)

The rates, slabs, standard deduction amount, cess rate, surcharge thresholds and regime rules should be taken from the current year's provisions. Do not hard-code them from memory or from last year's configuration.

Worked Example 3: TDS Recalculation After an Arrear

Illustrative scenario, all figures assumed. Meera's arrear of ₹1,80,000 is paid in the October payroll. The financial year runs April to March; October is month 7, so six months remain including October. Assume for illustration that her computed annual tax liability was ₹96,000 before the arrear and ₹1,50,000 after it, and that ₹48,000 of TDS had already been deducted from April to September.

Illustrative example only. Tax liability figures are assumed for demonstration, not computed from any actual slab schedule. Use current-year rates and the employee's actual declarations.

Two employee-facing points come out of this table:

• The arrear does not cause the entire additional tax to be deducted in the arrear month unless you choose to do it that way. Spreading is the default and is usually kinder.
• Some employees prefer a one-time larger deduction to get it over with. If your system supports an override, offer it — but get the request in writing.

Relief on Arrears

Indian income tax law provides for relief where salary is received in arrears or in advance and the receipt in a single year pushes the taxpayer into a higher tax burden than they would have borne had the income been taxed in the years to which it relates. The relief is computed by comparing the tax outcome in both scenarios and allowing the difference.

The broad mechanism, described generally:

1. Compute the tax on total income of the year of receipt, including the arrear
2. Compute the tax on total income of the year of receipt, excluding the arrear
3. Take the difference — this is the additional tax caused by the arrear falling into this year
4. For each earlier year to which the arrear relates, compute tax on that year's income with and without the relevant portion of the arrear
5. Sum the differences across those earlier years
6. Relief is broadly the excess of the amount in step 3 over the amount in step 5

There is a prescribed form — Form 10E — associated with claiming this relief, and it is generally required to be furnished before claiming. Availability of the relief, the form's current version and filing mechanism, whether it applies under a particular tax regime, and the exact computation rules are all matters to verify against the current provisions and the current e-filing portal. Do not rely on this article, or on last year's process note, for the current position.

Practical guidance for payroll teams:

• Do not compute relief on the employee's behalf and apply it silently in payroll. The relief depends on the employee's total income in each earlier year, which includes income you do not have visibility into.
• Do inform employees that relief on arrears exists, that a prescribed form is associated with it, and that they should consult their tax advisor or the e-filing portal.
• Do give them the data they need: a month-wise and, critically, a financial-year-wise breakdown of the arrear amount. Without knowing how much of the arrear relates to FY 1 versus FY 2, the employee cannot compute anything.
• If your organisation chooses to consider relief in TDS computation, understand that this typically requires the employee to furnish the prescribed particulars to the employer, and your policy should be documented and consistently applied.

Worked Example 4: Financial-Year-Wise Arrear Split for Relief

Illustrative scenario: Arjun receives arrears of ₹2,64,000 in the July payroll of FY 2, arising from a revision effective from October of FY 1.

Illustrative example only. Note: the FY 2 portion (April to June) is current-year income and would not usually be the subject of relief for earlier years; only the FY 1 portion relates to a prior year.

The point of the table is not the arithmetic — it is the discipline of splitting by financial year. An employee handed a single figure of ₹1,98,000 has no way to compute anything. An employee handed this table can hand it straight to their advisor.

Practical Tax Handling Notes

• Perquisites and non-monetary components are usually not part of arrear recomputation, but if a perquisite value was salary-linked (for example, a rent-free accommodation value computed as a percentage of salary), a retrospective salary increase can change the perquisite value for past months. Check this.
• Regime choice. Where an employee has opted for a particular tax regime for the year, the arrear is taxed within that regime. A large arrear can occasionally make a different regime more favourable, but regime switching rules are constrained; refer the employee to their advisor rather than advising them yourself.
• Form 16 presentation. The arrear should appear within the salary figures for the year of payment. If you have issued detailed annexures, make sure the arrear is visible as a separate line so the employee's advisor can identify it.
• Quarterly TDS returns. A large arrear run in one month will produce a visible spike in your quarterly return. Make sure the challan and the deductee-wise breakup reconcile before filing.

---

Showing Arrears on the Payslip

The payslip is where arrear processing either builds trust or destroys it. A payslip that shows a mysterious lump sum generates tickets. A payslip that shows a clearly labelled, component-wise arrear with a reference period generates almost none.

What a Good Arrear Payslip Looks Like

Separate earning lines, one per component, each explicitly labelled as arrears:

Illustrative example only. Deduction amounts are assumed for presentation and are not computed from any current statutory rate or slab.

Why a Separate Arrear Line Matters

For disputes. When an employee says "I didn't get my full increment," a payslip with a separate arrear column plus an attached arrear statement resolves the conversation in one exchange. Without it, you are reconstructing four months of history in an email thread.

For loan and visa documentation. Banks and consulates scrutinise salary spikes. An unexplained ₹1.24 lakh month in an otherwise ₹73,000 salary history raises questions. A clearly labelled arrear line explains it.

For statutory scrutiny. During an inspection or audit, the ability to point at a payslip line, then at the arrear statement, then at the approval document, is the difference between a five-minute answer and a week of file-pulling.

For the employee's own tax filing. The employee's advisor needs to identify the arrear component to consider relief. Bury it in gross salary and it becomes invisible.

For internal analytics. Compensation cost analysis, budget variance and headcount cost reporting all break when arrears are mixed into regular salary without a tag.

Payslip Presentation Rules

• Label arrears explicitly with the word "Arrears" and, where the layout allows, the period ("Arrears Apr–Jul")
• Never combine arrears of different components into one line
• Never net arrears against recoveries on the payslip
• Show the arrear statement as an attachment or a downloadable link from the employee self-service portal
• If the arrear spans financial years, show the split — this is a small effort that saves the employee real money and saves you real explaining

---

Arrears for Exited Employees and Full-and-Final Settlement

This is the category most frequently missed, and the one that most frequently comes back as a legal notice.

The Core Problem

If a revision is effective 1 April and an employee resigned in June, they worked April, May and part of June at the old rate. Their entitlement for those months increased retrospectively. Their full-and-final settlement was computed on the old salary. Several things are now understated:

• Salary arrears for April, May and the worked part of June
• Leave encashment, if it was computed on a salary base that has increased
• Gratuity, if they were eligible and the calculation base has increased
• Notice pay paid or recovered, if computed on the old salary
• Statutory bonus, if applicable and the base has changed
• The employer's PF contribution for those months

Deciding Eligibility

Before computing anything, establish policy. Common positions:

1. Effective-date eligibility. Anyone employed on or after the effective date gets arrears for the period they worked, regardless of whether they are still employed. This is the cleanest and most defensible position.
2. Employment-on-announcement-date eligibility. Only those on the rolls when the revision was announced receive it. This is used by some employers, particularly for discretionary merit increases, and it should be stated explicitly in the increment policy if you intend to rely on it.
3. Mixed. Statutory revisions (minimum wage, wage-definition changes, court-directed payments) go to everyone who worked in the period, without exception. Discretionary merit increases follow the stated policy.

Whatever you choose, write it down before the run and apply it uniformly. Inconsistency here — paying one exited employee and not another — is the fact pattern that becomes a dispute.

Note also that statutorily mandated arrears (a retrospective minimum wage revision, for example) are generally not discretionary. If an employee worked during the covered period, the entitlement typically attaches to the work performed. Verify the specific position for your situation.

The Exited-Employee Arrear Procedure

1. Identify the population. Pull every employee who was on the rolls at any point between the effective date and the processing date, including those who have since left. Most payroll systems default to active employees only — this is the single most common cause of missed exit arrears.
2. Recompute their worked months at the new structure, exactly as for active employees, stopping at their last working day.
3. Recompute derived amounts — leave encashment, gratuity, notice pay, bonus — at the revised base if your policy and the applicable law require it.
4. Recompute statutory deductions for the arrear months.
5. Recompute tax. This is the awkward part. The employee is no longer on your payroll, so you cannot spread TDS. You generally deduct applicable tax at the point of payment and reflect it in the relevant quarter's TDS return and the employee's Form 16 for the year of payment.
6. Issue a revised settlement statement. Do not send only a bank transfer. Send a document explaining the recomputation, referencing the original settlement, and showing the differential.
7. Confirm bank details before paying. Accounts close. Confirm in writing.
8. Handle PF properly. If the ex-employee has already withdrawn or transferred their PF, an additional employer contribution for past months creates a complication. Work out the mechanism with your PF consultant before remitting.

Worked Example 5: Exit Arrears and Settlement Differential

Illustrative scenario: Sneha resigned with last working day 20 June. Increment effective 1 April, processed in September. Old gross ₹50,000; new gross ₹58,000. She had 12 days of accumulated leave encashed at exit, encashed on basic. Old basic ₹25,000; new basic ₹29,000. Proration on calendar days; leave encashment on a 30-day divisor.

Illustrative example only. Leave encashment computed as basic ÷ 30 × 12 days. Gratuity not shown as service length is assumed below the eligibility threshold; verify the applicable eligibility rule for your situation.

The differential of ₹22,934 is a real liability. Ignoring it because "she's already left" is not a defence.

---

Recovery of Overpayments

Arrears run in both directions. Sometimes payroll pays too much — a duplicate payment, a salary change applied late in the wrong direction, an LOP not applied, a resignation processed after the payroll cut-off, an incorrect allowance switched on. Recovering it is legally and ethically more delicate than paying arrears, and it is worth slowing down.

The Ethical and Practical Frame

Start from a simple premise: the overpayment was almost certainly your error, not the employee's. They received money they did not expect, may have spent it, and now face an unexpected reduction in take-home pay. Handle it accordingly.

Three principles:

1. The employee did not cause this. Communicate without any implication of fault. "We identified an error in our processing" is the correct framing, not "you were overpaid."

2. Recovery should not create hardship. A ₹60,000 recovery from someone earning ₹35,000 a month cannot happen in one deduction. Instalments are the norm for anything material.

3. Consent and documentation matter. Deductions from wages are a regulated area in India, with rules about what may be deducted and in what circumstances. Rather than assuming you have a unilateral right to deduct, obtain the employee's written acknowledgement of the overpayment and written agreement to the recovery schedule. Check the applicable wage-payment provisions and any limits on total deductions as a proportion of wages. Where an employee disputes the overpayment or refuses to agree, get legal advice before deducting.

The Recovery Procedure

Step 1: Verify before you communicate. Recompute the disputed period independently. Confirm the overpayment is real, quantify it exactly, and identify the root cause. Nothing damages credibility more than raising a recovery and then withdrawing it.

Step 2: Determine the net versus gross question. If you overpaid ₹50,000 gross, you also over-deducted PF, PT and TDS on it, and the employee only received the net. Recovering the gross from a person who received the net is unfair unless the corresponding statutory over-remittances are also unwound or credited. Work out:

• Gross overpayment
• Statutory deductions applied to it (PF employee share, PT differential, TDS)
• Net actually received by the employee
• Whether and how the over-remitted PF and TDS can be adjusted

In many cases the cleanest approach is to recover the gross while adjusting the corresponding statutory amounts in the current period's computation, so the employee is made whole on the deductions side. This needs to be modelled explicitly, not assumed.

Step 3: Communicate in writing, privately, with the full workings. Attach a month-wise statement showing exactly how the overpayment arose. Offer a conversation. Do not send this as a payslip surprise.

Step 4: Agree a schedule. Propose instalments proportionate to the amount and the employee's salary. A common approach caps the monthly recovery at a modest percentage of net pay, extended over as many months as needed. Confirm the schedule in writing with the employee's acknowledgement.

Step 5: Set up the payroll mechanics. Configure a recovery deduction with:

• A clear, separate payslip line ("Recovery of excess payment")
• A defined instalment amount and number of instalments
• An outstanding-balance tracker visible to the employee
• Automatic stop when fully recovered
• A rule for what happens if the employee separates before the recovery completes

Step 6: Handle the tax side. Whether a recovery reduces taxable income, and in which year, depends on the facts and the applicable provisions. If the overpayment and the recovery fall in the same financial year, the arithmetic is usually straightforward — the year's net salary is lower. Across financial years it becomes more complicated, particularly if Form 16 has already been issued and the return already filed. Take advice for cross-year recoveries rather than improvising.

Step 7: Fix the root cause. Every recovery is a process failure. Document what went wrong and change the control that should have caught it.

Worked Example 6: Overpayment Recovery Schedule

Illustrative scenario: Due to a delayed exit notification, Vikram was overpaid for one month. Gross overpayment ₹48,000; statutory deductions applied ₹9,600; net received ₹38,400. Agreed recovery: gross ₹48,000 over 6 instalments, with the corresponding statutory amounts adjusted in the current period computation. His normal net pay is ₹52,000.

Illustrative example only. Net pay shown is indicative and ignores the statutory adjustment effects described above; model these explicitly in a live case.

Recovery from Exited Employees

If the person has already left, you cannot deduct from future payroll. Options generally include adjusting against any pending full-and-final amount, requesting voluntary repayment, or pursuing recovery through appropriate legal channels. The cost-benefit of the last option is often unfavourable for small amounts. Whatever you do, keep the tone professional and the documentation complete. And build the control that stops it happening again — usually a hard exit-notification cut-off tied to the payroll calendar.

Recovery Red Lines

• Do not deduct without notice
• Do not deduct an amount that leaves the employee without a reasonable take-home
• Do not recover from statutory dues that are protected
• Do not use recovery as leverage in an unrelated dispute
• Do not recover amounts that were, on the facts, a discretionary payment the employee was entitled to keep

---

Arrears in a Payroll System vs. Spreadsheets

Most Indian SMBs start with spreadsheets and move to a payroll system somewhere between fifty and two hundred employees. Arrears are usually the trigger, because they are the point at which spreadsheet payroll becomes genuinely unsafe.

Why Spreadsheets Struggle with Arrears

No historical state. A spreadsheet has whatever is in the current tab. Reconstructing "what were this person's exact component values in May, and what attendance did they have" requires opening an old file that may have been overwritten, edited or lost. Retrospective calculation requires reliable history, and spreadsheets rarely have it.

Formula fragility. Arrear workbooks accumulate lookups across tabs, hard-coded month counts and copy-pasted blocks. A single dragged formula, an inserted row, or a changed sheet name silently corrupts a column. Errors are found by the affected employee, not by the process.

No automatic statutory recalculation. Every PF, ESI, PT and TDS consequence has to be reasoned through manually for every employee. At scale, someone will miss the person whose arrear pushes them across a threshold.

No audit trail. Who changed the effective date from 1 April to 1 March? When? On whose approval? A spreadsheet cannot answer.

Single point of failure. The arrear logic lives in the head of the one person who built the workbook. When they are on leave during appraisal season, the run stalls.

No exit-population awareness. A spreadsheet built from the current active roster will silently exclude everyone who left during the arrear window.

What a Payroll System Should Do for Arrears

A payroll system that handles retrospective processing properly should provide:

• Effective-dated master data. Salary structures, grades, statutory applicability and attendance stored with valid-from and valid-to dates, so any past date can be reconstructed exactly.
• Retro or arrear runs. The ability to select a past period, recompute it under current master data, and generate a delta without disturbing the closed period.
• Automatic component-wise splitting. Arrears generated per component, per month, with the source period tagged.
• Statutory recalculation. PF, ESI, PT and TDS recomputed on the arrear per the configured rules, with the ability to configure attribution policy.
• Annual tax re-projection. Automatic re-forecast and TDS spreading after the arrear is posted.
• Inclusion of exited employees. The ability to run a retro across a population defined by employment during the period, not by current active status.
• Arrear statements. Auto-generated month-wise statements attached to the payslip or available in self-service.
• Simulation mode. Run the arrear, review outputs, adjust, and only then commit.
• Full audit logging. Who ran it, when, with what parameters, what changed, and who approved.

Audit Trail Requirements

Whether you use a system or spreadsheets, an arrear run should leave behind a defensible file. At minimum:

1. The authorising document — increment letter, promotion approval, board or management resolution, government notification, court order.
2. The effective date evidence and any explanation of why processing is later than the effective date.
3. The population list — every employee included, and, critically, a documented reason for anyone excluded.
4. The calculation workings — month-wise, component-wise, per employee.
5. The statutory impact summary — incremental PF, ESI, PT and TDS by employee and in total.
6. The reconciliation — arrear total per the payroll register tied to the arrear total per the approval.
7. The approval trail — who reviewed, who approved, when, with timestamps.
8. The payment evidence — bank advice or transfer reference tied to the run.
9. The communication record — what was sent to employees and when.
10. The remittance evidence — challans for the incremental statutory amounts.

Retain these for the period your statutory record-retention obligations require. Different statutes prescribe different retention periods; check the ones applicable to you.

---

Reconciliation and Month-End Checks After an Arrear Run

An arrear run distorts every routine month-end comparison. Your usual "this month versus last month" variance check will light up like a switchboard. Here is how to reconcile properly.

The Four Reconciliations

1. Arrear total reconciliation. Sum of all arrear lines in the payroll register must equal the approved arrear amount. If it does not, find every rupee of the difference before you disburse. Common causes: an employee wrongly included or excluded, a proration difference, a rounding policy mismatch, a component missed.

2. Component reconciliation. For each component, the sum of that component's arrears across all employees should tie to a separate independent calculation. Build the independent calculation from the source data, not from the payroll output — otherwise you are checking a number against itself.

3. Statutory reconciliation. Incremental PF, ESI, PT and TDS should be computed independently and tied to the payroll output. This is the check that most often catches a configuration error, because statutory logic is where the system's assumptions live.

4. Bank reconciliation. Total net pay in the register must equal the total of the bank transfer file, transaction by transaction. Never disburse without this tie-out.

The Variance Analysis

Run a month-on-month variance with arrears isolated:

Illustrative example only.

Every rupee should be attributable to a named cause. An unexplained variance of any size means you do not yet understand your own payroll for the month.

Additional Month-End Checks After an Arrear Run

• Negative net pay report. A large arrear combined with a large TDS catch-up and an ongoing recovery can push someone negative. Catch this before disbursement, not after.
• Threshold crossing report. List everyone whose wages crossed a statutory threshold this month because of the arrear, and confirm each was treated correctly.
• Zero-arrear exceptions. List everyone in the eligible population who received zero arrears, and confirm each has a valid reason (joined after the effective date, no change in structure, and so on).
• Outlier report. Flag any arrear above a threshold multiple of the employee's monthly gross for manual review. Data entry errors show up here.
• Exited-employee inclusion check. Confirm the run included the exit population, and that each exited employee's arrear stops at their last working day.
• Duplicate check. Confirm no employee received the same arrear twice — the classic failure mode when a run is aborted mid-way and restarted.
• Ledger posting check. Arrears should post to the correct GL accounts and cost centres, and to the correct period for accrual purposes. If your accounts already carried a provision for the increment, the arrear payment should release that provision rather than double-counting the expense.
• Provision release check. Coordinate with finance. If a provision was created month by month from the effective date, the arrear payment consumes it. If no provision was created, the entire arrear hits one month's P&L, which finance should know about in advance.

---

Communicating Arrears to Employees and Managers

Good communication converts a payroll event into a positive experience. Poor communication converts a pay rise into a complaint.

Principles

• Communicate before payday, not on payday. People plan around their salary.
• Show the workings. Attach the month-wise statement.
• Explain the deductions. Set expectations about PF and TDS so the net does not shock.
• Name a contact. One person or one mailbox for arrear queries.
• Say something about tax relief. Mention that relief on arrears may be available and that they should consult their advisor and the current rules.

Template: Employee Notification of Arrears

Subject: Salary revision arrears in your [Month] payroll Dear [Name], Your salary revision is effective from [effective date]. Since the revision was finalised after that date, the difference for [list months] will be paid to you as arrears in your [Month] salary. Total gross arrears: ₹[amount] A detailed month-wise and component-wise statement is attached, showing what you were paid for each month and what you should have been paid at the revised structure. Please note: - Statutory deductions (provident fund and, where applicable, professional tax) apply to arrears, so your net credit will be lower than the gross arrear amount. - Income tax has been recalculated for the full financial year including this arrear. Your monthly tax deduction from [Month] onwards will be ₹[amount] against ₹[previous amount] earlier. This is not an additional tax — it is the same annual liability spread across the remaining months. - Where arrears relate to an earlier financial year, tax law provides for relief in certain circumstances, claimed using a prescribed form. The statement shows the financial-year-wise split so you can discuss this with your tax advisor. Please refer to the current rules on the income tax e-filing portal. If anything in the statement does not match your understanding, write to [contact] by [date] and we will review it with you. Regards, [Name], [Designation]

Template: Manager Briefing Before an Arrear Run

Subject: Arrear payout in [Month] payroll — what your team will ask you Team, Increment arrears for [period] will be paid in the [Month] payroll, crediting on [date]. What to expect: 1. Net credit will be lower than the arrear figure in the letter. PF and income tax apply. This is normal and not an error. 2. Monthly tax deduction will rise for the rest of the financial year. The annual liability increased because annual income increased; it is being spread rather than deducted all at once. 3. Team members with loss of pay during the arrear period will receive proportionately less. Arrears are computed on days actually paid. 4. People who joined mid-period get arrears only from their joining date. 5. People whose structure had a fixed component that did not change will see a smaller arrear than a simple multiplication suggests. Every person receiving arrears has a month-wise statement attached to their payslip. Please direct calculation queries to [contact] rather than answering from estimates — the statement is authoritative. Regards, [Name]

Template: Overpayment Recovery Notification

Subject: Correction to your [Month] salary — action required Dear [Name], During a review of our payroll records we identified a processing error on our side that resulted in an excess payment to you of ₹[amount] gross in [Month]. The detailed workings are attached. To be clear, this was our error and not caused by anything you did. We propose to recover this amount in [N] monthly instalments of ₹[amount] each, beginning [Month], so that the impact on your monthly take-home is manageable. Your payslip will show this as a separate line with the remaining balance. If this schedule creates difficulty, please let us know and we will discuss an alternative. Please confirm your acknowledgement by replying to this email by [date], or write to [contact] if you would like to discuss the calculation first. We are sorry for the inconvenience and have put a control in place to prevent a recurrence. Regards, [Name], [Designation]

---

Common Mistakes and How to Catch Them

A catalogue of the failures that recur across SMB payroll teams, with the control that prevents each.

1. Flat Multiplication Instead of Recomputation

Mistake: Monthly difference × number of months. Consequence: Overpayment where there was LOP, wrong component split, wrong statutory base. Control: Mandate a month-wise recomputation for every arrear. Reject any arrear file that does not contain a month-wise sheet.

2. Forgetting LOP Months

Mistake: Applying the full monthly difference to a month with unpaid absence. Consequence: Overpayment; inconsistent treatment across employees. Control: A validation rule that compares paid days used in the arrear computation to paid days in the original payslip for the same month.

3. Excluding Exited Employees

Mistake: Running arrears only on the active roster. Consequence: Understated settlements, legal exposure, reputational damage. Control: Define the arrear population as "employed at any point between the effective date and today," and get the count signed off separately from the amount.

4. Ignoring Fixed Components

Mistake: Scaling every component by the same percentage. Consequence: Small but systematic overpayment; incorrect component split. Control: Maintain a flag on each component indicating whether it scales with revisions.

5. Missing the Statutory Recalculation

Mistake: Paying the arrear gross without recomputing PF, ESI, PT and TDS. Consequence: Under-remittance, potential interest and damages, reconciliation failures, a large unexpected tax burden on the employee at year end. Control: A mandatory statutory impact summary as part of the arrear approval pack.

6. Dumping the Entire Tax Liability in One Month

Mistake: Deducting the whole incremental annual tax from the arrear month. Consequence: A very small net credit, a flood of complaints, and in some cases genuine hardship. Control: Default to spreading over remaining months; require an employee's written request to do otherwise.

7. Not Splitting Arrears by Financial Year

Mistake: Reporting a single arrear figure spanning two financial years. Consequence: The employee cannot evaluate relief and may pay more tax than necessary. Control: Make FY split a mandatory field in the arrear statement template.

8. Netting Arrears Against Recoveries

Mistake: Showing one net figure. Consequence: Disputes, ambiguous statutory base, unclear audit trail. Control: A payslip layout rule forbidding netting; a validation that flags any employee with both an arrear and a recovery in the same run.

9. Editing Closed Periods

Mistake: Reopening a finalised month and changing it. Consequence: Payslips no longer match the filings and the disbursements already made; the audit trail is destroyed. Control: Hard period locks in the payroll system; retro processing only through a delta mechanism.

10. Inconsistent Proration Bases

Mistake: Using calendar days in one place and a fixed 30-day divisor in another. Consequence: Small discrepancies that employees notice and cannot be explained without embarrassment. Control: One documented proration policy, configured once, used everywhere.

11. Missing Derived Amounts

Mistake: Paying salary arrears but not revisiting leave encashment, gratuity, bonus or notice pay paid during the arrear window. Consequence: Understated payments discovered later, often by the employee. Control: A standing checklist of every salary-derived amount, reviewed on every material retrospective revision.

12. No Communication

Mistake: Money appears in the account with no explanation. Consequence: Tickets, mistrust, managers giving wrong answers. Control: Communication is a mandatory step in the arrear run checklist, not an optional courtesy.

13. Rounding Drift

Mistake: Different rounding at component, month and total level. Consequence: Totals that do not tie, and a rupee or two of unexplained difference that consumes an afternoon. Control: Define the rounding policy — where you round, to what precision, and how the residual is allocated — and apply it consistently.

14. No Approval Before Disbursement

Mistake: Payroll computes and pays; approval is obtained afterwards or not at all. Consequence: No control, no accountability, and a difficult conversation in the audit. Control: A documented approval gate between computation and disbursement, with named approvers.

---

Pre-Run and Post-Run Checklists

Print these. Use them every time.

Pre-Run Checklist

Authorisation

• [ ] Signed or system-approved authorising document on file
• [ ] Effective date confirmed and unambiguous
• [ ] Approved budget or total value on record
• [ ] Eligibility policy for exited employees documented and applied

Population

• [ ] Full population extracted: everyone employed at any point in the arrear window
• [ ] Exited employees included or explicitly excluded with a documented reason
• [ ] New joiners handled from their joining date
• [ ] Employees on long leave, sabbatical or suspension reviewed individually
• [ ] Employees who changed grade, location or entity during the window reviewed individually

Master Data

• [ ] Old and new structures captured component-wise for every affected employee
• [ ] Components correctly flagged as scaling or fixed
• [ ] Effective-dated records created; no overwriting of prior structures
• [ ] Statutory applicability re-checked for anyone crossing a threshold

Computation

• [ ] Month-wise recomputation completed for every employee
• [ ] Attendance and LOP for each arrear month pulled from actuals
• [ ] Proration basis consistent with policy
• [ ] Component-wise split produced
• [ ] Financial-year split produced where the window spans years
• [ ] Rounding policy applied consistently

Statutory

• [ ] PF impact computed; wage definition and ceiling policy confirmed against current rules
• [ ] ESI impact assessed against current thresholds and contribution-period rules
• [ ] Professional tax reviewed per applicable state rules
• [ ] Bonus and gratuity impact assessed
• [ ] TDS re-projected for the full year for every affected employee

Review

• [ ] Independent recomputation of a sample (at least the largest values and a random selection)
• [ ] Outlier report reviewed
• [ ] Zero-arrear exceptions reviewed
• [ ] Negative net pay report clear
• [ ] Approver sign-off obtained in writing

Communication

• [ ] Employee notification drafted with statements attached
• [ ] Manager briefing sent
• [ ] Query contact and response timeline defined
• [ ] Finance informed of the cash and P&L impact

Post-Run Checklist

Reconciliation

• [ ] Arrear total ties to approved amount
• [ ] Component totals tie to independent computation
• [ ] Statutory totals tie to independent computation
• [ ] Bank file ties to payroll register, line by line
• [ ] Variance analysis complete with zero unexplained variance

Compliance

• [ ] Incremental PF computed, remitted and reflected in the return per your documented attribution approach
• [ ] ESI handled per current rules
• [ ] Professional tax remitted per state schedule
• [ ] TDS deposited and reflected in the quarterly return
• [ ] Registers and records updated

Accounting

• [ ] Arrears posted to correct GL accounts and cost centres
• [ ] Any existing provision released rather than double-counted
• [ ] Accrual period treatment confirmed with finance

Documentation

• [ ] Complete calculation workings archived
• [ ] Approval trail archived
• [ ] Communications archived
• [ ] Payment evidence archived
• [ ] Remittance challans archived

Follow-Up

• [ ] Employee queries logged, tracked and closed
• [ ] Any errors identified, corrected and documented
• [ ] Root-cause review completed for the delay that created the arrears
• [ ] Process improvement actions assigned with owners and dates
• [ ] Next cycle's timeline adjusted to reduce arrear volume

---

Frequently Asked Questions

How do I calculate salary arrears for a backdated increment?

Do not multiply the monthly difference by the number of months. Instead, rebuild each affected month: take the new salary structure, apply the actual paid days and attendance for that month, and compute what the employee should have earned component by component. Compare that against what was actually paid in that month. The difference is that month's arrear. Sum across all months in the window, keeping the component split intact. Then recompute PF, ESI, professional tax and the annual tax projection on the resulting arrear. The month-wise method is the only one that handles loss of pay, mid-month changes and non-scaling fixed components correctly.

Is PF deducted on salary arrears?

Generally, provident fund contributions apply to arrears to the extent the arrear increases wages that qualify under the applicable definition. The practical answer for a specific employee depends on which components make up the arrear, whether your organisation restricts contributions to the statutory wage ceiling or contributes on actual wages, and whether the employee's wages were already at or above that ceiling. Because the ceiling amount, contribution rates and the treatment of specific allowances are all subject to current rules and interpretation, confirm the position with the current official guidance and your advisor rather than applying a rule of thumb. Also consider the month-attribution question — which wage month the arrear belongs to for return-filing purposes — and document a consistent approach.

Does ESI apply to arrears, and what happens if the arrear pushes someone over the wage threshold?

Where an employee is covered by ESI, arrears paid to them generally form part of wages for contribution purposes. On the threshold question, the scheme is built around fixed contribution periods, and the general structure is that an employee covered at the start of a contribution period continues to be covered for the remainder of that period even if wages rise above the threshold during it. So an arrear typically does not remove someone from coverage mid-period. The exact current threshold, the current contribution period definitions and the current rates must be verified from the official source before you compute anything, as these change.

How is income tax calculated on arrears, and can employees reduce it?

The arrear is added to the year's taxable income, the annual tax liability is recomputed under the employee's applicable regime, tax already deducted is subtracted, and the balance is spread over the remaining months of the financial year. Where arrears relate to an earlier financial year, income tax law provides for relief in certain circumstances, computed by comparing the tax outcome of taxing the arrear in the year of receipt against taxing it in the years to which it relates. A prescribed form, Form 10E, is associated with claiming this relief. Whether it is available in a given case, its interaction with the different tax regimes, and the current filing mechanism all need to be checked against the current provisions and the income tax e-filing portal. As an employer, provide the financial-year-wise arrear split and point employees to their advisor; do not compute the relief for them.

Do employees who have already resigned get arrears?

If the revision is effective from a date when they were still employed, they generally worked at least part of the arrear period, and an entitlement usually exists for the period they worked. For statutorily driven revisions — a retrospective minimum wage notification, for example — the entitlement typically attaches to the work performed and is not discretionary. For discretionary merit increases, the answer depends on your documented policy, which should be stated in the increment policy before the cycle begins. In either case, remember to revisit derived amounts: leave encashment, gratuity, notice pay and bonus may all have been computed on the old salary base at exit and may need a differential. Include the exit population in your arrear run population by default.

How do we recover an overpayment without breaching wage-payment rules?

Start by verifying the overpayment thoroughly and identifying whether the employee received the gross or the net. Communicate privately and in writing with full workings, framing it as an organisational error. Propose instalments sized so the monthly impact is manageable rather than recovering in one deduction. Obtain the employee's written acknowledgement of both the overpayment and the schedule. Deductions from wages are a regulated area in India with rules about permissible deductions and limits, so check the applicable wage-payment provisions and take legal advice where the employee disputes the amount or refuses to agree. Show the recovery as a separate payslip line with a visible outstanding balance, and never net it against arrears owed.

Can we just pay a lump sum and skip the month-wise calculation?

No, and the reasons are practical rather than pedantic. A lump sum computed by multiplication overpays anyone who had loss of pay in the window, misstates the component split that PF, HRA exemption and gratuity depend on, produces the wrong statutory base, gives the employee no way to evaluate tax relief, and leaves you with nothing to show an auditor or an inspector. It also makes the eventual employee query unanswerable, because you have no workings. The month-wise method takes minutes per employee in a properly configured system and is the only defensible approach.

What if the arrear period spans two financial years?

Split it. Compute the arrear month-wise as usual, then group the months by financial year and present both sub-totals separately in the arrear statement. The whole arrear is taxable in the year of payment, but the earlier-year portion is the part that matters for evaluating relief on arrears. Without the split, the employee's advisor cannot do the computation. Also check whether any earlier-year statutory or accounting treatment needs revisiting, and coordinate with finance on the accrual and provision position for the earlier year.

---

Bringing It Together

Salary arrears are not a special case to be handled by whoever has time. They are a recurring, predictable feature of Indian payroll — appraisal cycles run late, promotions get backdated, wage notifications arrive after their effective date, and attendance corrections surface weeks after the fact. The organisations that handle arrears well are not the ones with the cleverest spreadsheets. They are the ones that treat arrears as a defined process with a defined method.

The method, condensed:

• Recompute the past month by month. Never multiply and hope.
• Split by component and by financial year. The split is what makes everything downstream correct.
• Recompute the statutory consequences deliberately, verifying current rates, ceilings and thresholds every time rather than trusting a configuration set up two years ago.
• Include everyone who worked in the period, including those who have since left.
• Show your workings on the payslip and in a statement.
• Communicate before payday, and explain the deductions before people see them.
• Reconcile to zero unexplained variance, and archive the trail.
• Handle recoveries with consent, instalments and documentation — and fix the root cause.
• Reduce arrears at source. The best arrear run is the one you did not have to do because the appraisal cycle closed on time.

And keep the standing caveat in view: PF and ESI ceilings and rates, professional tax schedules, tax slabs, bonus and gratuity thresholds, and the wage definitions under the labour codes all change, and several vary by state. Everything in this guide describes mechanics. Verify the current numbers and the current rules with the relevant authority and your own advisors before every run.

Make Retro Runs a Non-Event with CozyHR

If you are reconstructing four months of payslips in a spreadsheet every appraisal season, the problem is not your arithmetic — it is the toolchain.

CozyHR is built for Indian SMB payroll, and retrospective processing is a first-class feature rather than a workaround:

• True retro payroll runs — select any past period, recompute it against effective-dated master data, and generate the delta without touching a single closed payslip
• Automatic component-wise arrear splits — basic, HRA, special allowance and every other component, tagged to the month they belong to
• Statutory recalculation built in — PF, ESI and professional tax recomputed on arrears per your configured policy, with rates and thresholds you control and can update as rules change
• Annual tax re-projection — TDS automatically re-forecast and spread across the remaining months after every arrear posting, with an option to deduct in one go where the employee prefers
• Exited-employee inclusion — retro runs that recognise anyone employed during the arrear window, not just the current roster
• Auto-generated arrear statements — month-wise, component-wise, financial-year-split, attached to the payslip and available in employee self-service
• Overpayment recovery workflows — instalment schedules, visible balances, automatic stop on completion
• Complete audit trail — every run, parameter, change and approval logged and exportable

Appraisal arrears, backdated promotions, retrospective minimum wage revisions and attendance corrections stop being a three-day exercise and become a review-and-approve step.

[Start your free CozyHR trial](#) and run your next retro cycle in an afternoon — or [book a walkthrough](#) and we will model one of your real arrear scenarios with you.

---

This article is intended as general guidance on payroll mechanics for Indian employers. It is not legal, tax or accounting advice. Statutory wage ceilings, contribution rates, tax slabs, professional tax schedules, applicability thresholds and the labour code wage definitions change over time and vary by state. All figures shown are illustrative assumptions used to demonstrate calculation method, not statements of current rates. Verify current requirements with the relevant government authorities and consult qualified professional advisors before acting.