Oman Fawtara e-Invoice
Oman Tax Authority Fawtara — PINT UBL 2.1, 5-corner, BYOK
Generate and submit Oman Tax Authority (OTA) Fawtara e-invoices directly from Odoo. This connector implements the Peppol-style 5-corner Continuous Transaction Control model and the PINT (Peppol International Invoice) UBL 2.1 syntax with the Oman jurisdiction alignment, and submits through your own accredited service provider using bring-your-own-key credentials.
Phased mandate — ship ahead of go-live
Per the official OTA e-invoicing FAQ, Fawtara rolls out in three phases: Phase 1 in August 2026 (the 100 largest VAT-registered companies), Phase 2 in February 2027, and Phase 3 in August 2027. Deploy now and be ready before your phase begins.
Honest status: as of mid-2026 the OTA has published the draft PINT Oman specification and opened accredited-service-provider (ASP) accreditation; the production clearance channel is not yet live. This connector is format-ready + BYOK transport — it builds the PINT document and QR today and submits to the ASP/OTA endpoint you configure once your provider is onboarded. It bundles no live OTA gateway or ASP account.
Fawtara PINT UBL 2.1
Invoice and credit-note XML built on the shared e-invoice engine: Oman
CustomizationID, VATIN endpoints under the Oman network
scheme, tax subtotals and totals, and the OTA clearance UUID embedded
on cleared documents.
Oman VATIN validation
Real structural validation of the Oman VATIN (OM followed
by 10 digits, e.g. OM1100005523) on companies and
partners, plus an advisory ISO 7064 MOD 11-2 typo check.
Business-rule validation
Oman rules layered on the EN 16931 core rule set, surfaced before generation and submission so you catch issues locally instead of after a provider round-trip.
QR & verification
GCC TLV (tag-length-value, base64) QR carrying seller, VATIN, timestamp and totals, rendered to a PNG, plus an OTA portal verification URL helper.
BYOK accredited-provider transport
Submit and poll clearance status over a resilient REST transport with retry, backoff and full call logging. Sandbox / production switching is built in, and the endpoints are pre-filled with placeholder, editable defaults — replace them with your own ASP gateway URL once Oman's mandate / spec goes live. Your API key is bring-your-own-key — stored only on your database and never bundled.
Inside the invoice
Generate, Validate, Submit and Check-Status buttons on the customer invoice, all routed through the engine e-invoice document. A guided onboarding wizard and an optional status-polling scheduled action round out the workflow.
Compatibility
Built for Odoo 18 & 19 (Community and Enterprise). Requires
the E-Invoice Core Engine base module. Python dependencies:
lxml, qrcode, requests.
Disclosure: this module transmits invoice data only to the accredited service provider endpoint you configure. No data is sent anywhere else.
Screenshots
Cleared Fawtara Customer Inv
Fawtara Pint E Invoice Docum
Update date: 2026-07-12
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2838 |
| Technical Name |
l10n_om_fawtara_einvoice |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module