What is the Tax Data Document (TDD) in the UAE e-invoicing framework?
The Tax Data Document (TDD) is a structured data payload generated within the UAE's 5-corner DCTCE e-invoicing model. Both the sending Accredited Service Provider (Corner 2) and the receiving ASP (Corner 3) are required to transmit a validated TDD to Corner 5—the MoF/FTA central data platform—creating a dual-submission record of the transaction for tax authority purposes.
Why must both Corner 2 and Corner 3 submit the TDD?
The dual-submission requirement creates a double-validation safeguard at the tax authority level. Corner 2 (sending ASP) submits the TDD after validating the supplier's invoice against PINT-AE rules and confirming the buyer is in the Peppol directory. Corner 3 (receiving ASP) submits a separate TDD after successfully delivering and acknowledging the invoice on the buyer's side. This two-stage confirmation allows the FTA to reconcile that a transaction was both sent and received, reducing opportunities for under-reporting or phantom invoicing.
What happens if Corner 3 rejects an invoice validated by Corner 2?
If Corner 3 rejects an invoice that Corner 2 has already validated and reported, complex resolution mechanics are triggered. The mismatch between the Corner 2 TDD submission and the Corner 3 rejection must be resolved before the transaction can be considered completed. This places extreme pressure on supplier master data accuracy—particularly TRNs, Peppol routing IDs, and item-level VAT breakdowns—as any master data error will cause rejection at Corner 3 after the TDD has already been reported by Corner 2.
Frequently Asked Questions
- Is the TDD the same as the invoice itself?
- No. The TDD is a tax-focused structured data extract derived from the invoice, transmitted to Corner 5 for regulatory purposes. The full commercial invoice (with all PINT-AE mandatory and conditional fields) is exchanged between Corners 1-4 in the normal Peppol message flow. The TDD contains the key tax-relevant fields required by the MoF/FTA for near-real-time transaction monitoring.
- When must the TDD be transmitted to Corner 5?
- The TDD must be transmitted in near real-time as part of the invoice exchange process. The 5-corner DCTCE model operates as a Continuous Transaction Control (CTC) system, meaning data reporting is expected to be contemporaneous with the invoice exchange rather than batched at periodic intervals.
Related Concepts
- What is an Accredited Service Provider (ASP) in UAE e-invoicing?
- What is the DCTCE (Decentralized Continuous Transaction Controls and Exchange) model?
- What is Message Level Status (MLS) in the UAE Peppol e-invoicing network?
- What ISO certifications are required for UAE Accredited Service Providers?
- What capital and presence requirements apply to UAE ASP accreditation?