Why Frappe HR onboarding and full and final settlement need one designed process
Joiners and leavers handled through email threads and spreadsheets produce the same failures every quarter: a laptop never collected, a mailbox left open, leave balances that nobody checked, and a final payment that becomes a dispute. Frappe HR onboarding templates address the first half of this problem by turning standard hiring activities into tasks per new hire, such as background checks, creating the employee and email account, and allocating leave. The value comes from making these tasks identical for every joiner and assigning each one to a named owner, so HR, IT and the hiring manager see the same open list. Confirm which tasks your organization actually needs, who signs off each one, and whether a task blocks the next step or only reminds someone.
The leaver side should start from the same employee record. A separation record, an exit interview and the leaver's offboarding tasks all hang off that employee, so the full and final statement can be checked against the same dates, leave balances and asset returns that the team recorded during exit. Decide before go-live which items count as dues (unpaid salary, leave encashment, notice pay, loans, advances and expense claims) and which count as assets that must be returned, and who may release the settlement when an item is still open. Ambiguous ownership of these decisions is the usual cause of late or disputed final pay.
Build this as a designed process rather than a set of manual reminders when you have multiple entities or countries, when leavers hold company equipment or system access, or when final pay rules differ by employment type. The payroll mechanics of the settlement, salary components, tax treatment and bank payout are covered on the sibling payroll pages, so this section only sets up the process that feeds them. Ask your implementation partner to show how each template task and separation step is recorded, and ask your legal and payroll leads to sign off the settlement rules before the templates are configured.
Which onboarding and separation setup fits your organization
A single template suits organizations with a small number of job families or a uniform onboarding path. In Frappe HR, an Employee Onboarding template lists the standard hiring activities as tasks, such as background checks, creating the employee and email account, and allocating leave, and each new hire receives a copy of those tasks. The template is quick to build and easy for HR to audit because every joiner passes through the same checklist.
- What it tracks: the same set of activities for every new hire, with due dates set relative to the joining date.
- Who owns each task: typically HR owns paperwork and background checks, IT owns the email account, and the reporting manager owns the first-week plan. Confirm these owners in your own process before building the template.
- Maintenance cost: low at first, but a single template tends to accumulate tasks that only apply to some roles, which slows every joiner down.
- Where it breaks: engineering, finance and field roles usually need different system access and equipment, so a shared list either over-assigns or gets ignored.
- What to check: whether a generic checklist can cover your access provisioning without manual follow-up for each hire.
Confirm which tasks are truly universal before you commit to this option.
Role or department templates give each job family its own checklist. Finance joiners might need ERPNext accounting access and approval limits, while warehouse joiners need stock and device setup. Each template is attached to new hires in that group, so the tasks match what the person actually needs on day one.
- What it tracks: activities specific to a department or designation, such as system roles, equipment and mandatory training.
- Who owns each task: department heads often own role-specific tasks, with IT and HR owning shared steps. Record the owner on each task so nothing falls to a default user.
- Maintenance cost: higher, because each template needs review whenever a role's tools, policies or reporting lines change. Ask who will own that review and how often it happens.
- Where it breaks: templates drift when a department reorganizes but nobody updates the checklist, leaving stale tasks behind.
- What to check: how many distinct templates you will run and whether each one has a named owner.
Illustrative example: a company with five job families might start with three templates and add more only when a group's onboarding repeatedly needs manual additions.
Some organizations handle leavers through a short separation record: the last working day, the reason for leaving and the owner of the exit. This keeps the employee record accurate and triggers the payroll run for the final period, without a formal interview or multi-department clearance. It suits smaller teams or organizations with low turnover and few company assets.
- What it tracks: the separation date, the reason, and the status of the final salary calculation.
- Who owns each task: HR typically owns the separation record, and payroll owns the final pay. Confirm that both teams receive the same date.
- Maintenance cost: minimal, since the process has few steps to update.
- Where it breaks: access revocation and asset return depend on people remembering to act, which creates risk when staff leave quickly or in bulk.
- What to check: whether a missed asset return or system account can still surface before the final settlement is paid.
This setup is lighter, but it leaves the settlement dependent on informal follow-up.
A formal separation setup adds an exit interview and a clearance checklist that each department signs off before the full and final statement is released. Clearance covers system access, equipment, advances, expense claims and any loans, so that dues and assets are settled in one place. This suits regulated organizations, organizations with significant assets or organizations that must document leaver controls for audit.
- What it tracks: the exit interview outcome, each department's clearance, asset return and open financial balances.
- Who owns each task: IT owns access removal and equipment return, finance owns advances and claims, HR owns the interview and the statement, and the line manager confirms handover.
- Maintenance cost: the highest of the four options, because clearance owners, asset categories and approval routes all need periodic review.
- Where it breaks: clearance stalls when one department does not respond, so set a clear escalation owner and a fallback rule.
- What to check: whether your settlement process can hold payment until every clearance item is closed, and who may waive an item.
Confirm the exact clearance steps with your HR, finance and IT leads, and check your own control requirements with your auditors.
How to set up onboarding templates and separation in Frappe HR
This sequence sets up standard joiner and leaver workflows in Frappe HR so every new hire gets the same tasks and every leaver clears dues and assets before final pay is released. Each step ends with a check you can run in the system before moving on.
Define task owners and departments
Before building any template, agree with HR, IT, facilities, finance and the line manager who owns each recurring task, such as creating the employee record, provisioning the email account, issuing equipment or allocating leave. Record these as the departments and users who will act on the tasks, and confirm that each owner has a system user with the right role in Frappe HR. Check: every task on your written list has one named owner who can log in and see the tasks assigned to them.
Create onboarding templates with tasks
In Frappe HR, create an Employee Onboarding Template and add one row per standard hiring activity, such as background checks, creating the employee and email account, and allocating leave. Set each task's assignee role or user and its description so the owner knows exactly what to complete. Check: open the template and confirm every task from your list appears with an owner, and that no task is left without one.
Link templates to designations
Attach each template to the designations it applies to, so that when an onboarding is started for a new hire the correct checklist is pre-filled. Keep a shared template for common tasks and add role-specific tasks only where a designation needs them, such as device issue for field roles. Check: create a test onboarding for one designation and confirm it loads the expected template and no tasks from unrelated templates.
Configure separation and exit interview records
Set up the separation workflow by creating an Employee Separation template with the tasks that must close before an exit, such as handover, access removal and asset return, and by preparing the exit interview questions your HR team uses. Confirm the separation record links to the employee and to the relevant exit interview. Check: start a test separation and confirm the tasks and exit interview are created and visible on the employee's separation record.
Define asset and dues checks
Work with finance and IT to list what a leaver must return or settle, including company devices, access cards, outstanding advances, expense claims and loan balances. Map each item to a task owner in the separation template, and agree which items must close before the full and final statement is finalized. Confirm the checklist with finance in writing. Check: every asset or dues item on the list has a task, and finance can name the accounts or documents that show each balance.
Test the full joiner and leaver cycle
Run one sample joiner (illustrative example: a test employee in a test designation) through onboarding, confirming tasks appear on the new hire record and close as owners complete them. Then run a sample leaver through separation and confirm that the full and final settlement stays unpaid while any asset or dues task is open, and becomes payable only after those checks close. Check: the leaver's settlement is blocked while checks are open and releases once they all close, and the test records are cleaned up or kept in a test site.
What a full and final statement must settle and where it reaches payroll
A full and final statement is the closing calculation for a leaver: it totals everything the company owes the employee and everything the employee owes the company, then nets the two. In Frappe HR the usual items are final salary for the days worked, leave encashment for unused balances, notice pay or the adjustment for notice not served, and any gratuity or other end-of-service amount your policy defines. Deductions typically cover unreturned assets, outstanding advances, and expense claims paid in excess. Each item should map to a salary component (earning or deduction) so it appears on a salary slip rather than in a side spreadsheet. Confirm with your HR team which items they settle through payroll and which through a separate entry, and keep that decision the same for every leaver.
On the ERPNext side, the settlement creates accounting effects that should be checked before anyone signs off. Earnings and deductions post to payroll payable and salary accounts, leave encashment goes through the leave encashment flow, and open advances and expense balances are cleared against the employee's payable or receivable ledger. Asset recovery is the item most often missed, so decide early whether an unreturned asset becomes a deduction, a receivable or a hold on the final payment, and make sure the asset record in ERPNext reflects that status at exit. Ask your implementer to show you the journal entries generated by a test leaver before go-live.
Statutory treatment is not something this page can settle. Final pay timing, leave encashment rules, gratuity, notice pay and tax withholding depend on the employee's jurisdiction and on your contracts. Confirm each rule with your payroll or legal advisor before you configure the components and formulas. The payroll pages in this group cover the calculation details, including salary components, tax slabs and running payroll, so use them to build the statement once the rules are agreed.
What goes wrong in joiner and leaver processes
Joiner and leaver work fails in predictable places: tasks slip, access lingers, assets go untracked, and final dues are calculated from stale balances. Each card below names a failure and the control that prevents it in Frappe HR, so the checks can be written into the process before the first exit.
Onboarding tasks missed for new hires
Onboarding templates only help when every new hire gets the same task list and each task has an owner. A template with background checks, employee record creation, email account setup and leave allocation can still be skipped if no one is assigned or if tasks are created by hand after the start date. Check that the template is attached to every hiring path, that each task has a responsible user, and that the HR lead reviews open tasks before day one.
Access not removed on exit
A separation record in Frappe HR does not disconnect systems on its own. Accounts in ERPNext, email, directory login and any connected application can remain active after the last working day. The control is a separation checklist that names each system, the person who revokes access, and the date it was done, reviewed before the final settlement is released.
Assets not recorded against employees
Laptops, phones, access cards and tools issued to an employee are often tracked in a spreadsheet or in the IT system, not against the person. At exit, nobody can confirm what must come back, so the final statement misses deductions or the asset is never recovered. Record each issue against the employee when it is handed over, and make asset return a separation task that must be closed before settlement.
Dues calculated from stale balances
A full and final statement uses leave balances, expense claims and employee advances as they stand on the calculation date. If leave is approved after the statement is drafted, or an advance repayment is posted late, the amount paid is wrong. Recalculate the statement from current records immediately before approval, and confirm that leave allocations, claims and advances are submitted and not left in draft.
Exit interviews not linked to the record
Exit interview notes kept in email or a separate document cannot be traced back to the separation, so reasons for leaving are lost and the leaver file looks incomplete. Link the interview to the employee's separation record in Frappe HR, record the owner and date, and restrict who can read the notes. Review the themes periodically rather than reading each one in isolation.
Templates drifting from practice
Onboarding and separation templates are written once and then diverge as teams add exceptions in chat or skip steps under pressure. Over time the template no longer matches what happens, and auditors or new HR staff cannot tell which version applies. Assign a template owner, review the task list against actual cases each quarter, and record changes with a date and reason.
Questions buyers ask before setting up Frappe HR onboarding and exits
What drives the cost of setting up Frappe HR onboarding and exits?
The main cost driver is how many distinct joiner and leaver paths the business runs, because each path needs its own onboarding template, task owners, and settlement rules. Cost rises with the number of departments, locations, contract types and countries that have different steps, and with the number of systems the tasks must touch, such as email, directory accounts, laptops and access badges. Setup is usually a one-time cost for design and configuration, while changes to policies, new asset types and upgrades recur over time. When you request a quote, ask for the written scope to list each template, each task type, each integration and each handover you expect DeployOpen to build, test and document, since that list is what the price follows from.
How long does a Frappe HR onboarding and exit build take?
Duration depends on scope, not on a single fixed number. A build that covers one standard joiner template and one leaver template with a simple asset return list is much shorter than one that adds country-specific full and final rules, directory deprovisioning, approval chains and reporting. The biggest timing factors are how quickly HR can confirm policy decisions, how many leave and gratuity rules need configuration first, and whether the test environment matches the production Frappe HR version. Ask for a timeline in the written scope that separates design sign-off, build, test with real HR cases, and go-live, so each dependency on your team is visible.
What must HR and IT provide before configuration starts?
HR and IT must supply the decisions and reference data that the templates encode. Typical inputs are:
- A role list per department and designation, with the equipment and access each role receives
- An asset register with item types, serial numbers and current holders, so returns can be checked at exit
- Leave policies, holiday lists and leave encashment rules that the settlement will read
- Notice period rules, dues categories and approval owners for each settlement step
Missing or inconsistent data here is the most common cause of rework, because templates copy whatever is entered. Confirm who owns each input and when it will be frozen.
Can an internal HR team set up onboarding templates without a partner?
Yes, a capable internal team can configure standard onboarding templates and tasks in Frappe HR, because the core workflow is documented and does not require custom code. The Frappe HR employee onboarding documentation describes templates that track hiring activities such as background checks, creating the employee and email account, and allocating leave, as tasks for each new hire. Work becomes harder when you need custom task logic, integrations with directory or ticketing systems, or settlement calculations that depend on local labour rules. Decide early which parts your team will maintain, and whether a partner is needed for the integration or for review before go-live.
How does access removal at exit connect to directory systems?
Frappe HR can track the exit tasks, but removing access in Active Directory, LDAP or a single sign-on provider is a separate integration. ERPNext supports LDAP login with group-to-role mapping at each login, so a user removed from the directory group may lose ERPNext roles at their next login, but this must be tested against your own directory design. Disabling the account in the identity provider, revoking tokens and removing application grants require the identity system to be part of the exit process. Confirm with your identity team whether deprovisioning is triggered by the Frappe HR exit record or by a separate workflow, and who signs off that access is gone.
Which Frappe HR version should we confirm before we design the workflow?
Confirm the exact ERPNext and Frappe HR version in use, and whether it is on a supported line, before designing anything. According to Frappe's supported versions page, ERPNext and Frappe Framework version 14 reached end of life on January 31, 2026, version 15 is planned to be supported until the end of 2027, and version 16 until the end of 2029. Your template fields, settlement doctypes and patch levels depend on the version, and upgrades can change them. Also confirm that your support arrangement matches the version, since Frappe's supported versions policy ties warranty coverage to a listed version and a matching Frappe Cloud support plan.
Do server scripts or custom code change how exit settlements work?
They can, and you should decide that before the build. Server Scripts run Python on document events, and according to the Frappe Framework documentation, starting from version 15 they are disabled by default and must be enabled with the server_script_enabled setting. Frappe Cloud public shared benches do not allow them, so a settlement rule that depends on a script may force a different hosting choice. Custom logic also needs review on each upgrade. Ask whether the settlement can be built from standard fields and documented rules, and which logic must live in a custom app that your team can version and test.
Access, data and audit controls for leaver records
Separation and settlement records hold salary, dues, asset and personal data, so access has to be designed before the first leaver is processed. The cards below cover who can see and close records, how changes are traced, how long exit data is kept, and how account removal in your identity provider stays in step with the HR record.
Role-based access to separation data
Exit records, exit interview notes and settlement amounts should sit behind separate roles from general employee data. Decide which HR, payroll and finance users can read the Employee Separation and Full and Final Statement documents, and which managers only see their own team's tasks. Test each role with a dummy leaver before go-live, since a user with broad read rights can see settlement figures for people they never manage.
Restricting who closes a settlement
Closing a full and final statement should need a different person from the one who prepared it. Map the submit and cancel permissions to a named finance or payroll role, and confirm which users can edit dues after submission. Check the approval path in writing with your own HR and finance leads, because the default permission set depends on the roles your site already uses.
Audit trails on changes to dues
Every change to a leave encashment, unpaid notice amount, advance balance or asset recovery line should be traceable to a user and a time. Confirm that version history is enabled on the documents involved and that your team reviews it before a statement is paid. Export or archive the trail on a schedule if your audit team needs it outside the application.
Retention of personal exit data
Exit interview answers, reasons for leaving and background details are personal data that many jurisdictions require you to limit in time. Agree a retention period with your legal or data protection lead, then decide how and when records are anonymized or deleted, including backups. Ask whether your site's backup policy can delete individual records within that period.
Login mapping and leaver access
If ERPNext signs users in through LDAP or social login, group and role mapping runs at each login, so a change in the directory can grant or remove access to leaver data. Check which directory groups map to HR and finance roles, and confirm what happens to a former employee's active sessions and linked accounts when their directory account is disabled.
Deprovisioning and custom leaver logic
Account removal in your identity provider should follow the separation date recorded in Frappe HR, not a manual reminder. If you need custom checks at separation, such as blocking exit until assets are returned, a Server Script can do it, but server scripts are disabled by default from version 15 and must be enabled with the server_script_enabled setting. Document that change and keep the logic under version control.
How the scope of a joiner and leaver build is agreed
DeployOpen agrees the scope of a joiner and leaver build in writing before work starts. The written scope names each onboarding template and the tasks it creates for a new hire, such as account creation, leave allocation and any background check steps your HR team runs outside ERPNext. It also names the separation workflow, the exit interview questions, the structure of the full and final statement and the accounts it posts to, the integrations in scope (for example, directory accounts or asset registers), and the test cases that prove each path works. Ask for each item to be listed by name, with the owner on your side who signs off the design. A scope that says only "HR onboarding and offboarding" leaves the hardest decisions unassigned.
Two questions should be settled during scoping rather than during testing. The first is which system is the source of truth for employment dates and status, because the separation workflow and the final settlement both depend on it. The second is which dues and assets the settlement must cover, including unrecovered advances, leave encashment, gratuity, asset returns and any recoveries under your own policies. Confirm with your finance and legal teams how each one is calculated and approved. Where a statutory or tax rule applies, confirm it with your payroll adviser or the relevant authority, since DeployOpen configures the process but does not decide the rule.
Once the build is live, changes such as a new onboarding task, an extra clearance step or a revised statement layout are common. DeployOpen can run these under a retainer, which covers ongoing support, upgrades and change work within an agreed arrangement, so each change does not need a new project. Ask for the retainer terms in writing, including how change requests are logged, tested and approved, and how upgrades to ERPNext and Frappe HR are scheduled and tested against your custom templates and scripts before they reach production.
What your team provides and what you receive at handover
This sequence sets out what your HR, finance, IT and asset owners must supply before configuration starts, and what you hold once Frappe HR runs joiners, leavers and full and final settlements without manual workarounds. Each step ends with a check you can review before sign-off.
Supply role, department and designation lists
Your HR lead provides the current lists of departments, designations, branches and the roles that hold them, along with the reporting lines that approvers depend on. DeployOpen maps these into Frappe HR masters so onboarding templates and separation workflows attach to the right population. You confirm the sign-off when the sample employee records in each department resolve to the expected approvers and no master is missing or duplicated.
Name owners for each onboarding task
Your team assigns a named owner for every task in the onboarding template, such as background verification, creating the employee record and email account, IT equipment issue and leave allocation. Owners are recorded as the people or roles responsible for completing each task in Frappe HR. The handover check is a written owner list that covers every task with no task left unassigned.
Define asset categories and settlement policy
Finance and HR agree the asset categories that must be returned on exit, such as laptops, access cards and tools, and the policy rules for final pay, leave encashment, notice recovery, advances and loan balances. These rules become the components and deduction logic in the full and final statement. The output is a signed policy note that DeployOpen translates into configuration, and you verify it against your current written policy.
Provide sample joiner and leaver cases
You supply a set of realistic sample cases, including a standard joiner, a resignation with notice recovery, a termination, a retirement and an employee with outstanding advances and unused leave. These are used as test scenarios, and they are the most useful input for surfacing policy gaps before go-live. The check is that each sample case has an agreed expected outcome written down by your HR and finance owners.
Configure templates, workflows and test records
DeployOpen configures the onboarding templates, separation records, exit interview forms and full and final statement setup in your environment, then loads test employees using your sample cases. Your reviewers run each case and compare the generated tasks, asset returns and settlement amounts against the expected outcomes. Handover begins when every test case matches its agreed result or a logged change has been accepted.
Receive the HR administrator runbook
You receive a runbook for HR administrators covering how to start an onboarding, assign and close tasks, record an exit, run the exit interview, generate and review a full and final statement, and handle common exceptions such as reversed resignations. It also explains which steps need finance approval and where the audit trail for each settlement is kept. You confirm acceptance when a nominated administrator completes a test walkthrough without assistance from the implementation team.
Adopt the documented change process
DeployOpen hands over a written change process for updates to templates, components, asset categories and settlement rules, including who requests changes, who approves them and how they are tested on a copy before they reach production. This keeps later policy changes from silently altering past statements. The check is an agreed change log and approval list signed by your HR and finance owners.
How DeployOpen delivers Frappe HR onboarding and exit processes
DeployOpen plans, implements and supports self-hosted open-source platforms in your own infrastructure, and that includes Frappe HR onboarding templates, separation workflows, exit interview forms and full and final settlement components inside an ERPNext site you operate. DeployOpen is a Chainscore Labs company. The work is delivered in your cloud accounts, data centers or air-gapped network, so employee records, salary components and settlement data stay under your control. Before build starts, the written scope should name the onboarding task templates, the separation checklist, the settlement components that tie to your accounts in ERPNext, the roles that can view and approve exit data, and the asset return items that gate final pay.
Most engagements are fixed-scope. Scope, deliverables, acceptance checks and timelines are agreed in writing before work starts, so you can compare a quote against your own team's effort. Ask the partner to list what is one-time work, such as template design, data mapping, testing with sample leavers and handover documentation, and what recurs, such as adjusting templates when policy or statutory rules change. Confirm who validates statutory calculations for each country where you employ people. DeployOpen prepares the configuration and evidence for your compliance reviews, but independent auditors and certification bodies issue any audit reports or attestations.
Ongoing support, upgrades and testing are available as a retainer, which suits teams that change onboarding or payroll rules during the year. Before you sign, confirm which ERPNext and Frappe HR versions the support covers, how upgrades are tested against your leaver and settlement scenarios, and who owns the site after handover. Ask for the runbook, the list of custom scripts and their owners, and a restore test for the database. Those items decide whether your joiner and leaver process keeps working after the project team leaves.
