Automation playbook
Payroll and attendance automation, from the punch at the gate to the bank file
Payroll is rules applied to attendance, which is exactly what software does well and people do slowly. We automate the whole chain: devices push punches in, the muster builds itself, salary is calculated from hours by your rules, and payslips and the bank file are generated for the month. It is what our own payroll product, AurumOne, does every month.
In short
Payroll and attendance automation connects your biometric devices to the system so punches arrive as they happen and the monthly muster builds itself, with missing or unmatched punches flagged for review. Salary is then calculated from hours worked against required hours, with overtime, advances, loans and statutory deductions applied by rule. You review, lock the month, and the payslips and bank transfer file are generated.
The flow
Step by step, who does what
- Punch at the device Pushed in as it happens
- Muster builds itself In, out, overtime, breaks, per day
- Exceptions reviewed Missing punches, late days, leave a person decides
- Salary calculated Hours, overtime, advances, deductions
- Month locked Values kept even if rules change later
- Payslips and bank file Generated for everyone at once
Stays with people: Approving leave, excusing a late day and signing off the month stay with your HR and accounts people.
What gets automated
Attendance. Each device is registered and pushes punches straight in; every employee is mapped to their record, so a punch always belongs to a person. The muster shows days present, offs, holidays, leave and absences with work and overtime hours, and the problems are counted instead of hidden: punches that match nobody, days with an in but no out, a device whose clock has drifted.
Pay. From a monthly salary and standard hours the system derives the rates, then calculates regular pay from hours actually worked, overtime at your multiplier, penalties for late days if you use them, advances and loans recovered through payroll, and deductions such as professional tax and ESIC. Payslips show their working, the bank report is generated, and a locked month stays locked.
- Device punches into the muster, live
- Orphan and incomplete punches flagged
- Hours-based pay with overtime, advances and loans
- Statutory deductions applied by rule
- Payslips, bank file and reports generated
How we build it
AurumOne, our payroll and HRMS product, is set up around your shifts, departments, devices and salary rules rather than written from scratch, which is why it is usually the fastest automation to put live. Every rule is versioned with the date it applies from, so a policy change next month never rewrites last month’s payslips.
We recommend running one month alongside your current method before switching over, and we stay on afterwards. Where your payroll has rules AurumOne does not have, we extend it; that is the advantage of owning the product.
What it connects to
Biometric attendance devices by serial number, bank transfer files in the format your bank accepts, exports to Excel and PDF for your accountant, and, where you need it, your accounting system for the salary journal.
- Biometric attendance devices
- Bank transfer files
- Excel and PDF exports
- Accounting system, for the salary journal
Questions
Common questions
Do we need to buy new attendance machines?
Usually not. If your devices can push or share their punch data, they can be connected. Tell us the make and model and we will confirm before you spend anything.
What if a rule changes mid-year?
Rules carry the date they apply from. The new rule applies from that date, the old one still explains every earlier payslip, and nothing already locked is recalculated.
Can we see who is in right now?
Yes. The dashboard shows who is clocked in, out, present, absent, late and on leave today, refreshing as punches arrive.
Related