// IMPLEMENTERS · DCTCE 5-corner · Peppol AS4

ASP payload reference

Concrete payload structures for the major mandate models. Use these to scaffold your ERP integration before you have a sandbox token. Every sample is annotated; the field tables tell you what is mandatory, conditional, or optional.

United Arab Emirates · MoF / FTA

PINT-AE — Tax Data Document (TDD)

The UAE DCTCE 5-corner Peppol model requires the supplier's ASP to validate, sign and transmit a Tax Data Document (TDD) to the FTA in near real time, while delivering the e-invoice to the buyer's ASP via Peppol AS4. The TDD is a UBL 2.1 subset (PINT-AE profile) with 51 mandatory fields per FTA Feb 2026 technical guidance. VAT is calculated at line-item level.

// Sample envelope (Peppol AS4 SBDH)

POST /as4 HTTP/1.1
Host: ap.pint-ae.example
Content-Type: multipart/related; boundary="ebms"; type="application/soap+xml"
SOAPAction: ""

--ebms
Content-Type: application/soap+xml; charset=UTF-8

<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
  <soap:Header>
    <eb:Messaging xmlns:eb="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core-200704/">
      <eb:UserMessage>
        <eb:PartyInfo>
          <eb:From><eb:PartyId type="urn:fdc:peppol.eu:2017:identifiers:ap">PAE000123</eb:PartyId></eb:From>
          <eb:To><eb:PartyId type="urn:fdc:peppol.eu:2017:identifiers:ap">PAE000456</eb:PartyId></eb:To>
        </eb:PartyInfo>
        <eb:CollaborationInfo>
          <eb:Service>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</eb:Service>
          <eb:Action>busdox-docid-qns::urn:peppol:pint:billing-3.0@ae-1</eb:Action>
        </eb:CollaborationInfo>
      </eb:UserMessage>
    </eb:Messaging>
  </soap:Header>
</soap:Envelope>
--ebms
Content-Type: application/xml; charset=UTF-8
Content-ID: <tdd-payload@einvoice.global>

// UBL 2.1 TDD body (PINT-AE profile)

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
         xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2">

  <cbc:CustomizationID>urn:peppol:pint:billing-3.0@ae-1</cbc:CustomizationID>
  <cbc:ProfileID>urn:peppol:bis:billing</cbc:ProfileID>
  <cbc:ID>INV-2027-00042</cbc:ID>
  <cbc:UUID>3fa85f64-5717-4562-b3fc-2c963f66afa6</cbc:UUID>
  <cbc:IssueDate>2027-01-15</cbc:IssueDate>
  <cbc:IssueTime>14:30:00+04:00</cbc:IssueTime>
  <cbc:InvoiceTypeCode listAgencyID="6" listID="UNCL1001">388</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>AED</cbc:DocumentCurrencyCode>

  <!-- Supplier (Corner 1) -->
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cbc:EndpointID schemeID="0235">100123456700003</cbc:EndpointID>
      <cac:PartyIdentification>
        <cbc:ID schemeID="TRN">100123456700003</cbc:ID>
      </cac:PartyIdentification>
      <cac:PartyName><cbc:Name>Acme Trading LLC</cbc:Name></cac:PartyName>
      <cac:PostalAddress>
        <cbc:StreetName>Sheikh Zayed Rd</cbc:StreetName>
        <cbc:CityName>Dubai</cbc:CityName>
        <cac:Country><cbc:IdentificationCode>AE</cbc:IdentificationCode></cac:Country>
      </cac:PostalAddress>
      <cac:PartyTaxScheme>
        <cbc:CompanyID>100123456700003</cbc:CompanyID>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:PartyTaxScheme>
    </cac:Party>
  </cac:AccountingSupplierParty>

  <!-- Customer (Corner 4) -->
  <cac:AccountingCustomerParty>
    <cac:Party>
      <cbc:EndpointID schemeID="0235">100987654300003</cbc:EndpointID>
      <cac:PartyTaxScheme>
        <cbc:CompanyID>100987654300003</cbc:CompanyID>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:PartyTaxScheme>
    </cac:Party>
  </cac:AccountingCustomerParty>

  <!-- VAT calculated at line-item level (FTA Feb 2026) -->
  <cac:TaxTotal>
    <cbc:TaxAmount currencyID="AED">250.00</cbc:TaxAmount>
    <cac:TaxSubtotal>
      <cbc:TaxableAmount currencyID="AED">5000.00</cbc:TaxableAmount>
      <cbc:TaxAmount currencyID="AED">250.00</cbc:TaxAmount>
      <cac:TaxCategory>
        <cbc:ID>S</cbc:ID><cbc:Percent>5</cbc:Percent>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:TaxCategory>
    </cac:TaxSubtotal>
  </cac:TaxTotal>

  <cac:LegalMonetaryTotal>
    <cbc:LineExtensionAmount currencyID="AED">5000.00</cbc:LineExtensionAmount>
    <cbc:TaxExclusiveAmount currencyID="AED">5000.00</cbc:TaxExclusiveAmount>
    <cbc:TaxInclusiveAmount currencyID="AED">5250.00</cbc:TaxInclusiveAmount>
    <cbc:PayableAmount currencyID="AED">5250.00</cbc:PayableAmount>
  </cac:LegalMonetaryTotal>

  <cac:InvoiceLine>
    <cbc:ID>1</cbc:ID>
    <cbc:InvoicedQuantity unitCode="EA">10</cbc:InvoicedQuantity>
    <cbc:LineExtensionAmount currencyID="AED">5000.00</cbc:LineExtensionAmount>
    <cac:Item><cbc:Name>Consulting hours</cbc:Name></cac:Item>
    <cac:Price><cbc:PriceAmount currencyID="AED">500.00</cbc:PriceAmount></cac:Price>
  </cac:InvoiceLine>

</Invoice>

Field reference (51 mandatory fields — abbreviated)

UBL Path	PINT-AE Field	Cardinality	Notes
cbc:CustomizationID	Specification ID	1..1	Must equal `urn:peppol:pint:billing-3.0@ae-1`
cbc:UUID	Document UUID	1..1	RFC 4122 UUID — used for hash chain
cbc:IssueDate	Issue date	1..1	ISO 8601 (YYYY-MM-DD)
cbc:InvoiceTypeCode	Document type	1..1	388 = standard, 381 = credit note, 383 = debit note
EndpointID schemeID="0235"	UAE TRN endpoint	1..1	15-digit FTA TRN — Peppol participant identifier scheme 0235
PartyTaxScheme/CompanyID	VAT TRN	1..1	Supplier 15-digit TRN
TaxCategory/ID	Category code	1..1	S (standard), Z (zero-rated), E (exempt), O (out of scope), AE (reverse charge)
TaxCategory/Percent	VAT rate	1..1	5 for standard, 0 for zero-rated
DocumentCurrencyCode	Currency	1..1	ISO 4217 — usually AED
ext:UBLExtension (XAdES)	Digital signature	1..1	XAdES-B-B enveloped signature applied by supplier ASP
cac:AdditionalDocumentReference	Advance / retention (v1.1)	0..n	Appendix 5 — link to original advance or retention invoice

// Full 51-field list and validation rules: MoF e-Invoicing Guidelines v1.1 (1 Jun 2026) + FTA Technical Guidance Feb 2026.

Saudi Arabia · ZATCA

Fatoora — UBL 2.1 KSA + XAdES-B-B

KSA runs a centralised clearance model. Phase 2 (Integration) requires real-time clearance for B2B (standard invoices) and 24-hour reporting for B2C (simplified invoices) via the Fatoora platform. Each invoice carries a cryptographic stamp, UUID, signed XML hash, and a TLV-encoded QR.

// Standard invoice header (clearance request)

POST /invoices/clearance/single HTTP/1.1
Host: gw-fatoora.zatca.gov.sa
Content-Type: application/json
Accept-Language: en
Accept-Version: V2

{
  "invoiceHash": "kdugAg5IetK0Hf4iZxqYGGE4XaFcS6FK1ZtNYwBzKr8=",
  "uuid": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "invoice": "<base64-encoded-signed-UBL-XML>"
}

// TLV QR code structure (5 mandatory tags, B2C)

Tag 1 (Seller name)              variable len      "Acme Trading LLC"
Tag 2 (VAT registration number)  variable len      "300012345600003"
Tag 3 (Timestamp)                ISO 8601 UTC      "2027-01-15T14:30:00Z"
Tag 4 (Invoice total with VAT)   decimal string    "5250.00"
Tag 5 (VAT total)                decimal string    "250.00"

Encoded as TLV, base64 → printed as QR on receipt.

// Wave 24 integration deadline: 30 Jun 2026 (SAR 375k+ taxpayers). Penalty waiver ends same date.

Malaysia · LHDN / IRBM

MyInvois — UBL 2.1 JSON envelope

LHDN accepts both UBL 2.1 XML and JSON via the MyInvois API. Each invoice carries 55 mandatory fields, an LHDN digital certificate signature, and a 72-hour cancel/reject window. Any single transaction at or above RM 10,000 must be its own e-invoice (the RM 10k rule, enforced throughout the Phase 4 relaxation period to 31 Dec 2027).

// API submission

POST /api/v1.0/documentsubmissions HTTP/1.1
Host: api.myinvois.hasil.gov.my
Authorization: Bearer <token>
Content-Type: application/json

{
  "documents": [{
    "format": "JSON",
    "documentHash": "f2ca1bb6c7e907d06dafe4687e579fce76b37e4e93b7605022da52e6ccc26fd2",
    "codeNumber": "INV-2026-00001",
    "document": "<base64-encoded-UBL-JSON>"
  }]
}

// UBL 2.1 JSON skeleton

{
  "_D": "urn:oasis:names:specification:ubl:schema:xsd:Invoice-2",
  "_A": "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2",
  "_B": "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2",
  "Invoice": [{
    "ID": [{ "_": "INV-2026-00001" }],
    "IssueDate": [{ "_": "2026-06-15" }],
    "IssueTime": [{ "_": "14:30:00Z" }],
    "InvoiceTypeCode": [{ "_": "01", "listVersionID": "1.0" }],
    "DocumentCurrencyCode": [{ "_": "MYR" }],
    "AccountingSupplierParty": [{
      "Party": [{
        "IndustryClassificationCode": [{ "_": "46510", "name": "Wholesale of computer hardware" }],
        "PartyIdentification": [
          { "ID": [{ "_": "C12345678901", "schemeID": "TIN" }] },
          { "ID": [{ "_": "202301234567",  "schemeID": "BRN" }] }
        ],
        "PartyTaxScheme": [{ "TaxScheme": [{ "ID": [{ "_": "VAT" }] }] }]
      }]
    }],
    "LegalMonetaryTotal": [{
      "LineExtensionAmount": [{ "_": 10000.00, "currencyID": "MYR" }],
      "TaxExclusiveAmount":  [{ "_": 10000.00, "currencyID": "MYR" }],
      "TaxInclusiveAmount":  [{ "_": 10600.00, "currencyID": "MYR" }],
      "PayableAmount":       [{ "_": 10600.00, "currencyID": "MYR" }]
    }]
  }]
}

// LHDN e-Invoice Specific Guideline v4.7 (20 Apr 2026). Phase 4 enforcement begins 1 Jan 2028.

Oman · OTA

Fawtara — PINT-OM (Peppol 5-corner)

Oman follows the UAE pattern with a Peppol 5-corner decentralised model. The PINT-OM specification (published via OpenPeppol Apr 2026) is a UBL 2.1 subset with 53 mandatory + 46 simplified + up to 66 conditional fields. The supplier's ASP submits a Tax Data Document to Fawtara in parallel with delivering the e-invoice to the buyer's ASP. XAdES digital signatures are mandatory.

// Customization ID (PINT-OM)

<cbc:CustomizationID>urn:peppol:pint:billing-3.0@om-1</cbc:CustomizationID>
<cbc:ProfileID>urn:peppol:bis:billing</cbc:ProfileID>

<!-- VATIN format: OM + 8 digits + check digit -->
<cac:PartyTaxScheme>
  <cbc:CompanyID>OM1100001234</cbc:CompanyID>
  <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
</cac:PartyTaxScheme>

// Phase 1 go-live: Aug 2026 · ASP paid-up capital reduced from OMR 60k → 6k (May 2026).

// Implementation note

These payloads are scaffolds for integration design — not validated against live regulator sandboxes. For each mandate, use the official sandbox token (FTA EmaraTax, ZATCA Fatoora dev portal, MyInvois sandbox, OTA Fawtara sandbox) before production cutover. Cloudare's UAE/KSA/Oman/Malaysia implementation teams reconcile these to current regulator behavior on every engagement.

Want the full PINT-AE field spec, Fatoora cryptographic stamp template, and MyInvois 55-field reference? We will email you Cloudare's complete ASP payload PDF (~40 pages, no marketing fluff).