OpenPeppol publishes the UAE DCTCE architecture on Confluence. That page is the architecture reference: a business reading, and a technical reading aimed at service providers.
The page was updated on 11 August. The edit note on the page records:
- an MLS response table was added
- typos were corrected
- further clarifications were added
Earlier versions are linked from the same page: https://openpeppol.atlassian.net/wiki/x/AQA9LQE.
What you will find there
- Enterprise Interoperability Architecture. The UAE DCTCE model at business and conceptual level.
- Solution Architecture. The same model at technical level, written for service-provider implementation.
- Pointers to the Peppol eDelivery specifications and the Peppol code lists.
- Pointers to UAE document specifications, including billing, self-billing, Tax Data (TDD / TDS), and MLS.
- Human-readable invoice visibility. Fields marked Mandatory, or Mandatory if applicable, have to appear on the human-readable rendition of the eInvoice. The page states that requirement against the UAE eInvoicing framework.
Some of the Confluence space is only visible with an OpenPeppol login. If a section is blocked, that is the source page, not this forum.
Versions: read this before you implement from the wiki alone
The DCTCE page is the architecture. It is not always the newest copy of the billing syntax. The page text still points at UAE Billing PINT and Self-Billing PINT version 1.0.1. The billing specification currently published on docs.peppol.eu is PINT AE 1.0.4:
Where the wiki and docs.peppol.eu disagree on a version, do not treat either this topic or a reply under it as the decision. Say which text you followed when you ask a question in Technical or Functional & Business.
This topic is a pointer. Please do not paste the architecture document into the thread.