- Seven groups of data for the HR record
- Why duplicate entry causes missed updates
- Which copy should be the original
- Whether to merge into one product
The short answer
HR records and payroll do not have to sit inside one product, but there has to be one agreed place where employee data lives. The goal is to eliminate the situation where an address exists only inside payroll software and an employment type exists only in an HR spreadsheet. Deciding which copy is the original matters more than deciding whether to merge the tools.
Putting the HR record at the centre
An HR record holds the facts about one person — one row, or one file, per employee. Put that at the centre and let attendance and payroll branch off it. The information at the centre falls into roughly seven groups.
- Identity: name, date of birth, gender, contact details
- Address: current address, registered address, commuting route
- Employment: start date, employment type, department, role, contract term, leaving date
- Pay terms: base salary or hourly rate, allowances, payment method, cut-off and pay dates
- Social insurance: which schemes apply, enrolment dates, remuneration basis, dependants
- Attendance setup: work pattern, contracted hours, paid-leave grant date
- Payroll results: monthly gross and deductions
Items one to six are the person's settings; item seven is the result that accumulates month after month. Because changing a setting changes every later result, limiting who can edit the settings side is the core of managing this well.
Why duplicate entry happens
Most companies buy payroll software first. It comes with an employee master, so names, addresses, pay figures and insurance details go in there. Later, HR builds a spreadsheet for start dates, departments and contract terms. At that moment, names and addresses exist in two places.
Add separate attendance tracking and there is a third. The cost is not the typing — it appears when something changes. One change-of-address form arrives and there are three places to update. Update one, feel finished, and two stay stale. A stale address affects commuting allowances and insurance paperwork.
Leavers are the other common failure. Payroll processes the departure, but the HR spreadsheet still shows the person as active and their attendance account still works. Beyond headcounts that no longer reconcile, this leaves unused accounts alive, which is a problem of a different kind.
Which copy is the original?
Work through it in this order.
| Data | Best home for the original | Why |
|---|---|---|
| Name, address, date of birth | HR record | Used for paperwork beyond payroll |
| Employment type, department, start date | HR record | Set by an HR decision |
| Base pay and allowances | HR record decides / payroll calculates | Separate the decision from the calculation |
| Social insurance status | HR record | It is where the paperwork starts |
| Monthly payment amounts | Payroll software | The calculation belongs with the calculator |
Pay is the interesting case. Deciding the figure is an HR act; working out what that figure produces for a given month is what payroll software does. Keeping the two apart means that at the next raise you can explain from the HR record exactly which month the new terms took effect.
Does it have to be one product?
Merging means entering data once. Not merging means it is easier to take HR data with you if you change payroll software, and easier to separate who can see what. Pay figures are visible to only a few people in most companies, so some prefer an arrangement where the whole administration team can see the HR record while only one person can open payroll.
Decide by how often things change. A handful of joiners and leavers a year and one annual pay review works fine with separate tools. In industries with constant turnover, keeping it in one place gains much more.
Japan's Ministry of Health, Labour and Welfare sets out conditions for producing and keeping employment-related documents on a computer: that they contain the legally required items and can be displayed on screen and printed, that the required details can be produced and submitted immediately, for example during a labour inspection, that they cannot be erased by mistake, and that they can be kept over a long period. If you hold your records electronically, check that your own process satisfies all four.
No product can be described as "install this and your HR administration is in order". A tool provides somewhere to put the data; the rule about who edits it is set by the company.
What this looks like in practice
Take a twelve-person design office where, in April, one employee marries and changes both surname and address. Without a central record, administration edits the payroll master, renames the attendance account, updates the internal contact list, and corrects the details used for ordering business cards. Four places. Miss one and that system keeps running on the old name.
With a central record, one row is edited and everything that consumes it — attendance, payroll, the contact list — refers back to that row. Even when nothing is automated, simply fixing the order ("edit the record first, copy from it afterwards") cuts the number of misses. Agree the order first; automate the handoff later.
Limits
Centralising also tends to widen the circle of people who can see everything. You probably do not want pay terms and dependant details visible to the whole team, so check during selection whether visibility can be set per field.
Which statutory records must be kept, and for how long, can also change. Check detailed requirements in the ministry's own guidance — this article does not cover them.
Summary
- Decide where the original employee data lives before deciding whether to merge tools.
- Collect identity, address, employment, pay terms, insurance and attendance setup in the HR record.
- Leave calculated results, such as monthly payments, with payroll.
- The harm of duplicate entry is missed updates and lingering leavers, not the typing.
- Holding records electronically means checking display and printing, immediate submission, protection from accidental erasure and long-term retention in your own process.
APOUL KINTAI