GlobalLocalization/Oman

Oman Fawtara Inbound

Name: Oman Fawtara Inbound
Price: 135 USD

Receive Oman Fawtara PINT UBL e-invoices from your accredited provider and import them as vendor bills

Odoo 20.0Odoo 19.0Odoo 18.0

Oman Fawtara Inbound

Receive supplier e-invoices from your Fawtara accredited provider and import them straight into vendor bills

In the Oman Tax Authority Fawtara Peppol 5-corner network the buyer receives supplier invoices from its own accredited service provider. This connector pulls those PINT Oman UBL 2.1 documents, validates and reconciles them, and drafts the matching vendor bill — ready for the Tier 1 go-live in 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 reporting reference the document arrived with is captured on the bill, under its own label so it is never confused with the reference of a document you filed.

Provider mailbox over BYOK transport

List the accredited-provider inbox, fetch each document and acknowledge receipt so it is not re-delivered. The sandbox and production base URLs are yours to enter and no host is pre-filled, because Fawtara standardises the network between providers, not the interface between you and yours; 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. A line whose VAT rate has no matching purchase tax in your chart stops the document, naming the line and the rate, instead of drafting a bill with no VAT on it.

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. The bill total is then compared with the total the supplier document states, and any difference is stated on the document, in both chatters and as a filter in the workspace. Polling and automatic drafting follow the two switches on the company: Enable Fawtara Inbound and Auto-create Vendor Bills.

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 & 20, 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. Rollout dates: Phase 1 August 2026 (one hundred large VAT-registered companies), Phase 2 February 2027 (all large VAT-registered companies), Phase 3 August 2027 (all remaining VAT-registered taxpayers), Phase 4 February, year to be announced (government institutions and entities), per the Oman Tax Authority Fawtara FAQ page (tms.taxoman.gov.om) and the FAQ PDF last updated 30 June 2026, both read on 5 September 2026.

Screenshots

The inbound workspace: supplier documents with their parsed header, each one at its own point in the received - validated - vendor bill lifecycle.

Inbound total reconciliation refusing a tampered document

Total reconciliation refuses a document whose stated LineExtensionAmount does not match the sum of its lines, before it can become a payable.

Draft vendor bill created from the supplier UBL

The draft vendor bill mapped from the supplier's PINT UBL, linked back to the inbound document it came from.

New receiver connection with no pre-filled host

A new receiver connection. Nothing is pre-filled with a Tax Authority host, because in a 5-corner network there is none to default to: the base URLs and the key come from your own accredited provider.

Support: support@pokutsoft.com

Update date: 2026-09-05