- 28
- March
Thai government agencies operate hundreds of IT systems, yet these systems "speak different languages" — they cannot exchange data across agencies. Staff must re-enter data manually, send paper documents, and wait for someone to key in the same information twice. This is not merely an inconvenience; it is the primary barrier to digital government — and TH-e-GIF is the standard designed specifically to solve this problem. This article explains what TH-e-GIF is, its 6 standard domains, and how ERP systems connecting to the Thai government must comply.
What is TH-e-GIF?
TH-e-GIF (Thailand e-Government Interoperability Framework)
A technical standards framework for connecting and exchanging data between Thai government agencies, developed and published by the Digital Government Development Agency (DGA) since 2006 (B.E. 2549). Currently at Version 2.0, it defines the technical standards that all government IT systems must follow, enabling efficient, secure, and standardized data communication between systems.
In simple terms, TH-e-GIF is like a "common language" that requires every government IT system to speak the same tongue — whether it's an ERP system, HR system, e-Tax system, or procurement system. All must use the same standards when exchanging data across agencies.
The 6 Standard Domains of TH-e-GIF
TH-e-GIF Version 2.0 organizes standards into 6 domains covering every aspect of data interoperability:
| Domain | Scope | Example Standards |
|---|---|---|
| 1. Interconnection | Protocols and methods for connecting systems | TCP/IP, HTTPS, TLS 1.2+, IPv4/IPv6 |
| 2. Data Exchange | Data formats used for exchange | XML, JSON, CSV, UTF-8 Encoding |
| 3. Web Technology | Web and Web Service standards | RESTful API, SOAP/WSDL, HTML5, CSS3 |
| 4. Data Integration | Database and Metadata standards | SQL, LDAP, Dublin Core, Data Catalog |
| 5. Security | Encryption, authentication, and security | OAuth 2.0, OIDC, PKI, Digital Signature, AES-256 |
| 6. Document Exchange | Electronic document formats | PDF/A, ODF, XML Signature, e-Document |
All 6 domains work together as a system — the Interconnection domain defines how to connect, Data Exchange defines the data format, and Security defines how to encrypt and authenticate. All domains must be supported simultaneously.
Why TH-e-GIF? — Before vs After the Standard
To illustrate clearly, let's compare the situation before and after TH-e-GIF:
| Issue | Before TH-e-GIF | After TH-e-GIF |
|---|---|---|
| Data format | Each agency defines its own — some use Excel, some PDF, some text files | Unified XML/JSON standard with defined schema |
| System integration | Custom connector for every pair — 10 agencies = 45 connectors | Standard APIs — 10 agencies = 10 APIs |
| Security | Some systems encrypted, some not — no central standard | Mandatory HTTPS/TLS + OAuth 2.0/OIDC + Digital Signature |
| Authentication | Each system uses different methods — username/password, tokens, certificates mixed | Centralized OAuth 2.0 / OpenID Connect standard |
| Integration cost | High — custom development needed for each new agency connection | Lower — same standard, build once, use with every agency |
| Integration timeline | 6-12 months per connection pair | 1-3 months when both sides support the standard |
Key Numbers
According to DGA data, Thai government agencies operate over 1,500 IT systems nationwide. Without a central standard, connecting all systems would require developing tens of thousands of custom connectors — impossible both budget-wise and technically. TH-e-GIF reduces the number of required connectors by several orders of magnitude through a centralized API standard.
TH-e-GIF and the Digital Government Plan 2025-2027
Thailand's Digital Government Development Plan 2025-2027, which recently completed public consultation on 23 March 2026, designates data interoperability between agencies as a core strategy with key goals:
- One Stop Service — Citizens contact a single point; data flows automatically between agencies
- Zero Copy — No duplicate document submission; agencies pull data from the central system
- Data-Driven Government — Decisions based on real data, not paper reports
- Open API — APIs open for private sector integration
None of this is possible without TH-e-GIF as the foundation — because TH-e-GIF is the "rulebook" that defines how systems communicate. This aligns with the concept of ERP Interoperability — an ERP system cannot be a closed system but must connect with others following standards.
API Standards Under TH-e-GIF
One of the most critical parts of TH-e-GIF is the API standard for data exchange:
| Topic | Required Standard | Details |
|---|---|---|
| API Style | RESTful API (primary) / SOAP (legacy) | New systems must support RESTful primarily; SOAP for legacy systems not yet upgraded |
| Data Format | JSON (primary) / XML | JSON for RESTful APIs; XML for SOAP and documents requiring Schema Validation |
| Authentication | OAuth 2.0 / OpenID Connect | Token-based authentication; no direct username/password transmission |
| Encryption | HTTPS / TLS 1.2+ | All data must be encrypted in transit; plain HTTP is prohibited |
| Digital Signature | XML Signature / JWS | Critical documents require digital signatures to prove data integrity |
| Encoding | UTF-8 | Full Thai language support with no character encoding issues |
| API Documentation | OpenAPI 3.0 (Swagger) | Every API must have documentation following the OpenAPI standard |
How Must ERP Systems Support TH-e-GIF?
For organizations using ERP systems, compliance with TH-e-GIF is essential for connecting with central government systems. Here is the compliance checklist:
| # | Requirement | What the ERP Must Do | TH-e-GIF Domain |
|---|---|---|---|
| 1 | RESTful API | Provide API endpoints for external systems to query and exchange data | Web Technology |
| 2 | JSON/XML Data Format | Send and receive data in JSON or XML as specified | Data Exchange |
| 3 | OAuth 2.0 / OIDC | Support token-based authentication (not just username/password) | Security |
| 4 | HTTPS / TLS 1.2+ | All API connections must be encrypted with TLS | Interconnection |
| 5 | Digital Signature | Support digital signatures on documents such as e-Tax Invoices, purchase orders, and receipts | Document Exchange |
| 6 | UTF-8 Encoding | Thai language data must not be corrupted whether via API or file export | Data Exchange |
| 7 | Audit Trail / Log | Log every API call — who called, when, what was sent, and the result | Security |
| 8 | API Documentation | Provide API documentation following OpenAPI 3.0 (Swagger) standard | Web Technology |
Important: Not Just for Government
While TH-e-GIF is a government standard, private companies selling software to the government or companies that exchange data with government agencies (e.g., submitting e-Tax Invoices to the Revenue Department, sending procurement data to e-GP) must also comply with TH-e-GIF standards.
Connection to Security Standards
The Security domain of TH-e-GIF goes beyond encryption to cover:
| Aspect | Standard | Purpose |
|---|---|---|
| Confidentiality | AES-256, TLS 1.2+ | Data is encrypted; intermediaries cannot read it |
| Integrity | SHA-256, Digital Signature | Verify data has not been tampered with in transit |
| Authentication | OAuth 2.0, OIDC, PKI | Verify the API caller's identity and authorization |
| Non-repudiation | Digital Signature, Timestamp | The sender cannot deny having sent the data |
| Audit | Logging, SIEM | Record and retrospectively review all data access |
All of this aligns with the principles of Smart Government ERP, which requires multi-layered security — not just a password and done.
Saeree ERP and TH-e-GIF Compliance
Saeree ERP was architecturally designed from the ground up to support government system connectivity following TH-e-GIF standards:
| TH-e-GIF Requirement | How Saeree ERP Complies |
|---|---|
| RESTful API | RESTful APIs across all modules with Swagger/OpenAPI 3.0 documentation |
| JSON/XML | Full JSON and XML data exchange with Schema Validation |
| OAuth 2.0 / OIDC | Token-based authentication following OAuth 2.0 standard |
| HTTPS / TLS | Mandatory HTTPS on all endpoints, supporting TLS 1.2 and 1.3 |
| Digital Signature | Digital signature support on critical documents (e-Tax Invoice, PO, receipts) |
| UTF-8 | System-wide UTF-8 encoding — no Thai character corruption |
| Audit Trail | Logs every API call and every data change |
TH-e-GIF is not just a technical standard — it is the foundation of digital government. An ERP system that does not support TH-e-GIF is like a system speaking a different language from every other agency — unable to send data, unable to connect, and destined to be left behind.
— Saeree ERP Team
Summary
TH-e-GIF (Thailand e-Government Interoperability Framework) is the most critical standard for Thai government data interoperability, covering 6 domains from interconnection and data exchange to web technology, data integration, security, and document exchange.
| Topic | Summary |
|---|---|
| TH-e-GIF is | A technical standards framework for government data interoperability |
| Developed by | DGA since 2006, currently Version 2.0 |
| 6 Domains | Interconnection, Data Exchange, Web Technology, Data Integration, Security, Document Exchange |
| Core API Standards | RESTful API + JSON + OAuth 2.0 + HTTPS/TLS |
| ERP Must Support | Standard API, Digital Signature, UTF-8, Audit Trail, OAuth 2.0 |
| Connected to | Digital Government Plan 2025-2027, One Stop Service, Zero Copy |
If your organization is about to connect an ERP system with government agencies, or is procuring a new ERP system, the first thing to verify is "Does this system support TH-e-GIF?" — you can schedule a demo or contact our consulting team to assess your organization's readiness.
