Complyance Logo

GETS Schema

Notice: GETS uses a canonical schema model. Integration payload examples may use SDK-style paths for readability, but the canonical GETS meaning and required behavior are defined by the schema and country rules.

Welcome to the GETS (Global E-Invoice Transformation Standard) schema documentation. This section defines the canonical structure, required vs conditional behavior, country extensions, and field mapping guidance used by Unify API v3.

What is GETS?

The Global E-Invoice Transformation Standard (GETS) is a unified schema designed to handle e-invoicing requirements across countries and regions. It provides a standardized approach to electronic invoice processing while supporting country-specific compliance rules.

Supported Coverage

  • Saudi Arabia (KSA) - ZATCA compliance
  • Malaysia (MY) - LHDN and Peppol
  • Belgium (BE) - Peppol BIS
  • Germany (DE) - XRechnung/Peppol
  • United Arab Emirates (AE) - PINT AE

Important Clarifications

  • Use documentNumber as the canonical field meaning (SDK/sample payloads may show invoice_data.document_number).
  • documentId is a retrieval/status identifier, not the invoice number.
  • Use Base/Variant/Modifiers instead of legacy logicalDocumentType for new integrations.
  • Follow country code lists and enum rules from the country mapping pages.

Key Features

  • Global Compatibility - Works across multiple countries
  • Country-aware Validation - Required/conditional rules by jurisdiction
  • Code-list Driven - Enum and codelist-based validation
  • Standardized Canonical Model - Consistent semantics across integrations

Support

Need help with GETS implementation? Check out our support documentation or Contact Complyance for E-Invoicing. Complyance has helped over 1000+ organizations simplify global e-invoicing. Let us help you understand how Complyance can work for you.