Skip to content
Request an invite
Request an invite

Attendance management system

Punches in the morning.
Reasons by evening.

An attendance management system for small teams. Web and mobile punch, shifts with grace, regularisation and a cycle that locks. Each person's day settles into a status, and every status names the rule that decided it.

Included in LekhaHR Operations: ₹79 per employee per month on annual billing for the first 25, no minimum; GST extra. See every band

Paiteq Technologies · Tue, 29 Sep 2026

Meenal Joshi's view · 5 people · office and remote

3 settled · 1 still in · 1 on leave

Live · 18:50:07 IST
  • Meenal Joshi

    09:00–18:00 · founder

    Present9 h 13 m

    because in 08:52, out 18:05; a full day needs 8 h on the clock

  • Asha Rao

    09:00–18:00

    Present8 h 12 m

    because 9 h 12 m on the clock, less a 1 h break

  • Vikram Nair

    09:30–18:30 · grace 10 min

    Late markstill in

    because grace for the 09:30 shift ended at 09:40

  • Rohan Das

    09:00–18:00 · remote

    Half day4 h 22 m

    because out at 13:40: over the 4 h half-day line, under the 8 h full day

  • Priya Menon

    09:00–18:00

    On leave

    because casual leave was approved by Meenal Joshi on Mon 28 Sep

September at Paiteq, so far

month 1–30 Sep · 21 working days

because 30 days, less 8 weekly offs and 1 holiday (Mon 14 Sep, Ganesh Chaturthi)

each column a day · each square a person

August 2026

21 working days · 5 people

because 31 days, less 10 weekly offs

Attendance lockedAug 2026 · 25 Aug, 19:30
  • present
  • late mark
  • half day
  • on leave
  • regularised
  • holiday
  • weekly off
  • not yet written

payroll cutoff Fri 25 Sep · 26–30 Sep are read in October's run

Design preview · sample data · a five-person team at Paiteq Technologies

No. 02

From punch to lock


Four entries, in order. Each one keeps the one before it.

Entered 29 Sep 2026 · 09:02 IST

How does an attendance management system work?

It records each punch with server time, settles the day into a status against the shift and the policy, lets people fix a wrong day before the cutoff, then locks the cycle and hands paid days and loss of pay to payroll. In LekhaHR each of those four entries keeps the one before it.

  1. Entry 1 · 09:02:14

    Punch

    09:02:14

    Punch in · web · Koramangala office

    Recorded

    Shown as recorded only once the ledger has it, with server time.

  2. Entry 2 · 18:14

    Day status

    Present · 8 h 12 m

    because in 09:02, out 18:14, with a 1 h break

    Settled the moment the day closes.

  3. Entry 3 · before cutoff

    Regularisation

    Fri 18 Sep · missed punch-out

    “Left at 18:40 after a client call.”

    Approved by Meenal Joshi · Mon 21 Sep, 10:05

    The day is rewritten, and both entries are kept.

  4. Entry 4 · 25 Aug, 19:30

    Locked cycle

    Attendance lockedAug 2026

    Cycle 26 Jul – 25 Aug. Later changes are written as adjustments, never over the top.

Design preview · sample data

No. 03

Shifts and rules


Rules are dated. A change applies from its date and never reaches back into a locked month.

Rules you can read back.

Set shifts, grace and the half-day line once, in plain terms. Every day status names the rule it used, so nobody has to rebuild a spreadsheet to answer “why was I marked late?”

  • General

    4 people · office and remote

    09:00–18:00

  • Late start

    1 person · Vikram

    09:30–18:30

  • Flexible

    8 h in any window

    07:00–22:00

Grace
10 min after shift start, then a late mark
Full day
8 h on the clock, less breaks
Half day
from 4 h, under 8 h
Regularisation cutoff
4 days after the day
Weekly offs
Sat and Sun, or a roster by location

Sample policy. Every value is yours to set.

No. 04

When a day needs a fix


A late sync is labelled, never hidden. The punch keeps the time it was made.

Attendance regularization: a missing punch waits for a fix.

Vikram Nair forgot to punch out on Fri 18 Sep. The day says so in plain words, and the fix goes to Meenal with his note, before the cutoff.

The day explains itself

In, out, the break and the rule that decided the status, on the person's own phone.

Fixes before the cutoff

A missed punch, a wrong time or a day from home, with a note for the approver.

Late syncs keep their time

A punch made with no network is held on the phone and keeps the time it was made.

Location at the punch only

If your policy asks, a punch checks the office geofence. Nothing is recorded between punches.

How the employee attendance app records a punch

Fri 18 SepShift 09:30–18:30

Needs a look

In 09:36 · no out

This day waits for your out time

You punched in at 09:36 and no punch-out arrived. Until you fix it, the day shows a missing punch.

Cutoff
Tue 22 Sep
A full day
8 h, less breaks
Goes to
Meenal Joshi
Tell us when you left
Design preview · sample data

Fix Fri 18 Septo Meenal

Your day becomes Present

8 h 04 m once approved

You punched out at

18:40

Note for Meenal

Left at 18:40 after a client call.

3 of 3 fixes left this cycle

Send to Meenal
Design preview · sample data

No. 05

Your team, live


What the founder sees at 10:14: who is in, who is away and why.

Your team, as it stands right now.

The view moves as punches land. Late marks and missing punches arrive with their rule, and regularisations are approved from the same screen.

  • Live from the moment you sign in
  • A team lead sees only their team
  • Private leave shows only as “on leave”
Paiteq Technologies/ Team todayLive · 10:14:06 IST

4

In now

because 4 of 5 punched in since 08:52

1

Late mark

because Vikram's grace ended at 09:40

1

On leave

because Priya's leave was approved Mon

  • Meenal JoshiIn 08:52 · officePresent
  • Asha RaoIn 09:02 · officePresent
  • Rohan DasIn 09:18 · synced 09:31Present
  • Vikram NairIn 09:41 · late markLate mark
  • Priya MenonOn leave · back Thu 1 OctOn leave

Needs you

Regularisation · filed 09:55

Vikram Nair · Mon 28 Sep

“Missed punch-out. On a client call until 18:30.”

if approved: Present, out 18:32

ApproveSend back

Heads-up · 09:31

Rohan's punch synced late

Punched 09:18 with no network. Time kept as 09:18.

Design preview · sample data

No. 06

Carried to


When the cycle locks, the record stops moving. Anything later is written as an adjustment.

One day status, read by the rest of HR.

Approved leave writes the day. When the cycle locks, paid days and loss of pay carry into the payroll run with their reasons, so there is no second entry and no mismatch at month end.

  1. AttendanceDay status with its because
  2. LeaveApproved leave writes the day
  3. Payroll inputsPaid days and loss of pay

September 2026 · payroll inputs

attendance 26 Aug – 25 Sep · for September salary

Meenal Joshi
30 paid days

LOP 0 · because she was present on every working day in the window

Asha Rao
30 paid days

LOP 0 · counted as paid days, because casual leave is paid leave (10–11 Sep)

Vikram Nair
30 paid days

LOP 0 · because his late mark on 21 Sep is counted, not deducted, under this policy

Rohan Das
29.5 paid days

LOP 0.5 day · because 16 Sep was a half day with no fix before the cutoff; 29 Sep goes to October's run

Priya Menon
30 paid days

LOP 0 · her casual leave on 29–30 Sep is paid leave and falls in October's input

Payroll cutoff Fri 25 Sep 2026, 19:30 IST
by Meenal Joshi
Attendance locked25 Sep 2026

Design preview · sample data

No. 07

An honest note


because the right tool for your team matters more than one more sign-up.

Who LekhaHR attendance is written for.

Written for you if

Small teams that want each day explained.

  • Your team punches from a browser or a phone, in the office or from home.
  • You want late marks, half days and fixes decided by rules you can read back.
  • Month end still means matching a spreadsheet against payroll by hand.

Talk to us first if

Some set-ups need a conversation before an invite.

  • Your attendance has to come from biometric or face-recognition terminals.
  • Your staff punch offline for days before their phones reconnect.
  • You need rosters across many sites, with shift swaps between staff.

No. 08

Questions


Short answers. Each one matches what the product does.

What small teams ask before they switch.

What is an attendance management system?

It is software that records when people work, checks each day against the shift and the attendance policy, lets people fix mistakes before a cutoff, and hands paid days and loss of pay to payroll. In LekhaHR every day status names the rule that decided it, so nobody has to guess why a day reads late or half.

What is attendance regularisation?

Attendance regularisation is how an employee corrects a day the system recorded wrongly, such as a missed punch or an on-duty day away from the office. In LekhaHR the employee files a request with a reason before the cutoff, a manager approves it, and the corrected day keeps the original entry attached.

What happens if someone forgets to punch out?

LekhaHR does not guess an out time. The day shows a missing punch until the person files a regularisation before the cutoff. Once it is approved, the day is rewritten and the original entry stays attached to it. The person's phone shows the cutoff beside the missing punch.

Can repeated late marks become a half day?

Yes, if your policy says so. Each day shows its own late mark, and a policy can take a half day from casual leave, or another leave type it names, after a set number of late marks in a cycle, or warn only. Late marks are not turned into pay deductions.

Does attendance flow into payroll?

Yes. At the payroll cutoff (for Paiteq's September salary, 26 Aug – 25 Sep), paid days and loss-of-pay days carry into the payroll run with the reason for each day. Days after the cutoff are read in the next month's run, and a fix approved after the lock is written as an adjustment there, never over the locked window.

Does LekhaHR work with biometric attendance machines?

No. LekhaHR records punches from the web and from the phone's browser, with location read once at the punch if your policy asks for it. It does not connect to biometric or face-recognition devices today, so a team that depends on those devices should keep them rather than switch attendance.

How much does an attendance management system cost for a small team?

LekhaHR works from two people up, priced per employee with no fixed monthly minimum, so a small team pays for the people it has. Attendance is included in Operations at ₹79 per employee a month for the first 25, on annual billing, before GST.

No. 09 · By invitation

Start your team's next day on LekhaHR.

because the bill is sized to the team you have. We reply to every request by email.