Employee Records
Employee self-service tools
Assess employee self-service by the tasks people can complete, the status they see, appropriate access and dependable HR records.
Employee self-service tools let staff view information and complete defined HR tasks without asking HR to enter every request. Assess them by following a task to its final record: what can the employee do, what needs a decision, and how will they know the outcome? A portal or app alone does not answer those questions.
An HRIS (human resources information system) is a category of HR software, and some HR software integrates with payroll systems. Employment Hero is one named HR software example; its name alone does not confirm which self-service tasks a particular configuration supports.
Choose the tasks
Start with work employees frequently need to do: finding a pay slip, checking a request, updating a permitted contact detail or reporting an error. For each task, name the record owner and the next action. A submitted request may still need review before another system uses the change.
Map tasks to the configured HRIS, portal or payroll-connected software rather than assuming a product supports every task. Include leave requests where employees need them, and distinguish an employee’s submission from the record that is ultimately changed.
| Task | Outcome to check | Boundary to explain |
|---|---|---|
| View a record | The employee can find the relevant item privately | Where is the authoritative copy? |
| Update a permitted detail | The saved value is visible | Does it take effect immediately? |
| Request a change | The employee can see its status and decision | Who decides and receives the result? |
| Report an error | Someone can investigate and respond | How is the correction recorded? |
The Fair Work Act 2009, section 535, requires time and wages records to be kept for seven years. Employees must receive a compliant pay slip within one working day of payment under the Fair Work Regulations 2009. Pay-related records can also include superannuation contribution amounts, dates paid and fund name.
If a task continues outside the tool, explain that handoff. A button labelled as a completed update should not merely send an unreviewed request.
Key Compliance Requirements for Employee Records in Australia
- Superannuation contribution details required
- Amount, date paid, fund name
- Tax File Number protection under Rule
- Privacy (Tax File Number) Rule 2015
Match access to the task
Employees need access to their own relevant information. Managers, HR and payroll may need different views of a request. Check reports, downloads and notifications as well as the main screen: a private profile is of limited use if an emailed status reveals unnecessary detail.
A useful baseline is for employees to see their own information and requests, managers to see requests needing their action, HR to administer workflows, and payroll to handle pay-related queries. Set access by task, not just by job title.
Privacy obligations depend on who handles the information and why. The Privacy Act 1988 (Cth) and Australian Privacy Principles provide a framework for applicable organisations, overseen by the Office of the Australian Information Commissioner (OAIC); the OAIC also publishes guidance on the employee records exemption, so check whether it applies.
The Privacy (Tax File Number) Rule 2015 concerns the protection of tax file number information; treat it as a specialist exception rather than ordinary profile data.
Separate entries from decisions
Decide whether a change can be saved directly, needs review or must follow a specialist process. Show a pending request as pending, and identify who checks any rejected downstream update.
Use distinct states such as submitted, pending, approved, rejected and applied. Do not show a request as applied until the receiving record has changed.
Follow the employee journey
Ask a supplier to show the proposed configuration with synthetic or suitably protected accounts. Follow an employee from sign-in through finding an item, submitting a request, reading its status and reporting an error. Then inspect the manager or HR view and any receiving system. Record what was shown, what requires configuration and what remains unverified.
Include the mobile and alternative access routes the workforce needs. W3C’s Guidance on Applying WCAG 2.2 to Mobile Applications is informative guidance, not a normative requirement.
Assign owners for permissions, field rules, instructions and unresolved requests. HR owns task definitions, instructions and general unresolved requests; payroll owns pay-slip or pay-record queries; managers act on decisions routed to them; a system administrator maintains the configured workflow. Escalate a request to its named owner when it cannot be completed or remains blocked.
Employee Journey Through Self-Service Tools
- Sign-in securely using multi-factor authentication
- Find personal records (e.g., pay slips, leave balance)
- Submit a request (e.g., update contact details)
- Monitor request status (submitted → pending → approved/rejected)
- Report an error if needed; confirm response received
In this guide
- Letting employees update appropriate personal detailsDecide which employee details suit direct editing, which need review, and how to show the final record and correction path.
- Designing approval steps for sensitive record changesDesign self-service approvals around verification, decision authority, effective dates, downstream results and correction.
- Testing self-service access on mobile devicesUse complete mobile tasks to check sign-in, private record access, forms, accessibility, interrupted sessions and request status.
- Reducing avoidable HR enquiries with clear self-service guidanceTurn repeated employee questions into clear task instructions, useful status wording and a reliable route for genuine exceptions.
