GETS schema

GETS is the standard invoice format used across countries. Use this overview to choose a document type and find the fields your country requires.

Your integration maps source invoice data to GETS, so you can invoice across countries without building a new integration from scratch for each one. Choose a country and documentType to find the fields required for that document.

Find the right fields

Choose a document type for the country. Select one base, optional variant and applicable modifiers in the request’s documentType.
Open the GETS field reference. Use the country dropdown to select your country and remove any other selected countries. The Table view shows field names, Requirement, Type, Description and, for fields with fixed allowed values, Enums.
Open List with sample request and select your document type, modifiers and variant under Scope. This view shows payload paths and the requirements for your selection beside a sample request.
Check country extensions for country-only fields and links to country field requirements. For UAE coded fields, use the UAE code lists.

In Table, Requirement summarises all document types, modifiers and variants for the country: Mandatory fields are always required, Conditional fields are required when the condition in Description applies, and Optional fields are not required. Do not assume a field optional for one country is optional for another.

How GETS organises an invoice

GETS field group	What it describes
`header`	Document details such as `documentNumber`, `issueDate` and `currency`.
`parties`	Seller and buyer details.
`lineItems`	Items or services being invoiced.
`totals`	Document amounts.
`extensions`	Additional fields for a country or applicable standard, when needed.

The following excerpt illustrates a UAE invoice in GETS. It is not a complete submission:

UAE document type and GETS header (excerpt)json

{
  "country": "AE",
  "documentType": {
    "base": "tax_invoice",
    "modifiers": []
  },
  "payload": {
    "header": {
      "documentType": { "base": "tax_invoice" },
      "documentNumber": "INV-2026-000184",
      "issueDate": "2026-09-18",
      "currency": "AED"
    }
  }
}

For a complete example of GETS fields and a sandbox response, see Send your first invoice. A successful Unify submission returns 200 with a documentId; use it to follow the document. A 422 response lists validation problems, including the GETS field path where available. See Unify errors to correct them before resubmitting.