Connecting Odoo to GoRoute means Odoo keeps issuing the invoice and GoRoute does everything that has to happen next: converting it to Peppol UBL, validating it against the destination country's own rules — PINT OM v1.0.1 for Oman — delivering it over the network, and writing the status back into the record.
The recording below runs 3 minutes 46 seconds: opening the Odoo invoicing workflow, connecting Odoo to the platform, sending invoice data across, the validation and processing that follows, and finding the transaction afterwards. The same walkthrough is written out further down the page, stage by stage, if you would rather read it than watch it.
Below is the recording written out, stage by stage and in its own order, so the page answers what the Odoo connection does without anyone pressing play. Nothing here describes a screen the recording does not show; where a detail comes from the Odoo integration page or the Oman Odoo guide rather than from the video, it says so.
It means nothing changes about how your finance team raises an invoice. Odoo remains the accounting system and the place the document is created. What the connection adds is the part Odoo does not do on its own: turning that invoice into a structured Peppol UBL document, checking it against the rules of the country it is going to, handing it to the receiving business over a certified network, and bringing the outcome back so the record in Odoo is not the only thing you have.
The integration is a Python addon module that uses Odoo's own API, so it extends the native invoicing workflow rather than replacing it. Existing workflows stay as they are, and the addon takes over once an invoice is validated in Odoo. That is the design the recording demonstrates, and it is why the whole thing fits in under four minutes.
The recording opens in Odoo's own invoicing screens, not in GoRoute. That is deliberate: the first thing to establish is that the starting point is the customer invoice a business already produces — from a sales order, a subscription or a service bill. Odoo raises it the way it always has. The GoRoute addon appears alongside that workflow rather than in front of it, which is the single most common question a finance team asks before agreeing to any integration.
Three things, done once. The addon module is installed — from the Odoo Apps
Store or directly from our repository, with dependencies resolved automatically. API
credentials are entered, so the addon can authenticate against the platform; the key
travels in the X-API-Key
header on every request and is scoped to your organisation. Then the mapping is set:
which Odoo invoice fields correspond to which UBL elements, plus customer Peppol
identifiers and tax settings.
A single Odoo instance running several companies is handled as several configurations rather than one, so each company keeps its own e-invoicing settings and compliance rules. Custom fields can be mapped to UBL elements too, which is what makes industry-specific invoicing survive the conversion instead of being flattened into a generic document.
Once an invoice is validated in Odoo, the addon converts it to UBL and posts it to the GoRoute REST API. Sales orders, subscription invoices and service bills all take the same route, which is the point of doing the conversion in a module rather than in a report template: one path, one place where the mapping lives, and no manual step between the two systems.
Month-end is where a naive integration usually fails, because it sends one invoice per call. The API takes batches of between 1 and 1,000 invoices in a single request, with validation and processing as separate stages, so a month of Odoo invoices can go in one submission rather than a thousand.
Every document passes the compliance gate before it leaves, and the rule set is chosen from the document itself rather than configured per country. For Oman that means the full PINT OM v1.0.1 rule set including its Schematron rules; elsewhere it is the baseline EN 16931 and Peppol BIS Billing 3.0 rules, or the national specialisation that applies.
What comes back is a compliance score with human-readable errors rather than a bare pass or fail, so a developer building the integration can see which rule broke and on which field. Validation-only calls carry no per-call charge, which means checking the same invoice repeatedly while the mapping is being tuned costs nothing.
The last stage of the recording is finding the transaction after it has been sent.
A document moves through queued
→ sending →
sent, and a failure
carries a reason instead of a silence:
TIMEOUT,
VALIDATION_ERROR or
RECIPIENT_NOT_FOUND.
An invoice raised in Odoo and an invoice raised in the GoRoute portal end up in the same register carrying the same kind of record, because the connector is a route in rather than a separate system. Where an integration is listening, webhooks push the same events out instead of being polled for.
The party identifiers, and they are usually the longest task in the project rather than the integration itself. Oman uses Peppol scheme 0248, and the identifier is the VAT identification number carried with an OM prefix — for the seller and for the buyer. That data lives in your Odoo contact and company records. Populating it across a customer base that has been growing for years is the work; wiring the addon is the afternoon.
The addon supports Odoo 14, 15, 16 and 17, in both Community and Enterprise editions, and it is deployed through Odoo's standard addon management. That covers Odoo.sh cloud hosting, self-hosted installations and third-party hosting alike. What the recording cannot settle is your own installation — its version, its customisations and the state of its data — which is a scoping conversation rather than something a video can answer.
Failed transmissions are retried automatically with exponential backoff, and the addon creates an activity record in Odoo so the failure lands in front of a person rather than in a log nobody reads. The error message names what went wrong. The invoice itself remains a valid invoice in Odoo regardless of whether transmission succeeded, which matters because an accounting document and its delivery are two different things.
On the same dates as everyone else, because the threshold is annual supplies rather than which system you run. 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. Which wave you fall in, and what the programme asks for beyond a working connection, is set out on the Oman e-invoicing page.
The connection itself is three steps: install the addon, enter the API credentials, and map the invoice fields. The recording on this page covers it in 3 minutes 46 seconds. What takes longer is the data behind it — the Peppol identifiers on your customer records — not the wiring.
Odoo 14, 15, 16 and 17, in both Community and Enterprise editions. The addon is deployed through Odoo's standard addon management, so it works on Odoo.sh cloud hosting, self-hosted installations and third-party hosting alike.
No. It extends Odoo's native invoice functionality. When an invoice is validated in Odoo it is converted to UBL and transmitted over Peppol; your existing workflows are unchanged and there is no second screen for finance to learn.
The party identifiers. Oman uses Peppol scheme 0248, and the identifier is the VAT identification number with an OM prefix, for the seller and for the buyer. It lives in your Odoo contact and company records, and populating it across an existing customer base is usually the longest task in the project.
Yes. Batch submission takes between 1 and 1,000 invoices in a single request, with separate validate and process stages. That matters at month-end, which is when a design that sends one invoice per call tends to fail.
It is retried automatically with exponential backoff, and the addon creates an activity record in Odoo for manual review with a detailed error message. The invoice remains valid in Odoo regardless of transmission status.
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. The longer version, Odoo to GoRoute over the REST API, is the one to watch when scoping the work rather than deciding whether to.
Press Esc, click outside, or use the ✕ to close and stop playback.
