Illustrative previewA build-to-order Frappe app that extends ERPNext leave management with rule-based accrual,
carry-forward and encashment, multi-country holiday calendars, team conflict checks and delegated approvers.
ECOSIRE scopes, builds, installs and supports it for you — it is not an instant marketplace download.
What is Leave Management Pro for ERPNext?
A build-to-order Frappe app that extends ERPNext leave management with rule-based accrual, carry-forward and encashment, multi-country holiday calendars, team conflict checks and delegated approvers. ECOSIRE scopes, builds, installs and supports it for you — it is not an instant marketplace download. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your ERPNext.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
Technical Specifications
- ERPNext Compatibility
- —
- License
- Licence confirmation required
- Python Requirement
- Python 3.10+
- Database
- MariaDB 10.6+
About this Product
Multi-region HR teams outgrow ERPNext native leave management quickly. Core Leave Policy, Leave Allocation and Leave Type DocTypes handle straightforward annual allotments well, but the moment your rules involve tenure-based accrual tiers, pro-rated joining/exit balances, capped carry-forward with expiry windows, or region-specific statutory leave, you end up patching gaps with spreadsheets and manual allocation entries. The native Holiday List is also single-calendar per assignment, which is painful when one company runs teams across the UAE, India, the Philippines and the UK, each with its own public holidays and weekend definitions.
Leave Management Pro is a proper Frappe app (its own module, DocTypes, hooks.py and fixtures) that layers advanced policy logic on top of ERPNext's existing leave engine rather than replacing it — so your Leave Application, Leave Ledger Entry and payroll integration keep working the way your team already knows. We model your accrual and carry-forward rules as configurable records (for example an Accrual Rule DocType with tenure bands, monthly/annual frequency, proration method and rounding), then enforce them through scheduler events for automated accrual and through doc_events hooks (validate, on_submit) on Leave Application and Leave Allocation. Carry-forward runs as a scheduled job that respects per-policy caps and expiry, writing standard Leave Ledger Entry rows so balances reconcile against ERPNext's own reports.
Encashment is wired to payroll: an encashment request DocType feeds a Salary Component into the employee's Salary Slip / Payroll Entry, using server-side calculation so the amount is auditable and never hand-keyed. Multi-country support lets you attach the correct Holiday List per employee group, branch or region and validate applications against it — so a Friday-Saturday weekend team and a Saturday-Sunday weekend team compute working days correctly on the same instance. A team leave calendar with conflict checks warns approvers when too many people in a department overlap, and a delegation/approver-hierarchy layer routes requests to backups when a manager is on leave, backed by ERPNext role profiles and permission rules so people only see what they should.
Everything is exposed cleanly: whitelisted methods and the standard Frappe REST API let your portal, mobile app or Slack/Teams bot read balances and submit requests programmatically, and client scripts add the in-form UX (live balance preview, conflict warnings) on the Desk. The app is built and tested against Frappe/ERPNext v15 and v16.
Because this is build-to-order, nothing ships until we understand your exact rules. We start with a short scoping call, produce a written scope and leave-policy matrix for your sign-off, then build on a staging bench that mirrors your version. You get UAT on that staging site, a rollback plan, and only after your acceptance do we install to production. Typical delivery is one working week from confirmed scope depending on how many regions and policy variations you need. You receive the full source in a Git repository, so you are never locked to us.
What you get
- Installable source code for your version of the app as a proper Frappe app (module, DocTypes, fixtures, `hooks.py`), built for Frappe/ERPNext v15 or v16
- Installation and configuration on your bench, including scheduler-event setup, holiday-list assignment and policy configuration
- Technical documentation: DocType reference, server-script/hook behaviour, whitelisted API method list and scheduler job schedule
- End-user and HR-admin guide plus one live training session for your team
- Post-go-live support window for defect fixes and configuration questions
- UAT on a staging bench that mirrors your ERPNext version, with a documented rollback plan before production install
- Git repository handover with full commit history so you own and can extend the code
- A signed-off leave-policy and accrual matrix documenting exactly what was built
Who this is for
Group HR Manager, multi-country operations
Runs one ERPNext instance across several countries and needs each region's statutory leave, holiday calendar and weekend definition enforced correctly without maintaining parallel spreadsheets.
HRIS / ERPNext Administrator
Owns the ERPNext deployment and wants complex accrual and carry-forward logic implemented as clean, maintainable DocTypes and hooks — with source in Git — rather than brittle manual allocations.
Payroll Lead
Needs leave encashment to flow into `Salary Slip`/`Payroll Entry` as an auditable Salary Component, and final-settlement leave balances calculated automatically at exit.
People Operations / Line Managers
Want a team leave calendar with conflict and coverage checks, and delegated approvals so requests are never stuck when a manager is away.
How Leave Management Pro for ERPNext Compares
| Criterion | ECOSIRE | Custom Build | Competitor | ERPNext Native |
|---|---|---|---|---|
| Fit to your leave rules | Built to your exact accrual, carry-forward and regional policies | Fully bespoke but you specify and manage every detail | Generic feature set; you bend rules to fit the app | Basic policies only; complex rules need manual workarounds |
| Multi-country holiday calendars | Per-region `Holiday List` assignment with correct weekends | Possible if you scope and build it yourself | Usually single-calendar assumptions | One holiday list per assignment; awkward across regions |
| Encashment to payroll | Auditable Salary Component into `Salary Slip`/`Payroll Entry` | Depends on your build effort | Often manual or absent | Limited; frequently hand-keyed |
| Delivery model | Scoped, staged UAT, rollback plan, then production install | Your team plans and runs the whole project | Self-install, no scoping of your rules | Already in ERPNext; you configure it yourself |
| Code ownership | Full source handed over in your Git repo | You own it, but you built and must maintain it | Often closed or licensed, limited access | Core code; not customisable without forking |
| Time to live | Typically one working week from confirmed scope | Months, plus hiring and project overhead | Fast install, slow to fit real rules | Immediate, but only for simple cases |
| Support & updates | Post-go-live support window; upgrades quoted after | You staff and fund all support | Vendor support varies; no rule-specific help | Community/self-support only |
| API & integration | Whitelisted methods + Frappe REST for portals and bots | Whatever you choose to expose | Limited or undocumented endpoints | Standard REST, but no advanced leave logic to call |
Frequently Asked Questions about Leave Management Pro
Is this an instant download from the Frappe marketplace?
No. Leave Management Pro is build-to-order. ECOSIRE scopes your exact leave rules, builds the app against your ERPNext version, tests it on a staging bench and installs it for you. There is no instant self-service download — you get code tailored to your policies plus support.
How long does delivery take?
Typically one working week from confirmed scope. The timeline depends on how many regions, accrual variations and integrations you need. After a short scoping call we send a written scope and policy matrix; the clock starts once you sign that off.
Which ERPNext versions do you support, and how do updates work?
We build and test against Frappe/ERPNext v15 and v16. You receive the source in a Git repository, so your team can maintain it. During the post-go-live support window we fix defects and answer configuration questions; version upgrades or new feature work beyond that window are quoted separately.
Will this break our existing ERPNext leave data or payroll?
No. The app layers on top of ERPNext's native leave engine — it writes standard `Leave Ledger Entry` rows and feeds payroll through Salary Components, so your existing `Leave Application`, balance reports and `Payroll Entry` continue to work. We validate everything on a staging copy and keep a rollback plan before touching production.
Can it handle different holiday calendars and weekends per country?
Yes. You assign the correct `Holiday List` per branch, department or employee group. Working-day and weekend calculations respect each employee's regional calendar, so a Friday-Saturday weekend team and a Saturday-Sunday weekend team compute leave correctly on the same instance.
Can our other systems read balances or submit leave requests?
Yes. The app exposes whitelisted methods and uses the standard Frappe REST API, so your employee portal, mobile app or a Slack/Teams bot can read balances and submit or approve requests programmatically.
Do we own the code?
Yes. You receive the full source with commit history in a Git repository you control. You are not locked to ECOSIRE and can extend or maintain the app with any Frappe developer.
Related Modules
KSA GOSI & Mudad Payroll Compliance
A build-to-order ERPNext app that adds Saudi payroll compliance — GOSI dual-rate contributions, Mudad WPS file generation, and end-of-service benefit calculation — natively into your Salary Slip and Payroll Entry flow. ECOSIRE builds, installs, and supports it after we agree on your scope.
KSA ZATCA E-Invoicing for POS (Fatoora Phase 2)
A build-to-order ERPNext app that makes your point of sale issue ZATCA Phase-2 compliant simplified tax invoices — cryptographically stamped, TLV QR-coded, and reported to Fatoora in real time. ECOSIRE builds, installs, and supports it for Saudi retailers and restaurants.
LinkedIn & Indeed Job Sync for ERPNext
A build-to-order Frappe app that pushes ERPNext Job Openings to LinkedIn and Indeed, then pulls applicants back into your ATS with source attribution and duplicate detection. ECOSIRE scopes, builds, installs, and supports it for you.
LinkedIn Lead Gen Forms Connector for ERPNext
A build-to-order ERPNext app that captures LinkedIn Lead Gen Form submissions in real time, enriches them with company and title data, and routes them into your ERPNext CRM as attributed, auto-assigned Leads. Designed, built, and supported by ECOSIRE after a scoping call.
Leave Management Pro
A build-to-order Frappe app that extends ERPNext leave management with rule-based accrual, carry-forward and encashment, multi-country holiday calendars, team conflict checks and delegated approvers. ECOSIRE scopes, builds, installs and supports it for you — it is not an instant marketplace download.
- Configurable `Accrual Rule` DocType: tenure bands, monthly vs annual accrual frequency, proration for mid-period joiners/leavers, and rounding policy per `Leave Type`
- Automated accrual via Frappe scheduler events that post standard `Leave Ledger Entry` rows so native balance reports stay authoritative
- Carry-forward engine with per-policy caps, expiry windows and year-end cutover run as an idempotent scheduled job
- Pro-rated allocation on joining and final-settlement clawback on exit, computed server-side from `Employee` date_of_joining/relieving_date