Why we built rather than bought
Most commercial HRMS platforms are designed for a generic organisation with standard pay structures and off-the-shelf workflows. They work well for simple cases but fall short when you need shift-based attendance with weekly rotation patterns, variable bonus components tied to output metrics, or biometric device integration via proprietary SDK.
We designed the Swenivis Friday One to handle these scenarios correctly. The product is built for organisations with hourly and salaried workers, complex pay components, multi-level approval chains, and full Indian labour law compliance. It is also the codebase we use to demonstrate our engineering standards — so quality was non-negotiable.
Key pain points
- ✕Shift-pattern management that changes weekly across teams
- ✕Piece-rate and variable bonus components not handled by off-the-shelf payroll libraries
- ✕Biometric attendance device integration via proprietary SDK
- ✕Indian statutory compliance: PF ECR, ESI challan, PT return, Form 24Q
- ✕Employee self-service for non-desk workers who do not use email
What we built
The Swenivis Friday One is a modular, full-stack application built on Next.js 16 (App Router) with a PostgreSQL database via Prisma ORM. Core modules: attendance and shift management, payroll with full Indian statutory compliance, leave management with configurable multi-level approval, performance reviews with manager and peer feedback cycles, statutory report generation, and employee self-service portal.
The payroll engine is a pure TypeScript function with 100% unit test coverage. Every calculation — basic pay, allowances, deductions, PF, ESI, PT, TDS, and variable bonus — is auditable to the rupee. Payroll for 500 employees processes in under 4 hours, including statutory report generation.
The attendance integration module handles biometric devices via a Windows service written in C# (.NET 8) that polls device APIs every 5 minutes and syncs punch-in/out records to the HRMS. The sync service queues failed requests locally with exponential backoff — records are never lost even during network outages.
Technology stack
Frontend
Backend
Database
Integrations
Key engineering decisions
Custom payroll engine over third-party library
The variable bonus and piece-rate calculation requirements were specific enough that no payroll library handled them cleanly. We built the engine as a pure TypeScript function with 100% unit test coverage — every rupee is independently auditable.
Offline-capable attendance sync
Manufacturing and field environments have unreliable connectivity. The Windows sync service queues failed requests locally and retries with exponential backoff — attendance records are never lost during network outages.
WhatsApp notification bridge for non-desk employees
Many floor staff do not use email. We integrated WhatsApp Business API to send leave approval notifications and payslip summaries — meeting employees on the channel they already use daily.
The results
The HRMS is live and in use by our team. The statutory compliance module generates PF ECR, ESI challan, and PT returns in a single operation. The codebase is modular and adaptable for different organisation sizes, industry types, and compliance requirements. If you need a custom HRMS built, we can start from this codebase or build to your specific requirements.
From our founder
This is real software we built for ourselves. The payroll engine handles our own statutory filings. We are happy to walk any prospective client through the codebase — the architecture, the test suite, the compliance module. We believe the most honest thing a new company can do is show, not tell.
Need a custom HRMS or similar product?
We can adapt this codebase to your organisation's requirements, or build from scratch to your specification.
Book a discovery callMore engineering work
