![\"\"](\"https:\/\/www.timeteccloud.com\/blog\/wp-content\/uploads\/2026\/05\/businesswoman-examines-financial-documents-workplace-checking-financial-statements-1024x683.jpg\")
<\/figure>Employers in Malaysia have a strict obligation to keep complete and accurate employment records, including signed contracts, attendance logs, and payroll registers, for inspections by the Department of Labour.<\/p>\n\n\n\n
Under Section 61(2) of the Employment Act 1955, employers must retain employee records for at least six years from the date of the last entry. This rule also applies after an employee leaves the company.<\/p>\n<\/div><\/div>\n\n\n\n
Six years. Not six months. Not until the next system update. Not until the Excel file gets overwritten. Six years from the last entry, meaning a company that terminates an employee today must be able to produce that employee’s attendance records in 2032 if required.<\/p>\n\n\n\n
Failure to maintain mandatory employee registers or to comply with a Director General’s order is subject to a general penalty of up to RM50,000.<\/p>\n\n\n\n
This is the legal baseline. But in practice, the requirement goes further than simply keeping records. In a labour dispute, the quality of the record matters as much as its existence.<\/p>\n\n\n\n
What the Industrial Court Actually Asks For<\/h2>\n\n\n\n
When an unfair dismissal case reaches the Industrial Court, attendance records become evidence. And evidence has a higher standard than operational data.<\/p>\n\n\n\n
Documentation such as appraisal reports, attendance logs, and meeting notes serves as vital evidence to justify employment decisions. The court does not just ask whether the record exists. It asks whether the record is credible.<\/p>\n\n\n\n
A credible attendance record has specific characteristics. It is timestamped at the point of capture, not entered manually after the fact. It is tied to a verified identity, whether through a biometric device or another authentication method. It has a clear audit trail showing any modifications that were made. It can be produced for any date range within the retention period. And it is consistent with other records: if the attendance log says the employee was present, the payroll record should show they were paid for that day.<\/p>\n\n\n\n
An Excel spreadsheet that HR exported from the system, edited to add annotations, and saved over the original does not meet this standard. A WhatsApp message from a supervisor saying “Ahmad was late again today” does not meet this standard. A verbal testimony from a colleague confirming the employee’s pattern of tardiness does not carry the same weight as a system-generated log with identity verification.<\/p>\n\n\n\n
Where Most Companies Fail<\/h2>\n\n\n\n
The failure is rarely about intent. Most companies keep attendance records. The problem is how they keep them.<\/p>\n\n\n\n Records that get overwritten.<\/strong> Many attendance systems retain only a rolling window of data. When storage fills up or a new period begins, older records are purged or overwritten. A company that cannot produce records from eighteen months ago because the system only retains twelve months has a six-year obligation it cannot meet.<\/p>\n\n\n\n Records that were edited without a trail.<\/strong> HR sometimes edits attendance records to correct errors, approve late clock-ins, or adjust for system glitches. These are legitimate operational actions. But if the system does not maintain an audit trail showing what was changed, when, and by whom, the edited record is less credible than the original. The court cannot tell whether the edit was a correction or a fabrication.<\/p>\n\n\n\n Records that exist in multiple versions.<\/strong> When attendance data is exported to Excel for month-end processing, the export becomes a separate copy. Over time, multiple versions accumulate. The version HR has may differ from the version the employee saved. In a dispute, the existence of multiple versions undermines the credibility of all of them.<\/p>\n\n\n\n Records that cannot be traced to a person.<\/strong> Attendance captured through card swipes or manual sign-in sheets can be disputed on identity grounds. The employee can claim someone else swiped their card or signed their name. Without biometric verification tying the record to the individual, the record is a log of card activity, not a log of the employee’s presence.<\/p>\n\n\n\n Records that were never approved.<\/strong> Some companies run attendance without a review or approval step. The raw data flows from the device into the system and then into payroll. Nobody verifies the timecard before it is processed. When a dispute arises, the company cannot demonstrate that the record was reviewed and accepted as accurate at the time it was generated.<\/p>\n\n\n\n The difference between an attendance system built for operations and one built for evidence is not the data it captures. It is whether that data can survive scrutiny.<\/p>\n\n\n\n![\"\"](\"https:\/\/www.timeteccloud.com\/blog\/wp-content\/uploads\/2026\/05\/ChatGPT-Image-May-12-2026-08_29_09-AM-1-1024x265.png\")
<\/figure>\n\n\n\nWhat Changes When the System Is Built for Evidence<\/h2>\n\n\n\n
![\"\"](\"https:\/\/www.timeteccloud.com\/blog\/wp-content\/uploads\/2026\/05\/ui-ta-2-1.png\")
<\/figure>