Oman Fawtara Inbound
Receive cleared supplier e-invoices from your Fawtara accredited provider and import them straight into vendor bills
In the Oman Tax Authority Fawtara 5-corner model the buyer receives cleared supplier invoices from its own accredited service provider. This connector pulls those PINT UBL 2.1 documents, validates and reconciles them, and drafts the matching vendor bill — ready for the phased mandate starting August 2026.
Real PINT UBL inbound parser
A namespace-aware lxml parser reads the supplier Invoice or CreditNote and reconstructs parties, lines, VAT category codes, tax subtotals and monetary totals — the exact inverse of the e-invoice engine UBL builder. The embedded OTA clearance UUID is captured on the bill.
Provider mailbox over BYOK transport
List the accredited-provider inbox, fetch each document and acknowledge receipt so it is not re-delivered. Sandbox and production endpoints are editable; requests retry with exponential backoff and every call is logged. Your provider API key is bring-your-own-key.
Validation & reconciliation
EN 16931 core rules plus Oman checks (supplier and customer VATIN, UNCL5305 VAT category codes, currency) run before anything is posted. Line sums are reconciled against the stated LineExtensionAmount and tax subtotals against the document TaxAmount, so a tampered or truncated document is caught early.
Straight-through vendor bills
The supplier partner is resolved (or created) by Oman VATIN or VAT, a matching purchase VAT tax is selected per line, and a draft vendor bill is created and linked back to the inbound document — with invoices and credit notes handled distinctly.
Clear inbound workspace
Every received document moves through a visible lifecycle — received, parsed, validated, vendor bill created, error or ignored — with the full UBL payload and validation report on file for audit.
Manual import & scheduled polling
Paste or upload a supplier's XML in the import wizard with a parsed preview, or enable the hourly polling cron to pull every receiver connection automatically. Both share the same parse, validate and map pipeline.
Built on the E-Invoice Core Engine
Reuses the shared engine REST transport, validation framework and logging, and the Oman Fawtara e-Invoice connector's VATIN validator, so the sending and receiving sides share one source of truth. Compatible with Odoo 18 & 19, Community and Enterprise. No Enterprise dependency.
Disclosure: this module only pulls invoice data from the accredited provider receiver endpoint you configure. Your API key is bring-your-own-key, stored only on your database and never bundled or sent anywhere else. Phase dates per the official Oman Tax Authority e-invoicing FAQ.
Screenshots
Inbound Fawtara Documents Li
Inbound Document Mapped To A
Vendor Bill Auto Created Fro
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4337 |
| Technical Name |
l10n_om_fawtara_inbound |
| 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