How to Send Oman E-Invoices Straight from Excel

Ask a shopkeeper in Muscat what they invoice with and the answer is usually the same: a spreadsheet. Not an ERP, not accounting software — a workbook that has been copied forward, year after year, with the customer's name typed in the same cell it has occupied since 2019.

Then Fawtara arrives, and the advice they hear is replace it.

That advice is mostly wrong. The spreadsheet is not the problem. What Oman requires is that an invoice reaches the buyer in a structured format over the Peppol network, and that a Tax Data Document derived from it reaches the Oman Tax Authority. Neither of those is a reason to change how you type an invoice — they are reasons to change what happens after you type it.

What Oman actually requires

The Fawtara model has five corners. The familiar four carry the invoice from supplier to buyer through two Access Points. The fifth is the Tax Authority, which receives a separate tax document for each transaction. We have written about that architecture in detail.

For a small business, three consequences matter:

Your invoice must be a structured document, not a PDF. A PDF emailed to a customer is not an e-invoice under Fawtara, however neat it looks.

You need to be reachable on the network. That means a participant identifier registered against your VAT number — something an accredited service provider does for you.

The tax report is separate from the invoice. Sending your customer an invoice does not report it. Both have to happen, and for consumer sales the Authority allows 24 hours for the report.

None of that requires new invoicing habits. It requires plumbing.

The two kinds of sale, and why the difference is smaller than it looks

Almost every question we get from Omani retailers comes down to this distinction, and it is worth stating plainly.

Selling to a consumer — a walk-in customer with no VAT number — produces a simplified tax invoice. Technically it is a normal invoice with type code 380, whose Oman transaction type field marks it as simplified. Because the buyer has no Peppol identifier, it is issued against the official substitute participant that Oman defines for exactly this case. The customer gets the Fawtara QR code, which they can verify against the Authority's records.

Selling to a VAT-registered business produces a full tax invoice, delivered over Peppol into their accounting system rather than as an attachment they have to re-key.

In practice the difference is one field. If you know the customer's VAT number, you enter it. If you do not, you leave it blank. Everything downstream — the transaction type bits, the substitute participant, the QR code, which document goes where — follows from that.

Where the money detail bites: baisa

One Oman-specific trap deserves its own paragraph, because it catches almost every implementation.

The rial has 1000 baisa, not 100. Oman's rules require line-level VAT to equal the rate times the net amount within 0.001. At two decimal places most ordinary retail prices cannot satisfy that: three items at OMR 5.500 with 5% VAT gives 0.825, which rounds to 0.83 — out by five times the tolerance, and the invoice is rejected.

So line amounts carry three decimals while document totals stay at two, which is what EN 16931 requires. Both rules at once, and the small difference between them is absorbed by a separate tolerance. If you have ever had an Oman invoice rejected for a rounding reason you could not see, this is usually why.

Doing it from the spreadsheet you already have

Modern Excel supports add-ins: a panel that opens beside your sheet and can read and write it. That is enough to close the gap without changing anything about how you work.

The shape that works for a small business is deliberately narrow:

1. A sheet with the columns a shopkeeper recognises — customer, description, quantity, price, VAT. Not the fifty-odd fields the standard defines. Your business details, participant identifier, tax classifications and document format come from your company profile, because they are the same on every invoice you will ever issue.

2. Checking before sending, in plain language. "Customer VAT number should be OM followed by ten digits" is useful. A Schematron rule identifier is not.

3. One button that does both jobs. The invoice goes to the customer over Peppol; the tax report goes to the Authority. A shopkeeper should not have to know there are two.

4. Several items on one invoice. Real invoices have more than one line. Repeating the invoice number across rows should mean "these belong together", not be treated as an error.

5. Arabic. In Oman this is not a nice-to-have.

What still needs care

Two things surprise people, and both are worth knowing before your first invoice rather than after.

Every invoice needs its own number. Oman derives the official document identifier from your VAT number, the invoice number, the document type and the date — a deterministic value, not a random one. Reuse a number and two genuinely different invoices claim to be the same document. That determinism is useful: it lets a retry be recognised as a retry rather than filed twice. It only works if numbers are unique.

You cannot unsend. Once an invoice has gone to the customer and been reported, correcting it means issuing a credit note that references it — the same discipline as paper, for the same reason.

The practical answer

If you invoice from Excel today, you do not need to stop. You need the structured document, the network connection and the tax report — and those can be added to the workbook you already use.

GoRoute Connect for Excel does exactly this: an add-in for Excel 2016 and later on Windows and Mac, and for Excel in a browser. Free to install, with step-by-step guides for both platforms.

If your Excel is too old to run add-ins, the spreadsheet upload path performs the same checking and sending from a template. And if you run TallyPrime rather than Excel, there is GoRoute Connect for TallyPrime.

GoRoute is an accredited Oman Fawtara service provider and a certified Peppol Access Point. More on Oman e-invoicing, the PINT OM v1.0.1 changes, and data residency in Oman.