Complyance Logo

Complete UAE GETS payload

The complete UAE payload exposes every GETS field registered for a UAE tax invoice in the current schema release.

Download uae-complete-gets-payload.json

The current artifact contains 373 registered paths: 306 core, 40 regional, and 27 UAE-specific fields. It is generated from the same schema resolver and example factory used to provision the ISV Payload Manager default.

How to use it

  1. Download the JSON file or select Default UAE GETS Payload in the ISV Payload Manager.
  2. Replace the populated example values with values from your billing system.
  3. Review every mandatory or conditionally mandatory field for your document type.
  4. Keep optional unused fields as null, empty arrays, or remove them.
  5. Wrap the payload in a Unify V2 request.
  6. Use the exact Source identity returned by company onboarding.

null means “not supplied.” It is not a valid substitute for a field that is mandatory for the selected document type or scenario.

Participant identifiers

Peppol identifier values and schemes are separate fields. For 0235:1234567890:

{
  "parties": {
    "buyer": {
      "peppolId": "1234567890"
    }
  },
  "extensions": {
    "peppol_buyer_peppolIdScheme": "0235"
  }
}

Apply the same rule to the seller using parties.seller.peppolId and extensions.peppol_seller_peppolIdScheme.

Arrays are examples, not limits

The download includes one representative line, tax subtotal, payment method, attachment, allowance or charge, and related-document object so every nested field is visible. Add or remove array entries to match the invoice.

Document scenarios

The download is a standard tax_invoice example. For another scenario, update header.documentType and populate the fields required by that scenario. Examples include credit notes and modifiers such as export, self_billed, margin_scheme, and reverse_charge.

Do not assume one standard invoice proves every UAE scenario. Validate the actual document type you plan to submit.

Related pages