Human resource management
HRM System
ASP.NET Core 8 HRM GraphQL API—employees, attendance, leave, Hangfire payroll jobs, SQL Server/Dapper.
Background & Context
Organizations need a centralized API for employee records, attendance clock workflows, leave requests, and scheduled payroll processing—especially when multiple client UIs may consume the same HR domain later. Spreadsheet HR and ad-hoc attendance sheets do not scale, and payroll jobs need a reliable background runner.
Tekvers built an HRM backend-only system on ASP.NET Core 8 with HotChocolate GraphQL (primary), a small REST auth surface under /api/auth, SQL Server via Dapper stored procedures, JWT Bearer auth, Serilog, health checks, and Hangfire (SQL Server storage) for monthly payroll processing and related jobs. Docker Compose packages API + SQL Server. There is no first-party frontend in this repository—clients are expected to consume GraphQL and REST.
Implemented GraphQL covers employees (CRUD-style mutations/queries), department reads, attendance clock-in/out/approve/report, and leave request/approve/cancel mutations. Payroll calculation/processing exists as a service plus Hangfire cron; there is no public GraphQL/REST payroll API. Multi-tenancy is modeled in schema/JWT but repositories currently resolve Guid.Empty. Several stored procedures and older REST docs are incomplete relative to code—portfolio claims stay aligned to what runs.
The Challenge
HR teams needed a production-shaped API for employees, attendance, and leave—with a path to scheduled payroll—without waiting on a full UI suite in the first backend release. Without a coherent human resource management foundation, HRM System stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
HRM System: ASP.NET Core 8 HRM GraphQL API—employees, attendance, leave, Hangfire payroll jobs, SQL Server/Dapper. Centralized HR API for employee, attendance, and leave operations. Tekvers delivered a maintainable human resource management system for HRM System using ASP.NET Core, HotChocolate GraphQL, SQL Server, Dapper, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
GraphQL-first HR domain
Employee, department, attendance, and leave operations were exposed through HotChocolate so future web/mobile clients share one contract instead of inventing parallel REST CRUD for every screen.
Attendance and leave workflows
Clock-in/out, approval, and attendance reports support daily ops; leave mutations cover request, approve, and cancel—keeping the highest-friction HR workflows in the API even where some SP scripts remain incomplete in-repo.
Background payroll and ops tooling
Hangfire runs monthly payroll processing and related schedules; Serilog, `/health`, Swagger (Development), and Docker Compose support operations—while documenting auth gaps (e.g. Hangfire dashboard not authenticated) honestly for hardening.
What We Delivered
- ASP.NET Core 8 HRM API (`net8.0`)
- HotChocolate GraphQL endpoint at `/graphql`
- REST auth: login and register (JWT)
- Employee GraphQL queries and create/update/delete mutations
- Department read queries
- Attendance clock-in/out, approve, and report queries
- Leave request / approve / cancel mutations
- Payroll service with Hangfire monthly processing job
- SQL Server schema scripts and Dapper stored-procedure data access
- Docker Compose for API + SQL Server
- Serilog logging and `/health` checks
Outcomes & Impact
- Centralized HR API for employee, attendance, and leave operations
- Scheduled payroll processing path via Hangfire
- Containerized backend ready for client UI consumption
- Clear honesty notes on tenancy enforcement and incomplete SP/doc surfaces
HRM System gives organizations a GraphQL-backed operating model for core people workflows—faster API integration for internal tools, better structure than spreadsheets, and a stack ready for a first-party UI or ERP embedding in a later phase.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.