示意预览Odoo module for accrual, carry-forward, encashment & multi-level leave approvals
— built, installed and supported by ECOSIRE.
什么是 Leave & Time-Off Advanced Management？
Odoo module for accrual, carry-forward, encashment & multi-level leave approvals — built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
Core Odoo Time Off handles the basics — request, approve, allocate — but real HR policies rarely fit inside it. Once you need service-tenure-based accrual, capped carry-forward with an expiry window, unused-leave encashment that flows into a payslip, or a three-tier approval chain that routes to the right manager, you hit the ceiling of what the standard hr.holidays / hr.leave models expose in the UI.
Leave & Time-Off Advanced Management is a net-new Odoo module that ECOSIRE designs, builds, installs and supports specifically for your leave rulebook. This is NOT an off-the-shelf apps.odoo.com download — after purchase our engineers scope your policies, write the module against your Odoo 17, 18 or 19 database (Community or Enterprise), and hand you a clean, upgrade-safe addon with a typical one working week lead time.
Under the hood we extend Odoo's HR stack the right way: new models (models.Model) and computed fields (@api.depends) drive accrual and balance logic; ir.model.access.csv plus record rules enforce who can see and approve what; XML/OWL views surface a self-service balance dashboard; QWeb reports produce leave statements and encashment vouchers; and automated actions (base.automation / ir.cron) handle month-end accrual runs, carry-forward roll-over and expiry. Everything integrates with hr.employee, hr.leave, hr.leave.allocation and — where you run Odoo Enterprise Payroll — with hr.payslip, so encashment lands on the right salary rule instead of a spreadsheet.
You get a documented, maintainable module scoped to how your company actually runs leave, plus configuration on your instance, admin and HR training, and a defined post-go-live support window. No fake customers, no inflated numbers — just a properly engineered Odoo addon and a team that stands behind it across Odoo 17, 18 and 19.
你得到什么
- A complete, installable Odoo addon (module source with __manifest__.py, models/, views/, security/, report/, data/) scoped to your leave policies and pinned to your Odoo major version (17, 18 or 19).
- Full configuration on your instance — leave types, accrual rules, carry-forward caps, approval tiers, public-holiday calendars and payroll salary rules set up and validated against your data.
- security/ir.model.access.csv and record rules configured for your Employee / Approver / HR Manager roles.
- QWeb report templates (leave statement + encashment voucher) styled with your company branding.
- Technical & admin documentation — how the accrual/carry-forward/encashment logic works, how to add a new leave type or approval tier, and how the scheduled jobs are configured.
- A live training session (recorded) for your HR admins and approvers, plus a written quick-start guide for self-service employees.
- A defined post-go-live support & bug-fix window with a named point of contact, covering defects in the delivered module.
- Deployment support — installation on your staging then production database, with an upgrade-safe module structure so future Odoo point releases don't break it.
这是给谁的
HR Manager with a complex policy book
Runs tenure-based accrual, multiple leave types and carry-forward caps that core Odoo Time Off can't express. Needs the rules encoded once and applied consistently every month instead of tracked in side spreadsheets.
Payroll & Compensation Lead
Owns encashment of unused leave and needs it to flow cleanly into hr.payslip via the correct salary rule, with an auditable voucher — not a manual adjustment keyed in each pay run.
HR Operations / People Ops Admin
Processes day-to-day requests and wants a multi-tier approval chain that routes to the right manager automatically, plus a self-service balance view that cuts the 'how many days do I have left?' emails.
IT / Odoo Administrator
Responsible for keeping the Odoo instance upgrade-safe. Wants a properly structured addon with clean models, access rules and scheduled jobs — not brittle Studio tweaks or unmaintained third-party code.
Leave & Time-Off Advanced Management 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Tenure-based accrual with pro-rata for joiners/leavers | Built to your exact rates and tenure steps, computed automatically each period | Possible but you design and maintain the logic yourself | Basic accrual only; tenure steps rarely configurable | 部分支持 |
| Carry-forward with cap + automatic expiry | Configurable cap and expiry window, swept unattended via ir.cron | Must build and schedule the roll-over/expiry job yourself | Sometimes a simple cap; expiry often missing | 不包括在内 |
| Leave encashment posted to payroll | Flows to the correct hr.salary.rule on the payslip, with a voucher report | Manual salary-rule wiring and reporting to build | Usually out of scope | 不包括在内 |
| Multi-level (3+ tier) approval hierarchy | Routes through your real org chart with per-tier conditions | Buildable via automations but you own the routing logic | Often single or two-step approval only | 部分支持 |
| Employee self-service balance dashboard | OWL/XML view of accrued/taken/carried/encashable, gated by record rules | Custom view and access rules to design | Varies; often read-only or limited | 部分支持 |
| Upgrade-safe, documented, maintainable addon | Clean module with __manifest__.py, docs, training and a support window | Depends entirely on your team's discipline | Third-party code you don't control or get support tailored to you | 包含 |
| Scoped to your exact policy rulebook | Yes — designed around your policies during scoping | Yes, but at your full build cost and risk | No — you bend your policy to the module | 不包括在内 |
| Delivery model | Build-to-order: built, installed & supported by ECOSIRE (2-4 wks) | In-house project you staff and manage | Instant download, self-install, generic | Already in Odoo core, no build |
关于Leave & Time-Off Advanced Management的常见问题
How long until the module is delivered and installed?
This is a build-to-order module, not an instant download. After purchase we run a short scoping call to capture your leave types, accrual rates, carry-forward and approval rules, then build, test and install the module on your Odoo instance. Typical lead time is one working week depending on policy complexity and how many approval tiers and payroll rules are involved. You'll get a schedule during scoping, and we install to staging first for your sign-off before production.
What support and updates are included after go-live?
Every build includes a defined post-go-live support window with a named contact, covering bug fixes and defects in the delivered module. We also make the addon upgrade-safe so Odoo point releases don't break it. Beyond the included window, we offer ongoing support and enhancement retainers, and we can re-target the module to a new Odoo major version (17 → 18 → 19) as a scoped upgrade when you migrate.
Which Odoo versions and editions does this work with?
We build against Odoo 17, 18 or 19 — you tell us your version and we pin the module to it. It works on both Community and Enterprise. Encashment posting directly into a payslip uses Odoo Enterprise Payroll (hr.payslip / salary rules); on Community, or where you run external payroll, we deliver the encashment value as a report/export you feed into your payroll system instead.
Will this conflict with the standard Odoo Time Off app?
No — it extends the standard HR Time Off models (hr.leave, hr.leave.allocation, hr.employee) rather than replacing them, so existing requests, calendars and reporting keep working. We add new fields, models, views, record rules and scheduled actions on top. Because it's a clean addon with its own __manifest__.py, it can be updated or uninstalled without corrupting core Odoo data.
Can it handle our specific accrual, carry-forward and encashment rules?
Yes — that's the point of a build-to-order module. During scoping we capture your exact rules (accrual frequency and tenure steps, pro-rata for joiners/leavers, carry-forward caps and expiry, encashment formula, negative-balance policy) and encode them as computed logic and configuration. If a rule is genuinely unusual we'll flag any impact on lead time before we start, so there are no surprises.
Do we need Odoo Studio or developer skills to run it day to day?
No. Once delivered, HR admins manage everything through standard Odoo configuration screens — leave types, accrual rules, approval tiers and calendars — that we set up and document. Approvers act on requests from their normal inbox/activities, and employees use the self-service balance view. No coding or Studio work is needed for daily operation; only new policy types or structural changes would call us back in.
相关模块
Leave & Time-Off Advanced Management
Odoo module for accrual, carry-forward, encashment & multi-level leave approvals — built, installed and supported by ECOSIRE.
- Configurable accrual policies — daily, monthly, quarterly or annual accrual per leave type, with rates that step up by service tenure (e.g. 1.5 days/month after 5 years), driven by computed fields with @api.depends recalculation.
- Carry-forward rules with caps and expiry — roll unused balance into the next period up to a configurable ceiling, with an optional expiry window after which carried days lapse automatically via ir.cron.
- Leave encashment to payroll — convert approved unused leave into a monetary value posted to an hr.salary.rule on the employee's hr.payslip (Odoo Enterprise Payroll), or exported for third-party payroll where Payroll isn't installed.
- Multi-level approval hierarchy — route a single hr.leave request through 2, 3 or more approval tiers (line manager → department head → HR) with per-tier conditions, so approvals follow your real org chart, not just Odoo's single Approve step.