Since VAT went live in Oman in April 2021, every registered business has had to file periodic returns with the Oman Tax Authority (OTA) at the standard 5% rate, distinguish zero-rated and exempt supplies, and issue compliant tax invoices in Arabic. Odoo ships a generic accounting engine and a light l10n_gcc_invoice layer, but it does not carry an OTA-ready Omani chart of accounts, the exact tax and tax-group structure the return expects, or a report that maps your ledger to the OTA return boxes. Teams end up hand-building taxes, guessing at fiscal positions for GCC and import/export flows, and reconciling returns in spreadsheets — which is slow and audit-risky.

The Oman VAT Compliance Pack is a purpose-built Odoo module (its own __manifest__.py, depending on account and building on l10n_gcc_invoice) that ECOSIRE writes to your Omani entity's requirements. We ship an Omani chart of accounts and a full 5% tax structure defined through account.tax and account.tax.group records — standard-rated 5%, zero-rated (exports, qualifying supplies), exempt, and out-of-scope — each with the correct tax tags wired into repartition lines so that debit and credit legs post to the right return boxes. account.fiscal.position records with their mapping rules automatically swap taxes and accounts for GCC B2B, imports (reverse charge), and exports, so users pick the customer or vendor and the system applies the right treatment without manual overrides.

Technically, the OTA return is delivered as a tax report built on Odoo's account.report / tax-report engine (Enterprise) or, for Community deployments, as a dedicated model with @api.depends computed fields plus a QWeb PDF and an XLSX export that follow the OTA box structure — so the numbers you file trace straight back to journal items you can drill into. Bilingual Arabic/English tax invoices are delivered as inherited QWeb report templates carrying the mandatory fields (supplier VAT/TIN, sequential invoice number, tax breakdown, and Arabic labels), with direction: rtl handling for the Arabic layout. Access is locked down with ir.model.access.csv and record rules so only accounting roles touch tax configuration, and everything is reachable over Odoo's XML-RPC / JSON-RPC API if you integrate an external billing or POS system.

Because this is a build-to-order engagement, we do not hand you a generic download. After a short scoping call we confirm your Odoo version (17.0, 18.0 or 19.0), Community vs Enterprise, your existing chart of accounts and any migration constraints, then build the module against a staging copy of your database. Typical delivery is one working week from confirmed scope. You get the installable source, UAT on staging with a rollback plan, documentation and a training session, and a post-go-live support window — see the deliverables and FAQs below for exactly what is included.