Can You Keep Basic Salary at ₹8,000 under New Labour Laws?

Practical Salary Structuring Mistakes after the Wage Code

For years, “keep basic as low as possible” was the standard advice to save PF and gratuity. That’s exactly what the new labour laws 2025 is trying to kill.

So the big question everyone asks:

“Can I still keep basic at ₹8,000?”

Short answer: you can only get away with a low basic if your overall structure still respects the 50% ‘wages’ rule and minimum wage. Most old-school structures won’t.

Let’s break it down.

1. The new idea of “wages” (not just basic)

Under the Wage Code, “wages” are not equal to “basic”:

• Included in wages:
• Basic pay
• Dearness allowance (DA)
• Retaining allowance (if any – rare)
• Excluded (initially):
• HRA
• Incentives/bonus
• Sales commission
• Overtime
• Many allowances (travel, special allowance, etc.)
• Employer PF, gratuity, etc.

However, there’s a catch:

If the total of the excluded parts goes above 50% of total remuneration, the extra is treated as wages.

So if you keep basic tiny and bloat allowances, the law silently relabels some allowance as “wages” for PF/gratuity/overtime calculations.

2. So can I keep basic at ₹8,000?

You can only do that safely if:

• Your wages portion (basic+DA+retaining) is at least 50% of total remuneration, and 
• You still meet the applicable minimum wage for that location & skill category.

If you’re paying someone ₹40,000/month total and keeping basic at ₹8,000:

• Wages = ₹8,000
• 50% of total = ₹20,000

That fails the 50% rule. Legally, at least ₹20,000 of that monthly pay is treated as “wages” even if your payslip doesn’t say so.

So your PF/gratuity base is not 8,000 – it’s 20,000 in the eyes of the law. You get compliance risk and the same or higher cost. Worst of both worlds.

 The law actually limits allowances to 50% of total pay; in practice this means wages must be at least 50% or the extra allowance gets pulled back into wages for calculations.  

3. Common mistakes in salary structuring after the Wage Code

Mistake 1: "Basic 8k for everyone, rest as allowances"

This was the classic “PF-saving” trick. Under the new rule:

• Any structure where wages < 50% of total is non-compliant.
• The law will deem part of the allowances as wages.

You don’t save PF or gratuity – you only create confusion and risk.

Mistake 2: Thinking the 50% is on “basic vs gross salary only”

The 50% test is on all remuneration (total pay for that period), not just on your “headline salary” or some internal “gross” figure.

That means:

• Monthly incentives, performance bonuses, and commissions also get counted when checking whether excluded components exceed 50%.

Heavy incentive months can push allowances way above 50% unless your basic+DA is already strong.

Mistake 3: Ignoring minimum wage while playing with structure

Even if you pass the 50% wages rule, you can still fail minimum wage compliance if:

• The wages portion (basic+DA+retaining) is below the notified minimum wage for that State / category.

So a ₹25,000 salary with wages at ₹12,500 might still be illegal if the local minimum wage for that role is ₹14,000.

Mistake 4: Treating PF as if it must automatically be on full CTC

The 50% “wages” rule affects the base on which PF can be calculated, but PF itself still operates under its own scheme (with wage ceiling, exemption, etc.).

You should:

• Use the new “wages” definition to get a legally clean base,
• Then apply PF scheme rules (e.g., wage cap) correctly on top of that.

 To see how the 50% rule works in practice, here is a simple example for an employee with total monthly pay of ₹40,000. The only difference is how we split basic and allowances.

The total cost to the employer is the same ₹40,000 in both cases. The only change is that the new structure is easier to defend under the Wage Code, minimum wage checks and future PF/gratuity calculations.   

4. A more sensible approach than “basic 8k”

Instead of asking “Can I keep basic at 8k?”, ask:

“For this CTC, what should my wages (basic+DA) be so I:

– pass the 50% rule, and

– meet minimum wages?”

As a thumb rule:

• Keep basic+DA = 50–60% of total fixed remuneration (excluding employer PF/gratuity).
• Then split the remaining 40–50% into:
• HRA
• Fixed allowances
• Well-defined variable pay

That way:

• You’re naturally safe on the 50% rule.
• Minimum wage compliance is easier to monitor.
• PF/gratuity/overtime calculations are predictable.

5. How IndiaFilings and LEDGERS help you get this right

Instead of fighting with spreadsheets, you can split the work in two:

a) Design the structure with IndiaFilings Fractional HR

• IndiaFilings’ fractional HR team can review your existing salary formats,
• Benchmark them against the Wage Code and State minimum wages, and
• Give you 2–3 standard, compliant templates for your salary bands (25k / 50k / 1L and beyond).

You get clean, documented logic for:

• What goes into “wages-core” (basic + DA + retaining allowance),
• Which allowances and incentives are safe, and
• How to update appointment letters and HR policies to match.

Talk to Fractional HR

Talk to our IndiaFilings Fractional HR team to re-design your salary structures.

b) Implement and monitor it inside LEDGERS HRMS

Once the structure is frozen, LEDGERS HRMS handles the day-to-day maths:

• You mark each salary head as “Wages (Code)” or “Excluded (allowance/bonus)”.
• For every employee, LEDGERS automatically shows:
  • Wages % of total (e.g. 42% – risky, 53% – safe buffer), and
  • Minimum wage status for their State and category (Compliant / Underpaid).
• The system can flag:
  • Employees where wages fall below the 50% threshold,
  • Roles where wages are below the applicable State minimum wage, and
  • Structures that need HR/legal review.

So you stop obsessing about “basic 8k vs basic 15k” and start running a clean, compliant, explainable salary system – which is exactly what inspectors, auditors and investors care about.

See LEDGERS HRMS Demo

Set this up once inside LEDGERS HR & Payroll (HRMS) and let the software watch your wage-code compliance every month