GETS Schema

Notice: These docs cover GETS Schema v1. For upcoming version details, see the Compatibility Matrix.

Welcome to the GETS (Global E-Invoice Transformation Standard) Schema documentation. This section provides comprehensive information about the unified schema structure, country-specific extensions, supported document types, and field mappings for global e-invoicing compliance.

What is GETS?

The Global E-Invoice Transformation Standard (GETS) is a unified, country-agnostic schema designed to simplify e-invoicing compliance across multiple countries and regions. Rather than building separate integrations for each country's unique requirements, GETS provides:

• Unified Data Model - A single, consistent schema that works across all supported countries
• Country Extensions - Flexible extension mechanisms to accommodate country-specific legal and technical requirements
• Standardized Validation - Built-in rules ensuring compliance with each country's tax authority requirements
• Integrated Submission - Direct integration with tax authorities and compliance networks

GETS acts as the transformation bridge between your business systems (ERP, invoicing platforms, etc.) and the specific formats required by tax authorities like ZATCA (Saudi Arabia), LHDN (Malaysia), Peppol (EU), XRechnung (Germany), and UAE e-invoicing standards.

Core Components

Unified API

The single entry point for all validation, transformation, and submission workflows. Handles payload processing across all supported countries with automatic routing to the appropriate tax authority or compliance network.

Source Configuration

Documents where invoices originate from—your ERP system, POS platform, billing software, or other business system. This tracking ensures audit trails and version compatibility across your invoice lifecycle.

Destinations

Specifies where transformed invoices are delivered: tax authority portals, Peppol networks, or custom compliance endpoints. GETS automatically handles all necessary format conversions for each destination.

Documentation Structure

Schema Overview

Deep dive into the core GETS schema structure, including:

• Schema architecture and design principles
• Source and destination configuration
• Complete field definitions and data types
• Required vs. optional fields
• Data validation rules

Country Extensions

Country-specific customization requirements:

• Saudi Arabia (SA) - ZATCA prepayment fields and compliance extensions
• Malaysia (MY) - LHDN submission requirements
• United Arab Emirates (AE) - Free-zone, agency, and customs fields
• Belgium (BE) - Co-contractor and VAT declaration fields
• Germany (DE) - XRechnung tax point and compliance fields

Document Types

All supported document types organized by country:

• Tax invoices, simplified invoices, and B2C variants
• Credit notes and debit notes
• Prepayment invoices
• Export invoices
• Self-billed invoices and special document types
• Compliance-specific document formats

Key Features

• Global Compatibility - Single schema works across SA, MY, AE, BE, DE, and more
• Flexible Extensions - Add country-specific fields without changing core schema
• Comprehensive Validation - Field-level validation aligned with tax authority rules
• Standardized Format - Consistent, JSON-based structure for easy integration
• Direct Tax Authority Integration - Built-in submission workflows for compliant filing
• Version Tracking - Source and system version tracking for audit and debugging

Supported Countries

Quick Start

1. Understand the Base Schema - Read Schema Overview for core concepts
2. Check Country Extensions - Review Country Extensions for your target countries
3. Review Document Types - Explore Document Types for supported invoice formats
4. Plan Integration - Use field definitions to map your business data to GETS fields
5. Validate & Submit - Use GETS Unified API for automatic validation and tax authority submission

Common Questions

Q: Do I need to redesign my system to use GETS? No. GETS is a transformation layer. Your existing systems stay the same; GETS maps your data to compliance-required formats.

Q: Which countries should I start with? Start with your primary market. GETS supports progressive multi-country rollout with minimal additional work per new country.

Q: Are there field mapping guides? Yes. Check our Field Mapping Reference for detailed Unify API v3 payload mappings.

Q: How do I handle country-specific requirements? Use country extensions. See Country Extensions for SA, MY, AE, BE, and DE customizations.

Need Help?

Have questions about GETS implementation or integration? Contact Complyance for E-Invoicing. We've helped over 1000+ organizations simplify global e-invoicing and can guide your compliance journey.