This is a build-to-order module, not an instant download. Typical lead time is 2–4 weeks from purchase, depending on how many salary structures, entities and WPS bank formats you need. The flow is: scoping session → development on your Odoo version → installation and configuration on a staging/copy instance → a validated test SIF reconciled to your totals → go-live on production and team training. If you have a MOHRE or bank deadline, tell us up front and we'll prioritize the critical path.

Every build includes a post-launch support window (typically 30 days) covering bug fixes and adjustments within the delivered scope. Because you receive the full source code, nothing is locked to us. Beyond the initial window we offer optional ongoing support/AMC — including re-testing and re-deploying the module when you upgrade your Odoo version (17→18→19) or when MOHRE/WPS specifications change. UAE labour-law or SIF-format updates that affect the module are handled as scoped update work under your support plan.

No. Odoo core (Community or Enterprise) provides a generic payroll engine — salary rules, contracts, payslips — but it ships no UAE localization: no WPS SIF exporter, no EOSB gratuity engine per UAE Labour Law, and no visa/Emirates ID/Emiratisation tracking. Odoo Enterprise adds some country payroll packs, but the UAE WPS SIF and end-of-service logic still have to be built. This module adds exactly that layer on top of Odoo's payroll, without patching core files.

Yes — that's the point of the build-to-order approach. Banks and exchange houses use slightly different WPS SIF layouts, so during scoping we map the exporter to your specific bank/agent specification (EDR and SCR records, routing codes, salary period, totals). Before go-live we produce a sample SIF from real data and reconcile it to your expected figures so you upload with confidence.

It supports Odoo 17, 18 and 19 on both Community and Enterprise — we build against your running version. Multi-company/multi-entity is supported: each UAE establishment can hold its own WPS credentials (MOL ID, bank agent) with data isolation enforced through ir.model.access.csv and record rules, while sharing a single Odoo database and chart of accounts.

Yes. Payroll runs post journal entries into Odoo Accounting automatically — salary expense, WPS clearing and EOSB provisions — so finance sees payroll in the general ledger. If you need to push or pull data from external HR, time-tracking or banking systems, the module's data is available through Odoo's standard XML-RPC/JSON-RPC API, and we can build specific integrations as part of the scope.