Field Mapping Payload Reference
Complete field mapping reference for all Unify API v3 payload fields organized by country.
Last Updated: 2026 · Scope: SA · MY · BE · DE · AE
Overview
This page is the entry point for country-specific field mappings.
Each country page contains:
- Full field mapping tables with original column names and examples
- Country-specific extension fields merged from GETS Country Extensions
- Data formatting and implementation notes for production use
Country Extensions Overview
Country extension fields are additional fields applied on top of the base mapping for regulatory or network-specific requirements.
Requirement levels
| Code | Meaning |
|---|---|
M | Mandatory |
CM | Conditionally mandatory |
O | Optional |
Country extension coverage summary
| Country | Extension status | Notes |
|---|---|---|
| Saudi Arabia (SA) | Active | sa_prepayment extension is used for prepayment and adjustment scenarios. |
| Malaysia (MY) | Base model only | Uses standard GETS payload without a separate extension block. |
| United Arab Emirates (AE) | Active | UAE-specific extension fields for authority, customs, process, and tax-currency details. |
| Belgium (BE) | Active | VAT and digital timestamp extension fields are supported. |
| Germany (DE) | Active | XRechnung-related extension fields are supported, including preceding invoice date behavior. |
Country Pages
| Country | Code | Coverage | Page |
|---|---|---|---|
| Saudi Arabia | SA | ZATCA field mapping + SA prepayment extensions | Open Saudi Arabia Field Mapping |
| Malaysia | MY | LHDN field mapping + Malaysia extension notes | Open Malaysia Field Mapping |
| Belgium | BE | Peppol BIS mapping + BE VAT/digital extensions | Open Belgium Field Mapping |
| Germany | DE | XRechnung mapping + DE extension fields | Open Germany Field Mapping |
| United Arab Emirates | AE | PINT AE mapping + AE extension fields | Open UAE Field Mapping |
How To Use This Reference
- Open your country page from the table above.
- Start with Document Header Fields, then follow Seller, Buyer, Line Items, and Totals in order.
- Review the Country Extensions (Merged) section to include country-only fields.
- Keep the field semantics exactly as documented in the table columns.
Data Formatting Guidelines
- Dates: All dates must be in
YYYY-MM-DDformat (e.g.,2024-01-15) - Times: All times must be in
HH:MM:SSorHH:MM:SSZformat (e.g.,14:30:00) - Decimal Amounts: Use
.as decimal separator (e.g.,1000.00) - Currency Codes: Follow ISO 4217 standard (e.g., SAR, MYR, EUR, AED)
- Country Codes: Follow ISO 3166-1 alpha-2 standard (e.g., SA, MY, BE, DE, AE)
- Phone Numbers: Include country code (e.g.,
+966501234567) - Amounts: Always include two decimal places (e.g.,
1234.56)
See Also
- Integration Guide — Complete API integration documentation
- Examples — Code examples and cURL requests
- Error Codes — Comprehensive error reference