Employee Records
Employee records and HR data
Build dependable employee records by defining data ownership, change history, access and retrieval across HR and payroll systems.
A dependable employee record lets an Australian employer identify the right person, see current employment arrangements and explain how they changed. Decide which system owns each fact, who may change it, and how an approved change reaches payroll and other users. Without clear ownership, approval and change processes, records can conflict and users may rely on outdated information.
What the record needs to explain
Keep the person, each period of employment and changes within a period distinguishable. Someone may change roles, leave and later return. Record those events without treating every arrangement as a new person or overwriting the earlier one.
For each important field, record its source. Record its owner as well.
| Part of the record | Question it should answer |
|---|---|
| Identity | Which person does this record refer to across HR and payroll systems? |
| Employment details | What arrangement applied, and from when? |
| Change history | What was approved, when did it take effect and what did it replace? |
| Supporting material | Where is the relevant agreement or decision kept, and who may see it? |
| System handoffs | Which approved value was sent to another system, and was it accepted? |
Required time and wages records under the Fair Work Act 2009 (Cth) and Fair Work Regulations 2009 (Cth) cover general employment details, pay, specified hours of work, leave, superannuation contributions and the end of employment. Other details depend on circumstances and applicable arrangements; map them with the payroll or workplace specialist. The HR platform need not hold every item if another controlled system retains it and the employer can retrieve it.
Make required record content retrievable, not merely present in a profile. Pay records may need gross and net amounts, deductions and monetary allowances; superannuation records may need contribution amount, pay period, payment date and fund name.
Australian Record-Keeping Requirements at a Glance
- Language requirement
- English
- Access rights under Privacy Act
- Employees can inspect & copy records
- Record format requirement
- Legible and readily accessible
Make one value authoritative
A field copied into several tools can become inconsistent. Name the authoritative source for each value and define how other systems receive changes. For example, HR may own an approved change to ordinary hours while payroll owns the resulting pay calculation. A shared employee identifier and effective date help connect the records; a successful transfer alone does not establish correct pay.
Separate a proposed change from an approved one. Record who requested it, who decided, when it took effect and when it was entered; those dates can differ. If a change arrives after a pay period has been processed, payroll must identify the affected period and review any correction needed.
Do not silently replace an earlier value. Keep enough history to show what applied at the relevant time and why a correction was made. Under the Fair Work Act 2009 (Cth) and Fair Work Regulations 2009 (Cth), time and wages records must be kept for seven years, be legible and in English, and be readily accessible to a Fair Work Inspector. The Fair Work Ombudsman provides record-keeping guidance for employers.
They must not be false or misleading; changes to those records are for correcting errors. An audit log alone does not prove that the required record has been retained.
HR System vs Payroll System Ownership of Key Data Fields
- Ordinary hours of work
- HR system (authoritative)
- Pay calculation
- Payroll system (authoritative)
- Employee ID
- Shared across systems
- Superannuation fund details
- HR system (authoritative)
Control access and retrieval
An employee, manager, HR officer and payroll reviewer may need different parts of a record. Set access according to each person’s work. Check reports, exports, notifications and supplier support access as well as the main profile screen. A manager who needs a commencement date may have no reason to see an unrelated supporting document.
Check whether s 7B(3) of the Privacy Act 1988 (Cth) applies; the Office of the Australian Information Commissioner (OAIC) provides guidance on the employee-records exemption. The exemption covers acts or practices directly related to a current or former employment relationship and an employee record held by the organisation about that person, and displaces Australian Privacy Principles (APPs) requirements for that handling. It does not cover contractors or job applicants.
Consider other privacy obligations for the records and information flows you manage.
The Fair Work Act 2009 (Cth) gives employees and former employees access to their own employee records, including the right to inspect and take copies of certain information such as pay and leave records. Keep a process for identifying the relevant records and providing access securely.
Plan a retrieval process that works after a system or administrator changes. A protected sample record can help check whether the relevant material can still be found.
Set retention and disposal rules
A retention policy can make ownership and retrieval practical across digital and paper records. Keep a schedule that identifies record types and retention periods, plus procedures stating who is responsible, where records are held, how access is controlled and how disposal is carried out.
For example, a schedule entry could read: time and wages records — seven years under Fair Work rules. Record the owner, system location and disposal responsibility alongside each entry.
Map the records and systems before setting the schedule, including records held by suppliers. Identify the legal and business retention periods that apply to each type rather than applying one period to every item. The schedule can also state how records are archived and how a legal hold affects normal disposal.
Align retention procedures with privacy and security documents, configure systems to support them and train the people who handle records. Review the policy regularly and when circumstances change; checks and audits can reveal records stored in unexpected places or procedures staff cannot follow.
Under the Fair Work Act 2009 (Cth) and Fair Work Regulations 2009 (Cth), when employment transfers as part of a business sale, the former employer must hand over records for transferring employees. The new employer must request records for people who become employees within three months of the sale, so transfer responsibilities belong in the retrieval process.
Keep the record dependable
Assign an owner for each change type and a route for resolving disagreements. Review records when someone starts, changes arrangements, moves manager or leaves. An exception report can flag missing identifiers, conflicting active arrangements and changes that did not reach their recipient. Investigate those flags before changing the record.
Before a migration, agree the target structure, check effective dates and resolve suspected duplicate profiles. Retain the source-to-destination mapping and unresolved decisions. After import, compare a varied sample with the source records and downstream outputs.
An authorised reviewer should be able to identify the employee, find the value that applied on a given date, see the decision behind a change and retrieve the required record. Where that is difficult, clarify ownership or repair the data before relying on the profile.
Include retention checks in routine record reviews, not only in system migrations. Confirm the schedule is followed across systems and suppliers, and that records due for secure disposal are not kept indefinitely without a legal or business reason.
In this guide
- Choosing a reliable employee record structureStructure employee records around stable identity, employment periods and dated changes so earlier arrangements remain explainable.
- Checking effective dates for employment changesReview approval, effective, entry and receiving dates so employment changes apply to the intended period and system.
- Finding duplicate employee profiles before migrationIdentify and review possible duplicate employee profiles before migration while preserving distinct people and employment history.
