Product features

Salary structures

Build reusable pay templates from earnings and deductions, assign them to teachers and staff, and keep a history of every change.

Last updated: 2026-09-09

What this feature does

A salary structure is a reusable pay template. Instead of typing the same figures for every employee each month, you define the structure once—basic pay, allowances, deductions—and assign it to the teachers and staff it applies to.

Salary structures are part of the Payroll module, available on eligible center plans. Open Payroll → Salary structures in the dashboard.

What a structure is made of

A structure has a name and one or more components. Each component is either:

  • An earning (basic pay, house rent allowance, travel allowance) or a deduction
  • Calculated as a fixed amount in rupees, or as a percentage

The base component

Percentage components need something to be a percentage of. You mark one fixed-amount earning as the base using the "Percentage components are a percentage of this" tick box—usually basic pay. Only one component can be the base.

  • If your structure has no percentage components, you do not need a base at all.
  • If it does have percentages but no base is marked, the structure will not save, and the message tells you to mark one. This is deliberate: without a base, those percentages would silently calculate to zero.

Structures created before the tick box existed still work—Edunza recognises a component named "Basic", "Basic Pay" or "Basic Salary" as the base automatically.

Rules a structure must follow

The same checks run in your browser and on the server, so a mistake is highlighted on the offending field rather than failing after you press Save.

  • The structure needs a name and at least one component
  • Component names must be unique within the structure
  • Values must be numbers and cannot be negative
  • A percentage cannot exceed 100
  • A blank value is reported as missing, not saved as zero

Change history

Every structure carries a version number plus who created it, who last changed it, and when. Each edit archives the previous definition and moves the version on, so you can see what a structure looked like before someone changed it.

Payslips are unaffected by later edits. Each payslip stores a snapshot of the structure it was generated from, including its version, so a payslip from six months ago still shows the figures that were actually used—even if the structure has since been edited or deleted.

Assigning a structure to an employee

A structure is assigned on the employee's own record, not from the structure screen. Edit a staff member or teacher and pick from the Salary Structure dropdown.

  • Once at least one structure exists, choosing one is required
  • Selecting a structure hides the free-form salary fields, because the structure replaces them

Deleting a structure

Deletion asks for confirmation, and Edunza refuses to delete a structure that is still in use—the message names the employees still assigned to it, for example "still used by Asha, Ravi and 3 others". Reassign those employees first.

Good to know

  • Values are rounded to two decimal places when saved, so totals reconcile.
  • If two administrators edit the same structure at the same moment, the edits are applied one after the other so neither loses its history entry.
  • Only center administrators can see or edit salary structures. Staff employees cannot, even by direct link.

Related articles

Related articles