Accounting System Selection & Migration in Thailand

Selection criteria that hold up in a Thai business

First, the system must produce filing-ready local reports: output tax and input tax reports, and the data behind withholding. If figures must be reworked by hand every month, the work has simply moved. Second, it should handle bilingual customer documents, since businesses with foreign counterparties issue English invoices while reporting internally in Thai. Third, user rights must separate duties, so whoever raises invoices is not the person approving payments.

The point most often ignored is getting data out. A system that exports every transaction in a standard file makes changing provider later unfrightening, and lets the auditor work from transaction files instead of screenshots. Integration with point-of-sale or e-commerce platforms is worth paying for only when volumes make it cheaper than importing a daily summary file.

A migration plan where opening balances can be proved

We always cut over at a month end, and at a financial year end where there is a choice, so the opening balances tie to audited statements. Before moving we print a reference set from the old system as evidence: the trial balance, receivable and payable detail by counterparty, the fixed asset register with accumulated depreciation, inventory by item, and the final month's tax reports. That set is what proves the new system's data was not simply typed in as totals.

After the import we run one parallel month: entries go into the new system while key balances are checked against the old one or against source documents. That month surfaces what sample testing misses — different tax rounding, wrong tax codes on some product groups, or a document layout a customer rejects. Once the month closes and balances agree, the old system stops being primary, while access to its data is retained for the statutory document retention period.

E-tax invoicing, data retention and internal control

Issuing e-tax invoices needs both technical and procedural readiness. Technically: the file format and either an electronic signature or an approved service provider. Procedurally: who may issue documents, how credit notes or cancellations are handled when something is issued wrongly, and delivery to the customer with proof of sending. Companies that solve only the technical half typically end up with duplicate documents or gaps in the numbering.

On retention, decide two things: where the data sits and who can reach it, and whether the company holds its own copy. Cloud systems are convenient, but schedule an export the company keeps at least quarterly, so access to history does not depend on the status of an account with a provider. The internal control with the most practical effect is separating whoever records from whoever approves, and leaving the edit audit trail switched on.

When to act, and when waiting is fine

• You still use a spreadsheet with a single user

  Move once more than one person edits the data; a spreadsheet leaves little usable edit trail

• You are heading into your first audit

  Make sure the system can export the full year's transactions before fieldwork begins; it cuts the time spent answering questions

• A counterparty is asking for e-tax invoices

  Confirm the system supports the format and the cancellation of wrongly issued documents before agreeing; fixing later is worse than preparing

• You run several branches and want results by branch

  Use dimensions alongside account codes from the start; duplicating codes per branch bloats the chart and complicates consolidation