Attendance and check in

Attendance is the shift. A fieldworker checks in on the mobile app when they start the day and checks out when they finish, and the Attendance tab is where those times are read back.

It is the hours a person was at work, not the hours they spent on jobs — for that, see worklog and timesheets. Attendance is what a salaried employee is paid for, which is why the month’s salary is worked out on this screen.

Users → a user → Attendance

Choosing the period

Users → a user → Attendance

• Monthly with the month picker beside it reads one calendar month, and is the setting to use when you are about to pay someone for it.
• Custom takes a start and end date instead, for a fortnight, a week, or the four days somebody worked before they left.

Auto CheckOut in the top-right corner shows whether automatic check-out is on for this person, and the gear beside it opens the attendance policies where it is set. With it on, a day where somebody forgot to check out is closed off for them at their shift end time rather than being left open — see auto check-out.

The report

Users → a user → Attendance

The report lists the days in the period with, for each one:

• Captured Log Time — the times the app actually recorded, exactly as they came in.
• Final Log Time — those times after the attendance policies have been applied: rounded to the interval, adjusted for the grace period. This is the figure the day is counted on.
• Log Duration — how long the person was checked in.
• Overtime — the part of it that falls beyond their shift.

Keeping both columns means the raw record survives the rounding. If somebody queries a day, the time their phone sent is still there beside the time they were paid for.

Data Not Found means there are no check-ins for the period — the month has not happened yet, the person did not work it, or they never checked in.

Working out the month’s salary

The panel down the right side turns the attendance into a figure.

Users → a user → Attendance

• Gross Salary for the month, which is the person’s pay before anything is worked out from it. The gear beside it opens where the wage is set.
• Working days in a Month — how many days the month is expected to contain, so a day is worth the right fraction of the salary. The gear beside it opens where that is set.
• No. of days employee work — how many of them they actually worked, filled in from the attendance above.
• No. of paid leave(s) — days off that are still paid, so they count as worked.
• Overtime, with the hours and the amount they come to. Untick it to leave overtime out of this month’s pay.
• Expenses, with the total of the claims for the period. Untick it to pay the claims separately rather than with the salary. The chevron opens the claims themselves — see a user’s expenses and leave.
• Attendance Policies opens the rules the hours were counted under — see attendance policies.

Calculated Salary at the bottom is the result: the salary for the days worked, plus overtime and expenses where they are ticked.

Finalising the salary

Finalize Salary closes the period off. The figure stops being a live calculation and becomes a record: it moves to the person’s Payment History, where it sits as unpaid until the money goes out and it is marked paid — see paying a user.

Finalise a month once you are satisfied the attendance behind it is right, because the calculation is only as good as the check-ins it read.