AWRA OpsHub Search

For Oman

Everyone is selling you the invoice you send. Fawtara also changes the ones you receive.

Oman did not copy the Saudi model. There is no clearance gate, no authority stamp and no number handed back before you may issue a document. What there is instead is a network — a decentralised five-corner Peppol arrangement in which invoices travel between accredited service providers as structured data, and the Tax Authority takes reporting from both ends of the transaction. Read that carefully, because the second half is the part the market has not priced in: as a buyer you acquire a reporting position on documents you did not create. Every vendor in Muscat is preparing you to send. Almost nobody is preparing you to receive.

Currency
Rial as a base preset, pegged — so the exposure sits on what you import in, not on what you sell in.
Tax
5% VAT preset with net, tax and gross split at capture. No Fawtara or Peppol connection — an accredited service provider handles the network.
Language
English only, no right-to-left layout. Usually survivable in Muscat; test it in a Sohar yard before you decide.
Support
Nairobi, in English, an hour behind Muscat — the overlap is your whole working day.

The fact the shortlists have not caught up with

Five corners, and the market is only selling you two of them

A clearance model has one seam and everybody can see it. A five-corner model has four, and they are easy to miss because none of them stops a sale. Worth drawing once, properly, because where your obligations land is not obvious from any vendor slide.

  1. Corner one

    The supplier's system

    Somebody else's ERP builds the document. You have no visibility of it, no influence over its quality, and no say in when it is sent. This is the first time in the history of your purchase ledger that has been true of a machine-readable document arriving in your books.

  2. Corner two

    Their accredited provider

    Their access point converts and signs it into the OM PINT format and puts it on the network. The Tax Authority is told about the sale from this side, separately.

  3. Corner three

    Your accredited provider

    Your own access point — you will have to appoint one, and it is registered against you in the network's directory so other people's systems know where to deliver. This is a procurement decision most buyers have not yet realised they need to make.

  4. Corner four

    You, receiving

    A structured supplier invoice lands in your business as data rather than as a PDF. That sounds like a gift. It is only a gift if you can already say, without a human, what was ordered, what was received, and at what price it was agreed — and if you cannot, all the network has done is deliver the wrong number faster.

  5. Corner five

    The Tax Authority

    Not in the middle of the transaction, which is the whole difference from the Saudi model — this is post-audit rather than clearance. It receives sales data from the supplier's side and purchase data from yours. Your purchase ledger stops being purely a management record and becomes a filing artefact.

Two things follow, and only one of them gets discussed. The first is that you will need an accredited service provider and it is not us — we say more about that below, in the plainest terms we can manage. The second is the one worth an hour of your board's attention: your accounts payable process is about to be reported on. Not audited eventually. Reported, from your side, as data. The gap between what you order and what you agree to pay is going to be considerably more visible than it has ever been, and the three-way match is where that gap is closed or is not.

Five questions worth putting to every vendor on your list — including us

  1. Who is our accredited service provider going to be, and has anyone actually started that conversation — or is it still sitting inside "the e-invoicing project"?
  2. When a supplier invoice arrives as structured data, which system holds it, and what happens to it before somebody approves payment?
  3. Can we say today, per invoice, whether the price billed is the price we agreed on the purchase order? How long does answering that take?
  4. What proportion of our purchase invoices arrive with no purchase order behind them at all? Most operators are surprised by this number.
  5. Which phase are we in, and did we confirm that with the Tax Authority rather than with a software vendor?

What this actually costs today

Four things that were already true before any of this

The mandate is new. None of these are, and they are what a buyer here is really paying for.

A purchase ledger that is about to be read by someone else

Buy-side reporting turns accounts payable from an internal control question into a filing one. Most operations we see could not produce, on demand, a list of invoices paid without a matching receipt — and that is exactly the shape of question the data will now support.

Four coasts and a thousand kilometres of them

Muscat, Sohar, Salalah and Duqm are not branches of one warehouse; Salalah is a two-day drive from the capital. Stock held in four places with no in-transit visibility is four businesses being reconciled monthly on trust.

Landed cost that settles into an overhead line

Freight, clearance, port handling and inland haulage arrive as separate invoices weeks after the goods. Absorbed into overhead, they leave you pricing against a unit cost that is confidently wrong in a direction nobody can measure.

Plant that is on a site, or possibly on another site

Compactors, generators, survey kit and tools move between jobs on a phone call. The second time you hire in something you already own is the moment the asset register stopped being a document and became a cost.

Corner four, in practice

What arrives, and what has to be true before you can pay it

A structured invoice removes the keying. It removes nothing else. Every question that made accounts payable slow is still open, and now it is open faster and against a document you cannot argue is illegible. These are the three that decide whether the network helps you or exposes you.

The price Check 01

What the network delivers

The supplier's system says the unit price is one thing. Your purchase order said it was another. The difference is usually small, usually defensible, and usually paid without argument because nobody has both numbers in front of them at the moment of approval.

What has to be true first

What has to be true first: the agreed price lives on an order, not in an email, and the approval screen shows the variance rather than requiring someone to remember it.

The quantity Check 02

What the network delivers

Billed against delivered. Twenty-four cartons invoiced, twenty-three received, one short-landed and signed for in a hurry on a phone at the gate. The credit note is owed and is almost never asked for, because the receipt record and the invoice never meet.

What has to be true first

What has to be true first: goods received are recorded at the point of receipt against the order they belong to, by the person who took delivery, working offline if the yard has no signal.

The authority Check 03

What the network delivers

Somebody ordered it. Whether that somebody was allowed to, at that value, is a question the invoice does not raise and the payment run does not either. In most operations this is discovered annually, by an auditor, in a sample.

What has to be true first

What has to be true first: the requisition and its approval are part of the same record as the order, and a threshold refuses rather than warns.

The discipline that makes an inbound network worth having

None of this is exotic and none of it is new. It is the ordinary purchase-to-pay discipline that gets deferred in every growing business because the pain is diffuse. Fawtara does not create the problem — it just makes the answer to "how do you know?" a thing you have to hold.

  1. A requisition with an approval that refuses above a threshold rather than warning and letting it through.
  2. A purchase order carrying the agreed price and quantity, so there is something to match against.
  3. A goods receipt taken where the goods actually arrive, offline if necessary, against the order rather than in a book.
  4. A three-way match that compares order, receipt and invoice and holds the exception rather than passing it on.
  5. Landed cost carried onto the consignment — freight, clearance and handling — so the unit cost you price against is the real one.
  6. The supplier's document attached to the transaction it belongs to, with the expiry dates on their trade licence and registrations watched rather than remembered.

The uncomfortable version of this argument, which we would rather state than have you discover: if your purchase process is currently held together by three people who know the suppliers, structured e-invoicing will not fix that and may quietly make it worse. Speed applied to an unmatched invoice is just a faster route to paying the wrong amount.

The buy side, in detail

What you would actually be buying

Each links to a fuller tour. The network itself — access points, PINT documents, tax data reporting — stays with the accredited provider who owns it, and the full boundary is drawn below.

Scope, stated plainly

No access point, no PINT, no Arabic, no SPF

We spend the top of this page arguing that the inbound half of Fawtara is under-served, so it is only fair to be equally direct that we are not the ones closing it.

Scope in Oman, stated before the demo

Running in the product today

  • The rial and a 5% VAT preset ship built in, with net, tax and gross separated line by line on purchases as well as sales, at the point of capture.
  • Three-way matching between order, receipt and invoice, with tolerances you set and exceptions that hold rather than pass through — the discipline this whole page argues for.
  • Stock across as many locations as you have — Muscat, the coast, site stores and vans — with governed transfers, in-transit visibility, batch and expiry tracking, blind counts and valued variance.
  • Landed cost on the consignment, so freight, duty, clearance and handling reach the unit cost instead of an overhead line.
  • An asset register with named custody — check-out and check-in, condition, maintenance history and depreciation — across plant, equipment, tools and vehicles.
  • Supplier documents attached to the transaction, with expiry dates on trade licences and registrations watched by the system rather than by somebody's calendar.

Not built — and the first two matter more here than anywhere

  • No Peppol access point, and we are not an accredited service provider. Not in Oman, not anywhere. We do not transmit on the network, we hold no accreditation with the Tax Authority, and we are not registered in any service metadata directory. Appointing an ASP is a separate purchase and it is not one we are bidding for.
  • We do not parse OM PINT or UBL XML, and we do not produce a Tax Data Document. This is the caveat that matters most on this page, so it goes second rather than being buried: everything above argues that the inbound side is under-served, and we are not closing it by consuming the network. What we do is the layer underneath — the order, the receipt and the match that a structured invoice gets compared against. If you read the page as a promise to ingest Fawtara traffic, we have mis-written it.
  • No Arabic interface and no right-to-left layout. English only, documents included. Muscat's commercial floor is comfortably bilingual and this is usually survivable; a site store in Duqm or a yard in Sohar is a different test. Run it with the people who would key transactions.
  • No Social Protection Fund calculation, no WPS wage file, no Omanisation tracking. Our maintained statutory payroll engine covers Kenya only. SPF contributions under the 2023 social protection law, wage files for the Ministry of Labour and Central Bank system, and quota positions all stay with an Omani payroll provider.
  • No corporate income tax computation and no statutory accounts. We do not calculate, apportion or file anything. We hold the costed records a computation is built from, and your adviser does the rest.
  • No customs or single-window integration. No connection to Bayan or any port community system at Sohar, Salalah or Duqm. Customs paperwork is attached to the consignment as evidence, not exchanged as data.

The shape of this list is deliberate. We are arguing that the buy side of Fawtara is the under-served half, and then telling you we do not touch the network that delivers it — which would be an odd thing to do if the argument were a sales device. It is not. The invoice arriving as data is somebody else's build and a fairly ordinary one; whether your business can say what it owes and why is the part that has never been solved by a file format. If you want both from one vendor, buy locally and buy well. If the second half is the one keeping you up, that is the conversation we are good at.

How this starts

Three moves, in this order

01

Find out which phase you are actually in

Phase one began in August 2026 with a hundred large VAT-registered companies; the remaining large ones follow in February 2027 and everybody else in August 2027. Dates in published rollouts have moved before. Confirm your own position with the Oman Tax Authority or your tax adviser — a software company is the wrong source and we will not pretend otherwise.

02

Appoint the access point, then ask it the receiving question

Choosing an accredited provider is a sell-side decision that quietly determines your buy-side experience. Ask each candidate what actually happens to an inbound invoice after it lands: where it sits, what it can be matched against, and whether it can reach the system your buyers work in. Most answers are thinner than the sending side.

03

Then fix the match, because that part is yours regardless

Take one month of purchase invoices and check them against orders and receipts by hand. The proportion with no order behind them is the number that tells you whether this is a software project or a process one. Do that before anybody demos anything, including us.

Questions we are asked here

Answered in full, including the ones that lose us the deal

Do you integrate with Fawtara or the Peppol network?

No. We are not an accredited service provider in Oman or anywhere else, we operate no Peppol access point, we are not registered in a service metadata directory, and we neither produce nor consume OM PINT documents or the Tax Data Document. That is a complete no rather than a "not yet with a roadmap". Our only fiscal e-invoicing integration anywhere in the product is Kenya's eTIMS, which is a direct authority integration and does not translate to a four-corner network. You will appoint an accredited provider for this and we will help you ask them better questions, which is a different service from selling you the pipe.

Then why is half this page about e-invoicing?

Because the five-corner model changes something on the buy side that the sell-side conversation is not covering, and that part is genuinely ours. When invoices arrive as structured data and the authority also receives purchase-side reporting, the quality of your accounts payable process stops being a private matter. What we run is the layer a structured invoice gets checked against: the requisition, the approval, the purchase order carrying the agreed price, the goods receipt taken where the goods arrived, and the three-way match that holds an exception instead of passing it on. Those are the things that decide whether an inbound invoice can be paid confidently. Getting the invoice into the building is the easy half and somebody else is already selling it.

Is Oman's model really that different from Saudi Arabia's?

Yes, and the difference is architectural rather than a matter of degree. Saudi Arabia operates clearance for standard invoices: the document goes to the authority, is validated and stamped, and comes back before it may be issued — so the authority is inside your sales process and a rejection stops a transaction. Oman's published model is post-audit and decentralised: invoices travel between accredited access points, the Tax Authority does not stamp the document, does not issue a clearance number and does not generate the QR code, and reporting reaches it separately from both parties. The practical consequence is that in Saudi Arabia the risk is a stopped sale, and in Oman it is a quiet mismatch between what you reported buying and what your supplier reported selling. Different failure, different system design. Confirm the current specification with the Tax Authority; published models are revised.

Does it handle the rial and 5% VAT?

The rial ships as a base currency preset and 5% ships as a built-in VAT rate, with net, tax and gross separated on every sales and purchase line at capture. Two caveats we would rather state than have you assume. First, we ship one maintained preset rather than a maintained rate history, and we do not interpret zero-rating, exemption or reverse-charge positions — the treatment is a question for the Tax Authority or your adviser. Second, the rial's peg to the dollar means it is almost never where your currency exposure lives; it sits on what you import in, which is why foreign-currency purchases stay in their own currency at the rate actually applied rather than at a standing monthly one.

What about the Social Protection Fund, WPS and Omanisation?

None of it is built. Our maintained statutory payroll engine covers Kenya only, so no Social Protection Fund contribution is calculated against the rates set under the 2023 law, no wage file is produced for the Ministry of Labour and Central Bank system, and no Omanisation position is tracked against the reserved-occupation rules. Keep those with an Omani payroll provider. What does travel is the employee side that is not statutory: records, contracts, leave with balances and approval, and payroll cost allocated to projects and cost centres so a job carries its labour as well as its materials.

We move goods through Sohar, Salalah or Duqm — do you connect to the ports or to customs?

No. There is no integration with Bayan, with any port community system, or with the free zone and special economic zone authorities. Customs and clearance paperwork is attached to the consignment as evidence rather than exchanged as data, and a customs event does not update the shipment automatically — somebody records it. What we do handle properly is what the paperwork costs: duty, clearance, port handling, demurrage and inland haulage allocated onto the receipt so the landed unit cost is real. If you are in a free zone or the Duqm special economic zone, note that goods held there sit outside the customs territory with duty suspended rather than waived, which means the same carton can carry two true costs depending on where it ends up. We can model both; we cannot tell the authority about either.

Where does support come from, and does the working week work?

Nairobi, with remote onboarding and live training in English. Muscat is UTC+4 and Nairobi UTC+3, so we are an hour behind you and the overlap is the whole working day. The working week is configured rather than assumed: set Friday and Saturday as non-working once and the organization's leave arithmetic, workflow due dates and escalation timers, and helpdesk response clocks all read that setting, along with the public holidays you enter. An approval will not fall due on your weekend because the system assumed a Saturday–Sunday one.

Bring one month of purchase invoices and we will match them with you

Not a demo of our software against our data — one real month of your own supplier invoices, checked against your orders and your receipts. The proportion that match cleanly is the single most useful number in this decision, and you will own it whether or not you ever buy anything from us.