Thai Localization - Tier Department Level Demo
This module adds demo data designed to comply with Thai Government regulations. You need to unarchive the demo data first for it to work.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Provides ready-made demo approval rules for Thai government-style expense and purchase request approvals, based on the requester's department level. The rules are installed inactive and must be unarchived to be used.
This is a demo data module for Thai localization. It does not add new screens or buttons; instead it pre-loads approval rule records so you can try out department-level approval workflows without configuring them by hand.
- For expense sheets, it creates five approval levels for regular expense claims and five for advance requests. The level that applies depends on the total amount: for expenses the thresholds are above 30,000, 100,000, 500,000 and 1,000,000; for advances they are above 5,000, 10,000, 30,000 and 100,000.
- For purchase requests, it creates five approval levels based on the estimated cost: above 30,000, 100,000, 500,000 and 1,000,000.
- In every rule, the approver is looked up from the requester's department using the department's reviewer level, falling back to the current user if no department reviewer is found.
- All rules are installed as inactive, so nothing changes in daily work until someone unarchives them.
The module touches the expense sheet and purchase request approval configurations. It depends on the Thai tier department module and on the tier validation modules for expenses, advances and purchase requests.
Text generated by AI (DeepSeek) from reading the Odoo 18.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: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.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.