How Do You Hire Your First Employee After Setting Up a Malaysian Company? Employer Registration and Onboarding Checklist

Start with the conclusion: separate the offer from the actual start date, then move through three gates

A Malaysian Sdn. Bhd. that has been incorporated, or is being incorporated, cannot treat its first offer as a purely HR action just because SSM documents already exist. The real question is whether the company can state identity, contract, pay, employer registration, withholding and records as one consistent thing from the day the employee starts providing services.

The answer is not that every government form has to be finished before an offer goes out. The statutory trigger points differ. EPF requires an employer to register within seven days of the registration liability arising; EIS requires a new employee to be registered within thirty days once the industry is registered; and the tax CP22 applies only to a new employee who is taxable or may be taxable, with its own deadline. Flattening these different points into one slogan makes it easier to miss the real deadline. KWSP: Employer Registration Employment Insurance System Act 2017, section 16 HASiL: notification of a new employee

In practical terms, though, the order should be stricter. The first gate is to classify the person correctly and confirm whether the real relationship is that of a direct employee, a part-time employee, a fixed-term employee or an independent contractor. The second gate is to give EPF, PERKESO/EIS, LHDN and any applicable labour department notification an owner and a path. The third gate is to make the contract and the payroll system produce payslips, payments, withholding and records from the same employee data. The biggest risk is not a missing account; it is an employee who has already started work while registration and the first payroll are still in a "we will catch up" state.

Where gaps remain at any of the three gates, the safer next step is to postpone the actual start date and close the information and process gaps, rather than covering them up with a backdated contract, writing the employee down as a consultant, or leaving the first month's pay for later. This article does not make the employment, legal or tax decision for the company; its purpose is to show the person in charge where to stop and confirm with a qualified Malaysian professional.

Scope: a first local employee is not every employment situation

This article covers the preparations for a Malaysian Sdn. Bhd. that has been incorporated, or is about to be, to hire its first direct employee, a Malaysian citizen or permanent resident. The employment conditions section is scoped to Peninsular Malaysia and the Federal Territory of Labuan: JTKSM states expressly that the Employment Act 1955, as amended in 2022, applies only to that area, while Sabah and Sarawak continue to apply their own labour ordinances. Where the employee actually works in Sabah or Sarawak, the contract and working-hours sections here cannot simply be copied. JTKSM: Employment Act 1955 Amendment FAQ

This article does not repeat the steps of incorporating a Sdn. Bhd.; if the company entity, resident director or company secretary is not yet in place, go back to the basic process for foreigners registering a Malaysian Sdn. Bhd. first. It also does not cover recruitment channels, candidate screening, EOR, payroll outsourcing or foreign employee visas. Work permits, immigration eligibility and employment approval for foreign nationals are separate processes and cannot be treated as settled because this local-employee checklist is complete.

"Local employee" here is not a loose label based on nationality either. PERKESO's guidance brings qualifying Malaysian citizens and permanent residents in the private sector employed under a contract of service or apprenticeship within registration and protection, while EIS has its own coverage and age conditions for people in the private sector bound by a contract of service, employment or apprenticeship. PERKESO: Employed Worker This sets the starting point for the article but does not replace a case-by-case judgement on special statuses, director's remuneration, family members, internships, part-time work or cross-border arrangements.

Gate 1: classify the person correctly before wiring up registration and payroll

Start with a plain question: is this person providing services under the company's actual arrangements for agreed remuneration? If so, calling the contract a "consultant agreement", paying by the hour or being on probation cannot by itself remove the fact that the person may be an employee. PERKESO's explanation of EIS defines an employee as a person employed under a contract of service or apprenticeship by an employer for wages, and the contract may be express or implied, oral or written. PERKESO: Employed Worker

That does not mean every service provider is necessarily an employee. The difficulty in classification lies in actual control and how the work is performed: who decides working time, place and tools, who approves the work, whether pay is made for an ongoing post, and whether the person can carry risk independently through their own business. All of these belong in one factual record. Where the boundary is unclear, do not attach the label "freelancer" first in order to avoid registration; putting the real arrangement in front of a qualified employment and tax professional is usually safer than correcting it afterwards.

Part-time, fixed-term and probation are not reasons to skip the basics

Full-time, part-time, fixed-term and probationary are different forms of contract and work arrangement, not substitutes for "already employed" and "not yet employed". Where a service or a term exceeds one month, section 10 of the Employment Act 1955 requires the contract of service to be in writing and to set out how it may be terminated. Leaving someone who is due to work for six months in a chat thread or a verbal offer removes the common reference point for the first day, the first month and termination. Employment Act 1955, section 10

In practice, the offer drafting stage should already settle the role, reporting line, actual start date, main place of work, contract term or open-ended status, pay components, pay cycle, normal working arrangements and who owns onboarding. Probation can be written with an assessment arrangement, but "probation" must not become a gap in which the employee is already providing services with no contract, no payroll master data and no owner for the statutory process.

Design the offer as a workable start condition

The offer does not have to replace the final contract, but the two must not contradict each other. A first offer should at least tell both sides the job title and main duties, the legal employer entity, the intended start date, basic salary and fixed items, the place of work or hybrid arrangement, the acceptance deadline, and how the formal contract and onboarding materials will be delivered. Where identity documents, bank payment details or role conditions are not yet verified, the start date can be left until the documents and signatures are in place; it must not be backdated after the person has already started.

For borderline cases, write the questions onto a one-page fact sheet instead of only asking whether the person can issue an invoice: what the person does, who manages them, from which date, how they are paid, whether they are in the company roster, and whether company equipment and system access are needed. That way the later EPF, PERKESO, LHDN and contract judgements all draw on the same inputs.

Gate 2: employer registration, employee data and location notification

The most common mistake here is treating SSM company registration and employer registration as one action. They are not. SSM states that the company exists; EPF, PERKESO/EIS and LHDN each begin with the employer, the employee, the contribution or the withholding liability. Before a first employee, the person in charge should build a small list of number, portal, owner, trigger date and supporting document, and run through the process once without real salary data.

EPF/KWSP: employer responsibility comes first, then employee data into payroll

KWSP requires an employer to register within seven days of the liability arising and states that an employer should do so as soon as an employee is engaged. For a Malaysian citizen or permanent resident, an employer can use MyKad details to complete the employee registration process when submitting Form A; that is not a reason to skip verification, and the name, identity number, start date and payroll master data still have to line up before the first wage payment. KWSP: Employer Registration KWSP: Register Employee

In practice, keep the employer registration number, the available employer portal, employee data verification, Form A or the equivalent electronic submission, the payroll owner and the contribution evidence on one owner list. Where the company has only an acknowledgement of application and cannot yet produce correct records from its payroll data, it should not treat itself as ready.

PERKESO/EIS: use one set of employee facts, not two lists

PERKESO's employer registration guidance makes employer registration and contributions the starting point for every industry with one or more employees, and provides routes for ASSIST, Borang 1 and 2 and the SIP forms. Its employed worker page states that qualifying Malaysian citizens and permanent residents, and employees in the private sector under a contract of service or apprenticeship, require registration and coverage, while EIS requires private-sector employers to contribute monthly for applicable employees with age and eligibility boundaries. PERKESO: Employer Registration PERKESO: Employed Worker

Section 16 of the Employment Insurance System Act 2017 provides that a new employee engaged after the industry has been registered must be registered and insured by the employer within thirty days from the start of the employment relationship, regardless of the wage amount. That deadline is not advice to postpone registration to the end of the first month. For a first employee, ASSIST, the data fields and the responsible person should be ready before the actual start date, so that inconsistent employee data, employer data or eligibility is not discovered after the first payroll. Employment Insurance System Act 2017, section 16

LHDN/HASiL: employer number, PCB and the conditional CP22

LHDN's employer responsibilities page lists the employer income tax number, monthly PCB/MTD withholding, CP22, Form E and EA/EC. At the first-employee stage, put the employer tax number, the payroll withholding tool or provider, the person who reviews it and the payment date on the calendar first; PCB/MTD should be paid by the fifteenth day of the following month. Do not leave the employer number in a folder while nobody confirms how payroll data actually flows into e-PCB, e-Data PCB or e-CP39. HASiL: Employer Responsibilities

CP22 is not a synonym for mechanically filing for every new employee. HASiL's new employee notification page limits it to a new employee who is taxable or may be taxable and requires notification within thirty days after employment begins; since 1 September 2024, CP22 has to be submitted as e-CP22. The first-month check should include a documented judgement on whether this person falls within the CP22 conditions, rather than assuming it must be filed or must not be filed. HASiL: Notification of New Employee

JTKSM workplace notification: do not let the SSM address hide it

Section 63A of the Employment Act 1955 brings the undertaking or place of business where employees are or may be employed within a written notification requirement: notice must be given to the nearest Labour Office with jurisdiction within ninety days after commencing business, taking over, starting operations, or changing the name, location and similar matters, and for some starting points the Act uses earlier dates such as the day the first employee begins work. It is not a registration item that completes itself once the company has an address. For a company with an office, retail outlet, warehouse or client-site arrangement, put the location, the jurisdictional labour office, the notification materials and the owner on the first-month calendar. Employment Act 1955, section 63A

HRD Corp is a milestone that is easily added to the first-employee checklist too early. The official FAQ states that registration is mandatory once an employer has at least ten Malaysian employees; with five to nine it is optional, and industry and eligibility verification still apply. A single local employee therefore does not trigger the ten-person threshold, but the headcount plan should hold review reminders for the fifth and tenth employees. HRD Corp: Employers FAQ

Gate 3: contract, working conditions and the first payroll have to connect

An employer number is not a contract, and a contract is not a payroll process. The first employee's documents should let the manager, the payroll owner and the employee read the same thing: who employs whom, from when, under which normal conditions, how pay is calculated, when it is paid, which deductions appear on the payslip, and who keeps the records.

Write the core fields in the contract first

Beyond the written-contract boundary in the previous section, the final contract, or a written policy cross-referenced with it, should include at least: the employer's full legal name; the role and reporting line; the start date and place of work; the basic components of pay and fixed allowances; the pay cycle and the actual payment date; normal working hours, rest days and leave rules; deductions permitted by law; confidentiality, company property and handover; notice and termination clauses; and the version date confirmed by both sides. Do not use an offer that says only "RM X per month" and leave the payroll team to guess the pay cycle, the nature of an allowance or how a partial first month is calculated.

The Employment Act 1955 requires a contract of service to specify a wage period not exceeding one month, and, apart from statutory exceptions, wages must be paid no later than the seventh day after the last day of the wage period. The Act also treats payment through a financial institution as the usual route; where the employee requests payment in cash or by cheque in writing, the employer also needs the Director General's approval. Collecting a verified payment account and configuring payment approval before the start date is therefore not just convenience; it reduces first-month payment errors. Employment Act 1955, sections 18, 19 and 25

Implement basic employment conditions through rosters and the pay calendar

Writing "comply with the law" into a contract does not make day one workable. The employer should give the employee the normal working days, daily start and finish, rest arrangements, weekly rest day, public holiday treatment, how leave is requested and who owns attendance. The Act sets rules on normal hours of work, rest after continuous work, normal weekly hours and the weekly rest day; section 60A, for example, sets the usual normal hours ceiling at forty-five hours a week, and section 59 provides for one rest day each week and requires the rest day roster to be prepared in advance. Where the role involves shifts, overtime, higher-paid employees, manual labour or other exceptions, check each one against the Act and professional advice rather than treating one general template as the whole answer. Employment Act 1955, sections 59 and 60A

Do not apply a fixed EPF, PERKESO, EIS or tax percentage from this article either. KWSP's current contribution schedules vary by wage, age, nationality or status, and the PERKESO pages also flag contribution boundaries that differ by scheme and eligibility. Before the first payroll, use the current official tables, an official calculator or a verified payroll system, and keep the version used and the calculation inputs. KWSP: Mandatory Contribution PERKESO: Employed Worker

Run a blank payroll first, before the real payday

The first run does not need real salary data, and employee sensitive information should not be scattered across chat tools. Use controlled test data to check whether the start date and pay cycle handle a partial month; whether basic salary and fixed items are separated; whether employer costs and employee statutory deductions are kept apart; whether the payslip is clear; whether bank payment approval is traceable; and how the contribution files for each body are exported. KWSP requires the employer to provide a monthly payslip or pay statement and states that contributions should be paid by the fifteenth of the following month; PERKESO's contribution page also sets the fifteenth of the following month as the deadline; and LHDN's PCB/MTD has the same fifteenth-of-the-following-month payment point. KWSP: Employer Contributions for Employee PERKESO: Payment of Contributions HASiL: Employer Responsibilities

Those three fifteenth-of-the-month points do not mean all the information can wait until the fourteenth. A genuinely useful calendar contains the payroll cut-off, the review date, the payment date, the filing export date, each contribution date and the owner of exception handling. Where an external payroll provider assists, the company should still appoint someone internally to confirm employer data, employee identity, pay changes and the final payment evidence; outsourcing does not move the statutory employer responsibility by itself.

Data minimisation and retention: collecting documents is not the end

The first-employee file should separate what is needed to run payroll and statutory registration from what might be useful later. Start with one controlled employee master record holding verified identity details, contact details, bank payment details, the fields EPF, PERKESO and the tax authority need, the signed contract and its version, pay and deduction inputs, attendance and rest day arrangements, payslips, and payment and contribution receipts. Every item should have a purpose, an owner and a storage location; do not drop full copies of identity documents, bank details and tax data into a chat group that several people can see at the same time.

A retention period cannot be satisfied just by having a company cloud drive either. Section 61 of the Employment Act 1955 requires an employer to keep a register of employees for at least six years, and JTKSM also requires the monthly rest day roster to be prepared and kept. HASiL's employer responsibilities page requires employee and payroll-related records to be kept for seven years. For the same employee data, it is practical to use the longer seven-year tax retention requirement as the calendar baseline, while linking labour records, payroll, payments and statutory contribution evidence together. Employment Act 1955, sections 59 and 61 HASiL: Employer Responsibilities

One boundary here cannot be replaced by a checklist: the company should collect and access data only for clear employment, payroll, tax and statutory registration purposes, and check separately against the actual data protection, confidentiality, cross-border access and third-party service arrangements. This article does not provide personal data law or cyber security advice.

A reusable checklist: before the offer, start day and first month

The purpose of this checklist is not to let the person in charge tick every box and declare absolute compliance; it is to place the things a first employee triggers at the right point in time. Every tick should map to an owner, a date and a traceable document.

Before issuing the offer

• [ ] Confirm that the employer is this Sdn. Bhd. and that the person is a direct employee, part-time, fixed-term, or a borderline case needing further legal review; do not substitute an invoice, probation or a job title for the factual judgement.
• [ ] Write out the role, reporting line, intended start date, place of work, pay components, pay cycle, normal working arrangements and the signing route for both sides; prepare a written contract, including termination arrangements, where the service or term exceeds one month.
• [ ] Build a responsibility card for EPF, PERKESO/EIS, LHDN and the JTKSM location notification: the number or entry point required, the data source, the submitter, the reviewer, the statutory trigger date and where the evidence is kept.
• [ ] Run payroll once with test data: partial month, payslip, bank payment approval, employer and employee deductions split out, EPF/PERKESO/EIS/PCB output, and the fifteenth-of-the-following-month contribution calendar.
• [ ] List only the data needed for onboarding and assign a controlled storage location; do not collect sensitive data whose purpose cannot be explained.

Start day

• [ ] Before or on the actual start of work, complete the signed contract, employee master data verification, payment account verification, role and salary input, and the minimum system and device permissions.
• [ ] Sync the real start date into the contract, attendance, payroll, EPF/PERKESO/EIS and tax judgement; any change to a date should be reviewed by the same owner, so that one system does not record this week while another records next week.
• [ ] Explain to the employee the payday, how payslips are obtained, normal working hours, the weekly rest day, leave and how to report exceptions; assign roster or attendance responsibility to a named manager.
• [ ] Check whether the taxable or potentially taxable CP22 conditions are triggered and record the judgement and the follow-up e-CP22 action; for a foreign national, stop using this checklist and move to a separate work permit and employment approval check.

First pay cycle and first month

• [ ] At the payroll cut-off, review the start date, partial month, fixed items, approved changes, statutory deductions and employer costs; do not change master data after payment.
• [ ] Pay wages in line with the contract and statutory timing, issue payslips, and keep the payment approval and evidence that the employee could obtain the pay statement.
• [ ] Complete the output, review and payment of EPF, PERKESO/EIS and PCB/MTD for the period; treat the fifteenth of the following month as a central contribution control point, not the only preparation day.
• [ ] Complete the seven-day EPF employer registration requirement, the thirty-day EIS new employee registration requirement and the thirty-day notification requirement where CP22 applies, and keep tracking the ninety-day JTKSM workplace notification point.
• [ ] Archive the contract version, employee registration, rest day roster, attendance, payslips, payment receipts, contribution receipts and tax judgements; set an HRD Corp threshold reminder for the fifth and tenth local employees.

Common states that look complete

The first is "the company is registered, so someone can start tomorrow". Company formation and employer responsibility are different; confirm at least who enters employee data, runs payroll, pays, contributes and keeps the evidence. The second is "let him try it for a month, then we register". Probation can be a contract stage, but it is not a reason for actual employment to sit outside registration, payroll and record controls.

The third is "the salary is in the offer, the details go to the accountant later". If the pay cycle, first-month calculation, bank payment, statutory deductions and payment approval are not connected, the salary figure itself does not get the employee onboarded properly. The fourth is "writing the employee as a contractor removes the employer issues". The relationship turns on actual arrangements; where it is borderline, record the facts and get professional review. The fifth is "the first person does not involve HRD Corp, so we will look at that as headcount grows". One person genuinely does not reach the ten-local-employee threshold, but starting from zero when the threshold arrives turns a simple calendar control into remedial work.

Next step: treat being ready to start as the finish line, not the offer

Reduced to one decision, this article says: if the company cannot produce one consistent factual classification, a written contract it can sign, a first-month payroll and contribution calendar it has run through, and traceable record locations, it has not yet reached the operating condition for the first employee to start work. Connect those basics first, then confirm the start date.

Where the person's status, the employee's actual place of work, the salary structure, working-hour exceptions, tax position or foreign work eligibility is uncertain, seek advice from a qualified Malaysian employment, tax, immigration or other relevant professional before the offer turns into an actual start. This article is a summary of public sources only. It is not recruitment, EOR, payroll outsourcing, legal or tax services, and it does not mean that any employment, registration, withholding or permit will necessarily be accepted.