Thai Localization - Expense Tax Operating Unit
This module transfers the Operating Unit value from the Expense to the withholding tax move in cases involving withholding tax clearing.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0When an expense report generates a withholding tax journal entry, this module copies the Operating Unit from the expense report onto that accounting entry.
This module is a small bridge between Thai withholding tax on expenses and Operating Units. It does not add any new screen, menu or field.
What it changes:
- When an expense report (hr.expense.sheet) creates its withholding tax journal entry, the Operating Unit selected on the expense report is automatically written onto that journal entry.
- Without this module, the withholding tax entry would be created without an Operating Unit, so the expense and its tax entry could belong to different operating units.
Where it appears: nowhere new in the interface. It works in the background when the withholding tax entry is prepared from an expense report. The Operating Unit field itself comes from the Operating Unit features already installed.
Business rule added: the Operating Unit of the expense report is the single source for the Operating Unit of the related withholding tax move, keeping the two documents aligned for reporting and analysis by operating unit.
Models touched: hr.expense.sheet is extended; the resulting journal entry (account.move) receives the operating_unit_id value. No scheduled jobs, emails or reports are added.
Models and fields (1)
- hr.expense.sheet · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/l10n-thailand.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.