Here’s Everything You Need To Know About E-Invoicing For Businesses In Oman

Oman has moved e-invoicing from policy discussion to law. Under Tax Authority Decision No. 189/2026, VAT taxable persons will have to issue tax invoices in an approved, secure electronic format – first from 1 April 2027 for businesses with annual supplies above OMR5 million, and from 1 October 2027 for those at or below that threshold.

A voluntary pilot involving 100 selected companies is due to begin at the end of August 2026. This article is intended to be a practical guide to Decision 189/2026, the rollout dates, the Peppol five-corner model and the work companies must begin now.

What is E-Invoicing?

E-invoicing is not simply emailing a PDF or replacing a printed invoice with a scanned copy. It is the creation, validation, exchange and storage of invoice data in a structured digital format that computer systems can read automatically. Under Fawtara, the supplier’s system sends the invoice through an accredited service provider; the buyer receives it through its own provider; and specified tax data is transmitted to the Oman Tax Authority (OTA) in parallel.

The reform is a major change to the plumbing of business in Oman. It will affect finance teams, tax departments, point-of-sale systems, ERP platforms, procurement workflows, customer master data, cybersecurity controls and relationships with suppliers and buyers. Its promise is faster processing and cleaner data. Its risk, for businesses that treat it as a last-minute accounting update, is operational disruption at the point where sales are billed and VAT evidence is created.

First, a crucial correction: it is not yet a mandate for literally every company.

Public discussion has often shortened the rule to “all companies must use Fawtara”. The legally accurate formulation is narrower: Decision 189/2026 applies to taxable persons under Oman’s VAT regime. The OTA’s latest FAQ also states that non-VAT-registered sellers are not required to join the Fawtara network. Once all rollouts are complete, all VAT-registered taxpayers fall within the e-invoicing framework; a business that is outside VAT registration is not brought into Fawtara merely because it holds a commercial registration.

There are no general industry exemptions in the OTA’s current guidance. The dividing line for the two mandatory dates is annual supplies – not employee count, legal form, profit or the popular SME classification. Businesses should therefore confirm both their VAT status and the correct calculation of annual supplies instead of assuming their deadline from size labels alone.

The binding timetable

Why some published timelines differ: Earlier project material described a four-stage roadmap beginning with large taxpayers and later extending to SMEs and government entities. Decision 189/2026, published in Official Gazette No. 1660 on 9 August 2026, is the controlling legal timetable for VAT taxable persons and sets the two mandatory dates above. The August 2026 exercise is a voluntary pilot, not the general legal deadline.

What Decision 189/2026 changes

The decision amends the Executive Regulations of the VAT Law issued under Decision 53/2021. Its revised Article 143 requires a taxable person to issue a tax invoice in an approved and secure electronic format that preserves its integrity, storage and a unique number for each invoice. The obligation arises when making supplies – including supplies to a non-taxable person or private-use supplies by a taxable person – when making deemed supplies, when receiving full or partial payment before the supply date, and in other cases covered by the regulations.

The invoice must generally be issued no later than 15 days from the relevant event. It must also remain possible to verify the authenticity of its source and content and to read it throughout the retention period. The decision also applies the Article 143 timing to simplified tax invoices and allows the OTA to specify additional required data.

New provisions place continuity and security duties directly on the taxpayer, wherein companies must use an electronic system, protect it from intrusion and unauthorised access, prepare for emergencies and technical failures, and maintain mechanisms for restoring lost information so the system continues to operate efficiently.

OTA may grant a time-limited exception on a supported application and for reasons accepted by the Authority. That is not a blanket opt-out: the applicant must continue filing VAT returns correctly and on time and paying tax when due. Businesses should not build their implementation plan around receiving an exception.

What qualifies as an e-invoice… and what does not?

The machine-readable record is the legal and operational core. The OTA requires XML as the mandatory structured format, mapped to Oman’s PINT specifications. A PDF may be a human-readable representation, but it is not by itself an e-invoice. Nor is a Word document, image, scan, spreadsheet or manually prepared invoice that is uploaded after the event. The OTA FAQ is explicit that invoices must be issued electronically in the prescribed format rather than created manually and entered later.

A useful way to understand the difference is to compare a photograph of a table with the data inside a spreadsheet. A person can read both, but software cannot reliably validate, route and reconcile the photograph. Structured XML labels each field – supplier, buyer, VAT number, invoice number, dates, line items, tax category, taxable amount, VAT amount and totals – so different systems can process it consistently.

How Fawtara’s five-corner model works

Oman is implementing a Peppol-based five-corner model. Peppol is not a single invoicing app; it is an interoperability network and rule framework. Oman’s PINT specification provides the local business and tax rules, while accredited providers act as secure access points.

1. Corner 1 – Supplier: The seller creates the invoice from its ERP, accounting, billing or point-of-sale system in the required structured format.
2. Corner 2 – Supplier’s accredited service provider: The provider checks the invoice against the required format and business-rule validations, then routes it securely.
3. Corner 3 – Buyer’s accredited service provider: For network participants, the buyer’s provider receives and exchanges the validated invoice.
4. Corner 4 – Buyer: The buyer receives invoice data that can flow into accounts payable, matching and reconciliation processes.
5. Corner 5 – Oman Tax Authority: Specified tax data is reported to the OTA in parallel, creating near-real-time visibility without making the OTA the business’s invoice archive.

For exports, where the overseas customer and its provider are outside the Oman network flow, the OTA’s FAQ describes a C1-to-C2-to-C5 path: the Omani supplier uses its provider to report the tax data, while the invoice is shared with the foreign customer under the existing commercial process. For imports, current guidance points to self-billing for reporting.

B2B, B2C and B2G: the practical differences

For business-to-business (B2B) transactions, the structured invoice moves through the two accredited providers and is reported in real time. For business-to-consumer (B2C) transactions, the buyer normally has no access point. The seller still submits the invoice to its provider for reporting to the OTA, while the customer can receive a compliant human-readable version through the existing channel, including paper or PDF. The OTA’s 30 June 2026 FAQ states a 24-hour B2C submission window and requires a separate e-invoice for every B2C invoice; consolidated B2C invoices are not allowed.

The human-readable B2C invoice must carry the prescribed QR code. The OTA says the taxpayer generates the QR code, and that it is intended to support future authenticity checks through a mobile application. The structured XML itself does not display the QR code. For B2G transactions, the same Fawtara framework is designed to support exchanges with government bodies, although organisations should continue watching for any transaction-specific onboarding instructions.

How can a company can become compliant?

The work begins with process discovery. Companies need to understand where invoice data originates, who approves it, how credit notes are created, how customer identities are maintained and what happens when systems or connectivity fail. A practical programme can be organised into the following steps:

1. Confirm scope and deadline. Verify VAT registration, annual supplies and the rollout period using the OTA’s VATIN rollout checker. Review all entities in a VAT group; current guidance requires group members sharing one VAT number to follow the procedures and use the same provider.
2. Map every invoice journey. Catalogue B2B, B2C, B2G, export, import/self-billing, advance-payment, deemed-supply, full, simplified, credit-note and debit-note scenarios. Include branches, e-commerce channels and high-volume POS environments.
3. Audit master data. Validate VATINs, legal names, addresses, item descriptions, tax categories, exemption and zero-rating reasons, currencies, units, payment terms and buyer identifiers. Structured validation exposes data weaknesses that PDFs often hide.
4. Assess the current system. Determine whether the ERP, accounting package or POS can generate the required Oman PINT XML, receive invoices, preserve unique numbering, produce a compliant human-readable view and manage acknowledgements and rejected documents. The OTA says an existing ERP may be retained if the provider can integrate it.
5. Select an accredited service provider. Use only providers shown as accredited by the OTA. Compare integration approach, implementation support, security, service levels, data location, archiving, dashboard and reconciliation functions, outage handling, portability and pricing. OTA does not set provider charges; providers may use subscription or transaction-based models.
6. Link through Fawtara. Request association with the chosen provider through the Fawtara portal. Current guidance allows a taxpayer to connect to one provider at a time, disconnect and switch, subject to the portal process.
7. Build and test. Map source fields to PINT Oman, test business and Schematron rules, validate tax calculations and exercise end-to-end exchange with realistic volumes. Test Arabic and English outputs, rounding, discounts, credit notes, duplicates, late invoices and incorrect buyer data.
8. Design controls and continuity. Set ownership for rejection queues, exception resolution, access permissions, change management, certificate management, backups, disaster recovery and audit logs. Prepare a documented fallback that complies with future OTA outage guidance.
9. Train users and trading partners. Finance, sales, procurement, tax, IT, internal audit and customer-service teams need role-based training. Buyers and suppliers should be told which identifiers and electronic channels will be required.
10. Go live early enough to stabilise. Run parallel reconciliations between sales ledgers, invoice XML, provider acknowledgements, customer receipts and VAT returns. Do not wait for the statutory date to discover rejected invoices or incomplete master data.

What to ask a service provider

• Is your accreditation live and visible on the OTA’s official list, and which Oman PINT release do you support?
• Can you integrate with our exact ERP/POS version without replacing it, and who owns the connector?
• How do you price implementation, subscriptions, invoice volumes, storage, support and future changes?
• What are your uptime commitment, disaster-recovery targets and process during network or customer-system outages?
• Where is data processed and stored, how is it encrypted, and what access and audit logs are available?
• How are rejected invoices, acknowledgements, duplicates, cancellations, credit notes and debit notes handled?
• Can we export our full archive and audit trail in a usable format if we change provider?
• What testing, training, sandbox access and go-live support are included?

Compliance responsibility does not move to the provider

The accredited provider validates format and defined business rules, but it does not decide whether the underlying commercial transaction or tax treatment is correct. The OTA’s FAQ says responsibility for invoice compliance remains with the taxpayer. A technically valid XML invoice can still contain the wrong VAT rate, an unjustified exemption, an incorrect supply date or inaccurate customer data. Tax policy, approval controls and reconciliation therefore remain essential.

Once issued, an invoice is not simply deleted or overwritten. Adjustments are made through an electronic credit note or debit note. If an invoice is sent to the wrong buyer or VAT number, current OTA guidance is to issue a credit note to reverse it and then create a new invoice for the correct buyer. Historical invoices do not need to be uploaded merely because the company joins Fawtara.

Archiving: Fawtara is not your filing cabinet.

The OTA will receive tax data, but it will not act as the taxpayer’s invoice repository. The Authority states that taxpayers must store their own e-invoice records and make them available under VAT law. Oman’s VAT Law generally requires tax invoices, accounting records and books to be retained for 10 years following the end of the relevant tax year; longer periods can apply to capital assets and real-estate-related records, reaching 15 years.

An archive must preserve more than a visual PDF. Businesses should retain the authoritative structured invoice, its human-readable representation where used, validation outcome, delivery acknowledgements, correction documents and a reliable audit trail. Retrieval, readability, integrity and access throughout the legal period matter as much as storage capacity.

Cybersecurity and operational resilience become tax controls.

Decision 189/2026 expressly requires protection against hacking and unauthorised access, emergency measures, data recovery and continuity. That language has practical consequences. Access to invoice creation and master-data changes should follow least-privilege principles; integrations and credentials should be monitored; sensitive invoice data should be encrypted; and backups must be tested rather than assumed (as it often isn’t in day-to-day operations).

The greatest operational risk may not be an obvious cyberattack. It may be an expired certificate, failed API, incorrect configuration, duplicated numbering sequence or unmonitored rejection queue that stops legally valid invoices from reaching customers. Finance and IT teams should jointly define incident ownership, escalation times and evidence needed to prove what occurred.

Why Oman is moving to e-invoicing?

For the government, structured invoice data can improve VAT compliance, identify suspicious patterns, reduce fraudulent or fabricated invoices and give policymakers more timely economic information. It also narrows the gap between a transaction taking place and tax data becoming visible. That supports a more transparent and efficient tax system without relying only on later returns and audits.

For businesses in the Sultanate of Oman, the long-term value can be broader than compliance: automated invoice capture, fewer manual keying errors, faster matching between purchase orders, goods receipts and invoices, shorter approval cycles, better cash-flow forecasting, easier audits and more reliable inventory and customer data. The benefits will be strongest where companies redesign processes rather than recreate paper habits in digital form.

For consumers, a verifiable invoice improves confidence that VAT details and the seller’s identity are authentic further reducing scam invoices. For the wider economy, a common standard reduces friction between different accounting systems and can support digital procurement, trade finance and cross-border interoperability over time. The Peppol model gives Oman a framework already used internationally rather than a closed format that works only inside one vendor ecosystem.

The cost and complexity question

Large groups with multiple ERPs, shared-service centres and thousands of daily invoices may face substantial integration and testing work. Smaller businesses may need a simpler cloud or portal-based product, but they will still need accurate data, trained users, archiving and continuity controls. The OTA does not charge taxpayers for the service-provider layer and does not prescribe provider prices; commercial fees are set by the providers.

The most visible cost may be software, but hidden costs often arise from cleaning customer records, redesigning approvals, connecting legacy systems, training branches and resolving rejected documents. Conversely, a narrowly chosen solution that only “sends XML” may miss savings in receivables, payables, audit and reconciliation. Procurement decisions should therefore compare total implementation and operating cost with process value and switching risk.

Questions that remain and why companies must keep checking

The legal dates and core obligation are now clear, but operational guidance can continue to evolve. The OTA regularly updates its FAQs, PINT Oman specifications, provider accreditation information and portal manuals. Businesses should watch for final or revised instructions on exceptional outages, B2C handling, sector-specific scenarios, government transactions, technical versions, QR-code verification and enforcement practice.

Where older web pages conflict with newer documents, companies should use the latest official legislation and dated OTA guidance. For example, an earlier service-provider FAQ said the B2C reporting timeframe remained under discussion, while the newer 30 June 2026 FAQ specifies 24 hours. Version control should therefore be part of the compliance programme: record which specification, FAQ and provider documentation underpinned each design decision.

What business leaders should do now

The April 2027 deadline may appear distant, but system integrations compete for technical resources and depend on clean data and coordinated testing. Companies above OMR5 million in annual supplies should already have an executive sponsor, accountable project owner, confirmed scope, provider-selection process and test plan. Those in the October 2027 phase should use the additional six months to avoid a compressed implementation – not as a reason to postpone discovery.

Boards and senior management should ask for a readiness dashboard covering legal scope, entities, invoice volumes, system interfaces, master-data quality, provider status, test results, rejection rates, cybersecurity, business continuity and archival evidence. The go-live criterion should not be “the system generated an XML file”. It should be that every material invoice scenario can be issued, validated, delivered, corrected, reconciled and retrieved reliably.

A change to the operating system of commerce

Fawtara is sometimes described as a tax-reporting project, but that understates its reach. An invoice sits at the junction of a sale, the customer relationship, revenue recognition, payment, VAT, inventory and audit. Standardising that document changes how data travels across the organisation and between trading partners.

Handled well, the mandate can turn a compliance obligation into faster processing, stronger controls and better information. Handled late, it can expose weak master data, fragmented systems and unclear ownership at the moment a company needs to bill its customers. Oman has now fixed the legal destination and the dates. The strategic question for businesses is whether they approach Fawtara as a deadline or use it as a catalyst to modernise the financial processes on which their cash flow depends.

OERLive fact box

Sources and further reading

• Tax Authority Decision No. 189/2026 (Official Gazette No. 1660)
• Oman Tax Authority: Fawtara e-invoicing overview
• Oman Tax Authority: Fawtara FAQs, updated 30 June 2026
• Oman Tax Authority: VATIN rollout checker
• Oman Tax Authority: accredited service-provider area
• OpenPeppol: PINT BIS Billing Oman specifications
• Oman Tax Authority: VAT Law

Editorial note: This is a general explanatory article, not legal or tax advice. Definitions, technical releases and implementation instructions may be updated by the Oman Tax Authority.

All images in this article are AI-generated and are not intended to bear resemblance to any individual – either living or otherwise.