Cloud Accounting & Digital Workflows

Define the requirements before choosing software

List the legal entities, branches, currencies, bank accounts and sales channels. Decide whether you need inventory, project costs, customer billing, purchase approvals, payroll integration or group reporting. Identify which documents must be produced in Thai or English and which data the accountant needs for statutory filings.

For a service business, project profitability and time-related billing may matter more than stock. For a retailer, item-level sales, returns and settlements may be central. For a BOI-promoted company, project-level separation and evidence may affect the accounting design. Avoid selecting a system only because its dashboard looks familiar.

• Can the chart of accounts and tax codes reflect the actual business?
• Can transactions be traced to their source documents and approval?
• Can the company export ledgers, attachments and relevant reports?
• Are branch details, invoice numbering and permissions configurable?
• What work remains manual, and who is responsible for it?

Design the document-to-report workflow

On smaller screens, scroll the table sideways to see all columns.

Automated extraction can misread a tax number, confuse an invoice with a receipt or import the same document twice. Keep a review queue for exceptions. An integration should be tested using real examples from each transaction type rather than one simple invoice that happens to work.

Migrate accounts with a reconciliation plan

1. Choose the cut-over date. Confirm the last period closed in the old system and who can still amend it.
2. Export and preserve the source. Retain ledgers, reports, attachments and the data needed to reproduce past filings.
3. Map the data. Align account codes, customer and supplier records, tax codes and reporting dimensions.
4. Import controlled opening balances. Reconcile banks, receivables, payables, assets and other material schedules to the approved trial balance.
5. Run a parallel check. Compare a representative reporting period and investigate differences before declaring the migration complete.

Decide whether to migrate full transaction history or opening balances with a retained archive. The right answer depends on reporting needs, data quality and cost. Neither approach should lose access to the evidence supporting earlier accounts.

Digital invoices and statutory e-tax documents

An invoice generated as a PDF is a digital document, but that alone does not make it an authorised e-Tax Invoice or e-Receipt. Review registration, format, authentication, submission and preservation requirements for the chosen official route. The Revenue Department’s e-Tax Invoice & e-Receipt service is the reference point for that framework.

Software must also support the relevant underlying tax-invoice rules. Confirm who checks mandatory information, manages credit notes and handles a document rejected by a customer or the transmission process. A system provider’s marketing statement should be tested against the company’s actual intended use.

If a tax incentive is relevant to software or implementation expenditure, obtain a separate eligibility review before including the benefit in a budget. The purchase of accounting software does not automatically qualify every business or every cost for a deduction beyond the ordinary rules.

Access, backups and ownership of the records

Keep the subscription and administrative recovery arrangements under agreed company control. Give users the access needed for their role: data entry, review, reporting and payment approval should not all be bundled into a shared administrator login. Use individual accounts and the security options supported by the platform.

Agree how employee data, identity documents and bank information will be shared. Sensitive payroll files may need a restricted workflow instead of the general bookkeeping folder. When someone leaves, revoke access and transfer any necessary responsibilities without losing the audit trail.

The Accounting Act’s retention obligations still matter when records are digital. Confirm where records are stored, how they can be retrieved and whether the arrangement satisfies applicable requirements. Maintain usable exports and test retrieval; the existence of a provider’s backup policy does not prove the company can obtain a complete archive after cancellation.

What an implementation scope should include

Define the system, entity and periods covered; data cleaning; configuration; migration; report design; training; and post-launch support. Identify subscription and integration fees separately from professional implementation work. List the checks that demonstrate acceptance, such as a reconciled opening trial balance and correct sample invoices.

For the initial discussion, prepare your current software details, sample exports, transaction volumes and the problems you want to solve. A short list of specific outcomes—fewer duplicate entries, faster document retrieval or project margins by month—creates a better implementation plan than a general request to “go digital”.