Employee self-service in Pitch N Hire HRMS

What employee self-service includes

What is an HR portal, and what does the Pitch N Hire one show an employee?

An HR portal is the single place an employee goes for anything about their own employment, instead of emailing HR and waiting. In Pitch N Hire the portal opens on what people check most: this month's payslip, leave balance, attendance for the current period, pending approvals and any task assigned to them. Below that sit the actions — apply for leave, regularise a punch, submit a declaration, update a detail, request a letter, raise a query. What an individual sees is driven by their role and their record, so a shift employee, a desk employee and a manager open the same employee self-service portal and find different things on it. Nothing shown is a copy: the payslip is the payslip payroll produced, and the balance is the balance leave calculated.

How do employees get their payslips and tax declarations?

Payslips publish to the portal when a payroll run closes, and stay there as a history the employee can open, download or forward without asking anyone. Each one carries earnings, deductions, employer contributions where applicable and the net paid, using the same figures the payslip and settlement module generated, so there is no second document to reconcile. Tax declarations work as a window HR opens: employees declare intended investments and exemptions at the start of the year, then upload proofs when the proof window opens later. Both are captured in structured fields rather than as mail attachments, so payroll computes deductions from what was declared and flags anything unproven once the window shuts. Employees can see how a declaration changes their expected deduction before submitting it.

How do leave and attendance requests work from self-service?

A leave application starts from the balance, not from a blank form. The employee picks a type, sees how many days that type has left and what the request will leave behind, chooses dates against the holiday and weekly-off calendar, and submits to the approver already shown on screen. That approver is derived from the reporting line on the record, so nobody has to be told where to send it. Attendance regularisation takes the same shape: the employee opens a day that is short or missing a punch, gives a reason, and it goes for approval before it counts. Approved requests write straight into leave and attendance, which is what turns month-end payroll input into a report rather than a reconciliation between mailboxes and spreadsheets.

Can employees update their own profile and bank details?

Yes, within limits you set. Fields such as personal phone number, emergency contact and address are opened to employees because they are the people who know when those change. Sensitive fields — bank account, name, statutory identifiers — can be edited by the employee but reach HR as a request carrying the old value, the new value and any supporting document, and apply only once approved. Fields that define employment, such as designation, department, reporting manager and salary structure, stay with HR entirely and appear in self-service as read-only. That split is deliberate: it removes the transcription work of employees mailing changes to HR without letting the master record drift. Every applied change lands on the record history with the approver's name attached to it.

How do employees raise letter and document requests?

Common requests are a menu rather than an email. An employee picks what they need — employment confirmation, address proof, salary certificate, a bank or visa letter — supplies whatever the template requires, and submits. The request routes to the team that owns it, the letter is generated from a stored template populated with data already on the record, and the finished document publishes back to the same portal for download. Because the template pulls from the record, the designation, joining date and address on the letter are the ones the system holds, which is where most manually typed letters go wrong. Employees also open their own files at any time: uploaded identity papers, issued letters, past payslips and policy acknowledgements sit on their profile, managed by the HR document module.

What does a manager see in the same portal?

A manager opens the same portal and gains a team layer on top of their own. Approvals waiting on them are grouped and actionable in place, with the context needed to decide — for a leave request, who else in the team is out on those dates; for a regularisation, the punch record that triggered it. Team views show attendance for the current period, who is on leave this week, upcoming confirmation and probation dates, and the documents their team still owes. Managers apply for their own leave in the same session, and their requests route upward along the reporting line. Where a manager will be away, approvals can be delegated for a period through HR workflows so requests keep moving rather than sitting until they return.

Does the employee portal work on mobile?

The portal is used most in moments when people are not at a desk — punching in from a site, applying for leave from home, checking a payslip on a commute — so it runs in a phone browser under the same rules as the desktop view rather than as a reduced version. Clocking, leave application, approvals, payslip download and document upload all work from mobile. Approvals are the case that matters most: a manager clearing requests from a phone is the difference between a request being decided the same day and waiting until they next open a laptop. Because the mobile view reads the same permissions, a manager sees nothing on a phone they could not see on a desktop, and every action carries the same audit entry wherever it came from.

How is access to the HR portal controlled and logged?

Every employee gets access tied to their own record, so their identity in the portal is the identity payroll and attendance already use. What they can open is governed by the same role and field-group permissions that protect the profile, which means self-service never becomes a side door into data the record protects. Actions are logged individually: a declaration submitted, a bank detail changed, a payslip downloaded, an approval given. When an employee is deactivated at exit, portal access closes with the record instead of being a separate task somebody has to remember, while documents already issued remain available for the window your policy allows. Login and access problems are raised as tickets, so they are tracked rather than arriving as direct messages to whoever is nearest.

What does self-service actually remove from the HR inbox?

The repetitive traffic. Payslip resends, balance queries, address-proof and employment-letter requests, bank detail changes, missed-punch corrections, tax proof submissions and status chasing make up the bulk of what HR teams answer, and each one is a question the system already knows the answer to. Moving them into the portal changes what HR spends its time on rather than only how fast answers arrive. The second effect is data quality: when the employee enters their own address or declaration, the record stops being a transcription of a mail thread. The third is traceability — every request carries a state, a requester, an approver and a timestamp, so an unanswered item is visible rather than buried. What people ask for, and how long it takes, then reports like any other module.