GETS Schema

Global E-Invoice Transformation Standard (GETS)

Version 1.0 - A comprehensive middleware schema for electronic invoicing that serves as a superset of UBL 2.1 while providing enhanced framework to support global e-invoicing requirements.

Design Principles

Core principles driving the GETS schema design

Single Integration

Integrate once, comply everywhere with unified interface for all e-invoicing standards

Extensibility & Flexibility

Multiple destinations support with custom fields and delivery options

Technical Architecture

Cross-platform compatibility with developer-friendly field names

Data Minimalism

Essential fields only required by default, with efficient data transformation as needed.

Schema Structure

Core components of the GETS payload structure

Unified API Operation Parameter

The root object includes method, mode, and operation fields to indicate the request type and processing mode.

{
  "method": "POST",           // HTTP method (GET, POST, PUT, DELETE, etc.)
  "mode": "documents",        // Operation type (documents, onboarding)
  "operation": "single",      // Processing mode (single)
  "source": { ... },
  "destinations": [ ... ],
  "payload": { ... }
}

Mode values: documents (for e-invoice submission), onboarding (for participant setup)
Operation values: single (one object)

Core Document Types

Supported document types in the GETS schema

tax_invoice

Standard tax invoice

credit_note

Credit note document

debit_note

Debit note document

Document Processing Modes

Different modes for processing documents through GETS

Single Mode

Default

Process one document at a time with immediate validation and response. This mode is optimized for real-time applications where immediate feedback is crucial for user experience.

Key Features

Real-time processing

Immediate feedback

Best for interactive flows

Low latency response

Error handling per document

Use Cases

Web applications with user forms

API integrations requiring immediate validation

Mobile applications

Testing and development environments

Performance

Response Time:< 2 seconds

Throughput:1 document/request

Validation:Immediate

Complete Field Definitions

Comprehensive field definitions based on GETS schema registry with data types, requirements, and descriptions

Header Fields

Field Path	Name	Data Type	Required	Description
header.documentType	Document Type	string	Required	Type of document
header.documentNumber	Document Number	string	Required	Unique document number
header.issueDate	Issue Date	string	Required	Document issue date
header.issueTime	Issue Time	string	Optional	Document issue time (HH:MM or HH:MM:SS:0000)
header.currency	Currency	string	Required	Document currency
header.taxCurrency	Tax Currency	string	Optional	Tax currency (often same as document currency)
header.exchangeRate.rate	Exchange Rate	number	Optional	Exchange rate when currency differs from tax currency
header.dueDate	Due Date	date	Optional	Payment due date
header.referenceId	Reference ID	string	Optional	Original invoice reference ID
header.noteIssuanceReason	Note Issuance Reason	string	Optional	Reason for credit/debit note