The submission is the easy part. The work is getting your ERP to produce an ETDA-standard document with the right Thai identifiers, signing it with a certificate that has not expired, and making sure every document for the month reaches the Revenue Department by the 15th.
None of these are exotic, but most ERPs implemented outside Thailand carry at least two of them badly.
Every document identifies the seller and buyer by Tax ID and by branch — head office or a numbered branch. Few charts of accounts carry branch as a first-class field.
Names and addresses in Thai where required. An ERP that stores one language per field needs a second one, or a mapping table.
Thai documents commonly show Buddhist Era dates. The ERP stores Gregorian; the conversion belongs in the mapping, not in the data.
Each adjustment has to reference the document it corrects — the same problem that slows down every e-invoicing rollout.
Certificates expire. Renewal has to be tracked like a payroll date, because electronic issuance stops on the day it lapses.
Month-end close and the reporting deadline become one calendar. Late postings to a closed month need a defined process.
API and OData extraction patterns for invoice data.
View SAP integration →Connector patterns for Finance & Operations.
View D365 integration →REST and interface-table extraction for both stacks.
View Oracle integration →Mid-market connectivity for multi-entity groups.
View Sage integration →Direct module integration for fast-growing businesses.
View Odoo integration →Staging-table and file-based methods for anything else.
View other integrations →