The statutory forms turn a payroll run into the filings and contribution files the Malaysian authorities require: the EPF, SOCSO, EIS and PCB submissions, generated straight from the month's payslips so you do not re-key a thing.
What you will learn
- Which statutory files are generated
- How a form draws from the payslips
- What is and is not yet covered
The filings
- EPF (KWSP) – the contribution schedule and the Form A submission file (in both CSV and the EPF text format).
- SOCSO and EIS (PERKESO) – a combined contribution file covering both.
- SKBBK – folded into the PERKESO file from 1 June 2026.
- PCB (MTD) – the CP39 summary and the e-Data PCB text file for LHDN.
How it behaves
Each form is generated from the batch's payslips: it produces a payable report (the per-employee breakdown) and a batch upload file in the authority's required format. Because the figures come directly from the contribution calculations on the payslips, the file you submit always matches what was actually deducted, there is no separate re-computation to drift out of step.
Honesty note. The contribution filings above (EPF, SOCSO, EIS, SKBBK, PCB) are generated. The annual EA form (the employee's yearly statement of earnings) is not yet produced in-product, and Zakat handling is minimal. Treat those as roadmap items for now.
Edge cases and good practice
- Generate from the confirmed batch, so the file reflects the final payslips.
- The file matches the deductions; if a figure looks wrong, fix it on the payslip, not the file.
- Handle EA separately until in-product generation lands.
Related
- How to: Generate statutory files
- Reference: Statutory contributions
- Reference: Payroll Batch