Enterprise E-Invoice Sending, Recorded From Every System We Integrate

The demos below show invoices leaving a particular system. This one shows where they arrive: the portal a finance, tax or IT team works in day to day. It covers the dashboard, invoices sent to customers, invoices received from suppliers, the single register that holds both, and what the record of a document looks like once it has been validated and delivered.

The second half is for the people who have to connect it: connectors and the API workflow, API keys and webhooks, and the archive and reporting an auditor asks for. Nothing is mocked up — it is the running portal, recorded in one pass.

Read next: the platform · API services · book a demo

If your business runs Odoo ERP and needs to prepare for the Oman Fawtara mandate, this shows the full path: raise an invoice in Odoo, push it over the REST API, watch real-time Schematron validation against PINT OM, then handle credit notes, debit notes and error responses — with a complete audit trail.

Read next: the Odoo connector · Oman's 5-corner model explained · PINT OM version updates

The same path as the demo above, in under four minutes: open the invoicing workflow in Odoo, connect it to GoRoute, send the invoice data across, watch it validated and processed, and find the transaction and its status afterwards. Watch this one first if you are deciding whether the integration is worth an hour of your team's time; watch the full 11:38 demo above when you are scoping the work itself.

It shows the connection and the invoice flow. It does not settle which Odoo versions are covered for your installation, how the integration is packaged for your environment, or what your own customisations do — those are answered against your system, and the Odoo article sets out what to ask.

Read next: the Odoo connector · Odoo e-invoicing in Oman · book a demo

One invoice, followed end to end. Fuel is dispensed at an Oracle APEX kiosk, the POS issues an electronic invoice, a unique UUID is generated, GoRoute runs five-point validation and returns a compliant QR code — and the same UUID and QR appear in every system: the APEX receipts table, the transactions dashboard, and the printable PDF.

Read next: the Oracle integration · industry use cases · API services

A full run through real-time e-invoicing from Oracle APEX: an invoice is raised in APEX, posted to the GoRoute connector, validated against PINT OM, delivered over Peppol and reported to the Tax Authority — and the compliant Fawtara QR code comes back while the customer is still at the counter.

The point of the demo is that the same document appears in three places at once: the APEX receipts table, the GoRoute transactions dashboard, and the printable receipt the customer takes away. That is what makes the invoice auditable rather than merely issued — and from 1 April 2027 it is what the mandate requires. Simplified B2C invoices are on the same clock.

Read next: the Oracle integration · Peppol API · book a demo

If your business runs TallyPrime, this shows the same path without changing how your team works: type the invoice in Tally exactly as always, and a small local connector reads it straight from Tally's own XML gateway, validates it against PINT OM and delivers it over Peppol. It covers all three Oman treatments — standard-rated 5%, B2C simplified, and zero-rated exports reported to Fawtara under the substitute participant when the buyer is not on the network.

The VAT figure is always the one Tally itself posted, never recalculated — so your ledger and your e-invoice can never disagree.

Read next: Oman Fawtara compliance · Oman's 5-corner model explained · Peppol API integration

Most small businesses in Oman invoice from a spreadsheet, and the advice they usually hear is replace it. This shows why that is unnecessary. GoRoute Connect for Excel adds a button to the workbook your team already uses: it checks each invoice against the Oman rules before anything is sent, delivers it to the customer, and files the Tax Data Document with the Oman Tax Authority.

It covers B2C simplified tax invoices with the Fawtara QR code, B2B delivery over Peppol, credit notes, debit notes and self-billing — and every document's delivery and tax-reporting status stays visible in the dashboard. Excel 2016 and newer on Windows and Mac, and Excel in the browser.

Read next: Connect for Excel · sending Oman e-invoices from Excel · book a demo

Microsoft Dynamics is not one product. Business Central, Finance & Operations, Sales/CRM and older on-premise systems each reach e-invoicing by a different route, which is why a single "Dynamics connector" rarely fits. This explains where GoRoute starts — Dynamics 365 Business Central and its built-in E-Document framework — and why that surface comes first.

It then follows an invoice out of Business Central into GoRoute for validation, Peppol delivery and transaction tracking, through to Oman Fawtara readiness. Credit notes, retries and invoice-status handling are covered, along with why webhook-only integrations can fail quietly — the failure mode that costs finance teams the most time to unpick.

Read next: Microsoft Dynamics e-invoicing · Peppol API integration · book a demo