GETS Document Types

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

Overview

All document types are based on the LogicalDocType enum from the Java SDK. These represent the active logical document types that can be processed by the GETS system.

Logical Document Types for KSA

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

B2B Document Types (22)

Document Type	Description
`INVOICE`	Standard business invoice for goods and services.
`CREDIT_NOTE`	Credit note for invoice adjustments and corrections.
`DEBIT_NOTE`	Debit note for additional charges and corrections.
`RECEIPT`	Payment confirmation document.
`TAX_INVOICE`	Standard B2B tax invoice with full compliance requirements.
`TAX_INVOICE_CREDIT_NOTE`	Credit note for B2B tax invoice adjustments.
`TAX_INVOICE_DEBIT_NOTE`	Debit note for B2B tax invoice adjustments.
`TAX_INVOICE_PREPAYMENT`	Prepayment invoice for B2B transactions.
`TAX_INVOICE_PREPAYMENT_ADJUSTED`	Adjusted prepayment invoice for B2B transactions.
`TAX_INVOICE_EXPORT_INVOICE`	Export invoice for international B2B transactions.
`TAX_INVOICE_EXPORT_CREDIT_NOTE`	Export credit note for international B2B transactions.
`TAX_INVOICE_EXPORT_DEBIT_NOTE`	Export debit note for international B2B transactions.
`TAX_INVOICE_THIRD_PARTY_INVOICE`	Third-party invoice for B2B transactions.
`TAX_INVOICE_SELF_BILLED_INVOICE`	Self-billed invoice for B2B transactions.
`TAX_INVOICE_NOMINAL_SUPPLY_INVOICE`	Nominal supply invoice for B2B transactions.
`TAX_INVOICE_SUMMARY_INVOICE`	Summary invoice for B2B transactions.
`EXPORT_INVOICE`	Export invoice for international transactions.
`EXPORT_CREDIT_NOTE`	Export credit note for international transactions.
`EXPORT_THIRD_PARTY_INVOICE`	Export third-party invoice for international transactions.
`THIRD_PARTY_INVOICE`	Third-party invoice for domestic transactions.
`SELF_BILLED_INVOICE`	Self-billed invoice for domestic transactions.
`NOMINAL_SUPPLY_INVOICE`	Nominal supply invoice for domestic transactions.

B2C Document Types (12)

Document Type	Description
`SIMPLIFIED_TAX_INVOICE`	Simplified tax invoice for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_CREDIT_NOTE`	Simplified credit note for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_DEBIT_NOTE`	Simplified debit note for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_PREPAYMENT`	Simplified prepayment invoice for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_PREPAYMENT_ADJUSTED`	Simplified adjusted prepayment invoice for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_EXPORT_INVOICE`	Simplified export invoice for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_EXPORT_CREDIT_NOTE`	Simplified export credit note for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_EXPORT_DEBIT_NOTE`	Simplified export debit note for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_THIRD_PARTY_INVOICE`	Simplified third-party invoice for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_SELF_BILLED_INVOICE`	Simplified self-billed invoice for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_NOMINAL_SUPPLY_INVOICE`	Simplified nominal supply invoice for B2C transactions.
`SIMPLIFIED_TAX_INVOICE_SUMMARY_INVOICE`	Simplified summary invoice for B2C transactions.

Document Types for Malaysia

Malaysia's LHDN MyInvois system supports the following document types

Primary Document Types

Document Type	Description	Usage
`INVOICE`	Standard business invoice	All B2B and B2C transactions with SST
`CREDIT_NOTE`	Credit note for invoice corrections	Returns, discounts, corrections
`DEBIT_NOTE`	Debit note for additional charges	Additional charges, interest
`RECEIPT`	Payment confirmation	Cash receipts, payment acknowledgments

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

UAE's Federal Tax Authority (FTA) PINT system supports the following document types

FTA Document Types

Document Type	Description	VAT Treatment
`TAX_INVOICE`	Standard VAT invoice	Full VAT calculation and display
`SIMPLIFIED_TAX_INVOICE`	Simplified invoice for small amounts	Simplified VAT details (up to AED 10,000)
`CREDIT_NOTE`	Tax invoice credit note	VAT adjustment for returns/corrections
`DEBIT_NOTE`	Tax invoice debit note	VAT adjustment for additional charges

FTA PINT Requirements

TRN Validation: 15-digit Tax Registration Number required
UUID: Unique identifier for each invoice
Clearance: FTA clearance status tracking
Arabic Support: Bilingual invoice support (Arabic/English)
QR Code: Optional but recommended for B2C

Document Types for Belgium

Belgium follows EU standards with Peppol network integration

EU-Compliant Document Types

Document Type	Description	Standard
`TAX_INVOICE`	Standard B2B tax invoice	EN 16931-1:2017
`CREDIT_NOTE`	Invoice corrections and returns	EN 16931-1:2017
`DEBIT_NOTE`	Additional charges	EN 16931-1:2017
`SIMPLIFIED_INVOICE`	Simplified tax invoice	EN 16931-1:2017 (Simplified)

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

Document Type	Description	Standard
`INVOICE`	Standard business invoice	XRechnung 3.0 / EN 16931
`CREDIT_NOTE`	Invoice corrections	XRechnung 3.0 / EN 16931
`DEBIT_NOTE`	Additional charges	XRechnung 3.0 / EN 16931
`SELF_BILLED_INVOICE`	Customer-generated invoice	XRechnung 3.0

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

Implementation Example

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): 4 document types with FTA PINT compliance
Belgium (BE): 4 document types with Peppol and EN 16931 compliance
Germany (DE): 4 document types with XRechnung and GoBD compliance

All document types are based on the LogicalDocType enum and provide comprehensive coverage for various e-invoicing scenarios across supported countries.