Employee Payroll Configuration

Last updated: June 20, 2026

Employee payroll configuration is where each person is enrolled in the pay items and statutory schemes that apply to them: their salary, their EPF citizen class, their SOCSO category, their PCB schedule and the account numbers. It is the per-employee setup the batch reads when it calculates a payslip.

What you will learn
  • How an employee is enrolled in pay items
  • The statutory specifics set per person
  • Why some values are derived and others set explicitly
  • How effective dating works

What is configured per employee

Each employee is enrolled in their pay items with effective dates, plus the statutory details that drive the calculations:

  • EPF (KWSP) – the citizen class (Malaysian or permanent resident, versus non-Malaysian), which selects the contribution schedule, plus the account number and any percentage override.
  • SOCSO (PERKESO) – the category: Category 1 (both employer and employee contribute) for most, or Category 2 (employer only) for those 60 and over, foreigners, or on invalidity, plus the account number.
  • EIS – the account number (an employee-borne contribution alongside SOCSO).
  • SKBBK – carried over from SOCSO; mandatory from 1 June 2026, an employee-only 0.75% capped at RM6,000 of wages.
  • PCB (MTD) – the tax schedule, the prior year-to-date tax, marital status and spouse income.

How it behaves

Derived versus set

Some things are worked out for you and some you must state. Age is derived from date of birth and drives the EPF and SOCSO tiers automatically. Citizen class and SOCSO category, by contrast, are set explicitly per employee, because they depend on facts the system cannot infer. Getting these two right is what makes statutory contributions correct.

Effective dating

An enrolment starts on an effective date and can be terminated, so a mid-year salary change or a scheme starting is handled by dating the change rather than overwriting history. The batch always reads the configuration in force for the period it is running.

Edge cases and good practice

  • Set citizen class and SOCSO category deliberately; they are not inferred and they change the contribution.
  • Keep date of birth accurate, since it drives age-based tiers.
  • Date changes, do not overwrite, so past payslips stay correct.

Related