Django · Celery · PostgreSQL
HR, Leave & Payroll Portal
Employee records, leave and attendance, shift rosters, payroll runs and payslips, with approval flows that match how the company actually works.
Screens are illustrative layouts of the product, not client screenshots.
Overview
What it is
An HR portal covering employee records, leave and attendance, shift rosters, payroll runs and payslips, with configurable approval chains.
The problem
Why it was needed
HR ran on spreadsheets and email threads. Leave balances were wrong, payroll took days to calculate and approvals got lost.
Features
What We Built
Employee records
Profiles, contracts and documents.
Leave and attendance
Balances, requests and calendars.
Rosters
Shifts, swaps and coverage.
Payroll
Calculation, deductions and approvals with an audit log.
Payslips
PDF payslips delivered by email.
Reports
Headcount, leave and payroll summaries.
Architecture
How It Fits Together
- Employee portalrequests and payslips
- Django appspeople, leave, payroll
- Approval engineconfigurable chains
- PostgreSQLrecords and audit log
- Celerypayroll runs, PDFs, email
- Storagedocuments on AWS
Payroll runs are repeatable and logged, so a correction means re-running with a record of what changed.
Roadmap
From Idea to Launch
A typical delivery roadmap for a project of this kind.
- 1
Requirements
1-2 weeks- Policies, leave types and approval chains
- Payroll rules and deductions
- Roles and permissions
- 2
People and leave
3 weeks- Employee records
- Leave balances and requests
- Attendance
- 3
Rosters and approvals
2 weeks- Shift rosters
- Configurable approvals
- Notifications
- 4
Payroll
3 weeks- Calculation engine
- Audit log and re-run safety
- Payslip PDFs
- 5
Launch
2 weeks- Data import
- Parallel payroll run
- Training and go-live
Want something like this?
Tell us what it should do and we'll come back with a stack, a scope and a timeline.