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.

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.