Payroll, Overtime, and PKWT Controls for Indonesian SMEs

Manual payroll mistakes start before payday

Payroll errors often begin during the week, long before finance opens the salary sheet. A late shift swap, a missed check out, or a verbal overtime approval can change pay inputs without leaving a reliable trail.

For many Indonesian SMEs, the risk is not fraud alone. The bigger daily problem is fragile evidence. HR, supervisors, and finance may each hold a different version of attendance, leave, overtime, and deductions.

When the final salary number is questioned, the team must rebuild the story from chats and edited spreadsheets. That costs time, weakens trust, and makes every payroll cycle feel heavier than it should.

Rules need records that operations can find

Indonesia's PP Nomor 35 Tahun 2021 record from JDIH BPK RI covers areas that affect day to day employment administration, including fixed term contracts, working time, rest time, overtime, and termination. This article is operational guidance, not legal advice.

The practical lesson is simple. If a rule depends on dates, hours, approvals, or status, the business needs records that are consistent and easy to retrieve. Manual files can work for a while, then strain as headcount and branches grow.

A system cannot replace HR judgment or legal review. It can reduce avoidable gaps by keeping the schedule, attendance event, overtime request, approval, and payroll input connected in one workflow.

Attendance data should explain the shift

A good attendance setup records more than who arrived. It connects the employee to the assigned shift, location, allowed tolerance, leave status, and any approved schedule change before payroll uses the data.

This matters for retail, F&B, clinics, schools, and field teams where rosters move often. Without a clean shift record, a normal evening shift can look like lateness, absence, or overtime depending on who edits the sheet.

Edit logs are part of the control. If HR fixes a missed check out, the system should keep the old value, new value, editor, reason, and time of change so later reviews are based on evidence.

Overtime works better as a request flow

Overtime becomes messy when it is approved after the fact in chat. Supervisors may remember the work, finance may see only extra hours, and employees may not know which record will be used for pay.

A request flow creates a cleaner path. The employee or supervisor submits the overtime need, the manager approves it, the system compares it with attendance, then finance receives an approved input rather than a loose note.

The flow should also show exceptions. If someone works beyond schedule without approval, the business can review it quickly instead of discovering the issue during payroll closing.

PKWT reminders protect the calendar

Fixed term employment contracts are calendar sensitive. A contract end date that sits only in a PDF folder or an HR notebook is easy to miss during a busy month.

A simple reminder can change the risk profile. HR can see contracts ending soon, prepare renewal or completion steps, and involve management before the date becomes urgent.

The same record should store contract files, role history, branch placement, and notes on agreed changes. That makes future checks faster and avoids depending on one person's memory.

Payroll inputs need a closed loop

Payroll should not start from a blank spreadsheet every month. It should pull approved inputs from attendance, leave, overtime, allowances, deductions, reimbursements, and contract status.

The closed loop is important because each department sees only part of the picture. Operations knows the shift. HR knows leave and contract status. Finance needs a final input that is approved and traceable.

Before salary is released, managers can review exceptions such as missing attendance, unapproved overtime, unusual deductions, or contract dates that need attention. The result is fewer surprises and calmer payroll days.

What Sundie can build for this workflow

Sundie can design an attendance and payroll support system around how your team already works, then tighten the controls where manual handling creates risk.

A practical build may include shift scheduling, attendance capture, overtime requests, approval trails, payroll input exports, PKWT reminders, dashboards, and role based access for HR, supervisors, and finance.

Start with the points that hurt every month. Once the workflow is clear, the system can grow branch by branch without forcing the whole company into a heavy enterprise platform.

Source note

PP Nomor 35 Tahun 2021 record from JDIH BPK RI was used as the official reference for the compliance areas mentioned. Teams should consult qualified counsel for legal interpretation and company specific employment decisions.