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.