HRIMS Leave Application and Leave Balance Module

This project is an internal HR module developed during my internship using ASP.NET, designed to streamline the management of employee leave processes within an organization.

It allows employees to submit leave applications through a structured workflow while automatically validating requests based on employment type—distinguishing between permanent and contractual staff. The system maintains accurate leave balances and provides real-time visibility through a dedicated leave balance card interface.

On the administrative side, the system supports comprehensive report generation, including individual leave histories, summarized leave reports per employee category, and printable leave balance cards. These reports were designed to support HR decision-making and ensure transparency in leave tracking.

Overall, the module focuses on improving efficiency, reducing manual computation of leave balances, and providing a reliable reporting system for organizational HR operations.

The Leave Application Module was developed using ASP.NET following a structured, layered architecture to ensure maintainability, scalability, and separation of concerns.

1. Presentation Layer: The user interface provides employees with an intuitive workflow for filing leave requests and viewing their leave balances. Separate views were implemented for permanent and contractual employees to reflect differences in leave entitlements and policies. The UI also includes a leave balance card display for quick status reference.

2. Business Logic Layer: The core application logic handles leave validation, approval rules, and balance computation. This layer ensures that leave requests adhere to organizational policies based on employee type (permanent or contractual). It also manages the generation of structured reports for both individual leave history and aggregated summaries.

3. Data Access Layer: A relational database is used to store employee records, leave applications, and leave balances. The data access layer abstracts direct database interactions using structured queries or ORM patterns (depending on implementation), ensuring consistency and maintainability of data operations.

4. Reporting System: A dedicated reporting component generates formal leave reports for administrative use. This includes leave history reports per employee, summaries, and leave balance card generation.