The core of the product
Attendance, however it arrives
Most payroll software assumes a clean file. This one assumes a real one.
What it handles
- A title merged across eight columns, then a blank row, then the real header
- Twenty empty rows left below the data for next month
- A TOTAL row that must not be read as a worker
- Nineteen sheets, of which three are attendance and the rest are invoices and masters
- A running log holding several months, split by period so April is not paid in July
- Day-by-day mark grids as well as summary columns
- Column names it has never seen, offered for confirmation rather than guessed
What it will not do
- Invent a UAN, an ESIC number, a bank account or an employee code
- Resolve two equally close name matches on its own
- Treat an unrecognised attendance mark as absence
- Assume every organisation uses the same abbreviations
- Produce an ECR while workers are still unresolved
- Hide a disagreement between the sheet's own totals and the arithmetic
Marks it understands out of the box
P
Present
A
Absent
WO
Weekly off
H / PH
Holiday
CL / SL / EL
Paid leave
LOP / LWP
Loss of pay
HD
Half day
Anything else
Asked, then remembered
Your sites may use different letters. Confirm an unfamiliar mark once and it becomes part of your organisation's dictionary.
After reading, before calculating
The review screen tells you what happened in plain numbers.
Total rows
Everything found in the sheet
Matched employees
Resolved to your master with confidence
New joiners
Not in the master, with details pre-filled
Ambiguous
More than one possible person
Missing information
What is needed before payroll can run
Ready for payroll
What will be calculated if you continue
Try it with your own attendance sheet
Upload the file you already use. You will see what the system read, what it matched, and what it wants you to check — before anything is calculated.