Every range in this guide is wide. That is not imprecision. A band of 35 to 55 lakh describes real variation in what the job actually involves, and the difference between the two ends is usually scope rather than seniority.
This section sets out the seven things that decide where a role sits inside its band. They apply across every industry section, and they are worth working through before a search begins rather than after the first offer is declined.
Entity structure
Reporting framework
Audit complexity
Team size
Systems
Build or maintain
Ownership
Most roles sit at the top on two or three of these and at the bottom on the rest.
Working through it
Entity structure is the fastest filter. Consolidating four entities across two currencies is a different skill from closing one. It also narrows the pool sharply, which is why roles requiring genuine multi-entity consolidation sit at the top of their band and take longer to fill. Ask how many entities a candidate has actually consolidated, not how many the group had.
Build versus maintain is the biggest single swing. A Controller joining an established function with a working close is a different hire, at a different price, from one who has to create it. This is the distinction job descriptions almost never make, and the one that most often explains why a search is failing.
Ownership is what separates two identical CVs. Two candidates with the same title and the same years can differ entirely on whether their work was reviewed before it left the building. The question worth asking is simple: what did you sign off, and who checked it?
Read next
Put a Number on Your Role
The ranges are the starting point. Tell us the scope — entities, framework, build or maintain — and we will tell you what the role should actually pay.