Salary Structure Done Right: Bands, Components and the CTC Breakup

Ask why two people doing the same job earn very different salaries and the honest answer is usually that one negotiated harder, or was hired in a tight market, or joined when budgets were looser. None of these is a reason — they are accidents of history that have hardened into unfairness. This is what happens when a company sets salaries one person at a time instead of designing a salary structure: pay drifts, inconsistencies accumulate, and eventually someone compares notes and the whole thing becomes a morale problem.

A salary structure is the system that prevents this. It is not a spreadsheet of what everyone earns; it is a framework of bands and components that decides how pay is set for any role, so that two people in the same band are paid consistently and every number can be explained. Getting it right is partly a fairness exercise and — this is the part Indian businesses cannot skip — partly a statutory one, because how a salary is split determines PF, gratuity, tax and several compliance outcomes.

Bands and grades: consistency by design

The foundation is a set of salary bands (or grades) — ranges of pay attached to levels of responsibility rather than to individuals. A band has a minimum, a midpoint and a maximum, and every role maps to a band. When you hire or promote into a band, the offer sits within that range; when you give an increment, it moves the person through the band. The effect is that pay for similar work stays within a known range instead of being reinvented in every negotiation.

• Each band has a floor and ceiling, so no single hire quietly sets a new, unbudgeted precedent.
• New offers and increments are checked against the band, which makes them defensible and consistent.
• Bands make pay-equity review possible — you can actually see whether similar roles are paid similarly.

The CTC breakup is not cosmetic

In India, the total cost-to-company is only half the story; how it is broken up into components carries real consequences. A typical structure splits CTC into basic pay, House Rent Allowance (HRA), various allowances, the employer's PF contribution, and often a special allowance that balances the rest. Each component behaves differently for tax and statutory purposes, so two offers with the same CTC can leave employees with very different take-home pay and very different PF and gratuity accruals.

Why basic pay is the number that matters most

Basic pay is the load-bearing component of the whole structure. Provident Fund is calculated on it, gratuity is calculated on it, and several other statutory figures flow from it. This creates a temptation that gets many companies into trouble: setting basic artificially low (and inflating allowances) to reduce PF and gratuity liability. Beyond a point this is not just aggressive — it invites scrutiny, because regulators expect basic to be a realistic proportion of total pay, and a suspiciously low basic can be challenged.

The defensible approach is to keep basic at a sensible share of CTC, apply it consistently across the structure, and let the statutory contributions follow honestly. A structure built to minimise every liability at the edges is fragile; one built on a realistic basic is stable and stands up to an audit.

Statutory floors are the non-negotiable baseline

Underneath the whole structure sits a hard floor: statutory minimum wages, which vary by state and by skill category. No salary — however it is packaged — can fall below the applicable minimum wage for that role and location. For most white-collar roles this floor is far below actual pay and never binds, but for entry-level and blue-collar roles it is the binding constraint, and a structure that ignores it is non-compliant regardless of how neatly its components are arranged. A salary structure has to be built on top of the minimum-wage master, not alongside it.

Templates turn the design into daily practice

A salary structure only delivers its benefits if it is actually applied every time, and that is where salary templates and components come in. Instead of building each employee's pay by hand, you define the components once and apply a template per band, so a new hire's salary is composed correctly and consistently by default. This is also what connects the structure to payroll: the same components that define the structure are the ones the pay run computes, so there is no translation step where errors creep in.

A salary structure is ultimately a promise that pay is decided by role and rules rather than by who negotiated hardest. It makes hiring and increments defensible, keeps PF, gratuity and tax honest, and holds the whole thing above the statutory floor. The companies that struggle with pay are usually the ones setting it one person at a time; the ones that don't have decided, once, how compensation works — and then apply that decision every single time.