The timesheet
Every payroll period has a timesheet: one row per employee, holding the days and minutes that pay depends on. Payroll reads this table and nothing else. Take it from attendance once the period is locked, or import a file.
It is the only thing that passes between the two modules. Most companies fill it from attendance; one still moving its attendance over, or with a department that clocks by hand, imports it from a file. Payroll cannot tell the difference, and does not need to.
Before you start
payroll.runto fill the timesheet, andattendance.viewto export one from the attendance sheet.- A payroll period, not yet finalized. See Running a payroll period.
- To take it from attendance: the attendance module, and the attendance period for the month locked. See Closing the month.
Steps
Take it from attendance
- Open Payroll, choose the month, and open Timesheet.
- Press Take from attendance.
The whole timesheet is replaced with what the locked attendance period says, the way pressing Calculate replaces the whole draft. Press it again after reopening and relocking the month, and the timesheet follows.
Export from the attendance sheet
- Open Attendance on the attendance site and choose a locked month.
- Press Export timesheet.
The file you get is exactly the file the import accepts. It is how a company runs payroll somewhere else while it uses MekongHRM for attendance, and it is a good template to start from when you fill the sheet by hand.
Import a file
- Open Payroll, choose the month, and open Timesheet.
- Press Import timesheet and choose the file.
- Press Check file. Nothing is written yet; you get a list of every problem, with its row and column.
- Fix the file until the check is clean, then press Import {count} rows. Importing replaces the whole timesheet of this period.
The file
One sheet. Row 1 holds the column codes below, in English, and never changes. Row 2 holds the column names in the language of whoever exported the file, so the sheet can be read; the import skips it. Data starts on row 3. A missing column is an error; an extra column is ignored. Employees are matched by their staff number, with or without its leading zeros: 123 and 00123 are the same person.
| Code in row 1 | Column | Unit |
|---|---|---|
employee_code | Employee code | |
unpaid_absence_days | Unpaid absence (days) | days, to 0.01 |
partial_leave_days | Partly paid leave (days) | days, to 0.01 |
partial_leave_percent | Paid share (%) | percent |
late_minutes | Late (minutes) | minutes |
overtime_normal_minutes | OT weekday (minutes) | minutes |
overtime_night_minutes | OT night (minutes) | minutes |
overtime_rest_day_minutes | OT rest day (minutes) | minutes |
overtime_holiday_minutes | OT holiday (minutes) | minutes |
overtime_rate_<percent>_minutes, for example overtime_rate_250_minutes | OT x2.5 (minutes), one column for each rate | minutes |
standard_minutes_per_day | Standard minutes per day | minutes |
working_days | Working days | days, to 0.01 |
Working days. working_days is read only by a company that divides a month by each person's working days (see The daily rate). It is optional: a file without it, or with it blank, imports, and such a company's calculation then stops at the first row without it, asking for the column to be filled.
Overtime is written in minutes, not hours, because that is what the pay is worked out from and it avoids a decimal hour meaning different things to different people.
Overtime by rate. The four overtime columns by kind hold only overtime from requests filed before requests carried a rate. Overtime at a request's rate goes in a column for that rate, named after the rate in whole percent: overtime_rate_150_minutes is x1.5 and overtime_rate_250_minutes is x2.5 — see Overtime. Rates are each company's own, so an export has a column for every rate somebody in the period was paid at, lowest first, just before standard_minutes_per_day, with row 2 reading like OT x2.5 (minutes). The rate columns are optional: a file exported before requests had rates has none, and imports as no overtime by rate. To pay minutes at a rate the file does not have yet, add its column.
What you should see
The timesheet page lists every employee in the period with their figures, the source of the sheet — From attendance or Imported — and when it was filled. After a successful import the page says Imported: {count} employees.; after taking it from attendance, Taken from attendance: {count} employees..
When the period is finalized, the timesheet is frozen with it, alongside the tax and NSSF figures that were in force. The period is finalized; its timesheet no longer changes. Years later the period can still be explained with the days it was actually paid on.
If something goes wrong
This period has no timesheet yet. — the period cannot be calculated until it has one. Take it from attendance or import a file.
Lock the attendance period first. — the sheet can only be taken from a month that has stopped moving. Lock it on the attendance site, then press the button again.
Not in the timesheet, so counted as full attendance. — an employee is in the period but not in the sheet. They are paid as if they worked every day, and the review flags it so you can decide whether that is right. Add their row and import again if it is not.
No employee has this code — a staff number in the file matches nobody. Check it against the employee list; the import does not create people.
Outside the allowed range — a negative number, a percentage above 100, or more days than the period has. Nothing is imported while any row has a problem, so one wrong cell holds the whole file until it is fixed.
The file is refused over a rate column. A column named like overtime_rate_..._minutes that is not a rate a company can have — not a whole multiple of 10 percent, or above 1000, which is x10 — refuses the whole file, because the minutes in it would be paid at no rate. Correct the code: x2.5 is overtime_rate_250_minutes, x1 is overtime_rate_100_minutes.
The period is finalized. Its timesheet cannot be taken again or imported again. A wrong day count found afterwards is corrected with an adjusting line in the next period.
Last checked 06/10/2026