Skip to content
Guide 14 min read

VAT accounting and POS software in Oman: what it must do, and how to get it ready for Fawtara

By Manager & CEO, SmartTech Studio

Value Added Tax has applied in the Sultanate of Oman since 16 April 2021. Five years on, most VAT-registered businesses have some system that produces tax invoices and a quarterly return. The question many of them are now asking is whether that system is good enough: whether it applies the rules correctly every time, whether it can survive an audit, and whether it will cope with Fawtara, Oman’s e-invoicing programme, when it becomes mandatory in 2027.

This guide is for owners, finance managers and operations leads in Oman who are choosing or upgrading VAT accounting software or a POS system. It sets out what the law asks of your invoices, returns and records, translates that into features you can test in a demo, covers the specific problems of retail tills and branches, and compares packaged software with a custom build. The last sections give a realistic implementation order and what it costs.

SmartTech Studio is a software house based in Abu Dhabi. We serve clients in Oman remotely from Abu Dhabi and do not have an office in Oman; our approach to the Omani market is on our Oman page. We build and connect ERP, accounting and POS systems; we are not tax advisers. What follows is general information, not tax advice. The figures were checked against published sources in November 2026, and you should confirm the treatment of your own supplies with your tax adviser or the Oman Tax Authority.

Which Omani VAT rules must your software implement?

Oman’s VAT Law was issued by Royal Decree No. 121/2020 and its Executive Regulations by Decision No. 53/2021, both later amended. The law follows the GCC framework agreement, so a business that knows UAE or Saudi VAT will recognise the shape. The details, however, are Omani, and software configured for another GCC country will be wrong in small ways that add up.

The standard rate is 5%. Your system needs at least four tax treatments, not one: standard-rated at 5%, zero-rated at 0%, exempt, and out of scope. The difference between zero-rated and exempt matters most. Both show no VAT on the invoice, but a zero-rated supply keeps your right to recover input VAT on the related costs, while an exempt supply does not. Software that lumps them together under a single “no VAT” code will produce a wrong return sooner or later.

Zero-rating applies to certain transactions in defined categories, including exports of goods and services, international transport of goods and passengers, certain basic food items, certain medicines and medical equipment, investment gold, silver and platinum, oil, oil derivatives and gas, and some supplies into special zones. Exemption covers certain financial services, healthcare and education services, local passenger transport and some residential property, including residential rent. Each category has conditions, and the food and medicine lists are set by specific decisions, so the right approach in software is a tax code on every item, chosen by someone who has read the rules, never a guess at the till.

Registration rules decide who needs the system at all. Registration is mandatory when your annual taxable supplies exceed, or are expected to exceed, OMR 38,500. Voluntary registration is possible above OMR 19,250. A business close to the mandatory line needs software that can report rolling twelve-month supplies, so the owner sees the threshold coming instead of finding out after the fact.

Finally, the system must know your own tax position: your VAT registration number, your tax periods, and whether you have any partially exempt activity, because a business making both taxable and exempt supplies has to apportion its input VAT. If your accounting package cannot apportion, your finance team will do it on a spreadsheet each quarter, and that spreadsheet will be the weakest part of your audit trail.

What must a tax invoice in Oman show?

Every taxable person must issue a tax invoice for each taxable supply, including deemed supplies and advance payments. The Executive Regulations list what a full tax invoice must contain. In summary: the words “tax invoice”; the dates of issue, supply and payment; a sequential serial number; the supplier’s and the customer’s names, addresses and tax identification numbers; a description of the goods or services and their quantity; the date of any advance payment; the consideration excluding tax; the tax rate; any discount or state subsidy; the taxable value; and the VAT due.

For software, three of those items cause most of the trouble. The serial number must be sequential and unique, which rules out letting each branch invent its own numbering by hand. The customer’s tax number must be captured and validated for business customers, which means your customer master data has to hold it. And the dates of supply and payment can differ from the invoice date, so the system has to store all three rather than assume they are the same day.

The regulations also allow a simplified tax invoice with fewer contents, which is what most retail receipts are. This is not automatic: according to the 2021 regulations it needs the Tax Authority’s prior approval and must meet set conditions, and those conditions have been amended since. If your business issues simplified invoices, check the current conditions and keep the approval on file, and make sure your POS prints the simplified format only where it is allowed and switches to a full tax invoice when a business customer asks for one.

Amounts in Omani rials carry three decimal places, because the rial divides into 1,000 baisa. A price is 1.250 OMR, not 1.25. Software built for two-decimal currencies, such as many products designed around the dirham or the riyal, can round VAT to the nearest 10 baisa without anyone noticing, and the error shows up as a small, persistent difference between your invoices and your return. Ask any vendor to show an invoice with three-decimal line amounts, a line discount and 5% VAT, and check the totals by hand.

On language, the published summaries we checked do not state that every invoice must be in Arabic. They do state that records may be kept in another language but must be available in Arabic if the Tax Authority asks. In practice, bilingual Arabic and English invoices and reports are the safe default in Oman: your customers, your auditors and the Authority can all read them, and you avoid translating records under time pressure during an audit. Arabic product names and customer names also need correct right-to-left printing on receipts, which is worth testing on the actual printer.

VAT returns, records and the audit trail

VAT returns in Oman follow calendar quarters: January to March, April to June, July to September and October to December. The return is filed electronically through the Tax Authority’s portal, and the return and the payment are due within 30 days after the end of the quarter. Published summaries add that a deadline falling on a weekend or public holiday moves to the next working day.

Good software turns that into a routine rather than a project. It should produce a draft return that maps each tax code to the right box, with a drill-down from every box to the invoices behind it. It should lock a period once the return is filed, so that a late correction goes into the next period as an adjustment instead of silently changing a return you already submitted. And it should reconcile the VAT accounts in the ledger to the return, because a difference between the two is the first thing an auditor looks for.

Records must be kept for ten years in general, and longer for real estate businesses, which published summaries put at fifteen years. That includes tax invoices issued and received, credit notes, import and export documents, customs records, inventory records and the ledgers themselves. Electronic records are allowed under conditions. For software, ten years is longer than the life of most systems, so the questions to ask are practical: can you export every invoice and journal in a readable, standard format, and will the archive still open after you change systems?

Penalties are a reason to take this seriously, not a reason for alarm. Published summaries of the law cite an administrative penalty of OMR 500 to OMR 5,000 for late filing and 1% a month on late payment, alongside separate penalties for invoicing failures. Check the current figures with your adviser before relying on them; the practical lesson is that most penalties come from missed dates and missing documents, which is exactly what a well-configured system prevents.

Imported services and the reverse charge

When a VAT-registered business in Oman buys services from a supplier outside Oman, such as software subscriptions, cloud hosting, advertising, consultancy or a design agency abroad, the supplier normally does not charge Omani VAT. Instead, the Omani business accounts for the VAT itself under the reverse charge: it reports output VAT on the service and, where it is entitled, recovers the same amount as input VAT in the same return.

For a fully taxable business the net effect is usually nil, which is exactly why the reverse charge gets forgotten. It still has to appear on the return, and it does not net to nil for a business with exempt activity, such as a clinic, a school or a financial services firm, which can recover only part of its input VAT. For those businesses an unrecorded reverse charge is real tax that has not been paid.

Your accounting software should therefore have a reverse-charge tax code on purchases, post both sides automatically when that code is used, and show reverse-charge amounts separately in the return workings. It should also make it easy to flag a foreign supplier at the supplier level, so that the code is suggested every time a bill from that supplier is entered. Which purchases fall under the reverse charge, including some purchases from other GCC states, is a question for your adviser; the software’s job is to apply the answer consistently.

Imports of goods are handled separately, through customs. The VAT on goods imported into Oman is accounted for under the rules for imports, and your system needs to record the customs documents and the import VAT so that it can be recovered where allowed. A trading company that imports most of its stock should test this flow in any demo, with a real customs declaration.

What makes a POS system VAT-ready in Oman?

Retail is where VAT rules meet speed. A cashier serving a queue cannot think about tax codes, so the POS has to get everything right by itself, thousands of times a day, in every branch. These are the points we test when we review or build a POS for an Omani retailer or restaurant:

VAT-inclusive pricing done properly. Shelf prices in retail are usually shown including VAT, so the POS must back-calculate the net amount and the 5% VAT from the inclusive price, to three decimals. An item priced at 1.050 OMR including VAT is 1.000 net plus 0.050 VAT. Rounding should be applied by a defined rule, either per line or per invoice, and the same rule must be used by the POS, the online store and the accounting system, or the totals will not reconcile.

Receipts that meet the invoice rules. The receipt is a tax document. It needs the sequential number, your tax number, the date, the items, the VAT and the total, in the simplified format where approved and the full format when a business customer gives a tax number. Reprints should be marked as copies, and the original should never be editable.

Returns and voids as documents, not deletions. A refund must create a credit note that references the original sale. Deleting a line after the receipt has printed, or editing a closed sale, breaks the audit trail and, from 2027, will also break the link with e-invoicing.

Offline mode with safe numbering. Networks fail. A good POS keeps selling offline, keeps numbering invoices without collisions, usually by giving each terminal its own number range, and syncs everything when the connection returns. Ask the vendor what happens if a terminal is offline for a whole day, and how duplicates are prevented.

Branch and terminal reports. Daily Z-reports per terminal, sales and VAT by branch, cash and card reconciliation, and a consolidated VAT summary for the company. If each branch runs its own database, these reports become a manual merge every quarter.

One product and price list. The tax code belongs to the product, maintained centrally, not typed at each till. The same record should feed the online store; we cover the shared-stock setup in getting a POS and stock ready for the sale season, and the accounting side in our POS and ERP integration guide. If you also sell online in Oman, see our guide to building an online store in Oman for the payment and checkout side.

How do you get your software ready for Fawtara?

Under Decision No. 189/2026, which amends the VAT Executive Regulations, e-invoicing becomes mandatory on 1 April 2027 for VAT-registered businesses whose annual supplies exceed OMR 5 million, and on 1 October 2027 for all other VAT-registered businesses. Oman’s programme, Fawtara, runs on the Peppol network: you connect through an accredited service provider rather than directly to the Tax Authority, invoices between businesses travel as structured data, and consumer receipts are expected to carry a QR code, with the sale reported to the Authority.

The important point for anyone buying software now is that Fawtara does not replace VAT invoicing; it is VAT invoicing delivered as data. Every rule in the sections above still applies, and a structured invoice is checked automatically. Errors a person used to fix quietly, such as a missing customer tax number, the wrong tax code on a product or a rounding difference of a baisa, become rejected invoices.

So a system that is “Fawtara-ready” has four things. Clean master data: customer tax numbers, product tax codes, units and addresses held in one place. Immutable documents: invoices are never edited, and corrections are credit or debit notes that reference the original. An integration path: either the vendor commits in writing to supporting Fawtara through a named provider, or the system exposes an API that a provider connection can be built on. And three-decimal accuracy end to end, from the till to the provider.

To see which date applies to you and which steps remain, use our free Oman e-invoicing deadline checker. The full preparation sequence, from listing every system that issues an invoice to testing returns and credit notes, is in our guide to e-invoicing in Oman. If you choose a new system before 2027, make Fawtara support a contract condition, not a promise on a slide.

Off-the-shelf VAT software or a custom system?

For most small and medium businesses in Oman, packaged accounting software with an Omani VAT localisation is the right core. The vendor tracks the rules and ships the updates, which is valuable when the rules are about to change for e-invoicing. Custom software earns its place around that core, where the business works differently from the package: a POS for a particular retail or restaurant model, a branch network, a distribution flow, a customer app. The table below is a general orientation, not a ranking.

Packaged vs custom VAT and POS software in Oman
FactorPackaged softwareCustom system
Omani VAT rulesMaintained by the vendor if it has an Omani localisationBuilt to your tax codes; you or your partner maintain them
Fawtara e-invoicingUsually delivered as a vendor update; get the date in writingConnected through an accredited provider by API
Three-decimal rials and ArabicVaries by product; test both in the demoDesigned in from the start
POS workflowsStandard retail and restaurant flowsFits your counter, menu, pricing and branch model
Upfront costLow: subscription per user or terminalHigher: a project, from AED 25,000 excl. VAT with us
Best whenYour processes are standardYour operations are the business, and no package models them

The common and sensible answer is both: packaged accounts that own VAT and e-invoicing, and custom operational systems, such as the POS, warehouse or ordering app, connected to them through an API so that every sale arrives in the ledger with the right tax code. The trade-offs are set out in more detail in custom versus off-the-shelf ERP in the Gulf.

Whichever you choose, ask every vendor the same questions. Show me an Omani tax invoice and a simplified invoice from your system. Show me a 5% VAT calculation on three-decimal prices with a discount. Show me the VAT return working with drill-down. Which accredited provider will you use for Fawtara, and by what date? Can I export all my invoices and journals in a standard format if I leave?

A realistic implementation order

1. Confirm your tax position. Registration number, tax periods, any exempt or partially exempt activity, any simplified-invoice approval, and which Fawtara date applies to you. Your adviser signs this off.

2. Map every system that issues an invoice or receipt. Each POS terminal and branch, the online store, the accounting package, any delivery or ordering app, and the spreadsheet someone uses for corporate customers.

3. Build the tax code table. Standard 5%, zero-rated, exempt, out of scope and reverse charge, each mapped to a return box, with a short note on when to use it. Then assign a code to every product and service.

4. Clean the master data. Customer tax numbers, Arabic and English names, addresses, product units and prices to three decimals. This step decides how smoothly e-invoicing goes later.

5. Configure and test with real scenarios. A cash sale, a card sale, a sale to a business with its tax number, a discount, a return, an export, a reverse-charge purchase and an offline sale, then a full draft return for one quarter.

6. Run in parallel for one period. Keep the old process for one month or one quarter, compare the VAT figures line by line, and switch off the old process only when the two agree.

7. Connect to Fawtara before your date. Choose the provider, connect, test every document type in every branch, and train the counter and finance teams on corrections and failed submissions.

What does it cost, and how do we work with Omani businesses?

Packaged accounting and POS software is usually a monthly or annual subscription per user or per terminal, plus setup and training from a local partner. The real cost is often in the configuration and the data cleaning, not the licence, so ask for those days to be quoted separately.

A custom or hybrid system is a project. Our ERP, CRM and POS systems start from AED 25,000 excl. VAT for a focused system. Connecting systems you already run, for example a POS to your accounting package, or both to a Fawtara provider, is usually a smaller piece of work, and we will say so if that is all you need. We quote in AED, and larger projects are scoped after a short discovery, because the number of branches, systems and document types decides the effort.

We work with clients in Oman remotely from Abu Dhabi, in Arabic and English, over video calls, shared test environments and on-site visits when a project needs them; we do not claim an office in Oman. More on how that works is on our Oman page. We are not tax advisers or an accredited e-invoicing provider. Your adviser decides the treatment and your provider carries the e-invoices; we make your systems apply that treatment consistently and connect them to each other.

If you are choosing or upgrading VAT software, the most useful first step is a list of every system that issues an invoice, with a sample invoice from each. Send that to us through our contact page and we will tell you plainly where the gaps are.

FAQ

What is the VAT rate in Oman, and who must register?

The standard rate is 5%, under the VAT Law issued by Royal Decree No. 121/2020. Registration is mandatory when annual taxable supplies exceed, or are expected to exceed, OMR 38,500, and voluntary registration is possible above OMR 19,250.

Why do Omani invoices need three decimal places?

The Omani rial divides into 1,000 baisa, so prices and VAT are shown to three decimals, such as 1.250 OMR. Software built for two-decimal currencies can round VAT incorrectly, creating small differences between invoices and the VAT return.

When is the VAT return due in Oman?

Returns are filed quarterly through the Tax Authority portal, and the return and payment are due within 30 days after the end of each quarter. Records, including invoices, should generally be kept for ten years.

Can a POS print simplified invoices in Oman?

Yes, where the conditions in the Executive Regulations are met and the Tax Authority has approved it. The POS should still issue a full tax invoice when a business customer provides its tax number, and refunds must be credit notes, not deletions.

When does Fawtara e-invoicing start in Oman?

Under Decision No. 189/2026, it starts on 1 April 2027 for VAT-registered businesses with annual supplies above OMR 5 million and on 1 October 2027 for all other VAT-registered businesses, through accredited service providers on the Peppol network.

How much does a custom VAT-ready POS or accounting system cost?

Custom ERP, CRM and POS systems from SmartTech Studio start from AED 25,000 excl. VAT. Connecting existing systems to each other or to a Fawtara provider is usually smaller. We serve Oman remotely from Abu Dhabi and quote in AED.

العربية