HR Payroll

Zerithonlabs - Modern HRM + Payroll platform rebuilt with Laravel for real company workflows and long-term maintainability.

Legacy version note: this main branch is the Laravel rebuild. Older legacy implementation may exist in a separate branch.

Live Demo

Explore the hosted Zeri HR demo environment.

💛 Support My Work

Your support helps me continue building better software, maintaining open-source projects, and creating useful tools through MADCODERZ.

 

Why This Project

A complete HRM and Payroll platform for organizations that need one system to manage employee lifecycle, attendance, leave, payroll, approvals, and reporting.

It is designed with a modular Laravel architecture so teams can run day-to-day HR operations with cleaner structure, maintainability, and long-term scalability.

Main Features

• Role-based HR dashboard with employee, attendance, leave, notice and quick-note widgets
• Employee lifecycle management with profile updates, employee status, departments, designations and reporting lines
• Employee self-service login for own profile, attendance, leave, tasks, payslips, loans, deductions and provident fund records
• Attendance management with clock in/out, time change requests, reports, print and export
• Leave management with categories, quotas, balances, applications, approvals and reports
• Resignation workflow with employee apply, supervisor review and final HR/Admin approval
• Notices, announcements, holidays and holiday calendar
• Teams, projects, tasks, members, file preview and comments
• Salary grades, reusable salary templates and employee-specific salary assignment
• Payroll draft generation, review, final submission, payslips, payment status and payroll reports
• Bonus, employee loan, deduction and provident fund management
• Loan approval workflow with supervisor approval, final approval and salary-based installment deduction
• Confidential payroll access: employees see only own salary data unless explicit payroll permissions are assigned
• Reports for employees, attendance, leave and payroll with scoped data access
• Dynamic database-driven roles and permissions with scope labels
• Notifications, private notes and user account approval
• Settings-managed company profile and SMTP configuration
• Responsive Bootstrap-based admin interface

Language Support

Zeri HR includes multilingual UI support for core HR, payroll and admin screens.

🇺🇸 English   🇩🇪 German   🇫🇷 French   🇮🇳 Hindi

Screenshots

1. Settings Page

2. Update Profile

3. Holiday Calendar

4. Attendance & API Integration

Tech Stack

• PHP 8.2+
• Laravel 12
• MySQL
• Blade templates
• Bootstrap-based admin UI
• Vite

Quick Start

1. Clone and enter the project

git clone https://github.com/Devnawjesh/hr-payroll.git
cd hr-payroll

2. Install dependencies

composer install
npm install

3. Configure environment

cp .env.example .env
php artisan key:generate

4. Set DB credentials in .env, then run:

php artisan migrate
php artisan db:seed --class=AdminUserSeeder

The default admin seeder creates all permissions, default organization roles, role-permission assignments, and the default admin user.

5. Run app

php artisan serve
npm run dev

Default Seeded Admin

• Email: admin@zerihr.local
• Password: password
• Role: Admin

You can change these values before seeding by setting:

DEFAULT_ADMIN_NAME="System Admin"
DEFAULT_ADMIN_EMAIL=admin@zerihr.local
DEFAULT_ADMIN_PASSWORD=password

Default Organization Roles

The default seed creates ready-to-edit role templates for a typical organization:

• Super Admin and Admin with full permissions
• HR Admin and HR Manager for HR operations and approvals
• Payroll Manager for salary, payroll, payslip, bonus, loan, deduction and provident fund modules
• Finance Manager for billing, invoices, estimates, expenses and finance reports
• Department Head, Supervisor, Project Manager and Team Lead for scoped team/project workflows
• Auditor for read-only review access
• Employee for self-service profile, attendance, leave, task and own payroll records

Admin or HR users can adjust these default mappings later from the Roles and Permissions screens.

Demo Users

For demo environments, seed four ready-to-use users:

php artisan db:seed --class=DemoUserSeeder

All demo users use password P@ssword.

Role	Email
Admin	demo.admin@zerihr.local
HR Admin	hr.admin@zerihr.local
Department Head	department.head@zerihr.local
Employee	employee@zerihr.local

The login page includes these demo accounts with copy buttons for visitors.

Access Model (Current)

Access is permission-driven. The default seed creates common organization roles and assigns practical permissions by default. Admin or HR users can change those permissions later based on company policy.

Menus and module actions are shown or hidden based on assigned permissions.
Self-service profile update remains available via topbar dropdown when user is linked to an employee profile.

Basic role scope:

• Employee: own profile, attendance, leave, assigned work, payslips, loans, deductions and provident fund records
• Department Head / Supervisor: own records plus scoped department/team attendance, leave, resignation and work approvals
• HR Admin / HR Manager: employee lifecycle, attendance, leave, profile updates, resignations and HR reports
• Payroll Manager / Finance Manager: salary setup, payroll runs, payslips, bonuses, loans, deductions, provident fund and payroll reports
• Admin / Super Admin: full system setup, roles, permissions, settings and all modules

Payroll, payslip, loan, deduction and provident fund data are confidential. Department heads and supervisors do not see subordinate salary data unless explicit payroll permissions are assigned.

Payroll Flow

Payroll is generated as a draft first. HR or Payroll reviews the draft payslips, then final submits the payroll run. Final submission posts salary-linked effects such as due loan installments and provident fund transactions. Salary payment status can be marked after the payroll run is processed.

For full module and permission details, see Documentation/index.html.

SMTP and Outbound Email

SMTP values are configured from the Settings page and stored in DB-backed system settings.

Current implemented email flow:

• when a permitted user creates a user, credentials can be emailed
• sender config is loaded from system settings (mailer/host/port/username/password/from)

Project Structure (High Level)

• app/Modules/Employees employee domain
• app/Modules/Users user, role, permission domain
• app/Modules/Settings system and SMTP settings
• resources/views/hr backend UI
• database/seeders permissions, settings and default admin user seeders

Contributing

Contributions are welcome.

1. Fork the repository
2. Create a feature branch
3. Commit with clear messages
4. Open a pull request with:
   • problem statement
   • approach
   • screenshots (if UI)
   • migration/seed impact

Roadmap

• stronger test coverage (feature + service tests)
• audit trail improvements
• notification system enhancements
• API layer for external integrations
• richer reporting and exports

💛 Support My Work

Your support helps me continue building better software, maintaining open-source projects, and creating useful tools through MADCODERZ.

 

License

MIT