Build-to-order Odoo Qatar payroll with WPS SIF export, end-of-service gratuity and expat/national salary policies. One-time license from $299.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Odoo Qatar payroll with WPS SIF export, end-of-service gratuity and expat/national salary policies.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Odoo core payroll gives you a solid engine, but it ships with nothing Qatar-specific: no WPS SIF file, no end-of-service gratuity rules under the Qatar Labour Law, no QAR salary structures, and no expat-versus-national policy handling. ECOSIRE closes that gap with a purpose-built Qatar localization module that we design, build, install and support for your Odoo database.
WPS Salary Information File (SIF) generation in the fixed-width/CSV layout required by Qatari banks and the Qatar Central Bank, populated directly from posted payslip data
Establishment ID, employee QID, IBAN, basic wage, allowances, deductions and net-pay mapping validated against WPS field rules before export
End-of-service gratuity computed via an @api.depends method applying Qatar Labour Law accrual (three weeks of basic wage per year after one year of continuous service), prorated for partial years
QAR-native salary structures and rules for basic wage, housing, transport, food and custom allowances, built on Odoo's hr.payroll salary rule engine
Separate policy sets for expatriate versus Qatari national employees, so social insurance and nationality-specific items apply only where required
Document expiry automated actions monitoring QID, passport, visa and health-card dates with advance email/activity alerts to HR before lapse
This is a build-to-order engagement, not an instant download from apps.odoo.com. Over a typical 2-4 week window our Odoo engineers scope your company's pay elements, employee categories and bank formats, then deliver a proper Odoo module: a versioned __manifest__.py declaring dependencies on hr and hr_payroll, Python models extending hr.contract, hr.employee and hr.payslip, salary rules and structures configured for QAR, security via ir.model.access.csv plus record rules, backend views in XML/OWL, and QWeb PDF reports for payslips and gratuity settlements.
The centerpiece is compliant Wage Protection System output. The module generates the WPS Salary Information File (SIF) in the fixed-width/CSV layout your bank and the Qatar Central Bank require, populating establishment ID, employee QID, IBAN, basic wage, allowances, deductions and net pay from live payslip data. End-of-service gratuity is computed automatically with an @api.depends compute method that applies the Qatar Labour Law accrual (typically three weeks of basic wage per year of continuous service after one completed year), prorated for partial years and driven by contract start, end and reason for leaving.
You get QAR-native salary structures with configurable basic wage, housing, transport and other allowances; distinct rule sets for expatriate and national employees so items like social insurance for Qatari nationals are handled separately from expat contracts; and Odoo automated actions that watch QID, passport, visa and health-card expiry dates and alert HR before they lapse. Everything runs inside your Odoo (Community or Enterprise, versions 17, 18 and 19) and integrates with the standard payroll, accounting and HR apps you already use — payslips post to journals, and the SIF can be regenerated for any pay period through the backend or the XML-RPC/JSON-RPC API.
Because we build it for your establishment, the salary rules, WPS field mapping and gratuity policy match how you actually pay people, and you own the source. After go-live we hand over documentation, train your HR team, and back the module with a support and warranty window.
Runs monthly payroll and must submit a compliant WPS SIF to the company's bank on time. Needs gratuity, allowances and expat/national rules handled automatically inside Odoo instead of in fragile spreadsheets.
Owns net-pay accuracy, journal postings and audit trails. Wants payslips that reconcile to accounting, deductions applied correctly, and WPS totals that match the bank transfer to the fils.
Responsible for keeping the Odoo deployment clean and upgradeable across versions 17/18/19. Prefers a properly structured localization module (manifest, models, security, tests) over ad-hoc customizations that break on upgrade.
Buy the license on ecosire.com and download the Qatar Payroll & WPS 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 Qatar Payroll & WPS, 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 |
|---|---|---|---|---|
| Qatar WPS SIF file export | Built and validated against your bank's exact spec | Possible but you build and maintain it yourself | Sometimes included but generic, may not match your bank | |
| End-of-service gratuity (Qatar Labour Law) | Automated @api.depends compute, configured to your policy | Hand-coded per project | ||
| Expat vs Qatari national policies | Separate rule sets driven by employee category | You design the logic | ||
| QAR salary structures & allowances | Pre-configured to how you actually pay | |||
| Document/visa/QID expiry alerts | Automated actions with advance HR alerts | You wire the automation | ||
| Fits your exact pay policy & bank format | Scoped and built for your establishment | |||
| Delivery, install, training & support | ECOSIRE builds, deploys, trains and supports | Your team or contractor's responsibility | Self-install, vendor ticket support | |
| Upgrade-safe across Odoo 17/18/19 | Extends core hr/hr_payroll cleanly, source owned | Depends on build quality | Depends on vendor's version support |
This is a build-to-order module, not an instant apps.odoo.com download. Typical delivery is 2-4 weeks: we scope your pay elements, employee categories and bank SIF format, then build, test and deploy the Odoo module (manifest, models, salary rules, security, views and QWep reports) to your staging environment before production go-live. Timeline depends on the number of salary structures, entities and how quickly we get your bank's WPS file specification.
Every engagement includes a post-go-live support and warranty window covering bug fixes and adjustments to the WPS SIF format if your bank or the Qatar Central Bank changes it. You also receive documentation and team training. Because you own the source, we can provide extended support, version upgrades (17 to 18 to 19) and new features under a separate maintenance agreement whenever you need them.
Yes. The module generates the WPS Salary Information File in the layout your Qatari bank expects, populating establishment ID, employee QID, IBAN, basic wage, allowances, deductions and net pay from posted payslips. We validate the output against your bank's exact specification and a sample period during the build, because minor field/format differences exist between banks.
Gratuity is computed automatically using an @api.depends method that applies the Qatar Labour Law accrual — generally three weeks of basic wage per completed year of continuous service after the first year — prorated for partial years and driven by the contract's start date, end date and reason for leaving. The exact rule is configured to match your company policy and any contractual enhancements.
The module targets Odoo 17, 18 and 19 on both Community and Enterprise editions. It extends the standard hr and hr_payroll apps rather than replacing them, so it coexists with the accounting, HR and other apps you already run. We confirm your exact version and installed apps during scoping and build against that.
The module ships distinct rule sets. Qatari nationals get national-specific handling (for example social insurance contributions) while expatriate contracts use their own allowance and deduction rules. Employee category drives which salary rules apply, so a single payroll run correctly processes a mixed workforce and produces one WPS file per establishment.
Yes. Beyond the Odoo backend, WPS SIF generation and payslip data are accessible over Odoo's XML-RPC and JSON-RPC APIs, so you can trigger regeneration for a pay period or push data to a bank portal integration programmatically. We can build a specific integration as part of the scope if you need automated submission.
Build-to-order Odoo Qatar payroll with WPS SIF export, end-of-service gratuity and expat/national salary policies.