GETS Document Types

Comprehensive reference for all supported document types in the Global E-Invoice Transformation Standard (GETS)

Overview

This page includes legacy LogicalDocType enum values for existing Java SDK integrations alongside current country-specific contracts. New integrations should use Base/Variant/Modifiers as defined in the applicable country guide.

Logical Document Types for KSA

All 34 active logical document types based on the GETS LogicalDocType enum

B2B Document Types (22)

B2C Document Types (12)

Document Types for Malaysia

Malaysia's LHDN MyInvois system supports the following document types

Primary Document Types

MyInvois-Specific Requirements

• Invoice Number Format: Must follow sequential numbering
• SST Compliance: Sales and Service Tax details required
• TIN Validation: Tax Identification Number mandatory
• Classification Codes: Business activity codes required
• Multi-Currency: Support for MYR and foreign currencies

Document Types for UAE

Use UAE document types and treatments for the ratified UAE document contract.

The UAE contract uses two customer-facing document selections—Tax Invoice and Tax Credit Note—across six supported routes:

• Ordinary tax invoice
• Ordinary tax credit note
• Out-of-scope commercial invoice
• Out-of-scope commercial credit note
• Self-billed tax invoice
• Self-billed tax credit note

Debit notes and separate UAE document variants are not included in the current contract. The UAE reference defines the customer selections, official document type codes, treatment compatibility, and PINT AE validation profiles.

Document Types for Belgium

Belgium follows EU standards with Peppol network integration

EU-Compliant Document Types

Belgium-Specific Requirements

• VAT Format: BE + 10 digits
• CBE Number: Crossroads Bank for Enterprises registration
• Peppol ID: Format 9925:BEXXXXXXXXXX
• Multi-Language: French and Dutch support
• IBAN/BIC: Required for payment information

Document Types for Germany

Germany's XRechnung format follows EU standards with additional requirements

German Document Types

XRechnung Requirements

• Leitweg ID: Routing identifier for public administration
• Buyer Reference: Mandatory purchase order reference
• GoBD Compliance: 10-year archiving requirement
• Tax Number: German Steuernummer format
• SEPA: SEPA payment integration support
• Format: XML-based XRechnung or ZUGFeRD

Document Type Usage

Legacy Implementation Example

This LogicalDocType example applies only to legacy integrations. New integrations should use Base/Variant/Modifiers as defined in the applicable country guide.

import io.complyance.sdk.LogicalDocType;

// Use logical document types
LogicalDocType docType = LogicalDocType.TAX_INVOICE;

// Create document with logical type
Map<String, Object> invoice = Map.of(
    "logicalDocType", docType.name(),
    "invoiceNumber", "INV-001",
    "issueDate", "2024-01-15",
    "seller", sellerData,
    "buyer", buyerData,
    "items", itemsData
);

Summary

The GETS platform supports comprehensive document type coverage across multiple countries:

By Country

• Saudi Arabia (KSA): 34 document types (22 B2B, 12 B2C) with ZATCA compliance
• Malaysia (MY): 4 primary document types with LHDN MyInvois integration
• United Arab Emirates (UAE): 2 customer-facing document types and 6 supported routes with FTA PINT compliance; see UAE document types and treatments
• Belgium (BE): 4 document types with Peppol and EN 16931 compliance
• Germany (DE): 4 document types with XRechnung and GoBD compliance

The LogicalDocType enum applies only to legacy integrations. New integrations should use Base/Variant/Modifiers as defined in the applicable country guide.