How do Message Level Status and Tax Data Documents work together in the UAE DCTCE model?
Effective: 2027-01-01 · Authority: UAE Ministry of Finance (MoF) / Federal Tax Authority (FTA)
In the UAE's 5-corner DCTCE model, the Tax Data Document (TDD) and Message Level Status (MLS) form the core reporting and acknowledgment mechanisms. Both the sending ASP (Corner 2) and the receiving ASP (Corner 3) are required to transmit TDDs to Corner 5 (MoF/FTA). MLS acknowledgments provide the closed-loop confirmation that transactions were both sent and successfully received, enabling the FTA to reconcile dual-submitted TDDs.
Why must both Corner 2 and Corner 3 submit TDDs to Corner 5?
The dual-TDD requirement creates a double-validation safeguard: Corner 2 (sending ASP) submits the TDD after validating the supplier's invoice and confirming the buyer's Peppol directory entry. Corner 3 (receiving ASP) submits a second TDD after successfully delivering and acknowledging the invoice. The FTA cross-references both submissions to confirm that a transaction was both validly sent and validly received, preventing phantom invoice reporting where a TDD is submitted for a transaction that was never actually delivered.
How does MLS enable FTA reconciliation of TDD submissions?
After Corner 3 delivers the invoice, it generates an MLS acknowledgment document indicating acceptance or rejection. The MLS status is propagated back through the network to Corner 2 and also forwarded to Corner 5. The FTA can then reconcile: (1) the TDD submitted by Corner 2 (invoice sent); (2) the MLS from Corner 3 (invoice accepted); and (3) the TDD submitted by Corner 3 (delivery confirmed). A mismatch between any of these three data points triggers a regulatory discrepancy requiring formal resolution.
Frequently Asked Questions
- What causes an MLS rejection in the UAE DCTCE model?
- MLS rejection at Corner 3 is typically caused by: buyer Peppol ID not found or inactive in the UAE Peppol directory; PINT-AE mandatory field validation failure (e.g., incorrect TRN format, missing line-item VAT rate); mathematical total discrepancy between document sections; or buyer ASP system unavailability. Since the TDD has already been submitted to Corner 5 by Corner 2 before the MLS rejection arrives, any rejection creates a regulatory gap that must be resolved through a corrected invoice submission.
- Is MLS used only in the UAE or is it a global Peppol standard?
- MLS is a global Peppol standard used across multiple Peppol jurisdictions including Australia, Singapore, and New Zealand for transaction acknowledgment. The UAE mandate adopts MLS as part of its broader PINT-AE framework, applying the global standard within its 5-corner CTC architecture.
AutoFact AI is not certified by, affiliated with, or endorsed by any regulatory authority referenced on this page. References describe technical alignment with published regulatory requirements only.
Related Concepts
- What is the Tax Data Document (TDD) in the UAE e-invoicing framework?
- What is Message Level Status (MLS) in the UAE Peppol e-invoicing network?
- What is an Accredited Service Provider (ASP) in UAE e-invoicing?
- What is the DCTCE (Decentralized Continuous Transaction Controls and Exchange) model?
- What ISO certifications are required for UAE Accredited Service Providers?