Fawtara penalties and non-compliance in Oman

A penalty for failing to issue a compliant e-invoice already exists in Oman law. It is not waiting for a new Fawtara regulation. It was added to the VAT Executive Regulations in October 2022, and from your rollout date it applies to the electronic invoices you are required to issue.

There are two layers: an administrative fine the Tax Authority can impose, and a criminal penalty for deliberate failure that a court imposes.

The administrative fine: Article 202(4)

Article 202 of the VAT Executive Regulations lets the Chairman of the Tax Authority impose an administrative fine of not less than OMR 500 and not more than OMR 5,000 in the cases it lists.

Decision No. 456/2022, issued on 13 October 2022, added a fourth case to that list:

Failure to issue the tax invoice in accordance with the requirements specified in these Regulations and any requirements the Authority specifies for issuing the electronic tax invoice.

The same decision defines the electronic tax invoice as a tax invoice issued in a structured electronic format through an electronic means, containing at least the information the Regulations and the Authority specify. Decision No. 189/2026 then set the dates from which those electronic requirements apply: 1 April 2027 for taxable persons whose annual supplies exceed OMR 5 million, and 1 October 2027 for everyone else.

Three things about the wording matter:

• The fine is discretionary. The text says the Chairman may impose it. It is a power, not an automatic charge on every failure.
• It is set per case. The fine is imposed "in the following cases", within a range of OMR 500 to OMR 5,000. The text does not multiply it by the number of invoices. Claims of a fine "per invoice" do not come from the Regulations.
• It is not new. The provision has been in force since October 2022. What changes on your rollout date is that the electronic-invoice requirements it refers to start to apply to you.

The criminal penalty: VAT Law Article 100

Article 100 of the VAT Law sets imprisonment of 2 months to 1 year, a fine of OMR 1,000 to OMR 10,000, or both, for a list of deliberate acts. Three of them concern invoices:

• deliberately failing to issue a tax invoice that must be issued (item 8);
• deliberately stating a tax amount on an invoice other than the tax due (item 9);
• deliberately failing to keep tax invoices and documents for the required period (item 7).

On a repeat offence, the court may double the fine.

Every item in Article 100 turns on the word deliberately. It is aimed at intent, not at mistakes. A failure that is not deliberate can still fall under the administrative fine in Article 202(4).

How the two fit together

	Administrative fine	Criminal penalty
Source	VAT Executive Regulations, Art. 202(4)	VAT Law, Art. 100
Imposed by	The Chairman of the Tax Authority	A court
Trigger	Failing to issue a tax invoice per the requirements	Deliberate acts, including deliberately not issuing a required invoice
Amount	OMR 500 – 5,000, per case	2 months – 1 year, and/or OMR 1,000 – 10,000
Intent required	No	Yes
Legal basis	Added by Decision No. 456/2022, October 2022	Royal Decree No. 121/2020

What is not confirmed yet

The penalties themselves are set out in law. How they will be applied is not:

• how the Authority will use its discretion within the OMR 500–5,000 range, and which failures it will treat as priorities;
• whether there will be any grace period after a rollout date;
• whether a buyer can lose its input-VAT deduction because a supplier's invoice was not a compliant e-invoice — the Tax Authority has not stated this, so treat it as unconfirmed;
• whether invoice blocking, service-provider suspension or other operational controls will be used alongside fines.

Non-compliance risks to prepare for

The fine attaches to failing to issue a compliant tax invoice. These are the ways that usually happens in practice:

Risk area	What can go wrong	Preparation step
Deadline readiness	The business reaches its rollout date without a working provider or integration path.	Check the OTA rollout period and work backward with a six-month readiness plan.
Invoice format	The business keeps issuing only PDF, paper, or spreadsheet invoices.	Map invoice data to the approved structured format and test validation early.
Reporting timing	Invoices are issued but not reported through the required Fawtara flow on time.	Confirm B2B, B2C, export, import, credit note, and debit note timing with the provider path.
Data quality	Customer VATINs, tax categories, item data, or branch data fail validation.	Clean master data before technical integration starts.
Archiving	The business cannot retrieve structured invoice records and correction history later.	Define archive ownership, export format, retention process, and provider-exit terms.
Staff process	Finance, sales, or branch teams keep using old invoice workflows after go-live.	Train the people who issue invoices and rehearse exception handling before the deadline.

How to talk about penalties accurately

Accurate:

• "Article 202(4) of the VAT Executive Regulations allows an administrative fine of OMR 500 to OMR 5,000 for failing to issue a tax invoice according to the e-invoicing requirements."
• "Deliberately failing to issue a required tax invoice is a criminal offence under VAT Law Article 100."
• "The administrative fine is discretionary and is set per case."

Inaccurate:

• "Oman has no penalty for e-invoicing yet."
• "The fine is OMR 5,000 per invoice."
• "Any mistake on an e-invoice is a crime."
• "There will be no penalties during a grace period."

A practical compliance plan

The work that avoids the fine is the same work that makes e-invoicing possible.

1. Confirm VAT registration and rollout period.
2. Assign an internal Fawtara owner.
3. Inventory every invoice source: ERP, POS, accounting software, Excel, manual templates, and branch systems.
4. Separate B2B, B2C, export, import, self-billing, credit note, and debit note flows.
5. Map invoice data to the Oman requirements.
6. Select and test the provider or compatible ERP path.
7. Decide how structured records, validation status, timestamps, and correction history will be archived.
8. Train staff and run a go-live rehearsal.
9. Re-check OTA updates before the deadline.

What to monitor before launch

• any further amendment to the VAT Executive Regulations or the VAT Law;
• any enforcement guidance from the Tax Authority on how it applies Article 202(4);
• the OTA e-invoicing FAQ and portal;
• the OTA rollout checker for your VAT number;
• the final PINT OM and Oman technical documentation, since the fine refers to the Authority's requirements.

Next step

Check your rollout period first, then work backward from that date. The fine attaches to failing to issue a compliant invoice, so the best protection is having your invoice data, provider path, reporting process and archive in place before your go-live.