Oman e-invoicing API (Fawtara)

Connect your invoicing system to Fawtara, Oman's e-invoicing system, through the Complyance API. Onboard the company, send each invoice in GETS and follow its status, starting in the sandbox environment.

Fawtara is the e-invoicing system of the Oman Tax Authority (OTA). Invoices are exchanged as structured data over Peppol, a network for exchanging business documents, using PINT OM, Oman’s Peppol invoice specification. You send each invoice to Complyance in GETS, the common invoice format used across countries. Complyance checks it against the PINT OM rules for the document type and produces the Omani e-invoice. A PDF or scanned invoice on its own is not an e-invoice.

Oman is available in the sandbox environment. Use it to build and test your integration.

Onboard a company Register the company's Peppol participant ID and its invoice source. Check invoice fields Find the GETS fields accepted for Oman. Send a sandbox invoice Submit a complete Omani tax invoice and read the response. Fix validation errors Find the PINT OM rule behind an error and correct the invoice.

Who is in scope?

The OTA introduces Fawtara in phases, starting with a pilot for selected large taxpayers and extending to all VAT-registered businesses. Check the OTA’s e-invoicing page for the phase that applies to your business. Do not use this page to decide a legal start date.

Send an Omani invoice

Onboard the company with its VAT identification number (VATIN), OM followed by 10 digits. Onboarding creates the company’s Peppol participant ID and links the source that sends its invoices.
Choose the document type from the table below. It goes in the request’s documentType.
Use the Oman field reference to map your invoice data to GETS.
Send a sandbox request to Unify, and correct any validation errors. An HTTP 200 means the invoice passed validation and was stored; it does not mean the buyer received it.
Check the document status with the returned documentId.

Document types

Set documentType.base, and add modifiers or a variant for the transaction. Send modifiers: [] when none applies.

Document	`base`	`modifiers` or `variant`
Tax invoice	`tax_invoice`
Simplified tax invoice	`simplified_invoice`
Credit note	`credit_note`
Simplified credit note	`simplified_credit_note`
Debit note	`debit_note`
Simplified debit note	`simplified_debit_note`
Prepayment invoice	`tax_invoice`	variant `advance`
Simplified prepayment invoice	`simplified_invoice`	variant `advance`
Self-billed invoice	`tax_invoice`	`self_billed`
Self-billed credit note	`credit_note`	`self_billed`
Export invoice	`tax_invoice`	`export`
Import of goods invoice	`tax_invoice`	`import_goods`
Import of services (reverse charge) invoice	`tax_invoice`	`reverse_charge`
Third-party invoice	`tax_invoice`	`third_party`
Summary invoice	`tax_invoice`	`summary`
Continuous supply invoice	`tax_invoice`	`continuous_supply`
Deemed supply invoice	`tax_invoice`	`deemed_supply`
Profit margin invoice	`tax_invoice`	`margin_scheme`
Profit margin self-invoice	`tax_invoice`	`self_billed` and `margin_scheme`
E-commerce invoice	`tax_invoice`	`e_commerce`
Special zone supplies invoice	`tax_invoice`	`special_zone_supplies`

A prepayment invoice sends the variant beside the base:

Prepayment invoice document typejson

{ "base": "tax_invoice", "modifiers": [], "variant": "advance" }

Some combinations are not allowed. self_billed, import_goods and reverse_charge work only with tax_invoice or credit_note. summary, export and margin_scheme need a full document, not a simplified one. The advance variant works only with tax_invoice and simplified_invoice. Unify rejects any other combination.

Self-billed documents, imports of goods and imports of services under reverse charge follow the PINT OM Self-Billing specification. Every other document follows the PINT OM Billing specification.