
Ask ten HR professionals what a salary advance policy should cover, and most will list the same five things: eligibility, request process, approval, limits, and repayment.
What they won’t tell you is where those policies quietly fall apart, in the tax sequencing during payroll, in the silence after a rejected request, or in what happens when an employee exits before the advance is fully recovered.
Hence, we will be sharing the tax and compliance mechanics behind a salary advance, and a framework for handling the messy parts, like rejections, repeat requesters, and mid-tenure exits.
A salary advance is a payment of wages an employee has already earned, or is about to earn, released ahead of the regular payroll cycle. It is not a credit. The employee is not borrowing money from the company; they are simply receiving their earnings early.
This distinction is not just semantic. Under the Payment of Wages Act, 1936, and the corresponding State’s Shops and Establishments Acts, advances must be documented, voluntary, and limited to what the employee is owed for work already performed. If you treat a salary advance like a loan in your official policy documentation, you risk two problems:
In contrast, an employee loan is a separate financial arrangement that can carry interest, requires its own documentation, and is not tied to wages already earned. If your company policy overlaps the two, you must rewrite it at the earliest.
To understand the legal and tax mechanisms of salary advances, let us go through:
In India, an advance is recovered from net pay only after standard statutory deductions are applied, in the following order:
For example, consider an employee on a gross salary of ₹40,000, with PF wages capped at ₹15,000. Their PF deduction will be ₹1,800. Professional Tax follows the applicable state slab, commonly ₹200 a month in states that levy it. Their TDS is calculated on the full monthly salary based on their tax regime and slab. Only after these three deductions does the advance recovery amount get subtracted from what remains.
HRs and organizations should state the exact eligibility criteria explicitly in the policy document itself, as vague eligibility language is the single most common reason advance requests turn into disputes. Most organizations in India build salary advance eligibility around the following criteria:
Two models are common in salary advance, based on the kind of organization:
If your workforce spans entry-level and senior salary bands, percentage-based limits are the fairer model. A ₹25,000 limit means very different things to someone earning ₹20,000 a month versus someone earning ₹2 lakh a month. Hence, you should state your chosen model explicitly in the policy, along with the calculation method, so there is no ambiguity at the point of approval.
Organisations usually follow a standard application-to-disbursement workflow:
However, organizations differ in executing these steps. Prompt payment matters here, as employees usually request advances during genuine financial stress. Hence, disbursement within 24 hours to 3 working days is a reasonable benchmark to commit to in writing.
This is where having a robust HR software helps streamline your workflow from application to disbursement. A request that sits unactioned in someone’s inbox for a week defeats the purpose of offering an advance at all. Hence, whichever system you use, the policy should specify the maximum turnaround time and who is accountable if that timeline slips.
A rejected advance request is a moment of vulnerability handled badly. Hence, your salary advance rejections require:
The standard operating procedure in the organization is to deduct the advance either as a single lump sum from the next payroll cycle or spread across a small number of instalments. Such instalments make sense for larger advances relative to salary, while lump sum works for smaller, one-off amounts.
However, what happens if the employee exits before the advance is fully recovered? This needs to be explicitly mentioned in the policy document. You should state clearly that any outstanding advance balance will be deducted from the employee’s Full and Final Settlement, and specify what happens in the rare case where the settlement amount is insufficient to cover the balance.
Frequency limitations and documentation requirements exist to protect the policy’s long-term sustainability. Hence, the language in your policy document should reflect that framing. A policy that reads like a list of limitations will be misunderstood by your staff as being restrictive and discouraging. A policy that explains why the safeguards exist, so the benefit remains available to everyone who genuinely needs it, helps increase your employees’ trust in your organization’s transparency.
Some of the practical safeguards worth including are:
If you wish to know how good your salary advance policy is, you should track:
No, as salary advance is a prepayment of wages already earned by the employee. It does not attract separate tax at disbursement. TDS continues to apply to the employee’s monthly salary.
Yes, employers can set eligibility criteria and frequency limits, and can decline requests that fall outside them. A well-drafted policy should specify these conditions clearly and require a documented response for any request decline.
There is no statutory limit for salary advance requests; however, many organizations limit advances to a percentage of earned wages, commonly up to 90%, or a fixed sum defined in the company policy. The Payment of Wages Act requires that any advance not exceed wages for work already performed.
The outstanding balance is typically recovered from the employee’s Full and Final Settlement. Policies should state this explicitly, along with the process if the settlement amount does not cover the outstanding balance.