Release notes · 9-14 Jun 2026
New SKBBK payroll support, a Compliance workspace, more sales reports, and fixes.
Payroll – SKBBK support
From 1 June 2026, SKBBK (Skim Keselamatan Sosial Bukan Bencana Kerja, PERKESO’s 24-hour protection scheme) is supported in payroll.
- SKBBK contributions calculated from the official PERKESO Jadual, effective-dated to 1 June 2026
- Bulk enrolment: enrol all eligible employees in one action, with per-employee status feedback
- Combined SOCSO + EIS + SKBBK export (Format 11) for PERKESO; the separate SOCSO + EIS export stays available
- EPF schedule now correctly driven by employee age and citizenship class (Part A/B/D/E)
Payroll: Run Readiness
- A new Run Readiness preflight check flags missing or misconfigured employee data before you run payroll.
New: Compliance workspace
A Compliance area is now available under Organisation settings.
- Overview: a health summary across compliance areas; pass / warn / fail at a glance
- e-Invoice: checks your LHDN registration, TIN, BRN, MSIC, SST and document classification
- Payroll: checks statutory configuration and employee payroll readiness
- Configuration: set your jurisdiction and answer a short questionnaire; Cloudby decides which checks apply
- Log exceptions per check with a reason and exclude them from the summary
More sales reports
- Customers Who Bought Product: find which customers bought a specific product within a period
- Product × Customer coverage matrix: purchase coverage across your catalogue per customer
What’s New, in-app
- A What’s New page is now built into Cloudby, browse recent updates without leaving the app.
Fixes
- Payroll: payslip ledger mapping could carry over incorrectly between payroll items in some setups
- Payroll: EPF citizen class, PCB marital/residency and similar fields didn’t display correctly in queue view
- Payroll: Payout Analysis excluded some confirmed batches from the status filter
- Finance: reimbursement category showed the wrong label in a payroll report
- Sales: settlement (knock-off) labels were inconsistent across transaction views