Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $249.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Oman VAT Compliance Pack
A built-from-scratch Oman VAT localization for Odoo — 5% tax structure, a localized chart of accounts, GCC fiscal positions and an Oman Tax Authority (OTA) return template, with bilingual Arabic/English tax invoices. ECOSIRE scopes, builds, installs and supports it for you.
$249.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
Omani chart of accounts template (`account.account` records) aligned to OTA return and reporting needs, importable into a new or existing company
5% standard-rated, zero-rated, exempt and out-of-scope taxes defined as `account.tax` records grouped under Oman `account.tax.group`
Tax tags wired into `account.tax` repartition lines so each debit/credit leg maps to the correct OTA return box
`account.fiscal.position` records with mapping rules for GCC B2B, imports (reverse charge) and exports — taxes and accounts swap automatically per partner
OTA VAT return report built on Odoo's tax-report engine (Enterprise) or a dedicated computed model with QWeb PDF + XLSX export (Community)
Drill-down from every return figure back to the underlying `account.move.line` journal items for audit defensibility
Bilingual Arabic/English tax invoice via inherited QWeb templates with `rtl` layout and all OTA-mandated fields (supplier VAT/TIN, sequential number, tax breakdown)
Reverse-charge handling on imported services and goods so input and output VAT post correctly in the same period
Company VAT/Tax Identification Number fields surfaced on invoices and in report headers
`ir.model.access.csv` plus record rules restricting tax configuration and return generation to accounting roles only
Optional automated action / scheduled `ir.cron` reminder before each OTA filing deadline
Sequential, gap-free invoice numbering configured to Omani requirements
Clean `__manifest__.py` with pinned dependencies (`account`, `l10n_gcc_invoice`) and version-specific branches for Odoo 17.0 / 18.0 / 19.0
XML-RPC / JSON-RPC compatible so external POS, e-commerce or billing systems can create compliant invoices programmatically
इस उत्पाद के बारे में
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.
Oman VAT Compliance Pack क्यों चुनें
Omani chart of accounts template (`account.account` records) aligned to OTA return and reporting needs, importable into a new or existing company
5% standard-rated, zero-rated, exempt and out-of-scope taxes defined as `account.tax` records grouped under Oman `account.tax.group`
Tax tags wired into `account.tax` repartition lines so each debit/credit leg maps to the correct OTA return box
`account.fiscal.position` records with mapping rules for GCC B2B, imports (reverse charge) and exports — taxes and accounts swap automatically per partner
OTA VAT return report built on Odoo's tax-report engine (Enterprise) or a dedicated computed model with QWeb PDF + XLSX export (Community)
Drill-down from every return figure back to the underlying `account.move.line` journal items for audit defensibility
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 2-4 weeks 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.
What you get
- Installable module source code built and pinned for your exact Odoo version (17.0, 18.0 or 19.0) and edition (Community or Enterprise)
- Installation and configuration on your environment, including chart of accounts, taxes, tax groups and fiscal positions
- Technical documentation — module structure, models, tax/tag mapping to OTA boxes, and configuration notes
- End-user guide plus a live training session for your accounting team on filing and invoicing
- UAT on a staging copy of your database with a documented rollback plan before any production change
- Post-go-live support window for defect fixes and configuration questions
- Git repository handover with full commit history and tagged release
- Sample filed-return walkthrough reconciling Odoo figures to the OTA return format
Who this is for
Omani SME finance lead
Runs accounting for a VAT-registered business in Oman and needs Odoo to produce OTA-ready returns and compliant Arabic tax invoices without spreadsheet reconciliation each period.
GCC Odoo implementation partner
Delivers Odoo projects across the Gulf and needs a reliable Oman localization layer — correct taxes, fiscal positions and return mapping — to drop into client deployments instead of rebuilding it per project.
Group financial controller with a Muscat entity
Manages a multi-entity group where one company operates in Oman and requires localized VAT treatment, reverse charge on imports and export zero-rating that reconciles cleanly at consolidation.
ERP migration manager
Moving from a legacy system to Odoo and needs the Omani chart of accounts, tax structure and historical fiscal treatment brought over with a tested, reversible cutover.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Oman VAT Compliance Pack module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Oman VAT Compliance Pack, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Oman VAT Compliance Pack Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Oman OTA return mapping | Taxes and tags mapped to OTA return boxes, drill-down to journal items | Possible but you design and validate the box mapping yourself | Rarely Oman-specific; usually a generic GCC template | |
| 5% tax + fiscal positions | Standard/zero/exempt/out-of-scope taxes + GCC, import, export fiscal positions prebuilt | Built by hand per your spec, time-consuming to get right | Partial; often missing reverse-charge and export cases | |
| Bilingual Arabic/English invoice | Inherited QWeb template, RTL layout, all OTA-mandated fields | Requires QWeb work and Arabic layout testing | Sometimes English-only or partial Arabic | |
| Odoo version fit (17/18/19) | Built and pinned to your exact version and edition | Depends on your team's version discipline | Often lags new Odoo releases | |
| Community vs Enterprise | Enterprise tax engine or Community model+QWeb variant built to fit | You decide and implement the approach | Frequently Enterprise-only | |
| Access control | `ir.model.access.csv` + record rules scoped to accounting roles | Only if you implement it | Varies by module quality | |
| Testing & rollback | UAT on staging with documented rollback plan | Your responsibility to arrange | None — install at your own risk | |
| Support & code ownership | Post-go-live support window + full source and Git handover | You own it but carry all maintenance | Vendor support tiers; code usually closed |
Frequently Asked Questions about Oman VAT Compliance Pack
How long does delivery take?
This is a build-to-order module, not an instant download. Typical delivery is 2-4 weeks from confirmed scope, after we agree your Odoo version, edition and chart-of-accounts requirements on a scoping call. Complex multi-entity or migration work may run longer, and we tell you the honest timeline before you commit.
Does it work with Odoo Community, or only Enterprise?
Both. On Enterprise we use the built-in tax-report engine for the OTA return; on Community, where that engine isn't available, we deliver an equivalent dedicated return model with a QWeb PDF and XLSX export. We confirm your edition during scoping and build the right variant for it.
Which Odoo versions are supported?
Odoo 17.0, 18.0 and 19.0. We build against your specific running version so the `__manifest__.py`, models and views match it exactly — no forward-porting surprises on install.
Are the tax invoices actually OTA-compliant and bilingual?
Yes. Invoices are inherited QWeb templates carrying the OTA-mandated fields — supplier VAT/TIN, sequential invoice number, per-line tax breakdown and the 5% VAT summary — with an Arabic/English right-to-left layout. We tailor the exact template to your branding and any specifics OTA expects for your activity.
How does it handle imports, exports and GCC transactions?
Through Odoo `account.fiscal.position` records with mapping rules. Selecting a GCC B2B, import or export partner automatically swaps to the correct taxes and accounts — including reverse charge on imported goods and services and zero-rating on exports — so users don't set tax treatment by hand.
What about support and updates after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration questions. Because you receive the full source and Git repository, you own the code. If OTA rules change or you upgrade Odoo versions, we can quote a maintenance retainer or a one-off update — nothing is locked to us.
Will this touch our existing accounting data?
We build and test on a staging copy of your database first and run UAT there with a documented rollback plan before any production change. Your live data is only touched during a controlled, reversible cutover you sign off on.
Related Modules
कोटेशन का अनुरोध करें
Oman VAT Compliance Pack
A built-from-scratch Oman VAT localization for Odoo — 5% tax structure, a localized chart of accounts, GCC fiscal positions and an Oman Tax Authority (OTA) return template, with bilingual Arabic/English tax invoices. ECOSIRE scopes, builds, installs and supports it for you.
- Omani chart of accounts template (`account.account` records) aligned to OTA return and reporting needs, importable into a new or existing company
- 5% standard-rated, zero-rated, exempt and out-of-scope taxes defined as `account.tax` records grouped under Oman `account.tax.group`
- Tax tags wired into `account.tax` repartition lines so each debit/credit leg maps to the correct OTA return box
- `account.fiscal.position` records with mapping rules for GCC B2B, imports (reverse charge) and exports — taxes and accounts swap automatically per partner