Attendance records versus timesheets

Attendance records whether a person was present against a shift or calendar. Timesheets record how effort was allocated to work, clients, or tasks. They answer different questions, feed different owners, and should not be forced into one log. This page is the distinction. It is not a project-management tutorial, and it does not describe a Dayzen timesheet product — Dayzen does not publish one.

Indian offices mix the two because both involve “hours.” Payroll then inherits a punch that was edited to match a client bill, or a delivery lead inherits a biometric total that says nothing about which job was done. Keep the records reconcilable. Do not make them identical.

What an attendance record is for

Attendance is a presence ledger. For each employee and each day (or each shift instance), it answers: were they expected, did they punch in and out, did the day close as present, absent, half-day, on duty, weekly off, holiday, or leave, and was any exception regularised. HR, leave, and often payroll read that ledger. The commercial surface for punches, shifts, calendars, and regularisation is attendance management. The operating walkthrough of how those pieces fit sits in how attendance management works.

Presence is not a quality score. A full shift on site can still be an unproductive day. An outdoor punch can still be honest work. Attendance policy should not pretend to measure delivery. It measures whether the person occupied the time window the company rostered, under the method you published (device, app, GPS/IP, or another named method).

Typical consumers of attendance

• HR: daily roster, exception queues, month-end close.
• Managers: who was in, who is pending regularisation, who is on leave.
• Leave: whether a day was already a rest day or a working day before an application is judged.
• Payroll: paid days, unpaid absence, and LOP derived after freeze — not a list of client codes.

If a consumer needs “what the person worked on,” they are asking for a timesheet or a project log, not for a punch.

What a timesheet is for

A timesheet is an effort ledger. It answers: against which work item, client, project, or task were hours spent, on which date, and by whom. Delivery, billing, utilisation, and sometimes internal cost allocation read that ledger. The unit is usually hours (or fractions) tagged to work, not a shift window on an HR calendar.

Timesheets can exist on paper, in a spreadsheet, in a professional-services tool, or inside a project tool. None of those is implied by an HR punch. A person can be present eight hours and still have no valid timesheet if they never allocated the day. A person can complete a timesheet from home on a weekly off; that does not make the weekly off a working day for attendance unless you have a separate policy for that case.

Attendance says you were at work (or not). A timesheet says what the hours were spent on. Payroll usually cares about the first unless you designed otherwise in writing.

Why collapsing them fails both jobs

If you treat the punch as the timesheet, delivery gets a single daily blob with no client split. If you treat the timesheet as attendance, HR gets hours that employees can still type after they have left the building, without an in/out event, without a shift, and without a regularisation trail. Month-end then has two truths: “present on Tuesday” versus “six hours on Client A and two on internal.”

Question	Attendance	Timesheet
Was the person expected today?	Yes — roster, shift, weekly off, holiday, leave	No — work items do not define rest days
When did they start and stop?	In/out punches against a window	Optional; many timesheets are daily totals only
What was the work?	Out of scope	Client, job, task, billable flag
Who approves exceptions?	Attendance regularisation / manager of presence	Project or billing owner of hours
What does payroll usually read?	Closed day status and unpaid absence	Nothing, unless you explicitly pay on billed hours

Some organisations pay overtime from timesheets and still keep attendance for presence. That is a designed dual feed, not proof that the two logs are the same object. Write which system is authoritative for which pay element. Do not let managers invent the mapping in a chat during freeze week.

Dayzen PMS is not HR time tracking

In Dayzen’s product set, PMS means Project Management System — tasks, projects, and delivery work — not performance management and not attendance. Mentioning it here is only so the acronym is not read as “people management system” or as a timesheet module. The product home is Dayzen PMS. Do not hang punches, late marks, LOP, or leave on that product. Dayzen HRMS attendance is the presence product; there is no invented timesheet module to list beside it.

If your company uses a project tool (Dayzen PMS or any other) for work, keep allocation there. If HR needs presence, keep punches in attendance. Reconciliation, if you need it, is a report that compares totals — not a requirement that every punch carry a task code.

Reconciling totals without merging records

Growing teams often want a sanity check: attended hours versus booked hours. That check is useful when both logs are closed for the same period. It is harmful when someone edits attendance to match the timesheet so that billing looks “clean.” Presence fraud and billing inflation hide in that edit.

A practical monthly check:

1. Close attendance exceptions for the period (missing in/out, wrong shift, open days).
2. Close timesheets on the delivery calendar you already use (Friday, month-end, or billing cycle).
3. Compare totals only at employee level first: attended hours versus booked hours.
4. Investigate large gaps. Do not auto-overwrite either log.

A gap can be honest. Travel, training, internal meetings, and waiting time may be present-but-unallocated. Night shifts and weekly offs can also skew a naive “calendar Tuesday” compare. If you chase gaps as an HR process, the sibling article is monthly working-hours gaps — expected hours versus recorded attendance hours — not a billing utilisation lecture.

Do not use the gap report as a substitute for a missing-punch queue. A person with no punch and no timesheet is an attendance exception first. A person with a full punch and a blank timesheet is a delivery exception. Different owners.

Who owns which cutoff

Attendance close belongs to the people-ops loop: regularisation and leave decisions before payroll freeze. Timesheet close belongs to whoever bills or reports utilisation. Those dates can coincide on a calendar and still be different decisions. If payroll freeze is the 3rd and billing lock is the 5th, do not reopen attendance because a timesheet arrived late unless your written policy says that late allocation changes paid days — which it usually should not.

Name owners in one short SOP:

• Presence exceptions: employee, then reporting manager, then HR attendance owner.
• Hour allocation: employee, then project or delivery manager — not HR by default.
• Payroll inputs: HR/payroll after attendance and leave are closed. See attendance to payroll and LOP for that handoff; this page does not retell LOP math.

Managers who approve both presence and billing still need two actions. One click that “approves the week” without saying which ledger was approved is how disputes start.

What to write in policy (without turning it into a timesheet spec)

Attendance policy should state punch method, shift windows, grace, late marks, regularisation reasons, and month-end close. Timesheet policy, if you have one, should state which work must be tagged, who approves, and whether hours are billable. Cross-reference only where needed: “Payroll uses attendance day status, not timesheet hours, unless listed in the compensation annex.” That one sentence prevents most collisions.

For mixed office and field teams, attendance method (office device versus GPS/IP punch) still does not become a timesheet. Location of punch is a presence signal. Client name is a work signal. Capture them in the systems that own those questions.

Do not require employees to enter the same eight hours in two places as a control. Dual entry without a purpose is busywork. Dual entry with a reconciliation report is a control. Choose.

Common failure modes in Indian SME offices

• Biometric as billing. The machine total is treated as billable hours. Clients then get a dump of gate times, and delivery still cannot say which job ran.
• Spreadsheet timesheet as attendance. Someone emails hours on the 2nd; HR types them into a register as present. There is no punch, no identity check, and no regularisation trail.
• PMS task updates as punches. Completing a ticket is treated as “in.” That is not attendance, and it is not how Dayzen PMS should be described.
• Editing punches to match invoices. The attendance calendar becomes a billing worksheet. Auditability dies.

Fix the design: presence in attendance, allocation in the work log, payroll from closed attendance unless you have a documented exception for a named pay element.

---

Keep punches for presence and timesheets for effort. Reconcile totals if you must; do not merge the ledgers. Dayzen attendance is the HR presence record. Dayzen PMS is a Project Management System, not a timesheet or punch product. If payroll depends on who was present, close attendance on its own calendar and leave client hours to delivery.