A forecourt receipt is a simplified tax invoice, and Oman puts simplified invoices on the same 2027 clock as the finance department. This recording follows one of them the whole way: fuel dispensed at an Oracle APEX kiosk, the till issuing the invoice, a unique identifier generated, validation run, and a compliant QR code returned.
It runs 9 minutes 19 seconds, and the point of the last third is that the same identifier and the same QR code appear in the APEX receipts table, in the GoRoute transactions dashboard and on the printed PDF. The whole sequence is written out further down this page, stage by stage, if you would rather read it than watch it. The rules behind it are in simplified tax invoices in Oman.
Below is the recording written out, stage by stage, so this page answers what happens at a forecourt without anyone pressing play. Where a detail comes from Oman’s published rules or from the guide on simplified tax invoices rather than from the video, it says so.
Yes, and on the same dates as everyone else. The amended Article 146, paragraph two says the simplified tax invoice must be issued within the timeframes specified in Article 143 — which puts every till in the country on the finance department’s clock rather than a slower retail one. Article 143 covers supplies “to a non-taxable person” explicitly, so business-to-consumer is named in both places rather than left to inference. Any taxable person making supplies to non-taxable persons issues simplified tax invoices, and fuel stations and exchange counters are squarely inside that.
Because a business-to-business rollout is a project about documents, and a business-to-consumer rollout is a project about volume, uptime and physical estate. A distributor issuing 8,000 invoices a year is changing a format in one system. A retail chain with 40 counters is changing behaviour at 40 devices, some old, some leased, and at least one that nobody is quite sure who maintains.
Three things make the retail version the harder one. Volume changes the architecture: hundreds of thousands of documents a year is a different system from thousands, and storage, retrieval, retention and reconciliation stop being incidental. The device estate is the project: tills, forecourt controllers, exchange-counter terminals and kiosk software are each an issuing point. And the customer is standing there — a business-to-business invoice can fail and be retried in the background, but a queue cannot wait for a retry. That last one is why the recording is set at a pump rather than at a desk.
The reduced-content invoice used for supplies to non-taxable persons — in practice, the receipt handed over at a counter. It carries less party detail than a full tax invoice, and it is still a tax invoice: it needs the approved electronic format, integrity, retention and a unique number. That last requirement is the one that quietly reshapes a forecourt system, and it has its own section below.
The recording opens on the ordinary sale. A customer fills the vehicle’s tank at an Oracle APEX kiosk, and the point of sale issues the electronic invoice as part of completing the transaction rather than as a second step somebody has to remember. Nothing about the attendant’s workflow changes, which is the design constraint on any forecourt integration: a compliance step that adds seconds to a queue is a compliance step that gets skipped at the busy hour, and the busy hour is when the volume is.
Because two counters must never issue the same invoice number, and on a forecourt there are more issuing points than anyone counts on the first pass. The recording shows a unique identifier generated for the transaction at the moment the invoice is issued. Oman’s rules put a shape on it: IBR-002-OM requires a unique document identifier that is a valid UUID version 5 — not a sequence number, and not any UUID, but one generated from a namespace and a name. A namespace-derived identifier is exactly what stops pump three and the kiosk colliding, which is why the design is worth understanding rather than copying.
The invoice data leaves APEX as structured data rather than as a printed image, and is routed to GoRoute. That is the whole point of the exercise: a tax authority and a buyer’s system both read fields, and neither reads a picture of a receipt. GoRoute is a Peppol-certified Access Point (Service Provider ID POP000991, ClayDesk LLC), so the same route serves a forecourt receipt and a corporate invoice — what differs is the document type, not the infrastructure.
The recording calls this stage five-point validation. Underneath it, the document is checked against the full PINT OM 1.0.1 rule set including its Schematron rules, and what comes back is a compliance score with human-readable errors rather than a bare pass or fail. An error that names the field and the rule is a ticket a developer can act on; a rejection code is a conversation.
Three layers can refuse the document. Counted in the packs GoRoute ships on 22 August 2026: the shared Peppol PINT layer holds 170 rules, all fatal; Oman’s own jurisdiction pack holds 155, of which exactly two are warnings; and the tax data document has its own pack of 66 rules, all fatal. For a retail system the constraint most likely to be discovered late is IBR-DEC-03-OM, which refuses any amount carrying more than three decimal places — the Omani rial’s own precision, where fuel pricing tempts a system into more.
It comes back with the response, once compliance processing is done. Oman’s specification requires a QR code on simplified tax invoices, and two things about it are commonly got wrong by teams arriving from a neighbouring Gulf regime. It is business-to-consumer only — full tax invoices do not carry one. And the Oman QR contains no hash and no digital signature: carrying over another country’s QR construction produces a document Oman’s validation rejects. Both are cheap to get right at design time and expensive to unpick after a device estate has been programmed.
The compliant invoice and its QR code, returned into Oracle APEX and written to the fuel receipts page. This matters more than it looks: the till’s own record and the compliance record are the same record, so there is no second register to reconcile and no window in which the two disagree. A forecourt system that keeps its compliance state somewhere else is a forecourt system that will one day be asked to explain a difference between them.
In the GoRoute transactions dashboard, which holds the audit trail: what went out, what each document was validated against, and what came back. A transaction whose status nobody can see is not auditable, and from the mandate date it is the record that has to stand up rather than the act of sending. For a chain, the dashboard is also the only place where 40 counters look like one estate.
It is previewed, downloadable and printable from the same record, carrying the same identifier and the same QR code. The closing section of the recording is about exactly that agreement: one identifier and one code across the APEX table, the dashboard and the PDF. It sounds mundane and it is the difference between a reconciliation that takes minutes and one that takes a week — and, in year six of a ten-year retention period, between finding a single receipt and not.
Decision 189/2026 does not impose real-time clearance at the point of sale. What Article 143 bis 1 does impose is procedures for breakdowns and malfunctions, and recovery of data lost for any reason, so that the system does not cease operation. Applied to a till, that turns “what happens when the link drops” from an implementation detail into a compliance question.
Three decisions are worth writing down before selecting anything: whether the counter keeps trading offline and what the customer receives if it does; where the document lives until it can be transmitted; and what guarantees a locally held document is not lost when the device is replaced. The third is the one that bites quietly, because a till holding documents in local storage is a retention failure waiting to be found at audit — Oman requires records to be kept for ten years under Royal Decree 121/2020.
One per transaction, which for a mid-sized chain means moving from thousands of business-to-business invoices a year to hundreds of thousands of documents. Size that honestly before choosing anything: documents per year, retention for ten of them, and what retrieving a single receipt from year six actually involves. On dates, Decision 189/2026 makes electronic tax invoices mandatory from 1 April 2027 for taxable persons whose annual supplies exceed OMR 5,000,000, and from 1 October 2027 for those at or below that figure — by annual supplies, not by headcount or sector. The detail of what the Decision changed is on the page that owns Oman’s e-invoicing dates.
Yes. Any taxable person making supplies to non-taxable persons issues simplified tax invoices, and the amended Article 146 paragraph two puts those on the Article 143 timeframes — the same dates as business-to-business. There is no slower track for retail, fuel or exchange counters.
Yes. Oman’s specification requires a QR code on simplified invoices. It is a business-to-consumer feature: full tax invoices do not carry one. Unlike some neighbouring regimes, the Oman QR contains no hash and no digital signature, so carrying over another country’s construction produces a document Oman’s validation rejects.
Because every issuing point — till, forecourt controller, kiosk, back-office terminal — needs a unique invoice number that cannot collide with another counter’s. Oman’s rule IBR-002-OM requires the document identifier to be a valid version 5 UUID, generated from a namespace and a name rather than at random or in sequence.
Decision 189/2026 does not impose real-time clearance at the till. What Article 143 bis 1 does impose is that the system keeps operating and that data lost for any reason can be recovered — which makes offline behaviour a design decision you have to make deliberately rather than discover.
Ten years, under Royal Decree 121/2020. That is why a till holding documents only in local storage is a retention failure waiting to be discovered at audit: the question is not whether the receipt printed, but whether it can be retrieved from year six after the device has been replaced twice.
The same dates as everyone else, set by annual supplies rather than by sector. Decision 189/2026 makes electronic tax invoices mandatory from 1 April 2027 for taxable persons whose annual supplies exceed OMR 5,000,000, and from 1 October 2027 for those at or below that figure.
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.
