- 首页
- Apps
- SaaS Tools
- Qatar Payroll & WPS
示意预览Build-to-order Odoo Qatar payroll with WPS SIF export,
end-of-service gratuity and expat/national salary policies.
什么是 Qatar Payroll & WPS?
Build-to-order Odoo Qatar payroll with WPS SIF export, end-of-service gratuity and expat/national salary policies. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制,全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线,并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
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.
This is a build-to-order engagement, not an instant download from apps.odoo.com. Over a typical one working 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.
你得到什么
- Installable Odoo module (source code) with versioned __manifest__.py, Python models, salary rules, XML/OWL views, QWeb reports and security files, licensed to your company
- WPS SIF export configured and test-validated against your bank's file specification and a sample pay period
- Configured QAR salary structures, allowance rules and expat/national rule sets matching your actual pay policy
- End-of-service gratuity and final-settlement logic configured to your contract terms and the Qatar Labour Law
- Deployment onto your Odoo instance (staging then production) with an installation and upgrade runbook
- Admin and HR-user documentation plus a live training session for your payroll team
- Post-go-live support and warranty window covering bug fixes and WPS format adjustments
- Source ownership and a handover so your team (or ours) can maintain and extend the module later
这是给谁的
HR Manager at a Qatar-based company
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.
Finance/Payroll Controller
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.
Odoo Implementation Lead or IT Manager
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.
Qatar Payroll & WPS 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| 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 | 包含 |
关于Qatar Payroll & WPS的常见问题
How long does delivery take and how is it built?
This is a build-to-order module, not an instant apps.odoo.com download. Typical delivery is one working week: 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.
What support and updates are included after go-live?
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.
Is this a Qatar-compliant Wage Protection System (WPS) SIF file?
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.
How is end-of-service gratuity calculated?
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.
Does it work with our Odoo version and edition?
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.
How does it handle expat versus Qatari national employees?
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.
Can we generate the WPS file and payroll data through an API?
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.
相关模块
Qatar Payroll & WPS
Build-to-order Odoo Qatar payroll with WPS SIF export, end-of-service gratuity and expat/national salary policies.
- 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



