HR software where payroll comes out of attendance, not a spreadsheet

Soham Dang built the HR suite inside Avani Business OS — onboarding, leaves, attendance, payroll, salary slips, team performance and HR analytics — which removed more than 20 hours of manual HR work per week.

HR software fails in a specific way. The system holds the leave requests, and payroll still happens in a spreadsheet, because the export never quite matched what payroll needed.

So the month-end process is: download attendance, download leaves, reconcile them by hand, calculate deductions, generate slips, email them individually. Every month, for every employee.

The parts that matter

  • Onboarding

    A new joiner's documents, access and details captured once, into the same record payroll will read.

  • Leave and attendance

    Requests, approvals and balances in one place, with the data payroll needs already in the right shape.

  • Payroll from real data

    Salary slips generated directly from attendance and leave records, including penalty and deduction calculation — not from a reconciled spreadsheet.

  • Salary slips

    Generated and distributed, with a history employees can access themselves rather than emailing HR.

  • Performance

    Goal tracking and team performance, on the same employee record as everything else.

  • HR analytics

    Attendance trends and performance rates from aggregation pipelines, so the reporting stays fast as history accumulates.

Why the integration is the whole point

Each of those modules exists as a standalone product. The value is not in any one of them — it is that leave, attendance and payroll read the same records, so month-end is a calculation rather than a reconciliation.

That single property is where the 20+ hours a week went.

What it runs on

React.js, Node.js, Express.js and MongoDB, with role-based access control so an employee sees their own record, a manager sees their team, and HR sees the organisation.

Payroll rollups and the analytics dashboards run as MongoDB aggregation pipelines. Computing them in application code is what makes HR systems slow once a few years of attendance history exists.

The access control is not optional

HR data is the most sensitive data most companies hold — salaries, documents, performance notes. Permissions have to be enforced in middleware rather than by hiding buttons, and a request for another employee's record has to fail at the API.

This is the part that separates an HR system from a shared folder with a login screen.

What it costs

Avani Business OS is priced at ₹25 per employee per month. Custom modules, integrations and bespoke builds are quoted separately against the feature set.

  • Per employee — ₹25 per employee / month

    The whole platform, priced on headcount rather than per module.

  • Custom build — Quoted on the feature set

    For modules that do not exist yet, or a process no product models.

Common questions

What does the HR portal built by Soham Dang do?

It covers onboarding, leave management, attendance tracking, automated payroll with penalty and deduction calculation, salary slip generation, employee goal tracking, team performance and HR analytics dashboards — all on one employee record.

How much manual work does HR software actually save?

In the case of the HR suite inside Avani Business OS, more than 20 hours per week. The saving comes from payroll generating salary slips directly from attendance and leave data rather than from a spreadsheet reconciled by hand each month.

Can HR software integrate with an existing payroll provider?

Yes, through their API where one exists. The decision is whether payroll calculation should live in the system or in the provider — which depends on how unusual your deduction and penalty rules are.

How is sensitive HR data protected?

Role-based access control enforced in middleware rather than in the interface, so an employee cannot retrieve another's record by changing an id. Salary and document access is scoped per role, and every access path goes through the same guard.