Payroll Management

Payroll that runs correctly, every month, without the three-day ordeal.

Malaysian statutory compliance built in. Every contribution calculated, every file generated.

Every contribution calculated, every file generated, every payslip reviewed before anything is confirmed. Payroll closes on time because the system does the work.

EPF, SOCSO, EIS, PCB Draft payslip review Statutory export files
HR manager reviewing payroll data on a laptop with payslip information visible
Payroll document showing employee net pay and statutory contribution line items
Office administrator reviewing a payroll checklist at their desk
Review before confirm. Nothing committed early.
The Challenge

The last few days of every month should not feel like this.

For most small businesses, payroll is the same exercise every month. Open the salary spreadsheet. Check the latest EPF contribution table. Compute PCB manually or with a separate tool. Calculate proration for anyone who joined or resigned mid-month. Prepare the EPF text file, the SOCSO file, the EIS file. Submit to three different portals. Generate payslips and send them individually.

It is repetitive, high-stakes, and entirely unforgiving of errors. A wrong PCB deduction affects an employee’s tax position. A late EPF submission triggers a penalty. A proration mistake requires a correction run next month. The stakes are real and the margin for error is zero.

The deeper problem is timing. Salary increments need to be applied at exactly the right moment. New joiners need their first payslip prorated to their start date. Resignations need to be closed out correctly. When everything depends on the admin making the right update at exactly the right time, the process is only as reliable as the calendar reminder they set last week.

The Full Payroll Cycle

From salary configuration to statutory payment — one connected process.

Payroll runs in two phases. The preparation phase builds and verifies every payslip before anything is committed. The execution phase turns the confirmed batch into payable documents your finance team processes through their standard payment workflow.

Phase 1 — Payroll Team

Preparation

Build, verify, and confirm every payslip before a single ringgit moves.

1

Employee records and pay attributes configured

Salary, allowances, deductions, statutory flags — all with effective dates so changes apply automatically at exactly the right time

2

Payroll batch generated

System calculates every payslip — basic salary, allowances, statutory contributions, PCB, proration for joiners and leavers — automatically

3

Draft payslips reviewed

Every employee’s payslip visible as a formatted preview before confirmation. Net pay, deductions, contributions — exactly as the employee will receive it.

4

Overrides applied where needed

Any line item on any draft payslip can be adjusted before confirmation. Admin has final say on every number.

5

Batch confirmed

All payslips locked. Statutory files generated automatically.

Phase 2 — Finance Team

Execution

Confirmed batch converts to payable vouchers finance processes through their standard workflow.

1

Salary payable voucher generated

Aggregated total — individual salaries not visible to finance. Privacy preserved by design.

2

Statutory payable vouchers generated

One payable per statutory body — EPF, SOCSO, EIS, LHDN. Each appears as a standard vendor payable.

3

Payments processed through finance

Finance team pays each payable using the standard payment workflow they already know.

Payroll cycle closed

All payables knocked off. Statutory obligations met. Payslips accessible to employees. Cycle complete.

What Makes It Work

Built for Malaysian businesses running payroll correctly, not just quickly.

Full Malaysian Statutory Compliance

EPF, SOCSO, EIS and PCB calculations are built into every payroll run. Contribution rates are maintained within the system. Statutory export files for EPF i-Akaun, PERKESO, and LHDN are generated automatically in the exact format each portal requires. Submit directly without reformatting or manual preparation.

Salary Changes That Apply on Time, Automatically

Every payroll attribute is stored as a dated history rather than a single current value. A salary increment effective on the 15th is entered when it is approved, weeks in advance if needed. When the payroll batch runs, the system applies the new rate from exactly the right date and prorates the difference automatically.

Draft Payslip Preview Before Confirmation

Every generated batch produces a complete set of draft payslips — formatted exactly as the employee will receive them, with all totals calculated. Review every payslip before confirming the batch. If something looks wrong, it is correctable before any number becomes permanent.

Surgical Override on Any Line Item

Any value on any draft payslip can be overridden before confirmation. A reimbursement can be partially deferred to the next cycle. A deduction can be adjusted for a special circumstance. A statutory figure can be corrected for an eligibility edge case. The system calculates the default. The admin has the final word.

Privacy-Preserving Payment Workflow

When a batch is confirmed, the salary payable is generated as an aggregated total — not an itemised list of individual salaries. The finance team processes the bank transfer without seeing who earns what. Statutory payables for EPF, SOCSO, EIS and LHDN are generated as separate payable documents through the standard finance payment workflow.

Accurate Proration for Every Scenario

New joiners, mid-month resignations, salary changes effective on any date — the system calculates the correct prorated amount automatically based on the exact dates involved. Day-accurate proration means the first and last payslip for any employee reflects precisely what they are owed.

Multi-Run Batch Processing

Run payroll as many times as needed in a single month. A mid-month advance run for a specific group of staff. A commission run after sales figures are confirmed. An off-cycle run for a resignation settlement. Each run is separate, clearly labelled, and does not interfere with the main month-end batch.

Available at Growth tier and above

Year-End Statutory Forms

EA forms and Form E are generated from the confirmed payroll history as permanent, audit-ready records. Once generated, the form reflects the payroll data at that point in time — subsequent changes to employee data do not alter historical forms. Every employee’s EA form is accessible through their self-service portal at Business OS tier.

Available at Business OS tier
Built for Your Team

For everyone responsible for getting payroll right.

Business Owner or HR Manager

You carry the full weight of getting it right

You process payroll every month and carry the full weight of getting it right — correct contributions, correct deductions, correct files submitted on time. Cloudby removes the calculation burden and handles Malaysian statutory compliance automatically, so the monthly process becomes a review and confirmation rather than a calculation exercise.

Most relevant: Statutory compliance, draft payslip preview, statutory file generation
Payroll Administrator

You manage the detail

You manage the detail — salary changes, new joiners, resignations, reimbursements, advances. Cloudby gives you the tools to pre-enter changes with effective dates, review every payslip before confirmation, and override any figure that needs adjustment. The system does the calculation. You retain complete control over the output.

Most relevant: Effective-date versioning, draft payslip review, surgical override
Finance Manager

Your involvement in payroll is the payment

Your involvement in payroll is the payment. Cloudby generates a clean set of payable documents — aggregated salary payable and individual statutory payables — that integrate directly into your standard payment workflow. Process and knock off payroll payments the same way you handle any vendor payment. No separate payroll payment interface, no salary data exposure.

Most relevant: Aggregated salary payable, statutory payables per body, finance workflow integration
Simple, Transparent Pricing

Malaysian payroll compliance, handled. Starting from a price that makes sense for a small team.

All prices in MYR. Billed monthly. Pro-rated from your start date.

75% off first 3 months — as low as ~RM50/month

For small businesses processing a straightforward monthly payroll for a stable team.

Up to 20 employees
  • Full salary calculation with EPF, SOCSO, EIS and PCB
  • Draft payslip preview and confirmation workflow
  • Line item override before batch confirmation
  • Aggregated salary payable and statutory payables
  • Statutory export files for EPF, SOCSO, EIS and LHDN portals
  • Employee payroll profiles and pay structure configuration
  • Monthly payroll processing on a fixed end-of-month schedule
RM199 / month, from
Start Free Trial →

For businesses running payroll as part of a fully connected operation — employee self-service, manager approvals, and year-end compliance all in one system.

Up to 500 employees
  • Everything in Growth
  • Employee self-service payslip access through Workplace
  • Leave application and approval workflow
  • Unified manager approval cockpit for leave, expenses and overtime
  • EA form and Form E generation as permanent audit-ready records
  • Benefit-in-kind tracking for year-end tax reporting
  • Full statutory compliance archive — every submission, every period
RM599 / month, from
Get Started → View Demo →

Enterprise

For multi-entity businesses, large headcount operations, or organisations with specific deployment, data residency, or custom pay structure requirements. Unlimited employees. Multi-entity payroll with consolidated reporting. Private cloud or on-premise deployment available.

From RM900/month Contact Sales →

See a complete Malaysian payroll cycle in a real working environment.

The Cloudby demo includes a pre-configured payroll environment with active employees, a generated batch in draft review, and statutory files ready for export. Explore the full process at your own pace — no signup required.