A build-to-order Odoo module that lets employees request salary advances, routes them through a configurable approval chain, and recovers the balance automatically through payslip deductions. ECOSIRE designs, builds, installs, and supports it around your policy — it is not an off-the-shelf download. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
Uygulama manifestosu
İş akışınıza göre tasarlandı
A build-to-order Odoo module that lets employees request salary advances, routes them through a configurable approval chain, and recovers the balance automatically through payslip deductions. ECOSIRE designs, builds, installs, and supports it around your policy — it is not an off-the-shelf download.
Kendiniz kurmanıza gerek yok — ECOSIRE tarafından geliştirilen, kurulan ve desteklenen çalışır bir uygulama.
Tek seferlik geliştirme fiyatıyla başlayın. Kapsamı başlangıçta sizinle birlikte belirleriz.
ECOSIRE, Odoo ortamınızda geliştirir, yapılandırır ve kurar.
Yaklaşık 2–4 haftada yayına alırsınız; lansman sonrası bir destek süresi de dahildir.
Most HR teams handle salary advances in spreadsheets, chat messages, and one-off manual payroll adjustments. An employee asks a manager for an advance, someone approves it over email, finance pays it outside the payroll run, and then a person has to remember to claw the money back across the next few payslips. Odoo's native HR and Payroll apps don't model a "salary advance" as a first-class object at all — there is no request document, no advance-specific approval flow, and no automatic recovery schedule tied to hr.payslip. The result is untracked liabilities, disputes over how much is still owed, and advances that quietly never get fully deducted.
We build a dedicated Advance Salary Management module that turns the whole process into a governed Odoo workflow. At its core is a new hr.advance.salary model (models.Model) capturing the requesting employee_id, requested amount, reason, request date, and a state machine (draft → submitted → approved → paid → recovering → closed, plus refused and cancelled) enforced through ORM write overrides rather than editable dropdowns. Eligibility guardrails are computed fields with @api.depends — a maximum advance derived from the employee's contract wage, a check that no other advance is still recovering, and a configurable minimum-tenure rule — so ineligible requests are blocked at submission instead of after payment.
Recovery is the part off-the-shelf approaches usually get wrong, so we build it properly. Each approved advance generates an installment plan (hr.advance.salary.line) — either a fixed monthly deduction or a number of installments — and the module hooks into the payslip computation so a dedicated salary rule (hr.salary.rule, category "Deduction") pulls the due installment into each run, decrements the outstanding balance, and moves the record to closed when it reaches zero. Approvals are wired through Odoo's mail.activity and mail.thread chatter for a full audit trail, with an optional multi-step approval chain (manager → HR → finance) driven by ir.rule record rules and group-based access from ir.model.access.csv. Employees see only their own requests via a self-service portal or the backend, managers see their team, and HR sees everything. Views are standard XML/OWL (list, form, and a status-grouped kanban), plus a QWeb PDF advance agreement/receipt the employee can sign. The whole record set is reachable over the XML-RPC/JSON-RPC API for integration with an external HR portal or approval bot.
Because this is built to order, delivery works from a confirmed scope, not a shopping cart. We start with a short scoping call to nail down your advance policy (limits, installment logic, approval steps, and payroll rule placement), confirm your Odoo version (17.0, 18.0, or 19.0) and whether you run Community or Enterprise payroll, then build, test on a staging copy of your database, and deploy with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company advance policies, deeper localization of the deduction rule, custom approval hierarchies, and migration of historical advance data increase the quoted scope.
Owns the advance policy and needs every request documented, approved on-record, and recovered without manual tracking. Wants eligibility rules enforced by the system so exceptions are deliberate, not accidental.
Runs the monthly payslips and is tired of hand-adding deduction lines and reconciling who still owes what. Needs the outstanding installment to flow into each run automatically and the balance to close itself out.
Treats outstanding advances as a real liability and wants an auditable trail from request to full recovery, with an optional finance approval step and a signed agreement per advance.
Maintains the Odoo instance and wants a clean, upgrade-friendly module with proper access rules and a git handover, not a black-box customization that breaks on the next version bump.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Advance request as a tracked document | Dedicated `hr.advance.salary` model with enforced states and audit trail | Possible, but you design and maintain the model yourself | Provides a request object, but fixed to its own workflow assumptions | |
| Automatic payslip recovery | Deduction salary rule pulls installments into each run and auto-closes at zero | Must be built and tested against your payroll config from scratch | Often present, but recovery logic may not match your installment rules | |
| Eligibility & policy guardrails | Computed limits (wage %, tenure, one-active-advance) enforced at submission | Whatever you have time to specify and code | Basic limits, rarely configurable to your exact policy | |
| Approval chain | Configurable multi-step (manager → HR → finance) via groups and record rules | Fully bespoke, at bespoke cost and timeline | Usually single or fixed approval step | |
| Fit to your process | Built to your confirmed scope after a scoping call | Fully tailored, but you own architecture, testing, and risk | Take-it-as-shipped; you adapt your process to the app | |
| Version & edition targeting | Built and tested for your 17.0/18.0/19.0, Community or Enterprise | Depends on your developer's coverage | Version support varies; edition wiring may not match yours | |
| Support & handover | Post-go-live support window, docs, training, and git repo handover | Whatever your contractor agrees to | Vendor-dependent tickets; source access varies | |
| Total cost profile | From $249 indicative; fixed quote after scoping | Typically higher — full bespoke build and QA | Low upfront, but customization and misfit costs add up |
No. This is a build-to-order module. ECOSIRE designs, builds, installs, and supports it around your specific advance policy and Odoo version — there is no instant download. After a scoping call we implement your requirements, test on staging, and deploy.
Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on the complexity of your approval chain, installment logic, and whether historical advance data needs migrating. We confirm dates during the scoping call before any work starts.
Pricing starts from $249 (indicative, single-company base scope). After a short scoping call we send a fixed quote. Drivers that increase scope include multi-company advance policies, custom approval hierarchies, deeper localization of the deduction rule, and migration of existing advance records.
We build for Odoo 17.0, 18.0, or 19.0 — we target the version you run. The automatic payslip recovery relies on the Payroll app; we wire the deduction to whichever payroll setup you have and confirm Community vs Enterprise details during scoping.
Each approved advance creates an installment plan and a dedicated deduction salary rule pulls the due installment into every payslip run, decrementing the outstanding balance until it reaches zero and the record auto-closes. You choose a fixed monthly amount or a set number of installments.
Every build includes a post-go-live support window for defect fixes and configuration tweaks. Because we hand over the git repository and full documentation, you own the code. We also offer ongoing support and version-upgrade engagements separately if you want us to maintain it long-term.
Yes. We can expose submission through a self-service portal or the backend, scoped by security groups so employees only see their own requests. Approvals route through your configured chain (manager → HR → finance) with a full chatter audit trail on each record.
A build-to-order Odoo module that lets employees request salary advances, routes them through a configurable approval chain, and recovers the balance automatically through payslip deductions. ECOSIRE designs, builds, installs, and supports it around your policy — it is not an off-the-shelf download.