Skip to article
HSJGlobal

FIRST-HIRE COMPLIANCE BRIEF

How to Register the First Employees of a Thai Company

Build the first-employee file from the real employment relationship, the employer record and a time-controlled Social Security registration process.

By Elara Vance 6-minute read

To register a Thai company’s first employees correctly, first decide whether each person is an insured person under Section 33 of the Social Security Act, then align the start date, employer identity, payroll record and SSO filing. The Act requires an employer employing Section 33 insured persons to file both employer and insured-person registration forms within 30 days from the date employees become insured. The disciplined approach is to build one dated first-hire roster and use it to control the filing, rather than sending forms after salaries are already paid.

Key takeaways

  • The first task is a worker-status decision for each person, not a generic registration for everyone who joins a startup.
  • Use the actual employment start date as the deadline anchor and retain the evidence that supports it.
  • The first-employee file should tie the person’s identity and wage record to the correct Thai legal employer.
  • Foreign directors, founders and secondees require an additional work-authorisation and tax analysis; SSO registration is only one part of the answer.

Start with each person’s employment status, rather than their job title

The term “first employees” can conceal several different arrangements: an ordinary employee, a managing director, a founder paid by the company, a consultant invoicing independently, a student intern, a seasonal worker or a person seconded from an overseas parent. The SSO filing should follow the real legal and employment facts, not a casual label in an organisation chart. Section 33 is the statutory starting point for ordinary insured employees; it is not safe to presume that every person receiving money from a company is automatically in the same category.

For each person, record the contractual employer, service or employment start date, place of work, remuneration basis, reporting line and the person who assessed their status. The Social Security Act’s Sections 33 and 34 provide the legal frame: where an employer employs employees who are insured persons under Section 33, both the employer and insured-person forms are due within 30 days from the date those employees become insured persons.

The company that hires must be clear. If a regional parent negotiates the role but a Thai subsidiary pays the person, the employee file should identify the Thai employer and its authority to hire. Confirm the entity first through the Thai company setup process ; a payroll platform cannot choose the legal employer for you.

Build a first-employee roster before the deadline is close

Set out each person’s status, starting facts and evidence in one controlled file before payroll creates separate data trails.

Create a first-hire registration roster before the deadline starts to disappear

Use a single roster for the first group, even if it contains only one person. The roster should show the employee’s legal name, identity and contact details, actual start date, position, wage basis, workplace, section-status conclusion, expected SSO deadline, employment contract location and filing owner. It should also show whether the employer record must be set up at the same time. This is a much safer control than trying to extract the necessary information from email threads on the twenty-ninth day.

Avoid two date errors. Do not use the DBD incorporation date as an employee’s insured-person date merely because it is easy to find. And do not use the first bank transfer as the start date if the employee actually began work under a signed contract earlier. If the first employee begins before the bank account is ready, document the actual wage arrangement and employer identity rather than changing the employment facts to fit banking convenience.

Turn the first hire into a dated compliance task

A first-hire roster makes worker status, records and the 30-day filing deadline visible to the person who must act.

Collect employee and employer evidence together, not in two incompatible folders

Each employee file should support the name, identity, start date and wage information used in the registration and payroll process. The employer side should support the company name, registered office, company authority and payroll contact. Build one controlled cross-reference between the two. It lets a reviewer quickly identify a passport spelling difference, a changed director, a missing authorisation or a wage date that does not agree with the contract.

For a startup, the employer file normally begins with its corporate records. Reconcile it against the company setup document pack , but do not mistake incorporation documents for employment evidence. The appointment, actual work arrangement and payroll facts must be captured separately.

Where the first worker is foreign, create a separate sub-file for immigration and work-authorisation analysis. The company should not use the SSO registration date as proof that the person can legally work in Thailand, or use a visa timeline to replace the employment-start analysis. The start date, employer and duties should be capable of being explained consistently to each relevant authority, but each authority decides a different question.

Do the same for a director who is also being paid. Director status in the company record, authority to bind the company, actual management work, contract terms and remuneration may each have consequences that a simple “employee” label does not capture. The first-hire roster should flag this combination rather than silently passing it to a payroll vendor as ordinary staff data.

First employee registration document path A document path connecting employment status, employer evidence, employee records, filing and ongoing change control. Employment status Employer record Employee roster SSO registration Change log record evidence outcome
Keeping employer and employee evidence together prevents the first filing from creating incompatible records.

Confirm the filing result, then control later changes and contribution timing

Registration is complete only when the company has retained the official result and can match it to the employee roster. The Act provides for the Office to issue a social-security registration certificate to the employer and social-security cards to employees after the required forms have been filed. Save the certificate or official output with the employee register, not only in a staff member’s personal inbox.

The next control is monthly, not annual. Section 47 sets a following-month contribution-remittance deadline, and the Act also requires notification of changes to filed facts within the 15th day of the following month. Create a trigger list for new hires, leavers, address changes, salary changes that affect payroll inputs and changes to the legal employer. A company that saves its first registration certificate but misses those dates is not operating a complete employer process.

Assign two named owners to the register: one for human-resources facts and one for payroll submission. The second owner should independently confirm the payroll start date and identify any worker whose facts have changed. This small division of responsibility is especially valuable in a new company, where the same founder may be director, hiring manager and payroll approver. It creates a basic check before an incorrect date becomes a filed fact.

The first-employees decision point for a Thai company

Proceed with employer and employee registrations when the company has a confirmed Section 33 employment relationship, a defensible start date, complete employee facts and an employer record that matches its corporate documents. File within the applicable 30-day period and set the monthly payroll calendar before the first payment cycle closes.

Pause when the person is a foreign founder, director, independent contractor or cross-border secondee, or when the Thai entity’s role as employer is unclear. Those are not clerical edge cases: they can change the employment, tax, immigration and SSO analysis. The right next action is a person-specific review before the company records an incorrect status.

Make the first employee record usable beyond the filing date

The employee roster should support payroll, ongoing updates and a defensible explanation of the person’s status.

On this page
Chat with an Expert