thailand's cpa base under the federation of accounting professions is in the tens of thousands, with bangkok carrying a large share. the firms split between three tiers: big four bangkok offices (pwc, deloitte, ey, kpmg) at the top, a mid-tier of 10 to 50 staff firms doing the day-to-day bookkeeping and tax compliance for thai smes and expat-owned businesses, and a long tail of single-cpa or partnership firms with portfolios of 40 to 120 clients. the mid-tier is the operating layer we build for. flowaccount is the dominant smb accounting tool in thailand. peakaccount and xero asia cover the english-first segment that expat-owned businesses gravitate to. business plus covers the larger enterprise tail.
the practice operations look the same across the tier. month-end close is a recurring sprint between days one to ten of each month. vat returns (po.po.30) due by the fifteenth, withholding tax returns (po.ngo.do.3, 53) due by the seventh, corporate income tax (po.ngo.do.50, 51) on a half-year and full-year cycle. each return requires data pulled from the accounting platform, reconciled against bank statements, formatted into the revenue department template, signed off by the cpa, and lodged through the rd portal or a tax preparation tool. the work is repetitive, time-sensitive, and unforgiving on accuracy. a junior accountant spends the majority of their monthly hours on input, reconciliation and chase work that requires availability, not technical judgment.
claudekick for bangkok accountants removes that input work without breaking the discipline of a thai accounting practice. claude wires onto flowaccount, peakaccount or xero asia via the documented api. bank statement import from bay, scb, kbank, bangkok bank and ttb is parsed and categorised against the firm's chart of accounts. vat preparation pulls invoices from the accounting platform, reconciles against bank transactions, and generates the po.po.30 template ready for the cpa to review and lodge. month-end prepper generates the close checklist with exceptions flagged. invoice chaser writes client emails or line oa messages in the senior accountant's voice. year-end audit prep generates the trial balance and supporting schedules in the format the external auditor expects.
governance sits on top, not as an afterthought. the federation of accounting professions code of ethics requires confidentiality of client information. pdpa requires data flow mapping, retention rules and a legitimate basis for processing client financial data. the cross-border data transfer question (claude api hits anthropic infrastructure outside thailand) is answered in the architecture: anthropic dpa in place, retention rules set so client data is not stored longer than the firm's own retention policy, audit log per workflow that survives an external audit or a regulator review. delivered alongside the technical build so the firm's senior partner can sign off before any client data flows through the system.