Designation Master

Navigation Path

Company → Masters → Designation Master

1. Add Designation Page

URL

/masters/designation-master

Page Description

Displays a list of all designations configured in the system
Allows management of role hierarchy, wage configuration, and statutory applicability
Provides actions to add, edit, and delete designation records

2. Add Designation Page

Add Designation – Fields

Field Name	Type	Mandatory	Description
Unit	Dropdown (Creatable)	Yes	Select or create a unit
Designation	Dropdown	Yes	Select designation (Unit dependent)
Level	Dropdown	Yes	Select designation level
Seniority Level	Text Input	No	Enter seniority level
Amount	Number Input	No	Enter wage amount
GPA Amount	Number Input	No	Enter GPA amount
Qualification	Text Input	No	Enter required qualification
Remarks	Text Area	No	Enter remarks
Wage Type	Dropdown	Yes	Select wage type
Provident Fund Applicable	Checkbox	No	Enable PF applicability
PF Based On	Dropdown	Conditional	Basis for PF calculation
ESI Applicable	Checkbox	No	Enable ESI applicability
ESI Based On	Dropdown	Conditional	Basis for ESI calculation
Bonus Applicable	Checkbox	No	Enable bonus applicability
Bonus Based On	Dropdown	Conditional	Basis for bonus calculation

Actions

Action	Behavior
Save	Validates and saves the designation
Reset	Clears all entered values
Cancel	Returns to Designation List page

Validation Rules

Unit is mandatory
Designation is mandatory
Level and Wage Type must be selected
Conditional fields become mandatory based on statutory applicability selection

Field Definitions, Usage, and Calculation Logic

This section provides a technical analysis of the Designation Master's role in salary structuring and statutory compliance.

1. Field Definitions

Field Name	Data Type	Description	Example Value
`designationName`	String	Official designation title (Uppercase).	`SENIOR MANAGER`
`unitId`	ObjectId	Reference to the parent Unit/Location.	`60b1c...`
`amount`	Number	Base salary or CTC for the designation.	`45000`
`PFBasedOn`	Enum	Basis for EPF deduction calculation.	`Basic`
`esiBasedOn`	Enum	Basis for ESI deduction calculation.	`Asper Rule`
`bonusBasedOn`	Enum	Basis for statutory bonus eligibility.	`21000Limit`
`wageType`	String	Type of wage (Monthly/Daily/Piece).	`Monthly`

2. Field Usage & System Impact

Category	Validation / Rule	System Behavior
Compensatory	`amount`	This value serves as the default entry point for salary structure definitions.
Statutory	`PFApplicable`	If checked, the system applies the `PFBasedOn` rule during payroll cycles.
Statutory	`ESIApplicable`	If checked, the system evaluates employee earnings against the `esiBasedOn` rule.
Integrity	Unit-Centric	Designations are unique per `unitId`. Different units can have distinct configurations for the same role name.

3. Business & Calculation Logic

The Designation Master is a high-level template for employee compensation.

A. Automated Salary Head Assignment

One of the most critical background processes in the system:

Trigger: When a new designation is saved (or bulk imported), a post-save hook is triggered.
Cloning: The system fetches all active heads from the Company Head Master (CompanyHeadMaster).
Seeding: It automatically populates the Salary Head Master for this specific designation-unit combination with those heads. This ensures that every new role created automatically inherits the company's standard earnings (Basic, HRA, etc.) and deductions.

B. Statutory Basis Logic

PF Based On: Supports complex logic like SpecialBasicCondition or Manual21kLimit. These enums instruct the payroll calculation engine whether to cap the PF contribution at the statutory limit (e.g., ₹15,000) or calculate on actual basic pay.
ESI Based On: Rules like Asper Rule With Condition allow the system to automatically handle ESI eligibility as employee's gross pay fluctuates across the monthly ESI threshold.

C. Role Revision Management

The RevisedDesignation field links to a secondary master tracking historical role changes, allowing the system to maintain a career progression trail for each employee profile.

The Designation Master module interacts with the following API endpoints:

Base URL

export const DESIGNATIONMASTER_URL = '/api/salaryDesignationMaster'

Endpoints

Endpoint	Method	Description	Parameters/Body
`${DESIGNATIONMASTER_URL}`	POST	Create a new designation	Body: `data`
`${DESIGNATIONMASTER_URL}`	GET	Get all designations	Query: `page`, `limit`
`${DESIGNATIONMASTER_URL}/:designationId`	GET	Get designation by ID	Path: `designationId`
`${DESIGNATIONMASTER_URL}/unique`	GET	Get all unique designation names
`${DESIGNATIONMASTER_URL}/:designationId`	PATCH	Update an existing designation	Path: `designationId`, Body: `body`
`${DESIGNATIONMASTER_URL}/delete/:designationId`	PATCH	Delete a designation	Path: `designationId`
`${DESIGNATIONMASTER_URL}/search/designation`	GET	Search designations	Query: `query`
`${DESIGNATIONMASTER_URL}/import`	POST	Import designations	Body: `data`
`${DESIGNATIONMASTER_URL}/export/search`	GET	Search and export designations	Query: `query`
`${DESIGNATIONMASTER_URL}/import/from-export`	POST	Import designations from exported sheet	Body: `data`
`${DESIGNATIONMASTER_URL}/unique/filtered`	POST	Get unique designation names with filters	Body: `data`

RTK Query Hooks

The following hooks are available for frontend integration:

useCreateDesignationMutation
useDeleteDesignationMutation
useGetAllDesignationsQuery
useGetDesignationByIdQuery
useUpdateDesignationMutation
useSearchDesignationQuery
useLazySearchDesignationQuery
useImportDesignationsMutation
useSearchAndExportDesignationsQuery
useLazySearchAndExportDesignationsQuery
useImportDesignationsFromExportedSheetMutation
useGetAllUniqueDesignationNamesQuery
useGetUniqueDesignationNamesWithFiltersMutation

End of Documentation

Department Revised Designation