Vendor Contract Practices to Understand First When Assigned to Thailand

Masaki Fujiwara, Managing Director and Attorney at Law (Japan), One Asia Lawyers (Thailand) Co., Ltd.
Hiroyasu Chiba, Partner and Attorney at Law (Japan), One Asia Lawyers (Thailand) Co., Ltd.

Key points for Japanese IT managers: contract types, customer cooperation, subcontracting transactions, and vendor personnel.

When you are assigned to a Thai subsidiary as an IT manager, you will encounter vendor contracts in many situations, including system implementation, maintenance, cloud services, and network construction. Japanese contract concepts cannot always be applied directly in Thailand because the legal frameworks differ. In system development projects, disputes also often arise from customer cooperation, changes in specifications, acceptance testing, and management of vendor personnel. The following sections highlight practical points IT managers should understand when contracting with IT vendors in Thailand.


1. Do Not Apply Japan’s “Ukeoi vs. Jun-Inin” Distinction Directly

In Japan, system development agreements are commonly classified between contracts that promise completion of a deliverable and quasi-mandate arrangements focused on properly performing specified services. Under Thailand’s Civil and Commercial Code, “Hire of Work” is broadly comparable to a Japanese contract for work. Section 587 describes an arrangement under which the contractor agrees to complete specified work and the employer pays remuneration for the result. Building and delivering an ERP system, developing a specific application, or constructing and handing over a server or network environment may fall within this concept.

Thailand’s Civil and Commercial Code does not, however, provide a contractual category that directly corresponds to Japan’s quasi-mandate concept. Continuous IT support, IT advisory services, and development assistance billed by time or effort are therefore commonly documented as service agreements, with the scope, fees, term, and responsibilities clearly specified.

Accordingly, when outsourcing IT services in Thailand, the substance is more important than the contract title. Confirm whether the vendor promises a completed result or provides ongoing work/services, and define the contractual terms accordingly.


2. Clearly Define What Constitutes Completion

One of the most common sources of system-development disputes is whether the system has actually been completed. Under a Hire of Work arrangement, completion and delivery are closely connected to payment. Contracts should therefore clearly define specifications, deliverables, delivery dates, test methods, acceptance criteria, acceptance periods, correction procedures for defects, and post-acceptance warranty and maintenance.

Vendor templates sometimes provide that acceptance is deemed completed if the customer does not respond within a specified number of days after delivery. IT managers should therefore confirm not only the contractual wording but also whether their organization can realistically complete testing and acceptance within that period.


3. The Customer Must Also Cooperate

When a project is delayed, the vendor is often blamed for missing the schedule. In practice, customer-side actions may also cause delay, for example failure to provide required data, slow internal decisions on specifications, failure to grant access to a test environment, delayed user acceptance testing, or repeated specification changes.

Section 591 of the Civil and Commercial Code provides, in certain circumstances, that a contractor may not be liable where delay or defects arise from materials or instructions supplied by the employer. Project documents should therefore specify what the customer must provide or approve and by when. They should also address schedule extensions and additional charges if customer-side actions are delayed.


4. Do Not Handle Scope Changes by Email Alone

Changes after project commencement are common. Problems arise when repeated verbal or email requests leave the parties disagreeing over whether the change is included in the original price, whether additional fees apply, or whether the schedule moves. A formal change-control process should therefore cover: (1) the requested change, (2) cost impact, (3) schedule impact, and (4) approval by both parties.


5. Thailand Does Not Have the Same Subcontract Act as Japan

Japan has legislation commonly known as the Subcontract Act that regulates matters such as price reductions and delayed payments in certain outsourcing relationships. Thailand does not have a standalone law with exactly the same framework.

Thailand’s Trade Competition Act does, however, regulate certain unfair trade practices, including conduct that unfairly obstructs another business and improper use of superior bargaining power. Strict conditions imposed by a customer do not automatically constitute a violation. The assessment depends on factors such as bargaining position, the terms imposed, and whether there is a reasonable business justification.

Special payment-term rules also apply to certain transactions between larger enterprises and SMEs. A 45-day benchmark has traditionally applied to general goods, manufacturing, and services. New rules effective 2 November 2026 further clarify matters including the scope of covered enterprises and obligations to clearly inform SMEs of payment procedures. When dealing with an IT vendor that qualifies as an SME, companies should confirm whether the rules apply and set payment terms and procedures appropriately.


6. Points to Note When Accepting Vendor Personnel

1) Where personnel are supplied by a vendor

Vendor engineers may work on-site at the customer’s office for several months. It is not sufficient to assume that there is no employment relationship simply because the arrangement is documented as outsourcing. Under Section 11/1 of Thailand’s Labour Protection Act, where a business arranges through a third party for workers to perform work that forms part of its production process or business, the business may in certain circumstances be treated as an employer even if the third party supervises and pays those personnel.

A key question is whether the vendor independently provides a system or service, or in substance supplies personnel for the customer’s business. A vendor that manages its own engineers under its own project leader and delivers an agreed system is more characteristic of genuine outsourcing. By contrast, placing multiple engineers at the customer site to continuously perform part of the customer’s day-to-day operations may create greater risk that the customer is treated as an employer.

2) Where the customer directly manages vendor personnel

Separately, even when personnel are contractually employed by the vendor, a direct employment relationship may potentially be found if they work in practice under the customer’s direct direction and supervision. Risk is higher where the customer gives individual personnel day-to-day instructions and manages working hours or leave. If an employment relationship is recognized, the customer may become responsible as employer for matters such as working hours, overtime, leave, and severance.

Where the vendor is intended to provide services independently, operational instructions should generally be routed through the vendor’s responsible manager, while attendance, leave, and other personnel matters should remain under the vendor’s management. The written contract and actual operation should be aligned.

Conclusion

IT managers should confirm:

  1. whether the vendor promises a result or the provision of work/services;
  2. whether specifications, deliverables, and acceptance conditions are clear;
  3. what information and approvals the customer must provide;
  4. whether a change-control process is defined;
  5. when vendor personnel are accepted

whether the arrangement is effectively personnel supply or involves direct customer supervision.

System-development disputes often arise not from the technology itself, but because it was unclear who was responsible for doing what and by when. When starting a vendor project in Thailand, companies should ensure that contractual terms match actual project operation and, where appropriate, coordinate with internal stakeholders and external professionals.

" + NS Solutions" is register trade mark of NS Solutions corporation.

Other description about company name and product name are trademark or register trade mark of each companies.