GoRoute Connect for Excel puts a button in the spreadsheet you already invoice from. You type the row as usual; the button checks the invoice against Oman's Fawtara rules, sends it to your customer over the Peppol network, and files the tax data document with the Oman Tax Authority. Nothing is replaced.
The recording below runs twelve minutes and covers the whole job in thirteen chapters, from installing the button to seeing a sent invoice on the dashboard. The same walkthrough is written out further down the page, chapter by chapter, if you would rather read it than watch it.
Below is the recording written out, chapter by chapter and in its own order, so the page answers what Connect for Excel does without anyone pressing play. Where a detail comes from the Connect for Excel product page or the Oman Excel guide rather than from the video, it says so.
An add-in that puts a GoRoute tab in the Excel you already have. It does three things that a spreadsheet cannot do on its own: check an invoice against Oman's e-invoicing rules before it goes anywhere, send it to the customer over the Peppol network, and file the tax data document with the Oman Tax Authority. The invoice itself is still a row you typed. That is the whole design, and the recording opens by making the point that nothing about the spreadsheet has to change.
Because Fawtara is not about how you write an invoice. It requires that the 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. A spreadsheet does neither, and emailing a PDF satisfies neither. That is the gap, and it is a different gap from the one most advice describes.
The advice an Omani small business usually hears is replace the spreadsheet. That is mostly wrong. The spreadsheet is not what fails the rule; the missing structured delivery and the missing report are. Close those two and the workbook that has been copied forward since 2019 is fine exactly as it is.
The add-in adds a GoRoute tab and a side pane. The pane is where the checking and sending happen; the sheet stays a sheet. You connect once by pasting the key from your dashboard, and it stays on your computer rather than inside the workbook — which matters the first time somebody emails the file to a colleague.
One detail from the product page is worth knowing before you start: Excel stores the add-in reference inside the file, not inside Excel. Open GoRoute once in a workbook and save it, and the button is there every time you open that workbook. A brand-new blank workbook will not have it. Keeping one workbook — call it Invoices — is the practical answer.
You enter what you sold and to whom: customer, description, quantity, price. Everything else — your own VAT registration, the identifiers, the document codes, the profile the invoice has to ride — is filled in from your company profile rather than typed. That division is the reason the whole thing is teachable in an afternoon: the parts a business knows are the parts it enters, and the parts nobody wants to learn are the parts it never sees.
Press Check and the invoice is validated against the Oman rule set — PINT OM v1.0.1, including its Schematron rules — before anything leaves your machine. Mistakes come back in plain language, naming the field, rather than as a rule identifier a small business has no way to interpret.
Doing it in this order is the entire point. An invoice stopped in your spreadsheet costs a minute; one rejected after it has been transmitted costs days and involves your customer. The same gate runs on every route into the platform, so a spreadsheet invoice is held to the identical standard as one from an ERP integration.
Press Send and one press does two separate jobs. The customer gets the invoice, and the Tax Authority gets its report. Delivery runs over the Peppol network through an accredited access point, which means the document arrives inside your customer's system rather than in somebody's inbox. There is nothing for a small business to certify, host or maintain to make that work.
It is filed as part of the same press. The tax data document is derived from the invoice and submitted separately from the delivery, because the Authority and the buyer are two different recipients with two different requirements. For a consumer sale the Oman Tax Authority allows 24 hours to report it. An invoice showing as awaiting the Authority inside that window is normal rather than stuck, and that one sentence saves more support tickets than anything else on this page.
Leave the customer's VAT number blank and the invoice goes out as a simplified tax invoice. Technically it is an ordinary invoice — type code 380 — whose Oman transaction type marks it as simplified, and it is issued against the official substitute participant because a consumer has no Peppol identifier of their own.
It carries the Fawtara QR code, which is the part the customer can actually check. In the spreadsheet, none of that is a setting: an empty VAT cell is the whole instruction.
Enter the customer's VAT number and the same row becomes a full tax invoice, delivered over Peppol to their system. The difference between the two kinds of sale is smaller than it looks from the outside: one cell. Everything downstream — which profile the document rides, which participant it is addressed to, what is reported — follows from whether that cell is filled.
A correction references the original document properly, so the Authority sees a correction rather than a contradiction. That reference is the part hand-built spreadsheet workarounds get wrong: a credit note that does not point at the invoice it corrects reads as a second, conflicting claim about the same sale. Both credit and debit notes are in scope for Fawtara reporting alongside the invoice they correct.
Self-billing is when you raise the document on your supplier's behalf rather than waiting for theirs — common where the buyer knows the quantity before the supplier does. Oman treats it as its own document flow, and Connect for Excel puts self-billed invoices and credit notes on that separate profile automatically.
One money detail sits underneath all of these flows and catches people out. The rial has a thousand baisa, so line amounts carry three decimals while document totals stay at two. Both rules apply at once, and the add-in holds them both rather than asking the person typing to remember which is which.
In two places. The row in the sheet turns green, which is the answer for the person who just pressed Send. The GoRoute dashboard holds the record, which is the answer for anyone asking later: what went out, what each document was validated against, and what the receiving side acknowledged. Removing the add-in later changes none of that — everything already sent stays on the dashboard and remains filed with the Tax Authority.
Excel 2016 and every version since, on Windows and Mac, whether you pay monthly for Microsoft 365 or bought Excel outright — plus Excel in a browser, which needs nothing installed and a free Microsoft account. Excel 2019 and 2016 run add-ins inside an older browser engine, so a second build ships for them and loads itself; there is nothing different to download. Excel 2013 and older cannot run add-ins at all, and those users fill in the GoRoute template and upload it instead — the checking, sending and tax reporting are identical, only the button is missing.
Yes. GoRoute Connect for Excel adds a button to Excel that validates every invoice against the Oman Fawtara rules (PINT OM v1.0.1), sends it to your customer over the Peppol network, and files the tax data document with the Oman Tax Authority. You do not leave the spreadsheet.
No. What Oman requires is structured delivery to the buyer over Peppol and a tax data document to the Authority. Neither is a reason to change how you type an invoice. The button handles the compliance, the sending and the reporting; the spreadsheet stays as it is.
It is the document for a sale to a consumer who is not VAT-registered. Technically it is an ordinary invoice, type code 380, whose Oman transaction type marks it as simplified, issued against the official substitute participant because the buyer has no Peppol identifier. In Excel you leave the customer VAT number blank and it is issued that way, with the Fawtara QR code the customer can verify.
The Oman Tax Authority allows 24 hours to report the tax data document for a consumer sale. GoRoute files it when you press Send, so an invoice showing as awaiting the Authority inside that window is normal rather than stuck.
No. Your invoices reach the network through an accredited service provider. There is nothing for a small business to certify, host or maintain.
Excel 2016 and every version since, on Windows and Mac, subscription or bought outright, plus Excel in a browser. Excel 2019 and 2016 use an older browser engine, so a second build ships for them and loads automatically. Excel 2013 and older cannot run add-ins at all; those users fill in the GoRoute template and upload it instead.
This recording shows the same platform you would be buying, doing the thing you would be buying it for — on a Peppol-certified access point.
Press Esc, click outside, or use the ✕ to close and stop playback.
