- Home
- Apps
- SaaS Tools
- Philippines Payroll (SSS, PhilHealth, Pag-IBIG)
Illustrative previewBuild-to-order Odoo payroll for the Philippines:
SSS, PhilHealth, Pag-IBIG, BIR tax and 13th-month pay.
What is Philippines Payroll (SSS, PhilHealth, Pag-IBIG)?
Build-to-order Odoo payroll for the Philippines: SSS, PhilHealth, Pag-IBIG, BIR tax and 13th-month pay. Built to order by ECOSIRE for Odoo 17, 18, 19 — 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 Odoo.
- 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
- Odoo Compatibility
- Odoo 17, Odoo 18, Odoo 19
- Editions
- Enterprise & Community
- License
- Licence confirmation required
- Python Requirement
- Python 3.10+
- Database
- PostgreSQL 12+
About this Product
Odoo's HR Payroll app ships with a generic salary-rule engine but no Philippine statutory localization — so PH companies end up maintaining SSS, PhilHealth, Pag-IBIG and BIR figures in spreadsheets and hand-keying every semi-monthly run. This ECOSIRE build-to-order module closes that gap. We design, build, install and support a purpose-built Philippines payroll localization on top of Odoo's native hr.payroll framework, tailored to your pay cycle, cost centers and reporting needs.
This is not an instant apps.odoo.com download. After purchase, our Odoo engineers scope your requirements, build the module against your Odoo version (17, 18 or 19 — Community or Enterprise), and deliver a tested, documented, production-ready localization in a typical one working week lead time.
Under the hood the module extends Odoo's salary structure with Philippine-specific salary rules and a set of custom models (models.Model) that hold the SSS, PhilHealth and Pag-IBIG contribution schedules as maintainable, versioned data rather than hardcoded numbers. Contribution and withholding computations are implemented as stored, compute-based fields (@api.depends) so payslip amounts recalculate deterministically and stay auditable. Access is locked down with ir.model.access.csv plus record rules so payroll officers see payroll data and line managers do not. Statutory outputs — SSS R-3/R-5-style schedules, PhilHealth remittance lists, Pag-IBIG (HDMF) contribution reports, BIR alphalist inputs and BIR Form 2316 employee certificates — are produced as QWeb PDF/Excel reports mapped to the government layouts you actually file.
Semi-monthly BIR withholding tax is calculated against the current TRAIN-law compensation tax table, with cumulative reconciliation so the December run trues up each employee's annual tax. Thirteenth-month pay is automated as a dedicated payslip run that aggregates basic salary earned across the calendar year and applies the correct non-taxable threshold. Where you need it, we wire automated actions and scheduled runs (server actions / ir.cron) so contribution registers, payslip batches and remittance reminders fire on schedule, and we expose the payroll data over Odoo's XML-RPC/JSON-RPC API for your reporting stack or government e-filing bridges.
Because it is built as a proper Odoo module (a versioned __manifest__.py, models, security, views in XML/OWL and QWeb reports), it upgrades cleanly, respects Odoo's multi-company and multi-currency, and remains fully yours — no per-employee SaaS lock-in.
What you get
- The complete, installable Odoo module (source code) built for your target version — 17, 18 or 19, Community or Enterprise — with a clean __manifest__.py, models, security files, views and QWeb reports
- Configured Philippine salary structure, salary rules and statutory contribution tables (SSS, PhilHealth, Pag-IBIG, BIR) loaded with the schedules current at delivery
- Installation and deployment on your Odoo instance (or a staging build you approve before production cutover), including a smoke-tested end-to-end payslip run
- Administrator and payroll-officer documentation: how to run a semi-monthly batch, generate 13th-month pay, update contribution tables, and produce each statutory report
- A live training session (recorded) for your HR/payroll team covering the full monthly and year-end cycle
- A post-go-live support and bug-fix window (two weeks, extendable) covering defects and statutory-figure adjustments
- Source repository access plus a short maintenance guide so your team or ECOSIRE can update rates when SSS/PhilHealth/Pag-IBIG/BIR revise them
Who this is for
HR / Payroll Manager at a Philippine SME
Runs semi-monthly payroll for 20–300 employees and is tired of maintaining SSS, PhilHealth, Pag-IBIG and BIR figures in spreadsheets. Wants Odoo to compute statutory deductions and 13th-month pay automatically and produce filing-ready remittance reports.
Finance / Operations Head at a BPO or shared-services firm
Manages a large, shift-based workforce with night differential and overtime. Needs accurate, auditable per-cutoff withholding tax, clean cost-center allocation into Odoo Accounting, and reliable year-end BIR annualization and 2316 issuance.
Odoo partner or in-house Odoo admin
Already runs Odoo for a PH client and needs a maintainable, properly-architected payroll localization rather than a brittle collection of hardcoded salary rules — with real models, security rules and QWeb reports they can extend.
How Philippines Payroll (SSS, PhilHealth, Pag-IBIG) Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Philippine statutory coverage (SSS, PhilHealth, Pag-IBIG, BIR) | Complete and built-in, tuned to your setup | Only what you scope and build yourself | Varies; often partial or one agency only | Not included |
| Editable, versioned contribution tables (no hardcoding) | Yes — stored as Odoo models you can update | Depends on your build discipline | Often hardcoded in salary rules | Not included |
| Semi-monthly BIR withholding + year-end annualization | Yes, with December true-up | Buildable but complex to get right | Rarely includes annualization | Not included |
| 13th-month pay automation | Dedicated run with non-taxable threshold | Manual rule work | Sometimes | Partial support |
| Statutory QWeb reports (SSS/PhilHealth/Pag-IBIG, alphalist, 2316) | Mapped to government layouts | You design every report | Limited or generic | Not included |
| Role-scoped security (ir.model.access.csv + record rules) | Designed for payroll confidentiality | Your responsibility | Varies by vendor | Partial support |
| Odoo 17/18/19, Community & Enterprise | Built for your exact version | Whatever you target | Often version-locked | Partial support |
| Delivery, installation, training & support | ECOSIRE builds, installs, trains and supports | Self-managed | Download only; support optional/paid | Not included |
Frequently Asked Questions about Philippines Payroll
This is build-to-order — how long until it is delivered and live?
Yes, this is a build-to-order module, not an instant apps.odoo.com download. After purchase we scope your pay cycle, cost structure and reporting needs, then build, test and install the module against your Odoo version. Typical lead time is one working week depending on scope (for example, custom bank-file formats or e-filing bridges add time). You approve a staging build before we cut over to production.
What support and updates do I get after go-live?
Every build includes a post-go-live support window (two weeks, extendable) covering defect fixes and adjustments to statutory figures discovered during that period. Because SSS, PhilHealth, Pag-IBIG and BIR periodically revise their rates and tables, we architect the contribution schedules as editable data models — your team can update most rates without code. For rate changes, new report layouts or Odoo version upgrades beyond the window, we offer an ongoing maintenance/retainer option.
Which Odoo versions and editions does it support?
We build for Odoo 17, 18 and 19, on both Community and Enterprise. The module extends Odoo's native hr.payroll salary-rule engine, so it works whether you already have HR Payroll or we add it as part of the engagement. We target your exact running version so the module installs cleanly and upgrades predictably.
How are SSS, PhilHealth, Pag-IBIG and BIR withholding actually calculated?
Contribution schedules are stored in dedicated Odoo models rather than hardcoded, so brackets are versioned and editable. SSS uses the current contribution table with employee/employer shares; PhilHealth applies the current premium rate against the floor/ceiling base; Pag-IBIG uses the standard tiered rates plus optional voluntary top-ups; BIR withholding uses the semi-monthly TRAIN-law compensation tax table with a year-end annualization run to true up annual tax. All figures compute as auditable, recomputable payslip lines.
Does it handle 13th-month pay and year-end BIR requirements?
Yes. Thirteenth-month pay is automated as a dedicated payslip run that aggregates basic salary earned across the calendar year and applies the current non-taxable threshold, taxing any excess correctly. At year end we provide the BIR annualization run plus QWeb reports for alphalist inputs and per-employee Form 2316 certificates, so your December close and January filing are covered.
Will payroll post correctly into Odoo Accounting and is the data auditable?
Yes. Payslips post to the correct salary, statutory-payable and cost-center accounts using Odoo's standard payroll accounting, so remittances and expense reporting reconcile in the ledger. Every computed line is stored and traceable to its salary rule and contribution-table version, and access is scoped with ir.model.access.csv and record rules so only authorized payroll staff can view or edit payroll data.
Related Modules

PDF Quote Builder & Branded Proposals
Turn Odoo quotations into branded, multi-page PDF proposals with cover pages, dynamic pricing blocks and e-signature.

Peppol Enhancement for e-Invoice
A build-to-order Odoo enhancement that extends native Peppol e-invoicing with multi-endpoint routing, participant validation, and richer document lifecycle handling. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17/18/19 instance.

Pipedrive CRM Connector
Build-to-order Odoo module that imports and syncs Pipedrive deals, persons and organizations into Odoo CRM — built and installed by ECOSIRE.

Pix Instant Payment for Odoo (Brazil)
A build-to-order Odoo module that generates Pix QR codes (copia e cola) and auto-reconciles instant BRL payments via bank/PSP webhooks.
Philippines Payroll
Build-to-order Odoo payroll for the Philippines: SSS, PhilHealth, Pag-IBIG, BIR tax and 13th-month pay.
- SSS contribution engine driven by an editable, versioned contribution table model — update the schedule when SSS revises brackets without touching code, with employee and employer shares split automatically per payslip
- PhilHealth premium calculation as a compute field (@api.depends on basic pay) applying the current percentage rate against the floor/ceiling salary base, with employee/employer split and rounding rules
- Pag-IBIG (HDMF) deductions with the standard tiered employee/employer rates and configurable voluntary top-up contributions per employee
- BIR withholding tax on compensation using the semi-monthly TRAIN-law tax table, computed per cutoff with taxable/non-taxable segregation of allowances and de minimis benefits