イメージプレビューBuild-to-order Odoo module: six-country GCC payroll rules,
per-country WPS/SIF/Mudad exports and unified EOSB across one multi-company instance.
GCC Unified Payroll Packとは？
Build-to-order Odoo module: six-country GCC payroll rules, per-country WPS/SIF/Mudad exports and unified EOSB across one multi-company instance. 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
本番稼働 + サポート
約1週間（営業日ベース）で稼働し、本番稼働後2週間のサポートが付きます。納品したコードの不具合は無償で修正します。
技術仕様
- Odoo互換性
- Odoo 17, Odoo 18, Odoo 19
- エディション
- Enterprise＆Community
- ライセンス
- ライセンスの確認が必要です
- Python要件
- Python 3.10+
- データベース
- PostgreSQL 12+
この製品について
Multi-entity GCC groups usually end up running a different payroll workaround in every country — a UAE WPS spreadsheet here, a KSA Mudad export there, an EOSB formula buried in someone's laptop. The GCC Unified Payroll Pack collapses all of that into a single Odoo module that ECOSIRE designs, builds and installs for you on one multi-company instance across Odoo 17, 18 and 19.
This is a build-to-order engagement, not an off-the-shelf apps.odoo.com download. After you purchase, our Odoo payroll engineers scope your entities, salary structures and file formats, then deliver a bespoke module — normally within one working week — that plugs directly into hr.payroll. You get country-specific salary rules (hr.salary.rule) driving compute logic through Odoo's ORM, per-country statutory file exporters (WPS/SIF/Mudad), and one gratuity engine that reads each employee's country, contract type and service length to calculate end-of-service benefits correctly.
The pack is built the Odoo-native way: proper models.Model definitions with computed fields via @api.depends, access controlled through ir.model.access.csv plus record rules so a KSA HR user never touches UAE payslips, QWeb PDF reports for country-formatted payslips and EOSB statements, and automated actions for period-end runs. Everything respects Odoo multi-company and multi-currency, so a group headquartered in Dubai paying salaries in AED, SAR, QAR, KWD, OMR and BHD reports cleanly in one place. Expat and national employees get the right structures per country — GOSI/social-insurance handling for nationals, WPS/labour-law handling for expats — without maintaining six separate databases.
You own the source. We hand over the module, the configuration, documentation and admin training, and back it with a defined support window. Because it is written against Odoo's stable payroll and accounting APIs (and exposes results over XML-RPC/JSON-RPC if you integrate downstream), it upgrades cleanly and stays maintainable long after go-live.
得られるもの
- The complete custom Odoo module source code (a proper __manifest__.py, models/, security/, views/, report/ and data/ tree) that you own outright
- Configured salary structures and hr.salary.rule sets for each of your live GCC entities, mapped to your actual allowances and contracts
- Configured WPS/SIF/Mudad and other per-country export formats validated against your banks' and authorities' current specifications
- Access-control setup (ir.model.access.csv + record rules) scoped to your per-country HR teams and reviewed with you
- Written administrator and HR-user documentation covering payroll runs, file exports, EOSB settlement and troubleshooting
- A live admin + HR training session (recorded) so your team can run payroll independently from day one
- A defined post-go-live support window for bug fixes and questions, with an SLA agreed during scoping
- Deployment assistance onto your Odoo 17/18/19 instance, including a UAT/staging validation cycle before production go-live
これは誰のためのものですか
Group HR Director of a multi-country GCC holding
Runs HR for entities in two or more GCC states on one Odoo instance and needs consistent payroll, WPS compliance and EOSB accuracy without juggling six separate systems or spreadsheets.
Finance Controller consolidating GCC entities
Needs each country's payroll posted to the right company and journal in the right currency, so month-end consolidation across AED, SAR, QAR, KWD, OMR and BHD is clean and audit-ready.
Odoo administrator / IT lead at a regional group
Owns the shared Odoo deployment and wants one maintainable, upgrade-safe module — built to Odoo conventions — instead of six brittle third-party apps that break on every version bump.
Payroll / PRO officer handling GCC compliance
Generates WPS, Mudad and wage-protection files each cycle and settles end-of-service benefits, and needs those files produced correctly and repeatably straight from validated payroll runs.
GCC Unified Payroll Pack の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | Odoo 標準機能 |
|---|---|---|---|---|
| Covers all six GCC countries' payroll rules in one module | Yes — UAE, KSA, Qatar, Kuwait, Oman, Bahrain built into one pack | Possible but you build and maintain all six yourself | Usually single-country; you buy and stitch several apps | No — Odoo core has no GCC statutory rule sets |
| Per-country WPS / SIF / Mudad file export | Delivered and validated for each country you run | You must research each spec and build every exporter | Often one country only; formats drift out of date | Not available out of the box |
| Unified end-of-service (EOSB) gratuity engine | One engine applying each labour law by country and contract | Hand-coded per country, easy to get accrual bands wrong | Rarely covers all six laws consistently | No EOSB logic in Odoo core |
| Expat vs. national (GOSI/social-insurance) handling | Correct structure auto-applied per employee per country | You model every case manually | Partial; usually national-scheme for one country | Not modelled |
| Multi-company, multi-currency on one instance | Native Odoo multi-company with per-entity access scoping | Achievable but you design the record rules yourself | Varies; often assumes a single company | Multi-company exists but with no payroll rules to drive it |
| Fits your entities, allowances and formats | Scoped and configured to your actual contracts before go-live | Fully bespoke — but on your time and risk | Off-the-shelf; you bend your process to the app | Generic; no localization |
| Ongoing support and version updates | Defined support window + optional 17/18/19 update retainer | You own all maintenance forever | Depends on vendor; may lapse or lag Odoo releases | Community/your team only |
| Source-code ownership and upgrade safety | You own the source; built to Odoo conventions for clean upgrades | You own it, but quality depends on your team | Vendor-locked; upgrades gated by their roadmap | N/A — nothing to own |
GCC Unified Payroll Pack に関するよくある質問
How long does delivery take, and is this an instant download?
This is a build-to-order module, not an instant apps.odoo.com download. After purchase we scope your entities, salary structures and file formats, then build, test and install the module — typically within one working week depending on how many of the six countries you run and how custom your allowances and export formats are. You get a scoping call up front and a UAT/staging validation cycle before production go-live.
What do I actually receive, and do I own the code?
You receive the complete custom Odoo module source (manifest, models, security, views, QWeb reports and data), the configuration for each of your live entities, written documentation, a recorded training session, and deployment support onto your instance. You own the source code outright — there is no per-seat license lock-in on the module itself.
How do support and updates work after go-live?
Every engagement includes a defined post-go-live support window (SLA agreed during scoping) covering bug fixes and questions. Because the module is written against Odoo's stable payroll and accounting APIs, it upgrades cleanly across Odoo 17, 18 and 19. When you move to a new Odoo version or a country changes its WPS/Mudad spec, we offer an update/maintenance retainer to keep exports and rules current.
Does it work with multi-company and multiple currencies?
Yes — that is the core design. It uses Odoo's native multi-company model so each entity keeps its own payslips, journals and access, and it handles AED, SAR, QAR, KWD, OMR and BHD with group-level reporting in your presentation currency. Record rules keep each country's HR team scoped to their own company's data.
Does it run on Odoo Community or only Enterprise?
We build and test against both Community and Enterprise on Odoo 17, 18 and 19. Odoo's HR Payroll app is an Enterprise module, so if you are on Community we scope the payroll foundation as part of the engagement and tell you exactly what is required before you commit. We confirm your edition and version during the scoping call.
How are the WPS, SIF and Mudad files handled per country?
Each country's wage-protection format is implemented as a dedicated exporter that reads validated payroll runs and produces the required file — UAE WPS SIF, KSA Mudad/WPS, and the Qatar, Kuwait, Oman and Bahrain equivalents. We validate the output format against your banks' and authorities' current specifications during UAT so the files are accepted first time.
関連モジュール
GCC Unified Payroll Pack
Build-to-order Odoo module: six-country GCC payroll rules, per-country WPS/SIF/Mudad exports and unified EOSB across one multi-company instance.
- Six ready-to-configure GCC country rule sets (UAE, KSA, Qatar, Kuwait, Oman, Bahrain) delivered as hr.salary.rule records driving payslip computation
- Per-country statutory file exporters: UAE WPS SIF, KSA Mudad/WPS, plus Qatar, Kuwait, Oman and Bahrain wage-protection formats generated straight from validated payroll runs
- Unified end-of-service gratuity (EOSB) engine that reads employee country, contract type and continuous-service length, applying each labour law's accrual bands automatically
- GOSI / social-insurance handling for GCC nationals vs. WPS/labour-law handling for expats, with the correct salary structure applied per employee per country