Prepare an invoice

Download the sample payload

This is the UAE GETS sample from the published documentation. It is a starting point, not a registered test identity or an invoice ready to send unchanged. Confirm its structure matches your source’s mapping; otherwise use a matching sample from your system.

Replace the example data

Use a document number such as INV-2026-0142 that you have not already submitted for this test. Replace all sample identity values with your agreed sandbox details.

Keep the Peppol identifier value in parties.buyer.peppolId separate from its scheme in extensions.peppol_buyer_peppolIdScheme. For a UAE identifier using scheme 0235, do not put the 0235: prefix into the identifier value itself.

Wrap the payload for Unify

jq --arg source "${COMPLYANCE_SOURCE}" '{
  country: "AE",
  environment: "sandbox",
  purpose: "invoicing",
  source: $source,
  documentType: {
    base: "tax_invoice",
    modifiers: []
  },
  payload: .
}' uae-invoice-payload.json > uae-invoice-request.json

COMPLYANCE_SOURCE must match the returned sourceName:sourceVersion. Leave the country and environment as AE and sandbox for this walkthrough.

Review the request

jq -e '.country == "AE" and .environment == "sandbox" and (.source | length > 0) and (.payload | type == "object")' uae-invoice-request.json

This checks the request envelope and JSON structure. It does not replace invoice validation or verify the buyer’s identity.