# Country extensions

Country extensions add fields to GETS for a specific country. Find the relevant field paths and requirements before submitting that country's documents.

Start with your country’s fields page below. In **Table**, read **Requirement** and the conditions in **Description**; **Enums** lists fixed allowed values. The requirement summarises all document types, modifiers and variants for the country, and **Required fields by document type** under the table lists them per document type. Open **List with sample request** to select your document type, modifiers and variant under **Scope** and see the matching requirements and payload paths.

`payload.extensions` holds additional document-level fields; individual `payload.lineItems[]` can also have `extensions`. Do not send every extension you see in a sample: supply those that apply to your document.

## Find the country requirements

- [United Arab Emirates (AE)](https://docs.complyance.io/countries/ae/fields/): UAE fields and conditions. Use the UAE code lists for coded values.
- [UAE code lists](https://docs.complyance.io/countries/ae/code-lists/): Allowed values for UAE coded fields.
- [Saudi Arabia (SA)](https://docs.complyance.io/countries/sa/fields/): Saudi Arabia fields and conditions. Values for coded fields are on its code lists page.
- [Oman (OM)](https://docs.complyance.io/countries/om/fields/): Oman fields and conditions. Values for coded fields are on its code lists page.
- [Malaysia (MY)](https://docs.complyance.io/countries/my/fields/): Malaysia fields and conditions. Values for coded fields are on its code lists page.
- [Belgium (BE)](https://docs.complyance.io/countries/be/fields/): Belgium fields and conditions. Document types are on its code lists page.
- [Germany (DE)](https://docs.complyance.io/countries/de/fields/): Germany fields and conditions. Values for coded fields are on its code lists page.

The country guides provide local requirements. Each country also has a code lists page, such as [Saudi Arabia code lists](https://docs.complyance.io/countries/sa/code-lists/), with the values its coded fields accept. The [field reference](https://docs.complyance.io/api-reference/gets/fields/) shows the core fields every country starts from.

## Example: document and line extensions

These paths and sample values appear in a UAE [Unify request example](https://docs.complyance.io/api/?operation=submitDocument). This is a **payload excerpt**, not a complete invoice. Include a country field only when its condition applies:

```json title="UAE extension fields (excerpt)"
{
  "payload": {
    "lineItems": [
      {
        "extensions": {
          "ae_itemType": "Services"
        }
      }
    ],
    "extensions": {
      "ae_buyer_authorityName": "Dubai Department of Economy and Tourism",
      "peppol_buyer_peppolIdScheme": "0235"
    }
  }
}
```

`ae_itemType` belongs to a line, while `ae_buyer_authorityName` belongs to the document. The `peppol_buyer_peppolIdScheme` value describes the buyer’s Peppol identifier scheme. Use the field reference to check the requirement and allowed values for your selection. The [quickstart](https://docs.complyance.io/get-started/quickstart/) has a complete UAE invoice you can submit in sandbox.

## If validation fails

For `422`, read each error’s `getsPath` and `message`. Check that the field is at the documented path, the country and document type match your selection, and coded values come from the applicable list. See [Unify errors](https://docs.complyance.io/api-reference/unify/errors/) for the full error shape.

Source: https://docs.complyance.io/api-reference/gets/country-extensions/