OdooWiki OCA HUB

Thai Localization - Government Purchase Agreement

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

There are 2 type of procurement, 1) with agreement document and 2) without agreement document.

This module allow creating agreement as reference to procurement process when required.

auto_awesome What this module does

AI-generated from the code · Odoo 16.0

Link purchase agreements to RFQs and purchase requisitions in Thai government procurement. Users choose whether a requisition needs an agreement, and Odoo blocks confirming an RFQ that requires one but has none.

This module adds a procurement type to purchase requisitions so buyers can mark each one as either "Agreement" or "No Agreement". That choice is carried over to the related request for quotation (RFQ), so the purchasing team can see at a glance whether a formal agreement document is required.

On an RFQ you get a new "Agreements" button showing how many agreements are linked. Clicking it opens the related agreement records, or the single agreement form if there is only one. When an RFQ is marked as requiring an agreement, Odoo will not let you confirm it until at least one agreement is attached, and it shows the message "No Agreement."

On the agreement form itself, a new RFQ field lets you pick a draft or sent RFQ that is flagged as requiring an agreement. Selecting it automatically fills in the same vendor, and Odoo refuses to save if the agreement vendor differs from the RFQ vendor. If the RFQ uses an invoice plan, an "Invoice Plan" tab appears on the agreement showing the instalments, dates, percentages, amounts and invoicing status, kept in sync with the RFQ.

The printed agreement report is also adjusted to show the agreement code, name and version in the title.

Depends on

purchasepurchase_requisitionpurchase_invoice_planagreement_legal

Required by other modules

Models and fields (3)
  • agreement · extends an existing modelinvoice_plan_ids, use_invoice_plan, purchase_order_id (RFQ)
  • purchase.order · extends an existing modelpo_type, agreement_ids (Agreement), agreement_count
  • purchase.requisition · extends an existing modelpo_type (PO Type)

Text generated by AI (DeepSeek) from reading the Odoo 16.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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 3 confirmed, 6 with no information of 9 versions.

Sources · Odoo 16.0

Confirmed on 2026-11-03 in branch 16.0 of OCA/l10n-thailand.

terminal Installation and usage

OCA documentation · Odoo 16.0

To use this module:

  • Go to Purchase > Orders > Blanket Orders.
  • Create a new purchase agreement (blanket order)
  • Choose between:
  • Agreement: Allows the creation of an agreement.
  • No Agreement: Does not allow the creation of an agreement.
  • Confirm purchase agreement
  • Click New Quotation for create new quotation and create invoice plan (if any)
  • If the PO Type is set to Agreement, Quotation can't confirm without agreement document.
  • Go to Agreements > Operations > Agreements to create an agreement.
  • Select RFQ in agreement, The partner details will be automatically pulled from the RFQ.
  • Access the Invoice Plan tab, which will now be visible, to apply the invoice plan for the installment.

No verified information in OCA: Installation, Configuration.

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.