Offboarding
Separation, clearance and exit interviews handled end to end.
Offboarding is where a leaver's last weeks are handled properly: the exit record, clearance, the exit interview, the final settlement and the approvals that sign each step off. Everything lives in one Employee Separation workspace with a tab for each stage, so HR is never reconstructing a departure from emails and spreadsheets after the person has already gone.
It starts with a single exit record. HR raises an Employee Exit for the chosen employee with one of eight exit types — Resignation, Termination, Retirement, End Of Contract, Absconding, Dismissal, Death or Others — alongside the resignation date, the last working date, a mandatory reason, and flags for whether clearance, an exit interview and automatic inactivation after settlement apply. Those flags then drive the rest of the workflow: the Clearance and Exit Interview tabs show exactly the leavers whose exits asked for them.
The final settlement is not a number typed into a box. Nexa People computes it from the same records payroll runs on — the employee's salary setup, encashable leave balances, approved loans and advances, and tenure between joining and leaving dates — and presents it as an itemised breakdown of earnings and deductions you can preview before committing anything. Because the figures come from live records rather than a side calculation, the last payment is as auditable as every one before it.
Access is controlled form by form. Each tab of the module — Employee Exit, Final Settlement, Employee Clearance, Exit Interview, Approvals and Settings — is gated by its own permission in the role template, and the server enforces the same keys: running a settlement requires the Final Settlement add permission, and employees have no settlement surface at all. HR administrators run separation; approvers sign off each step.
How Offboarding works
Raise the exit, set the flags
The Add Employee Exit form captures the whole departure in one screen: pick the employee from a code-prefixed list, choose the exit type, record the resignation date and the leaving date, and write the reason — employee, exit type, leaving date and reason are all required before the form will submit. Four Yes/No switches are stored on the record, and three of them drive what happens next: IsClearance places the leaver in the clearance queue, Exit Interview puts them in the interview tab, and Inactivate Employee After Fnf triggers automatic inactivation once the settlement runs. Restrict User On Login is recorded on the exit alongside them.
The Employee Exit list then shows every exit with the employee's station, department and group, the exit type and both dates, tick marks for the clearance, interview and inactivation flags, and a status badge. Each row's action menu offers View — a full detail dialog — Delete with a confirmation prompt, and Download, which exports that record as a CSV of every captured field.
Preview the settlement before you commit it
Run F.Settlement is deliberately a two-step screen. Select the employee, optionally a leaving date and a monthly or weekly payslip period, and press Preview: the server computes the full settlement and returns it read-only, persisting nothing. If no leaving date is given, it uses the one from the employee's latest exit record.
The preview shows the employee's code, joining date, monthly gross, leaving date and tenure, the net total, and an itemised Settlement Breakdown — each earning and deduction with the working behind it, such as days worked over days in the month, or encashable days times the per-day rate — followed by total earnings, total deductions and the net settlement. Only when you press Run F.Settlement is the result saved as a Final Settlement request that appears in the Final Settlement tab and the approvals queue.
What the settlement is made of
Every line is derived from records elsewhere in the platform. Earned salary pro-rates the final month's gross by days worked; the monthly figure is resolved from the employee's salary setup — basic plus allowance lines, each applied by its own calculation rule — with a fallback to the latest payroll record where no setup exists. Leave encashment multiplies the balance of encashment-enabled leave types by a per-day rate, and gratuity is computed from monthly basic and tenure in years, applied only when your gratuity policy is on and the tenure meets your configured minimum.
On the deductions side, outstanding balances from approved loan and advance requests are recovered, and — where you enable it — negative leave balances are recovered at the per-day rate. The breakdown also carries a notice-period line item, noting your configured notice days on the settlement. Totals for earnings and deductions net off to the final Total Salary carried on the request.
Clearance and exit interviews, driven by the exit record
The Employee Clearance tab lists exactly the leavers whose exit was flagged for clearance — the filter is applied on the server, not in the browser — with each person's placement details, exit type, leaving date and clearance tick. Search by employee, name or employee code, or narrow by station, department, sub-department or group.
Exit Interview works the same way for leavers flagged for an interview, showing interview status alongside the exit details, with an interview-date filter for scheduling. Settings lets you maintain named clearance templates, questionnaire categories and exit interview templates as reusable lists.
One approvals queue for the whole module
E. Separation Approvals gathers exit and settlement requests in a single filterable list, each row showing the employee, payslip period, exit type, leaving date, request title, status and total salary. Pending requests carry an Approve/Reject action; decided ones show their outcome. Approval chains come from the same engine used across Nexa People, resolving each level's approver from your configuration, and a settlement approval toggle in organisation settings controls whether a Final Settlement needs sign-off at all.
When a settlement runs for an exit flagged Inactivate Employee After Fnf, the employee is automatically marked In-Active — status updated and login disabled — so they drop out of the active employee list the moment their settlement is done.
Module settings your policies can lean on
E. Separation Settings holds the configuration in four tabs. General Setting groups toggles into three accordions — Final Settlement (approval required, auto run on exit, disburse with payroll), Gratuity & Notice Period (implement gratuity policy, minimum years from one to five, notice period days) and Clearance Setting (mandatory clearance, approval required) — all saved to your organisation's configuration. The gratuity policy and minimum-years settings feed straight into the settlement computation. The remaining tabs manage the clearance, questionnaire and interview template lists.
Features
Eight exit types, one record
Resignation, Termination, Retirement, End Of Contract, Absconding, Dismissal, Death and Others, each with resignation and leaving dates, a mandatory reason and workflow flags. The record is the single source the clearance, interview and settlement tabs all read from.
Settlement preview with nothing persisted
Preview computes the full settlement server-side and returns it read-only — nothing is saved until you press Run. HR can check the numbers, adjust the leaving date or payslip period and preview again before anything reaches the approvals queue.
An itemised, explainable breakdown
Every settlement line carries its working: days worked over days in the month for earned salary, encashable days times the per-day rate, tenure times basic for gratuity. Earnings and deductions are totalled separately before netting off, so an approver can see exactly how the figure was built.
Figures from live records, not re-entry
Monthly gross and basic come from the employee's salary setup with its allowance calculation rules, falling back to payroll history; encashment reads leave balances; loan recovery reads approved loan and advance requests. There is no second copy of the data to drift.
Configurable gratuity treatment
Switch the gratuity policy on or off and set the minimum qualifying years; the settlement computes gratuity from monthly basic and tenure only when both conditions are met, and shows 'Not applicable' on the line when they are not.
Server-side filtering on every tab
Station, department, sub-department, employee group, employee, exit type, year, month and status on the exit list; name and code search on clearance and interviews; payslip period and disbursement filters on settlements. Filtering and pagination happen on the server, so lists stay correct at any size.
Clearance and interview queues that build themselves
Flag an exit for clearance or an interview and the leaver appears in the matching tab automatically — no separate data entry. Named clearance templates, questionnaire categories and exit interview templates are maintained in settings.
Automatic inactivation after settlement
When an exit is flagged Inactivate Employee After Fnf, running the final settlement marks the employee In-Active and disables their login in the same action, so nobody has to remember a second step after the money side is done.
Record-level export and control
Any exit record can be downloaded as a CSV of its captured fields, viewed in a full detail dialog or deleted behind a confirmation prompt. Lists page at 10, 25 or 50 records with a running count of matches.
Used by: HR administrators run separation; approvers sign off each step.
Works with the rest of Nexa People
Offboarding reads and writes the same employee record as everything else. Leavers are picked from the Employee Management directory, exit rows carry the station, department and group held there, and when a flagged settlement runs, the module writes back — the employee is marked In-Active and their login disabled, moving them into the same In-Active pool the directory manages. The stations, departments, sub-departments and groups in every filter come from the Organization module.
The settlement computation is built on Payroll and Leave data: monthly gross and basic are resolved from the payroll salary setup and its calculation rules, with the latest payroll record as fallback; encashment reads encashment-enabled leave balances; and approved loan and advance requests from payroll self-service are recovered as deductions. Approvals run through the shared request engine, with the settlement sign-off toggle living alongside the other payroll approval settings.
Downstream, Reports & Analytics includes Separations and Resignation Detail reports, an Exit Interview report, a Final Settlement report and a gratuity report that applies the same formula and policy gate as the settlement itself, while the dashboard's headcount and retention timeline counts exits by each leaver's leaving date.
Frequently asked questions
What does an exit record capture?
The employee, one of eight exit types, the resignation date and last working date, a mandatory reason, and four flags: whether clearance applies, whether an exit interview applies, whether the employee should be inactivated after their final settlement, and a restrict-on-login flag. The record also carries the person's code, station, department and group for the list views and CSV download.
How is the final settlement calculated?
From your own records. Earned salary pro-rates the final month's gross by days worked; leave encashment multiplies encashment-enabled leave balances by a per-day rate; gratuity applies monthly basic times tenure in years, subject to your policy toggle and minimum-years setting; and approved loan and advance balances are deducted, along with negative leave balances where you enable that recovery. Earnings and deductions are totalled and netted to a single settlement figure.
Can we check the numbers before anything is saved?
Yes. Preview computes the entire settlement on the server and returns it read-only — the breakdown, per-line workings and totals — without persisting anything. Only pressing Run F.Settlement creates the settlement request that appears in the Final Settlement tab and the approvals queue.
What happens to the employee once the settlement runs?
If their exit was flagged Inactivate Employee After Fnf, running the settlement automatically marks them In-Active and disables their login, removing them from the active employee list. The exit and settlement records remain, with their statuses and full detail, for as long as you need them.
How do clearance and exit interviews work?
They are driven by the exit record's flags. Leavers flagged for clearance appear in the Employee Clearance tab and those flagged for an interview in the Exit Interview tab — filtered on the server, searchable by name, code and placement, with an interview-date filter for scheduling. Settings maintains reusable clearance templates, questionnaire categories and exit interview templates.
Who can run settlements and approve separations?
Every tab is gated by its own form permission in the role template, so you decide who sees Employee Exit, Final Settlement, Clearance, Exit Interview, Approvals and Settings. The server enforces the same rules: running a settlement requires the Final Settlement add permission, settlement endpoints refuse employee-role logins outright, and pending requests are approved or rejected from the approvals queue.
What can we configure about the module's behaviour?
E. Separation Settings records your separation policy in three accordions — final settlement (approval required, auto run on exit, disburse with payroll), gratuity and notice period (policy on or off, minimum years, notice days) and clearance (mandatory, approval required) — saved against your organisation as recorded preferences. The gratuity policy, minimum-years and notice-days settings feed the settlement computation directly; the toggle that actually controls whether a Final Settlement needs sign-off is the settlement toggle among the payroll approval settings, resolved by the shared approvals engine.
Related modules
See Offboarding in your own setup
We'll walk you through the modules you care about and email you login credentials to try it yourself.