In most growing Nepali businesses, salary is negotiated individually at each hire. The result is a patchwork of packages where two employees doing similar work at the same level earn significantly different amounts, not because one is higher performing but because one negotiated harder or joined in a year when the business was more cash-constrained. This is the core problem that a defined salary structure Nepal businesses need to solve.
An undocumented salary structure creates visible and invisible costs. When employees compare notes - and they do - unexplained pay differences damage trust and drive turnover. When management wants to review compensation, they are looking at individual negotiations rather than a structured grid, making fair adjustment nearly impossible. When a senior employee leaves and the role is reposted, no one is sure what the position should pay.
A structured salary grade system addresses all of these. It defines what each level in the organization pays, what components make up that package, and how salary moves when an employee is promoted or due for an increment. It also provides the foundation for calculating festival bonuses, gratuity, and SSF contributions correctly, because all of these derive from the salary structure.
Why a Defined Salary Structure Matters for Growing Organizations
The moment an organization reaches 20-25 employees, the informal approach to compensation starts creating friction. There are enough people in similar roles to make comparison inevitable, and enough variation in negotiated packages to produce inequities that are difficult to explain. At 50 employees, the problem scales: HR is managing dozens of individual compensation agreements, each with its own logic, and any organization-wide adjustment requires case-by-case review.
A salary structure replaces individual negotiation with defined bands. Each grade has a minimum, midpoint, and maximum. New hires are placed at a point within the band based on their experience level relative to the role. Increments move employees within the band or across bands based on performance ratings and time in grade. The parameters are set by management once and applied consistently by HR without judgment calls at each individual review.
The second benefit is compensation cost predictability. When finance wants to model the payroll cost of a planned headcount increase, a structured salary grade makes the calculation straightforward. The new roles fit into defined grades with known band ranges, and the total compensation cost can be estimated before the hires are made. Without a structure, every headcount addition requires a new negotiation whose cost cannot be predicted in advance.
A salary structure is not a constraint on flexibility - it is a foundation for fair, consistent, and defensible compensation decisions. Organizations that build the structure early find it easier to scale than those that try to impose structure after hundreds of individual packages have already been negotiated.
Component-Based Salary Structure in Nepal
Nepal's compensation landscape uses a component-based approach where the total package is divided into several distinct elements. Each component serves a different purpose in the employee's total cost of employment and has different implications for SSF calculation, festival bonus, and income tax.
Nepal salary packages typically include: basic salary (the core, used as the SSF contribution base), house rent allowance (commonly 30% of basic or a fixed amount), transport allowance, medical allowance, and sometimes telephone or fuel allowance. Festival bonus under Labour Act 2074 is calculated based on basic salary - organizations paying one month's basic as Dashain bonus use this component directly. Gratuity accumulates as a percentage of basic salary. Income tax applies to total taxable income including most allowances. Structuring components correctly affects both compliance calculations and the total tax burden for employees.
Below is a sample 4-grade salary structure with component breakdown relevant to a Nepali organization (illustrative figures in NPR per month):
| Component | Grade I (Entry) | Grade II (Junior) | Grade III (Mid) | Grade IV (Senior) |
|---|---|---|---|---|
| Basic Salary | 20,000 | 32,000 | 52,000 | 85,000 |
| House Rent (30% of Basic) | 6,000 | 9,600 | 15,600 | 25,500 |
| Transport Allowance | 2,500 | 3,000 | 4,000 | 5,500 |
| Medical Allowance | 1,500 | 2,000 | 3,000 | 4,500 |
| Total Monthly CTC | 30,000 | 46,600 | 74,600 | 1,20,500 |
| Dashain Bonus (1 month basic) | 20,000 | 32,000 | 52,000 | 85,000 |
| SSF Employer Contribution (20% of basic) | 4,000 | 6,400 | 10,400 | 17,000 |
These figures are illustrative. The actual band ranges depend on the organization's industry, location, and competitive market. The structure's value is not in the specific numbers but in the fact that the numbers are defined, documented, and applied consistently rather than negotiated fresh for each hire.
Nepal's component-based salary structure is not just a payslip format - it is the foundation for SSF calculation, festival bonus, gratuity, and income tax. Getting the component definitions right at the structure level prevents cascading errors in every downstream compliance calculation.
Linking Salary Grades to Job Levels and Performance Ratings
A salary grade structure only works if the grades mean something. The grades need to be mapped to the organization's job levels - what roles belong in Grade II, what distinguishes a Grade II role from a Grade III role, and what is the pathway from one grade to the next. Without these definitions, the structure becomes another layer of administration that HR manages rather than a tool that guides decisions.
The midpoint of each salary band is the reference point. Employees joining at full qualification for the role start near the midpoint. Employees joining with limited experience start below the midpoint. Employees who have been in the role for several years and are consistently high-performing reach the band maximum and become candidates for the next grade. Tracking where each employee sits within their band - as a percentage of the midpoint - gives HR a quick view of who is underpaid relative to their performance and who is approaching the ceiling of their current grade.
Performance ratings connect directly to the increment system. An organization might define that Exceptional performers receive a 15% increment, Exceeds Expectations receives 10%, Meets Expectations receives 7%, and lower ratings receive minimal or no increment. The increment percentages apply to basic salary, which then recalculates all the percentage-based components automatically. The salary structure and the performance appraisal system need to be in the same platform so the increment calculation happens from the rating data without manual entry.
Linking salary grades to defined job levels and performance ratings converts the salary structure from a static policy document into a dynamic management tool. HR can run a report showing which employees are at what point in their band and cross-reference it with performance ratings to identify who is due for an increment review.
Managing Multiple Salary Structures in One Organization
Many Nepali organizations have operational complexity that a single salary structure does not fully address. A construction company may have different grade structures for site staff, office staff, and project managers. A retail chain with Kathmandu and province locations may need different transport and house rent allowance amounts per location while keeping basic salary grades consistent. An NGO with donor-funded projects may need to segregate payroll for project staff from the core organizational structure.
Managing multiple salary structures manually - in different spreadsheets, applied by different HR managers, with different update cycles - produces the same inconsistencies that the structure was meant to eliminate. The organization ends up with an undocumented patchwork again, just with more formal-looking spreadsheets.
The right approach keeps the grade structure centralized while allowing parameters to vary by department, branch, or project. Basic salary grades remain consistent across the organization. Allowance amounts can differ by location. One update to the core grade structure propagates correctly across all departments rather than requiring each HR officer to update their own copy.
Multiple salary structures within one organization are legitimate and necessary - the key is that they are managed in one system rather than maintained as separate spreadsheets. Centralized structure management prevents the structural inconsistency from returning through the back door of distributed HR administration.
Salary negotiated individually at each hire - no consistent structure or documented bands
Defined pay grades with min-midpoint-max bands applied consistently across all hires
Components defined differently for each employee - no standard breakdown structure
Component templates per grade - basic, house rent, transport, medical configured once and applied
Festival bonus calculated manually from payslips with errors for new joiners and part-year staff
Bonus calculated from basic salary in the system - prorated automatically for partial-year employees
Increment decided informally without reference to performance rating or band position
Increment percentage pulled from performance rating, applied to basic, recalculates all components
Multiple salary spreadsheets per department - structures diverge through independent updates
Centralized salary structure with location-specific allowance variants - one update propagates everywhere
Frequently Asked Questions
Start with market data for roles in your industry and location. In Nepal, salary surveys from professional associations, job boards like Merojob, and peer organizations in the same sector give benchmark ranges for common roles. The band minimum should be the entry point for an inexperienced but qualified hire. The midpoint should be where a fully competent employee with typical experience sits. The maximum should represent the ceiling for excellent performance in the role before promotion is more appropriate than further increment. Bands typically overlap slightly between grades so that a high performer at Grade II can earn more than a new entrant at Grade III.
Both approaches are used in Nepal. A percentage of basic (commonly 30%) keeps the house rent allowance proportional to the grade and adjusts automatically when basic salary changes. A fixed amount simplifies payroll for lower-grade staff where the percentage produces a very small number. Many organizations use percentage-of-basic for mid-level and senior grades and a fixed floor amount for entry-level roles. Either approach works as long as it is consistently applied across the same grade. The income tax treatment of house rent allowance should be confirmed with the organization's tax advisor.
Most Nepali organizations review their salary structures annually, typically in Baisakh or Jestha before the new fiscal year starts. The review checks whether the bands are still competitive with market rates, whether the performance increment percentages are sustainable given the business's financial position, and whether any roles have been reclassified or restructured. Annual revision is practical because it ties the structure update to the budget cycle and prevents ad-hoc adjustments throughout the year that create inconsistency.
Configurable Salary Grades With Component Templates and Increment Automation
MISAC's salary structure module lets administrators define pay grades, component templates, and band ranges directly in the ERP without developer involvement. Each grade has configurable component types - fixed amounts, percentage-of-basic formulas, or conditional allowances per branch or department. When a new employee is assigned to a grade, the component structure applies immediately. When basic salary changes on increment, every percentage-based component recalculates automatically across the payslip, SSF contribution, and festival bonus calculation.
Nepal's compliance requirements are built into the structure. SSF contribution rates, festival bonus calculation basis, and income tax brackets are pre-configured and update when regulations change through a simple administrator setting rather than a formula rewrite. The component definitions respect the distinction between basic salary (SSF basis) and allowances (different tax treatment) so the structure produces the correct compliance output from the first payroll run.
MISAC Intelligence Pvt. Ltd. has helped organizations across Nepal's trading, manufacturing, and service sectors build salary structures that match their headcount complexity - from a 30-person office with one grade structure to a 400-person construction company with separate structures for site labour, office staff, and management. The team at mis.ac can walk through the grade setup for your organization's specific structure.
Ready to See MISAC in Action?
Replace your individual salary negotiations with a structured grade system that links pay to performance and calculates all compliance deductions correctly from the first payroll run.