Tax Data Document (TDD) in Oman: Fawtara E-Invoicing Reporting Explained

What is the Tax Data Document?

The Tax Data Document is a separate, purpose-built XML document that reports the tax-relevant details of an invoice directly to the Oman Tax Authority (OTA). It is not the invoice itself. According to the official PINT Oman specification published by OpenPeppol, the TDD is a regulatory report submitted to the tax authority for compliance purposes, and it is not exchanged between the invoice issuer and the invoice receiver.

That distinction is the whole point. Under Oman's Peppol five-corner model, two different things travel in two different directions at the same time. The commercial invoice flows across the Peppol network from the supplier to the buyer (corners one through four). The TDD branches off and goes to the OTA (corner five). One document does business. The other is compliance.

Think of the TDD as a tax-focused projection of your invoice. It carries the header identification, the supplier and buyer party details, the taxable amounts, and the tax line breakdown. It deliberately leaves out the commercial noise that the tax authority doesn't need, such as line-item descriptions, line-level discounts, and payment in

The technical anatomy (for the implementers)

For ERP and integration teams, a few specifics matter from day one. This is also where an ERP-integrated e-invoicing approach earns its keep, whether you run SAP, Oracle, or Microsoft Dynamics.

The TDD is identified by its own fixed values: a CustomizationID of urn:peppol:taxdata:om-1 and a ProfileID of urn:peppol:bis:taxdata. These two identifiers tell the network and the OTA exactly what kind of document is arriving, and they drive validator selection and routing. The document lives under its own root in the pxs: namespace, with structured blocks for document identification, a reference back to the source invoice, the parties, the tax breakdown per category and rate, and the monetary totals.

What the TDD reports also depends heavily on the transaction type, which is the central mechanism driving validation in PINT Oman. Every document declares a base type, either a Full Tax Invoice or a Simplified Invoice, plus a subtype for the scenario it represents. Supported subtypes include Self-Billed, Export, Import Reverse Charge, Deemed Supply, Summary, Continuous Supply, Profit Margin, E-Commerce, Special Zone, and Prepayment. The subtype decides which fields are mandatory and how VAT is applied, so a TDD for an export will carry a different shape from one for a domestic standard sale.

Crucially, the TDD has its own Schematron validation file, separate from the invoice rules. A Schematron error blocks submission to the OTA outright; only warning-level issues may pass. And there's a quirk worth flagging now: all document-level monetary amounts are currently limited to two decimal places, with three-decimal support noted as a planned future update. :contentReference[oaicite:0]{index=0}

The single most important engineering principle is this: never hand-author the TDD. The reliable approach is a deterministic transform that reads a valid PINT Oman invoice and emits the matching TDD automatically. Build it once, test it exhaustively against the official sample set, and you remove an entire class of compliance failures.

What this means for your business

The practical takeaways are straightforward. Your invoicing system must produce two compliant artifacts, not one. You need to keep two pieces of evidence for every transaction: the Peppol delivery receipt for the invoice and the OTA acknowledgment for the TDD. Lose either, and your audit trail has a hole in it. And because each TDD must be validated and reported individually, even in batch submissions, your reconciliation process needs to track them one by one.

Archiving deserves its own attention. Under Oman's VAT law, e-invoices must be retained in a secure, tamper-evident form for ten years, commonly structured as five years within the active system and five years in electronic archive storage, with full retrieval available throughout. The OTA platform is not expected to archive on your behalf, so the obligation to keep records intact and accessible sits with you, not your service provider.

A few edge cases catch businesses out. Import transactions are generally handled through self-billed invoices for reporting, governed by the separate PINT OM Self-Billing specification, where the buyer reports the document on behalf of the supplier. And if you operate under a VAT group, the whole group reports under a single VATIN through a single designated provider.

None of this is optional once your phase begins. Phase 1 of the Oman e-invoicing mandate starts in August 2026 for the largest taxpayers, with later phases extending to all VAT-registered businesses through 2027 and government transactions following by 2028. Because full ERP integration and testing typically takes eight to fourteen weeks, the specifications still being in draft is not a reason to wait. Build for the structured XML model now and treat display-layer details as a separate, evolving layer.

structions.

Why Oman built it this way

With its e-invoicing mandate, Oman becomes the third GCC country to require electronic invoicing, after Saudi Arabia and the UAE, and it has chosen a decentralized model rather than a central clearance portal. Invoices move peer-to-peer between accredited service providers, while tax data is reported in near real time to the OTA. The TDD is the mechanism that makes this real-time e-invoicing possible without forcing every commercial invoice through a government gateway. It gives the authority full visibility into VAT without sitting in the middle of every trade.

This also explains a detail many people miss: a TDD can be submitted by either the invoice issuer or the invoice receiver, depending on the reporting obligation. In a full Oman B2B e-invoicing flow, the supplier reports sales tax data and the buyer reports purchase tax data. Reporting is a two-sided responsibility, not just the seller's job.

The technical anatomy (for the implementers)

For ERP and integration teams, a few specifics matter from day one. This is also where an ERP-integrated e-invoicing approach earns its keep, whether you run SAP, Oracle, or Microsoft Dynamics.

The TDD is identified by its own fixed values: a CustomizationID of urn:peppol:taxdata:om-1 and a ProfileID of urn:peppol:bis:taxdata. These two identifiers tell the network and the OTA exactly what kind of document is arriving, and they drive validator selection and routing. The document lives under its own root in the pxs: namespace, with structured blocks for document identification, a reference back to the source invoice, the parties, the tax breakdown per category and rate, and the monetary totals.

What the TDD reports also depends heavily on the transaction type, which is the central mechanism driving validation in PINT Oman. Every document declares a base type, either a Full Tax Invoice or a Simplified Invoice, plus a subtype for the scenario it represents. Supported subtypes include Self-Billed, Export, Import Reverse Charge, Deemed Supply, Summary, Continuous Supply, Profit Margin, E-Commerce, Special Zone, and Prepayment. The subtype decides which fields are mandatory and how VAT is applied, so a TDD for an export will carry a different shape from one for a domestic standard sale.

Crucially, the TDD has its own Schematron validation file, separate from the invoice rules. A Schematron error blocks submission to the OTA outright; only warning-level issues may pass. And there's a quirk worth flagging now: all document-level monetary amounts are currently limited to two decimal places, with three-decimal support noted as a planned future update. :contentReference[oaicite:0]{index=0}

The single most important engineering principle is this: never hand-author the TDD. The reliable approach is a deterministic transform that reads a valid PINT Oman invoice and emits the matching TDD automatically. Build it once, test it exhaustively against the official sample set, and you remove an entire class of compliance failures.

What this means for your business

The practical takeaways are straightforward. Your invoicing system must produce two compliant artifacts, not one. You need to keep two pieces of evidence for every transaction: the Peppol delivery receipt for the invoice and the OTA acknowledgment for the TDD. Lose either, and your audit trail has a hole in it. And because each TDD must be validated and reported individually, even in batch submissions, your reconciliation process needs to track them one by one.

Archiving deserves its own attention. Under Oman's VAT law, e-invoices must be retained in a secure, tamper-evident form for ten years, commonly structured as five years within the active system and five years in electronic archive storage, with full retrieval available throughout. The OTA platform is not expected to archive on your behalf, so the obligation to keep records intact and accessible sits with you, not your service provider.

A few edge cases catch businesses out. Import transactions are generally handled through self-billed invoices for reporting, governed by the separate PINT OM Self-Billing specification, where the buyer reports the document on behalf of the supplier. And if you operate under a VAT group, the whole group reports under a single VATIN through a single designated provider.

None of this is optional once your phase begins. Phase 1 of the Oman e-invoicing mandate starts in August 2026 for the largest taxpayers, with later phases extending to all VAT-registered businesses through 2027 and government transactions following by 2028. Because full ERP integration and testing typically takes eight to fourteen weeks, the specifications still being in draft is not a reason to wait. Build for the structured XML model now and treat display-layer details as a separate, evolving layer.

Conclusion

The Tax Data Document is the part of Fawtara that quietly separates a compliant implementation from one that fails at go-live. It isn't your invoice, it isn't optional, and it can't be assembled by hand without risk. Getting it right comes down to one thing: an OTA-compliant e-invoicing solution that automatically generates, validates, and submits both the PINT Oman invoice and its matching TDD, every time, with a clean record of every acknowledgement.

That's exactly what SMARTeIS by Skill Quotient is built for. As a Peppol e-invoicing solution for Oman, it's Fawtara-ready and Peppol-aligned, handling the structured XML, the deterministic TDD generation, the transaction-type validation, and the OTA reporting so your finance and IT teams aren't stitching it together under deadline pressure. With Phase 1 starting in August 2026 and integration typically taking weeks rather than days, the businesses that adopt the best e-invoicing software in Oman early will transition without the last-minute scramble.

Ready to make your Oman e-invoicing effortless? Book a SMARTeIS demo and talk to our Fawtara readiness team today →

Frequently Asked Questions: Oman Tax Data Document (TDD)

1. If the invoice already travels across the Peppol network, why does Oman need a separate Tax Data Document?

Because the two documents do different jobs. The invoice is commercial and moves peer-to-peer between supplier and buyer. The TDD is a regulatory report sent only to the Oman Tax Authority (OTA). Since Oman uses a decentralized five-corner model with no central clearance portal, the TDD is how the authority keeps real-time visibility over VAT without sitting inside every transaction.

2. Who submits the TDD, the buyer or the seller?

Either, depending on the reporting obligation. In a standard B2B flow it's two-sided: the supplier reports sales-side tax data and the buyer reports purchase-side data for the same transaction. Unlike Saudi Arabia's seller-only clearance model, every invoice you receive may also carry a reporting duty, not just the ones you issue.

3. What's left out of the TDD compared to the full invoice?

The TDD is a tax-focused projection. It carries header details, the parties, taxable amounts, and the tax breakdown by category and rate. It drops commercial detail the authority doesn't need, such as line-item descriptions, line-level discounts, and payment instructions. So it can't simply be a renamed copy of your invoice; your system has to map fields into a narrower structure.

4. Can we batch TDD submissions for high-volume operations?

Yes, but each TDD must still be reported individually within the batch, with its own identifier and independent validation in Fawtara. Batching is a transport convenience, not a way to merge transactions, so your reconciliation has to track acknowledgements at the individual document level.

5. What identifies a TDD on the network?

Two fixed values: a CustomizationID of urn:peppol:taxdata:om-1 and a ProfileID of urn:peppol:bis:taxdata. These tell the network and the OTA what the document is, and they drive validation and routing. Emit the wrong identifier and the document is validated against the wrong rules or rejected outright.

6. What happens when a TDD fails validation?

The TDD has its own Schematron validation, separate from the invoice rules. A Schematron error blocks submission to the OTA entirely; only warnings pass. This is more dangerous than an invoice rejection, because a quietly failed TDD can leave you believing you've reported when you haven't. Treat the OTA acknowledgement as your only proof of success.

7. Should we author the TDD by hand in our ERP?

No. The safe approach is a deterministic transform that reads a valid PINT Oman invoice and automatically generates the matching TDD. Hand-authoring lets the two documents drift apart, creating mismatched totals and an entire class of avoidable failures. Treat the invoice as the single source of truth and the TDD as a derived artifact.

8. How does the TDD work for imports and self-billing?

Import transactions are generally reported through self-billed invoices, where the buyer issues the document on behalf of the supplier under the separate PINT OM Self-Billing specification. The TDD reporting principle still applies; only the document origin changes.

9. How long must we retain the underlying records?

Ten years under Oman's VAT law, in tamper-evident digital storage with full retrieval on demand, often split as five years in-system and five in archive. The OTA platform is not expected to store invoices for you, so retention is your responsibility.

10. How does Oman's TDD differ from Saudi Arabia's ZATCA model?

They look similar but behave differently. ZATCA uses centralized clearance, where the authority validates invoices before issuance. Oman uses a decentralized Peppol model where the invoice flows peer-to-peer and the TDD is reported separately. You can't reuse a Saudi implementation in Oman, and Oman's two-sided TDD obligation has no direct ZATCA equivalent.