Four myths that derail e-invoicing projects

We talk to Omani finance teams every week, and the same four beliefs come up again and again. Each one sounds sensible. Each one has stalled real projects. Worth ten minutes to retire them all.

Myth 1: "An e-invoice is just a PDF sent by email"

A PDF is a picture of an invoice. Fawtara requires structured PINT-OM data, exchanged machine-to-machine through accredited providers, with tax data reported to the OTA in near real time. A PDF satisfies none of that — not even a digitally signed one. The regulation is explicit on this point precisely because so many people assume otherwise.

Myth 2: "We can wait until our phase is announced"

Here's the math that breaks this one. ERP integration, field mapping, master-data clean-up, and testing routinely take a quarter, sometimes more. Provider onboarding slots tighten as each deadline approaches, because every business in your phase is shopping at the same time. Waiting for the announcement means doing all of it compressed, expensive, and under deadline pressure. The timeline is public; the head start is free.

Myth 3: "Our ERP already handles it"

Your ERP creates invoices, and it's good at that. What it doesn't do is connect to the Peppol network, validate against PINT-OM's rulebook, or report tax data to the OTA — that is, by design, the role of an accredited service provider. Under the five-corner model, even a fully modern cloud ERP still needs an ASP in the path. The question isn't whether you need one; it's which one.

Myth 4: "It's an IT project"

The hardest questions in an e-invoicing project aren't technical. Which of our eleven invoice scenarios are actually in scope? How do we handle self-billing? Who signs off when a mapped field changes VAT treatment? Those are tax and process questions, and when they're left to IT alone, they get answered by guesswork. The projects that go smoothly pair a finance or tax owner with IT from day one — one decision-maker, one escalation path.