Pakistan-localized Odoo payroll: EOBI, PESSI/SESSI, FBR tax slabs, gratuity/PF and bank salary files — built, installed and supported by ECOSIRE. One-time license from $299.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Pakistan-localized Odoo payroll: EOBI, PESSI/SESSI, FBR tax slabs, gratuity/PF and bank salary files — built, installed and supported by ECOSIRE.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Running payroll for a Pakistani company in vanilla Odoo means fighting the software: EOBI and provincial social security are not modeled, the FBR salary withholding slabs change every finance act, and there is no clean way to hand your bank a disbursement file. Teams end up patching salary rules by hand, exporting to spreadsheets, and reconciling EOBI and PESSI/SESSI returns off-system — which is exactly where errors and compliance penalties creep in.
EOBI contribution engine — employer and employee shares computed on the minimum-wage-capped pensionable amount via dedicated hr.salary.rule entries with @api.depends compute methods, kept configurable so rate/ceiling changes are a settings edit, not a code rewrite
Provincial social security (PESSI / SESSI / KPESSI / BESSI) — employee province drives the correct provincial fund, contribution base and rate automatically on each payslip
FBR monthly income-tax withholding — annual salary tax slabs from the current finance act applied to projected annual taxable salary, spread across the fiscal year, with year-to-date true-up so the final months self-correct
Gratuity accrual — configurable last-drawn-salary-per-year-of-service (or your scheme) computed and posted as an accrued liability per employee
Provident fund handling — employer and employee PF contributions as salary rules, with optional trust/CVT treatment and separate PF ledger accounts
Bank salary disbursement file export — one-click generation of your bank's required bulk-transfer format (HBL, Meezan, UBL, Bank Alfalah, etc.) from confirmed payslip batches, with account/IBAN validation
Pakistan Payroll is a build-to-order Odoo module that ECOSIRE designs, develops, installs and supports specifically for your organization. This is not an instant apps.odoo.com download — after purchase our Odoo engineers scope your salary structure, entities and provincial footprint, then deliver a production-ready localized payroll on your Odoo 17, 18 or 19 instance (Community or Enterprise) within a typical 2–4 week lead time.
Under the hood it extends Odoo's HR Payroll (hr.payslip, hr.salary.rule, hr.contract) with Pakistan-specific salary rules and computed fields (models.Model with @api.depends compute methods) for EOBI employer/employee contributions, provincial social security (PESSI in Punjab, SESSI in Sindh, and the equivalent KPK/Balochistan bodies), FBR monthly income-tax withholding using the current annual slabs, gratuity accrual and provident fund. Access is locked down with ir.model.access.csv and record rules so only HR and finance roles touch salary data, statutory registers are produced as QWeb PDF reports, and month-end bank disbursement files are generated in your bank's required format. Because it is proper Odoo, everything is auditable, upgrade-safe, and exposed over Odoo's XML-RPC / JSON-RPC API for integration with attendance, accounting and external systems.
You buy an outcome, not a code drop: a payroll that computes the right EOBI, PESSI/SESSI and WHT figures on the first run, generates the returns and bank file your finance team already expects, and comes with documentation, training and a support window so your staff can run it confidently every month.
Runs monthly payroll for 30–300 staff and is tired of maintaining EOBI, PESSI and tax math in spreadsheets. Wants payslips, statutory registers and the bank file to come straight out of Odoo, correctly, every month, without depending on one person's Excel template.
Owns statutory compliance and cash disbursement. Needs EOBI/PESSI and FBR withholding to be right and defensible in audit, payroll journals to hit the correct GL accounts, and a clean bank upload — with role-based access so salary data is not visible across the company.
Standardizing the business on Odoo 17/18/19 and refuses to bolt on a disconnected payroll tool. Wants a proper Odoo module (models, security, QWuery/QWeb reports, API access) that upgrades cleanly and integrates with attendance and accounting rather than a black-box export.
Manages payroll across companies operating in Punjab and Sindh (and beyond). Needs each entity's EOBI/PESSI registration, bank account and salary structure handled correctly on one database with the right province rules applied per employee.
Buy the license on ecosire.com and download the Pakistan Payroll (EOBI, PESSI, WHT) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Pakistan Payroll (EOBI, PESSI, WHT), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| EOBI, PESSI/SESSI & FBR WHT modeled correctly | Built-in as configurable salary rules and computed fields, validated on your first live run | Possible, but you specify and test every statutory rule yourself | Rarely complete — most generic payroll apps skip provincial social security and current slabs | |
| Bank salary disbursement file for your bank | Built and tested to your bank's exact bulk-transfer format | Bespoke development you scope and pay for separately | Generic CSV at best; usually needs manual reformatting | |
| Tailored to your entities, provinces and salary structure | Scoped and configured for your company before go-live | Fully tailored, but only to the depth your own team can build | One-size-fits-all; you adapt your process to the app | |
| Odoo 17 / 18 / 19, Community & Enterprise | Delivered on your exact version and edition, upgrade-aware | Depends entirely on your developers' discipline | Often lags new Odoo versions or is Enterprise-only | |
| Role-based security & audit on salary data | ir.model.access.csv + record rules scoped to HR/finance groups | Only if your team implements and reviews it | Varies by vendor; often coarse-grained | |
| Statutory registers & payslips as PDF reports | QWeb reports for EOBI/PESSI schedules and WHT summaries, filing-ready | You design and maintain each report | Limited or non-localized report templates | |
| Delivery model & lead time | Build-to-order: scoped, built, installed and validated in ~2–4 weeks | Weeks to months of in-house dev, QA and rework | Instant download, but then long DIY localization effort | |
| Ongoing updates for finance-act changes | Support window + optional annual maintenance keeps slabs/rates current | Your team tracks and re-implements every change | Depends on vendor release cadence, if any |
No, this is a build-to-order module, not an off-the-shelf apps.odoo.com download. After purchase we scope your salary structure, entities, provinces and bank, then build, install and validate the module on your Odoo instance. Typical lead time is 2–4 weeks depending on the number of companies, complexity of your salary components and the bank file format required. We agree a delivery schedule with you up front and finish with a supervised first live payroll run.
Statutory rates — EOBI employer/employee shares and ceiling, provincial social security bases, and FBR annual tax slabs — are built as configurable parameters and salary rules, so routine rate changes are a settings update rather than a code rewrite. Any code-level changes (for example a new statutory return format) are covered during your post-go-live support window; beyond that we offer an optional annual maintenance arrangement so each year's finance-act slab and rate changes are applied and tested for you.
Yes. The module is built on Odoo's HR Payroll framework and targets Odoo 17, 18 and 19, with the __manifest__.py and code aligned to your exact version. It runs on both Community and Enterprise editions — we confirm your edition and version during scoping and deliver against that so the payroll survives future minor upgrades cleanly.
Yes. Each is implemented as its own salary rule and computed field: EOBI employer/employee contributions, the correct provincial social security fund per employee (PESSI in Punjab, SESSI in Sindh, and KPK/Balochistan equivalents), employer/employee provident fund, and gratuity accrual on your chosen scheme. They post to the right payable and provision accounts and appear on the payslip and statutory registers, so nothing is tracked off-system.
Yes. We build the bank disbursement export to your specific bank's bulk-transfer specification (for example HBL, Meezan, UBL or Bank Alfalah). From a confirmed payslip batch you export a ready-to-upload file with employee account/IBAN validation, so finance stops rekeying salaries into the bank portal. If you use more than one bank, we can support multiple formats.
Yes. Confirmed payroll posts standard Odoo journal entries — net pay, EOBI/PESSI payable, WHT payable, PF and gratuity provisions — to the accounts you specify, so payroll and the general ledger stay reconciled. Because everything is stored as normal Odoo records, your attendance system, BI dashboards or external tools can read and write the data over Odoo's XML-RPC / JSON-RPC API.
Yes. Access is enforced with ir.model.access.csv and record rules so that only designated HR/payroll and finance security groups can view or edit salary, tax and bank-file data. Changes are auditable, and in a multi-company setup each entity's payroll is isolated to the users who should see it.
Pakistan-localized Odoo payroll: EOBI, PESSI/SESSI, FBR tax slabs, gratuity/PF and bank salary files — built, installed and supported by ECOSIRE.