Frappe HR leave policies: what they control and when you need them
Leave rules rarely apply the same way to every employee. Permanent staff, fixed-term contractors, shift workers and employees in different countries often carry different entitlements, and the HR lead has to get those differences right before the first leave application is approved. In Frappe HR, the Leave Policy is the record that sets the annual allocation for each leave type. It does not reach employees on its own. Each employee receives the policy through a Leave Policy Assignment, so the assignment dates and the employees included in each one determine when allocations start and who is covered. Changing a policy after leave has been taken is harder to unwind than setting it correctly at the start, so treat the policy design as a decision to sign off, not a detail to fix later.
This page covers the full chain: leave types, leave policies and their assignments, earned leave accrual, holiday lists, leave approvers, and leave encashment paid through salary slips. Each part depends on the one before it. A leave type defines how a day is counted and whether it carries forward or can be encashed. The policy decides how many days each type grants per year. The holiday list determines which calendar days are excluded from leave counts, so an incorrect list shifts every balance that uses it. Approvers decide who can sign off requests, and encashment links unused balances to payroll. Before go-live, ask your implementation partner or your own Frappe HR administrator to confirm which settings in your installed version control these behaviors, and test one employee through a full leave year on a non-production site.
Which leave setup fits which employee group
A fixed allocation suits roles where every employee receives the same number of days at the start of the leave year, regardless of when they joined. In Frappe HR, a Leave Policy sets the annual allocation for each leave type, and a Leave Policy Assignment gives that policy to employees. Use this setup for statutory or contractual days that do not depend on service length during the year.
- Leave Type: Create the type with the allocation behavior you need, such as whether unused days carry forward and whether the type is paid or unpaid.
- Leave Policy: Add one row per leave type with the annual allocation amount for that group.
- Leave Policy Assignment: Assign the policy by employee, designation or department, and set the effective date to match your leave year.
- Holiday list: Attach the correct holiday list so public holidays are not deducted from balances.
- Mid-year joiners: Decide with your policy owner whether a new hire receives the full allocation or a pro-rated amount, and configure the assignment to match.
Confirm with your employment lawyer or HR authority which minimum leave entitlements apply in each country and whether carry-forward or forfeiture rules limit how you set the allocation.
Earned leave suits staff whose entitlement grows with each month or period worked, so balances build up over the year instead of arriving in one allocation. The leave type and policy must describe how the accrual is calculated, and the balance should be checked against attendance and approvals before it is used. This setup is common where local rules tie leave to time worked.
- Leave Type: Mark the type as earned leave so the system accrues days instead of granting them all at once.
- Leave Policy: Set the accrual rate and the period on which it is credited, then assign the policy to the correct employee group.
- Maximum balance: Set any cap on accumulated days so balances do not grow beyond what your policy allows.
- Unpaid or partial periods: Decide how leave without pay, probation and part-time work affect accrual, and configure the policy or assignment to reflect that decision.
- Testing: Run a sample employee through several accrual periods and compare the balance with a manual calculation before you go live.
Confirm the accrual rate, the crediting period and any balance cap against the rules that apply to each employee location, and document how your policy handles periods of absence.
Encashment applies when unused leave can be paid out, either at year end or when an employee leaves. Frappe HR lets you mark a leave type as encashable and process the payment through salary slips, so the amount reaches payroll and accounting in the same run. Design this setup carefully, because the payout amount depends on the salary used for the calculation and on the rules that apply where the employee works.
- Leave Type: Enable encashment on the leave type and set the limits that define how many days can be paid out.
- Leave Encashment: Create the encashment record for the employee, period and balance, then process it through the salary slip.
- Salary components: Confirm which salary component the encashed amount uses and whether it is taxable under your payroll setup.
- Year-end and exit: Define whether encashment runs at a fixed year-end date, at separation, or both, and align that with your full and final settlement process.
- Records: Keep the encashment calculation and approval trail, since payroll and finance will need it for audit.
Confirm with your payroll and legal advisers whether encashment is mandatory, which days are eligible, how the rate is calculated and how the payout is taxed in each jurisdiction before you configure it.
Configuration options and when each fits
This table compares the leave configuration choices in Frappe HR, from leave type flags to approvers and policy assignment dates. Read each row as a decision: what the setting controls, when it fits, and what HR or legal must confirm before go-live. Most rework comes from settings that were copied from a template without checking the local leave rules.
| Option | What it controls | When it fits | Confirm with HR or legal |
|---|---|---|---|
| Carry forward flag on leave type | Whether unused leave balance moves into the next leave period | Teams that allow balances to roll over at year end, with a cap set by policy | Maximum carried days, expiry rules and whether carried leave is paid out |
| Encashment flag on leave type | Whether unused leave can be converted to pay through salary slips | Employers whose policy or local law permits cash-out of unused leave | Eligible leave types, rate basis, and whether encashment is allowed while employed or only at exit |
| Earned leave on leave type | Accrual of leave over time instead of a single annual grant | Roles where leave is earned per month or per period worked | Accrual frequency, rounding, probation treatment and how partial periods are counted |
| Holiday list | Which dates count as non-working days when leave days are calculated | Sites or departments with different public holiday calendars | Official holiday dates for each location and whether weekly offs are included |
| Leave approver on employee | The named person who approves that employee's leave requests | Small teams or individual exceptions to the department rule | Approval authority and backup approver during absence |
| Leave approver on department | A default approver for all employees in a department | Stable reporting lines where one manager approves most requests | Who approves for managers themselves and how changes are recorded |
| Leave policy assignment by date | Which leave policy applies to an employee from a given effective date | Policy changes that should apply only to new periods, not past balances | Effective dates for revisions and how existing balances are treated |
How to set up leave policies and encashment in Frappe HR
This sequence builds leave from the calendar up, so each employee receives the right annual allocation, accrues earned leave where your policy allows it, and can convert unused days into pay through the salary slip.
Create the holiday lists
An HR administrator creates one or more Holiday List records for each year and location, adding the public holidays and weekly offs that apply to each group of employees. Leave applications skip these dates, so the list must be correct before any leave is counted. Check that a sample employee linked to the list shows the expected holidays on a test date range, and that a leave application spanning a holiday deducts only the working days.
Define the leave types
The HR administrator creates a Leave Type for each category your policy recognizes, such as annual, sick or casual leave, and sets whether it is paid, whether it can carry forward, and whether it can go negative. Leave types are the reference points for everything that follows, so names should match your handbook. Confirm the types appear in the leave type list and that a test leave application offers the expected options.
Build the leave policy
The HR administrator creates a Leave Policy and adds one row per leave type, entering the annual allocation for each. Frappe HR documents this as the place that sets the annual allocation per leave type, so the policy should reflect the entitlement in your contracts. Check the saved policy lists every leave type with the intended number of days before you assign it to anyone.
Assign the policy to employees
HR creates a Leave Policy Assignment for each employee or group, selecting the policy and an effective start date. Assignments drive the leave allocation, so a wrong effective date changes every balance that follows. Verify with one test employee that the Leave Allocation created from the assignment matches the policy, and that the leave balance shows the correct figure in the employee's record.
Set leave approvers
The HR administrator sets the leave approver on each employee record, or assigns approvers through the approver rules your organization uses, and confirms that the approver has the Leave Approver role. Approvers without the right role cannot act on applications, so this is a common cause of stuck requests. Submit a test leave application for one employee and confirm the approver receives the request and can approve or reject it.
Configure earned leave accrual
For leave types that accrue over time, HR sets the earned leave rules on the leave type, including how often days are credited and the rate per period, following your policy. Accrual runs through the scheduler, so confirm with your platform team that scheduled jobs are running in the environment. Check the result by comparing one employee's balance after a scheduled accrual run with the expected amount, and confirm the calculation with your own policy wording before rollout.
Enable leave encashment on the leave type
On the leave type, HR enables encashment and sets the rules your policy uses, such as which balances can be converted and any cap on encashable days. The Leave Encashment document then records the days converted for an employee and the period it covers. Verify by creating a test Leave Encashment for one employee and confirming the amount calculated matches the policy.
Link encashment to salary components
The payroll team maps the encashment result to a salary component, so the amount is paid through a salary slip rather than a separate entry. Confirm with the payroll owner how the component is taxed and whether it is paid in the same cycle, since those rules depend on your country and salary structure. Generate a test salary slip for the test employee and check that the encashment earning appears with the right amount and that the leave balance reduces by the converted days.
How earned leave accrues and what changes mid-year
Earned leave in Frappe HR accrues through a scheduled process, not when someone opens a form, so the first task is knowing which allocation record each employee holds and when it was created. A Leave Policy sets the annual allocation for each leave type, and a Leave Policy Assignment applies that policy to an employee. Before go-live, confirm in the Frappe HR documentation for your installed version whether an edit to a policy rewrites allocations that already exist or only affects allocations created later. The answer determines whether you can correct a policy mid-cycle without manual adjustments.
Joiners and mid-year assignment changes create the most disputes. Check whether a employee who joins after the cycle starts receives a prorated allocation, and whether accrual begins on the joining date or on the next scheduled run. When an employee moves to a different policy partway through the year, confirm how the old allocation closes and whether the new one starts from the change date. Watch for double counting, where both allocations remain active, and for balances that carry into encashment. Agree a written rule for manual adjustments and who approves them before anyone is moved.
Test with a sample employee before go-live. For example, create a test employee with a mid-year joining date, assign a policy, run the accrual job for the test period, and compare the resulting balance with the value you calculated by hand from the written policy. Then change the policy and the assignment, and check each allocation and ledger entry that follows. Repeat the test for a leaver if your process needs it. Use Frappe HR leave policy documentation as the reference for expected behavior, and confirm exact accrual timing against the version you run, since encashment payouts depend on these balances.
Paying leave encashment through salary slips
Leave encashment turns unused leave into money, and the path from request to payout touches the leave ledger, payroll and final settlement. The cards below follow that path in order, so each one shows where a decision or check belongs before the amount reaches an employee.
The Leave Encashment document
A Leave Encashment record captures the employee, the leave type, the number of days to encash and the period it applies to. It draws on the balance in the employee's leave ledger at the time of submission, so the figure should be reviewed against the current allocation rather than an older report. Confirm in your own test site whether your leave type allows encashment and what caps apply before rollout.
The salary component it posts to
Encashed days are paid through a salary component that must be mapped to the leave encashment setting, so the amount appears on the next salary slip. A missing or wrongly typed component means the amount is either not paid or paid under an unexpected earning line. Test one employee end to end and check the slip line, its account and its taxability before you run the full payroll.
Tax treatment questions
Whether encashed leave is taxable, when it is taxed and whether it falls under a special exemption depends on your country and your employment terms. Frappe HR will compute what the component is configured to do, but it does not decide the tax position for you. Ask your payroll adviser to confirm the treatment, then reflect it in the component's tax settings and in the tax slab review.
Effect on full and final settlement
When an employee leaves, unused leave may be encashed in the final pay rather than in a regular cycle. Decide whether the exit settlement should include encashment, and make sure the same leave balance is not paid twice in a regular slip and a final statement. Check the leave ledger after each run so that the balance returned to zero matches what was paid.
Approval and reversal
Encashment should pass through an approver who checks the balance and the policy before submission, because a submitted document changes the ledger and feeds payroll. If an error is found, cancel and correct the document before the salary slip is generated, since later corrections require a reversal through payroll. Record who approved each encashment so that auditors can trace it.
Frequently asked questions about Frappe HR leave setup
How much effort does a Frappe HR leave policy build take?
The effort depends on how many leave types, policies and employee groups you have, and on how many rules each one carries. A single annual allocation per leave type is a small configuration task. Earned leave accrual, carry-forward limits, holiday lists per location and encashment rules each add design decisions that must be agreed with HR and payroll before anything is built. The Frappe HR documentation describes the basic model: a Leave Policy sets the annual allocation per leave type, and a Leave Policy Assignment gives it to employees. Ask any partner for a written breakdown of leave types, policies, assignments and test cases so you can compare scopes on the same terms.
Can an internal HR admin configure leave policies without a partner?
Often yes, for simple rules. An HR administrator with clear policy documents can create leave types, holiday lists, leave policies and assignments through the Frappe HR interface. The harder part is translating written policy into consistent rules, especially for accrual on pro-rata joining dates, carry-forward, expiry and exceptions for specific employee groups. Those cases need someone who understands both the policy and how assignments are resolved, and they need testing before go-live. Most teams decide on a mix: HR owns the policy content and approval workflow, and an engineer or partner checks the configuration against test employees.
What does the leave policy work need from HR and payroll?
Leave work needs decisions from both teams before configuration starts. HR must confirm each leave type, its annual allocation, how it accrues, who approves it and what happens at year end. Payroll must confirm whether unused leave can be encashed, at which rate, which salary components form the base, and how the amount appears on the salary slip. Both teams should sign off the same written rules. Without that agreement, configuration often has to be rebuilt after the first payroll run, which is more costly than settling the rules first.
How long does testing take across different employee groups?
Testing time depends on how many distinct rule combinations exist, not on the total headcount. Each group that has a different policy, such as shift workers, joiners in the middle of a year, employees on probation, or staff in another country with different holidays, needs at least one test case covering its allocation, accrual, leave application, approval and year-end result. Plan test cases from the policy matrix, run them on a staging copy of the site, and record the expected and actual results. Ask a partner to state how many groups and test cases the quote covers.
Does leave encashment through salary slips require custom code?
Usually not. Frappe HR documents Leave Encashment as a standard feature that calculates the payable amount and carries it through payroll. Custom code becomes necessary only when your encashment rule cannot be expressed through the standard inputs, such as an unusual rate, a cap tied to a non-standard component or a jurisdiction-specific calculation. Confirm the exact rule with payroll first, then test it against the Frappe HR Leave Encashment documentation before deciding whether any script or custom app is needed. Any custom logic should be reviewed and tested like the rest of your payroll rules.
What should a quote for leave policy work include?
A quote should list the work in writing so that you can compare it with your own estimate. Ask for the leave types and policies in scope, the accrual and carry-forward rules, the holiday lists and approvers covered, the encashment rule and its salary slip treatment, the employee groups and test cases, the staging and go-live steps, and handover documentation. It should also state what you must provide, such as signed policy documents and test employee data, and what is excluded, such as later policy changes. DeployOpen plans most engagements as fixed-scope work agreed in writing before the build starts, so the written scope is the basis for the quote.
How DeployOpen scopes Frappe HR leave configuration
DeployOpen starts leave configuration by collecting the written leave rules before anyone touches a Leave Type or Leave Policy in the system. The first working sessions cover each leave category your organization offers, how annual allocations are calculated, whether unused days carry forward, which employee groups follow which rules, and who approves each request. The output is a rules register that HR and payroll sign off, because every later setting traces back to one line in it. Ask your HR lead to confirm which rules come from a union agreement, a labor law or a contract template, since those sources decide who can change a setting later.
DeployOpen then writes a fixed scope and deliverables document before build work begins. For leave, that usually names the Leave Types, the Leave Policies and the Leave Policy Assignments to be created, the earned leave accrual schedule, the Holiday Lists by location, the leave approver logic for each department, and the encashment rules that flow into salary slips. The document also states what is out of scope, such as custom reports or mobile app rollout, and what your team must provide, such as sample employee records and the payroll calendar. Most engagements of this kind are fixed-scope, so the scope document is the reference for any later disagreement about what was agreed.
Configuration is tested with your HR and payroll staff using test employees and dated scenarios: a mid-year joiner, an employee on unpaid leave, an encashment request near a payroll cutoff and a holiday falling on a weekend. Those test results go into an acceptance record that your team signs. After go-live, changes to policy values, new leave types or a change in labor rules can be handled as new scope items or through a support retainer if you want DeployOpen to stay on call. Ask any provider to confirm in writing who owns the rules register once the project closes.
