Admire Wheel at a Glance
Attendances were noted in registers at the showrooms of Admire Wheel Private Limited, and that resulted in buddy punching. The first human resource software introduced at Admire Wheel Private Limited is called TankhaPay, which uses geo tagging for attendances via mobile phones and runs payroll.
| Client | Admire Wheel Private Limited |
|---|---|
| Industry | Wholesale and retail (automobile dealership) |
| Active users on TankhaPay | 150+ |
| Previously using | Paper registers. TankhaPay is its first HR software |
| Core problems | Attendance managed through registers, leading to buddy punching as they have multiple showrooms |
| Attendance mode | Mobile check-in with geo tagging |
| Core modules | Attendance with geotagging and mobile check-in, payroll |
| Result | 100% of check-ins tied to the employee's own login and a location. Monthly attendance consolidation cut from 4 days to under 1 |
- Attendance with geotagging and mobile check-in
- payroll
Who Was Really Marking Attendance at Your Showroom?
At Admire Wheel, a signature in a register could not answer that. Buddy punching is where this story starts.
Buddy punching means one employee marks attendance for another. A register cannot catch it, because it records a signature, not who made it or where they were.
With staff spread across several showrooms, no one person could check every register every day.
Who Is Admire Wheel Private Limited?
Admire Wheel Private Limited is a wholesale and retail company with 151 active users on TankhaPay. Its employees work across multiple showrooms.
In a showroom business, staff presence on the floor drives sales and service. That makes accurate attendance the first record the business needs to trust.
Why Do Paper Registers Fail Across Multiple Showrooms?
Because a register depends on honesty and on someone checking it, and neither scales across locations. Each showroom ends up with its own book and its own way of filling it.
Three gaps followed from that setup:
| Gap | What it meant at Admire Wheel |
|---|---|
| Authenticity | A colleague could sign for an absent employee, with no way to tell |
| Location | No record of where an employee actually was when attendance was marked |
| Consolidation | Registers from each showroom had to be gathered and added up by hand, taking about 4 days each month |
Each gap added manual work for HR and accounts. Time went into verifying attendance, not using it.
How Does TankhaPay Capture Attendance at Admire Wheel?
TankhaPay captures attendance through mobile check-in with geotagging, and runs payroll alongside it. These are the documented hero features for the account.
How Does Mobile Check-In With Geo Tagging Reduce Buddy Punching?
Each employee checks in from their own login, and the location of the check-in is recorded with it. Attendance becomes a record tied to one person and one place.
A signature in a register can be written by anyone. A check-in made from an individual's own account, with a location attached, is much harder for a colleague to do casually on someone's behalf.
HR can compare each check-in with the showroom the employee is assigned to. A check-in from somewhere unexpected is visible for review.
What Does Geo Tagging Record, and What Does It Not?
Geo tagging records the location from which a mobile check-in was made. It gives HR and showroom managers a location to review against the assigned showroom.
It indicates where the mobile device was at the time of check-in. It does not by itself prevent a check-in from happening somewhere else, which is what geofencing would do.
View geo-tags as an indication of presence for consideration, not as conclusive proof. They reduce the possibility of buddy punching but do not eliminate it.
How Does Payroll Run From the Same Attendance Record?
Payroll reads from the attendance TankhaPay has already recorded. HR does not collect registers from each showroom before a cycle can begin.
Days worked, absences and leave come from one system. The payroll team works from that record instead of retyping figures from paper.
"We had maintained registers for years, and we have known that there were some entries that were not genuine. As everyone now reports through their phones individually, it becomes possible to know who has signed where, and this is also our payroll entry point."
What Changed for Admire Wheel After Moving to TankhaPay?
Attendants went from logging on registers in showrooms to logging attendance in one mobile device and all logging of attendance now includes name and location. Consolidation is down to less than 1 day per month from 4.
The table sets the before against the after. The gain is a record with a person and a place on each entry, so disputes are settled from the system, not from memory.
| Area | Before TankhaPay | After TankhaPay |
|---|---|---|
| AreaAttendance method | Before TankhaPayPaper registers at each showroom | After TankhaPayMobile check-in |
| AreaAuthenticity | Before TankhaPayColleagues could sign for each other | After TankhaPay100% of check-ins made from the employee's own login |
| AreaLocation | Before TankhaPayNot recorded | After TankhaPayGeo tag captured on 100% of check-ins |
| AreaConsolidation | Before TankhaPayRegisters collected and added by hand, about 4 days each month | After TankhaPayOne attendance record across showrooms, ready in under 1 day |
| AreaDisputes | Before TankhaPaySettled from memory and signatures | After TankhaPaySettled from the system record, with 80% fewer attendance disputes |
| AreaPayroll | Before TankhaPayPrepared from register entries and retyped | After TankhaPayRun from recorded attendance, with 100% of entries carried over without retyping |
"The register only records what people write, not what occurs. Admire Wheel should not have had more supervision in all the showrooms. It should have had every entry linked to an individual and location."
What Should a Multi-Showroom Business Ask Before Choosing an HRMS?
Ask whether the system can prove both where an employee checked in and who checked in. Each point below tests a different part of that, from location to how one showroom's attendance reaches payroll.
Five points are worth checking in any demo:
- Is every check-in tied to a place? Ask whether each mobile check-in stores its location, and what happens when someone checks in from outside the showroom.
- How does the system confirm who is checking in? Geotagging shows where a phone is, not who is holding it. Ask how the vendor stops one employee checking in for another, because that is the buddy punching problem.
- Can one system cover several showrooms? Ask to see all showrooms together and drill into one, without a separate setup for each.
- Does attendance reach payroll without re-entry? If hours are exported and retyped, the manual step from the registers has only moved.
