Attendance from the plant, wages, PF and ESIC, and every statutory form. Plus face and GPS attendance at the gate, so the register is already done when the month ends.
Free until your first month is filed. No card to start.
| Worker | Days | Rate | Gross | PF | ESI | Net |
|---|---|---|---|---|---|---|
| Ramesh Kumar | 26.0 | 450 | 11,700 | 1,404 | 88 | 10,208 |
| Suresh Meena | 24.5 | 450 | 11,025 | 1,323 | 83 | 9,619 |
| Mahesh Jat | 26.0 | 520 | 13,520 | 1,622 | 101 | 11,797 |
| Dinesh Saini | 18.0 | 450 | 8,100 | 972 | 61 | 7,067 |
| 4 workers | 94.5 | 44,345 | 5,321 | 333 | 38,691 |
Illustration of the wage sheet. Names are invented.
Everything a labour contractor has to run — people, attendance, wages and the statutory side — in one place, instead of four spreadsheets and a register.
Every worker, his father's name, designation, wage category, bank and PF details — held once, used by every month and every filing.
Import the plant's own sheet, or mark it at the gate on a phone with face and location. Both end up in the same wage sheet.
Wages, overtime, half days, advances and deductions — computed on the server, locked when the month is closed.
PF ECR, ESIC challan and FORM A, B, C and D, produced from the month you just checked rather than typed again.
Many firms, many sites, many plants — each with its own rate card, its own ESIC code and its own month.
Bank transfer files, salary slips, gate passes and the month-end bundle — Excel or PDF, per site, per month.
⚠ It is not a general HR suite: there is no recruitment, no appraisals and no leave workflow, because a labour contractor does not run those. It does the part he does run, properly.
The plant's sheet arrives in whatever shape the plant sends it. Everything after that is typing, and every bit of typing is a chance to be wrong on a filing.
One sends a matrix of days. One sends punch times. One sends a PDF with the canteen table underneath. None of them match.
Ramesh, Rameshh, Ramesh Kumar, R. Kumar. Two men share a name and a father's name. Somebody has to decide, at speed.
Wage sheet, PF ECR, ESIC challan, bank file, FORM B. They must all agree, and nothing checks that they do.
PF and ESIC are due on the 15th whatever else happened that week. A mistake found on the 16th is a penalty, not a correction.
The same four every month, for every site.
Excel or PDF, exactly as it arrived. The format is recognised; you do not rearrange anything.
Matched workers go through. Anything doubtful is held for you — never guessed.
Days, rates, PF, ESI and advances, all computed on the server. Lock the month when it is right.
PF ECR, ESIC challan, FORM A–D, bank file and slips — from the month you just checked.
A supervisor marks his men at the gate, on the phone he already carries. Every punch carries the worker's face and the place it was taken, and the office sees it the same minute — no register to chase on the 1st, no muster to retype.
And it feeds straight into the wage sheet. The days on the sheet are the punches you already have.
The gate screen, as a supervisor sees it.
Ten families of attendance format, covering nineteen real sheets — day matrices, punch logs, work-hour registers, paired in/out columns, and gate PDFs. Formats are stored per plant, so a new contractor at a plant we already know works on day one.
Days are counted from the day cells, never from the client's total column. The two disagree more often than anyone expects — and when they do, the cells are the truth.
A doubtful name is never auto-matched. Two workers sharing a name and a father's name are flagged for you, not picked by the software.
| Name on the sheet | Matched to | Days | |
|---|---|---|---|
| RAMESH KUMAR | Ramesh Kumar | 26.0 | exact |
| SURESH MENA | Suresh Meena | 24.5 | spelling |
| MAHESH JAT | Mahesh Jat | 26.0 | father's name |
| DINESH | 2 workers match | 18.0 | confirm |
Not a report you retype. The PF ECR is generated for a firm, the ESIC challan for an ESIC code, and the site-wise split sits behind it so you can see which client owes what.
⚠ The ECR belongs to a firm and the challan to an ESIC code — never to one site. The month-end bundle is one site's month, so those two are deliberately not inside it. Handing a client a filing that is not theirs alone is a mistake you only make once.
Illustration. Numbers and UANs are invented.
If your plant is here, your sheet works from day one. If it is not, send us one month's file — teaching a new format is our job, and it is included in every plan, including the cheapest.
Plant and company names are the trademarks of their owners and are listed only to say which attendance formats this software reads. No endorsement or affiliation is implied.
This started as one contractor's own system, built over several years and thirty-two versions while running roughly forty sites for cement plants. Every rule in it — the rounding, the PF and ESI bases, the way a name is matched, the things it refuses to guess — is there because something went wrong at a plant once and had to not happen again.
WageWisely is that system, rebuilt properly so contractors anywhere in India can use it too.
Wage, attendance, PF and ESIC records are never removed — only marked. Every change carries who made it and when.
A blank rate says it is blank and that nothing will be assumed. A hidden sheet says it is hidden.
If a payment fails, the account still opens and every export still runs. A billing problem must never become a statutory penalty.
Download the whole account whenever you like, on any plan. If you leave, nothing is deleted.
Send us one month's file. We teach the format and it works from then on — for you and for the next contractor at that plant. It is included in every plan, including Basic, because a contractor whose sheet cannot be read has no use for the software at all.
No. That is the point. Upload the file as it arrived.
No. It runs on the supervisor's own phone in the browser — no app to install, no biometric machine to buy, nothing to maintain in the dust.
Punches are kept on the phone and sync when a network appears. They are marked as offline so the office knows the time came from the phone rather than from our server.
You get a warning, not a stoppage. A month already in progress always finishes — stopping a filing week to collect a subscription is how a customer goes back to Excel. If you stay over, you move up next month.
Nothing happens to your account. We never make an account read-only between the 1st and the 15th for any billing reason, because PF and ESIC are due on the 15th.
No. A site login sees only the sites you give it. Office and owner logins are separate roles with their own limits.
Yes, at any time, on any plan — including while an account is unpaid. It is your payroll.
No. Every record carries its company, and every query is restricted to it. See the privacy policy for exactly what is stored and who can see it.
That is the honest test. Put in a month you closed by hand, and compare every figure. The trial covers one full month-end, so you can.
WageWisely