E-Invoicing Overview

Electronic invoicing (e-invoicing) in the Sultanate of Oman is the automated, structured digital exchange of invoice data between suppliers, buyers, and the Oman Tax Authority (OTA).

Under the national Fawtara framework, e-invoicing replaces paper documents and unstructured PDFs with standardized, machine-readable messages based on the Peppol PINT OM specification. This continuous transaction control model supports real-time validation, security, and tax compliance across commercial exchanges.

B2B vs. B2C invoicing and the five-corner model

Oman uses a five-corner model that extends the standard Peppol four-corner framework:

• Corner 1 (C1): Supplier or sender.

• Corner 2 (C2): Supplier's Accredited Service Provider and Peppol Access Point.

• Corner 3 (C3): Buyer's Accredited Service Provider and Peppol Access Point.

• Corner 4 (C4): Buyer or receiver.

• Corner 5 (C5): Tax Authority Access Point and validation service.

• Corner 6 (C6): Oman Tax Authority central system.

Business-to-Business (B2B)

In a standard B2B exchange, both trading partners are registered on the Peppol network.

• Data flow: C1 sends structured invoice data to C2. C2 validates and sends the PINT invoice to C3, which processes and delivers the final invoice to C4.

• Tax reporting: In parallel with the C2-to-C3 exchange, C2 and C3 independently generate an Oman Tax Data Document (OM TDD), submit it to C5 for validation, and report it to C6.

• Delivery status: Message-Level Status (MLS) confirmations travel from C3 to C2 for invoice delivery and from C5 to C2 and C3 for tax-reporting validation.

Business-to-Consumer (B2C)

In B2C transactions, the buyer at C4 is not registered on the Peppol network.

• Data flow: C1 gives the consumer a human-readable printed or PDF invoice with the mandatory QR code, then sends the transaction data to C2.

• Tax reporting: C2 enriches the payload with standard consumer placeholders, including buyer identifier 0248:997770000099 and buyer name General customer, creates the OM TDD, and sends it to C5.

• Network omission: No C2-to-C3 or C3-to-C4 exchange occurs.

Architectural comparison

Key characteristics

• Standard semantic specifications: Documents follow Oman PINT for invoices and credit notes and the OM TDD specification for government reporting.

• Deterministic identifiers: The invoice UUID is generated with UUID version 5 and the fixed namespace e0bc4ac8-b025-46e5-a76d-0c893fc3027e, using mandatory payload fields. The TDD UUID is generated locally with UUID version 4 for traceability.

• Encrypted TLV QR codes: B2C invoices use a Base64 Tag-Length-Value QR code of no more than 700 characters. It includes the seller VATIN, timestamp, totals, and Seller UUID.

• Automated status feedback: MLS responses provide AP, AB, or RE status feedback across the network and help prevent silent delivery failures.

• Centralized registry lookup: Participant capabilities are resolved through Oman's central Service Metadata Publisher (SMP), linked to the global Peppol Service Metadata Locator (SML).

Why it matters for businesses

• Regulatory compliance: Supports compliance with the OTA Fawtara framework.

• Operational automation: Replaces manual entry, paper handling, and PDF parsing with direct system-to-system communication.

• Faster reconciliation and payment: Structured data and automated validation streamline procure-to-pay and order-to-cash cycles.

• Auditability and security: Cryptographic trust and deterministic UUID tracking provide traceable digital records.

• International interoperability: The Peppol foundation supports compatible cross-border exchange with trading partners around the world.