OdooWiki OCA HUB

Thai Localization - Government Purchase Request

l10n_th_gov_purchase_request folder_open OCA/l10n-thailand open_in_new
Localization / Purchase License: AGPL-3

This module add following features to Purchase Request document, aimed to follow Thai Government procurement regulation.

  • Add following data to Purchase Request 1.1 Procurement Type (ประเภท)
  • ซื้อ/จ้าง/เช่า
  • จ้างที่ปรึกษา
  • จ้างออกแบบและควบคุมงานก่อสร้าง 1.2 Purchase Type (ระเบียบ)
  • จัดซื้อจัดจ้างผ่านพัสดุ
  • วงเงินเล็กน้อย
  • 79 วรรคสอง
  • ว.119 1.3 Procurement Method (วิธีการ)
  • เฉพาะเจาะจง
  • E-bidding
  • คัดเลือก
  • ประกาศเชิญชวนทั่วไป
  • Use substate to add an extra step, to verify document before approved The states of normal purchase request is,
  • Draft \> To Approve \> Approved Now changed to
  • Draft \> To Approve (To Verify) \> To Approve (Verified) \> Approved
  • Add/edit following user fields to keep tracks of who is doing what
  • Prepared By (create_uid)
  • Requested By (requested_by)
  • Purchase Representative (assigned_to)
  • Verified By (verified_by)
  • Approved By (approved_by)
  • Add new Committee tab for both Procurement (คณะกรรมการจัดซื้อจัดจ้าง) and Work Acceptance (คณะกรรมการตรวจรับ)
  • Check exception logics when sent to approve The exception logic are based on Thai Government procurement regulation year 2560, in summary,
  • จ้างที่ปรึกษา ต้องมีกรรมการจัดซื้อจัดจ้างอย่างน้อย 5 คน และกรรมการตรวจรับอย่างน้อย 5 คน
  • จ้างออกแบบและควบคุมงานก่อสร้าง ต้องมีกรรมการจัดซื้อจัดจ้างอย่างน้อย 3 คน และกรรมการตรวจรับอย่างน้อย 3 คน
  • ระเบียบ วงเงินเล็กน้อย ไม่เกิน 100,000 บาท และต้องมีกรรมการตรวจรับอย่างน้อย 1 คน
  • ระเบียบ 79 วรรคสอง ไม่เกิน 500,000 บาท
  • ระเบียบ ว.119 ไม่เกิน 10,000 บาท และต้องมีกรรมการตรวจรับอย่างน้อย 1 คน
  • ซื้อ/จ้าง/เช่า ไม่เกิน 500,000 บาท ต้องมีกรรมการตรวจรับอย่างน้อย 3 คน
  • ซื้อ/จ้าง/เช่า เกิน 500,000 บาท ต้องมีกรรมการจัดซื้อจัดจ้างอย่างน้อย 3 คน และกรรมการตรวจรับอย่างน้อย 3 คน

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Adds Thai government procurement fields to Purchase Requests: procurement type, purchase type and procurement method, plus a verification step and committee members. It also enforces Thai procurement rules on amounts and committee composition.

This module adapts Purchase Requests to Thai government procurement rules. On each Purchase Request you now choose a Procurement Type (e.g. goods/services/rental, consultant hiring, construction design and supervision), a Purchase Type (the regulation applied, such as small amount, Section 79 paragraph 2, or Wor.119) and a Procurement Method (specific, e-bidding, selection, general invitation). The allowed methods are filtered by the chosen purchase type, and if only one method is allowed it is filled in automatically.

Approval now goes through an extra verification step: Draft > To Approve (To Verify) > To Approve (Verified) > Approved. A user in the "Can verify purchase request" group sees a Verify button; the Approve button only appears once verified. The document records who prepared, requested, verified and approved it, with dates, and the Purchase Representative can only be changed in certain states.

A Committee tab lets you list Procurement Committee and Work Acceptance Committee members (employee, role chairman/committee, contact details). Automatic checks block saving or approving when Thai rules are broken: amount limits per purchase type (100,000 / 500,000 / 10,000 baht), minimum committee sizes, exactly one chairman when more than one member, and no chairman when there is only one member. A purchase order exceeding the linked Purchase Request amount by more than 10% also raises an exception. Only approved requests whose purchase type allows it can create a purchase agreement.

Configuration menus appear under Purchase > Configuration > Procurement Government for managers.

Depends on

hrpurchase_exceptionpurchase_request_exceptionpurchase_request_substatepurchase_request_to_requisition

Required by other modules

l10n_th_gov_hr_expensel10n_th_gov_purchase_reportl10n_th_gov_work_acceptance

Menus it adds

Procurement Governmentprocurement_method_menuprocurement_type_menupurchase_type_menu
Models and fields (7)
  • purchase.type · new modelcode, name, active, sequence, to_create, is_default (Default), description, visible_on_expense (Expense), procurement_method_ids (Allowed Procurement Method), visible_on_purchase_request (Purchase Request)
  • procurement.type · new modelname, active, sequence, product_id, description
  • purchase.request · extends an existing modelto_create, approved_by, assigned_to (Purchase Representative), verified_by, date_approved (Approved Date), date_verified (Verified Date), expense_reason (Reason), purchase_type_id (Purchase Type), substate_sequence, procurement_type_id (Procurement Type), procurement_method_id (Procurement Method), procurement_method_ids, procurement_committee_ids (Procurement Committees), work_acceptance_committee_ids (Work Acceptance Committees)
  • procurement.method · new modelname, active, sequence, description
  • procurement.committee · new modelname (Committee Name), note, email, phone, request_id (Purchase Request), employee_id (Employee), approve_role (Role), department_id, committee_type
  • purchase.request.line · extends an existing modelproduct_id
  • purchase.request.line.make.purchase.requisition · extends an existing model

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 3 confirmed, 6 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 information

Installation 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.

info

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.