Most Thai SME owners do not lose sleep over whether Odoo can calculate VAT correctly. It can. What keeps finance managers up at night is the calendar: which report is due on which day, and whether the number the Revenue Department expects actually matches what Odoo shows on screen. Odoo accounting Thailand setups can get this right. But only when the tax configuration and the closing routine are treated as part of the same job. We have sat through enough month-end closes with Thai clients to know the gap between "the system is configured correctly" and "the filing is submitted on time" is almost always a process gap, not a software gap.
This post lays out a working compliance calendar for Odoo accounting Thailand setups, phase by phase, with the exact screens and reports behind each number. It assumes VAT and withholding tax are already configured. If you are still setting that up, start with Odoo implementation services built for Thai filing requirements rather than a generic install.
Why Odoo accounting Thailand setups live or die on the monthly rhythm
Two filings repeat every month for almost every Thai company, regardless of size: VAT (Por Por 30) and withholding tax (PND 3 and PND 53). The deadlines are not the same. VAT is due by the 15th of the following month on paper, or the 23rd through the e-filing portal. Withholding tax is due earlier: the 7th on paper, or the 15th through e-filing. Mixing these two up is one of the most common scheduling mistakes we see.
In Odoo, the VAT number comes from the Tax Report under Accounting > Reporting. This report reads directly from the tax grids attached to each invoice line. That is why we insist on correct tax mapping during setup, rather than after the first filing goes wrong. If a vendor bill was posted with the wrong tax tag, the Tax Report will be wrong, and no amount of manual Excel reconciliation fixes that at the source.
Withholding tax numbers come from a different place: the Withholding Tax Report. It pulls from the WHT entries generated when you post a vendor bill or customer invoice with a WHT tax applied. We have seen companies compute WHT using a spreadsheet pulled from bank statements, and that almost always diverges from what Odoo actually posted, because the spreadsheet remembers payments while Odoo remembers invoices and the tax lines attached to them. Reconcile against the system, not against memory.
Where each monthly number actually lives
| Filing | Due date (paper / e-filing) | Odoo report | Source data |
|---|---|---|---|
| VAT (Por Por 30) | 15th / 23rd of next month | Accounting > Reporting > Tax Report | Tax grids on invoice/bill lines |
| WHT PND 3 (individuals) | 7th / 15th of next month | Accounting > Reporting > Withholding Tax Report | WHT tax on vendor bills to individuals |
| WHT PND 53 (companies) | 7th / 15th of next month | Same report, filtered by WHT type | WHT tax on vendor bills to juristic entities |
| PromptPay reconciliation | Daily, closed monthly | Accounting > Bank > Reconciliation | Bank statement import matched to invoices |
| e-Tax Invoice submission | Per invoice, reviewed monthly | Accounting > Customer Invoices, e-Tax status field | Invoices flagged for e-Tax/e-Receipt |
A practical note on e-Tax Invoice and e-Receipt: Odoo does not submit directly to the Revenue Department's system by itself. Depending on how your e-Tax invoice workflow is configured, invoices are exported in the format your certified service provider requires, or pushed through an API connector. Either way, the monthly review is the same. Confirm every invoice that needed an e-Tax document actually has one, before the filing deadline, not after.
Half-year check: PND 51 and the drift it catches
Thai corporate income tax includes a half-year estimate, PND 51, filed within two months of the close of the first six months of the fiscal year. This is where Odoo accounting Thailand setups either pay off or expose a problem that has been accumulating quietly.
PND 51 needs an estimate of annual net profit. That means the management accounts for the first six months need to be genuinely closed, not just roughly entered. We walk clients through three checks before the half-year filing:
- Every bank account is reconciled through the period end, not just the obvious ones.
- Inventory valuation is current, especially for companies using landed costs or lot-based costing, since unposted stock moves understate cost of goods sold.
- Fixed asset depreciation has run for the period, so profit is not overstated by missing entries.
The Profit and Loss report (Accounting > Reporting > Profit and Loss) is the source for the estimate. If this report has not been reviewed monthly, the half-year estimate becomes a guess dressed up as a filing. Guessed numbers tend to create either an underpayment penalty or an overpayment that ties up cash until year-end.
Annual filings: PND 50 and the audited statements
The annual corporate income tax return, PND 50, is due within 150 days of the fiscal year end, alongside audited financial statements for most juristic companies. This is the heaviest filing of the year, and it is also the one most exposed to small errors made earlier.
By year-end, the numbers behind PND 50 should already exist inside Odoo: the full-year Profit and Loss, the Balance Sheet, and the general ledger detail an auditor will ask for. If monthly closes were done properly, the annual close is mostly a formality. If they were not, year-end becomes an archaeology project. Someone ends up digging through twelve months of unreconciled entries under deadline pressure.
One honest caveat: Odoo does not file anything with the Revenue Department or the Department of Business Development on its own. It produces the numbers and the supporting detail. Submission still runs through your accountant, auditor, or the relevant e-filing portal. Treat Odoo as the source of truth for the figures, not as a filing agent.
Building the calendar inside Odoo
A compliance calendar only works if someone actually looks at it. We generally set up a recurring activity schedule in Odoo, tied to the responsible accountant, with reminders five business days before each due date. That buffer matters. Five days is usually enough to catch a missing vendor bill or an unreconciled bank line before it becomes a late filing.
For companies selling through Shopee, Lazada or TikTok Shop, add one more recurring check: marketplace settlement reconciliation. Orders and fees flow in through the marketplace connector, but settlement timing rarely lines up neatly with the calendar month. Give it its own line on the schedule instead of folding it into general bank reconciliation.
A realistic month-end checklist
Here is the sequence we actually use with clients before closing a period and trusting the numbers for VAT, WHT, or management reporting:
- Confirm all customer invoices for the period are posted, not left in draft.
- Confirm all vendor bills received are entered, including ones still pending approval.
- Run bank reconciliation to zero outstanding unmatched lines older than the period.
- Review the Tax Report and Withholding Tax Report for anomalies against the prior month.
- Confirm e-Tax Invoice status on all qualifying invoices.
- Lock the period (Accounting > Lock Dates) so nothing posts retroactively without a deliberate override.
That last step, locking the period, is the one companies skip most often. It is also the one that causes arguments three months later, when someone asks why a closed month's VAT number changed.
When the calendar breaks down
Filing calendars usually fail for one of two reasons. Either the chart of accounts and tax configuration were never quite right to begin with, or no single person is accountable for closing the books on schedule. Software does not fix either problem by itself. What it can do is make the correct number easy to find and the incorrect number hard to miss, provided the setup was done with Thai filing requirements in mind from day one.
If your current Odoo instance was configured generically, the calendar above will be harder to follow than it needs to be. That often means PND 3, PND 53, e-Tax Invoice, and VAT grids were never mapped specifically for Thai reporting. That is usually where we start when a client brings us an existing system rather than a fresh implementation. We review the tax configuration first, before touching the calendar or the closing process. Our ongoing support engagements typically begin exactly there.
