- Why triple registration is the real problem
- Five situations where things break
- How mismatched effective dates skew figures
- What to agree before integrating
The short answer
Having attendance, HR and payroll in separate systems is not the problem. The problem is registering the same employee three times and then having to change three copies whenever something moves. Without an agreed order and an owner, one of the copies stays stale. Start by deciding which place gets updated first.
What actually happens when someone joins
Follow one new hire through a typical company.
- HR: name, address, date of birth, start date, department and employment type go into a list
- Attendance: an account is created from the name and employee number, with a work pattern and contracted hours
- Payroll: name, address, base pay, dependants and insurance details are entered
The name has now been typed three times, the address twice, the employee number twice. Even if one hire takes only fifteen minutes, ten hires a year means thirty acts of re-typing. Thirty acts of re-typing will eventually produce a mistake.
The awkward part is that the mistake does not surface straight away. One wrong character in an address does not stop payroll from running. It surfaces when year-end paperwork comes back, or when someone notices the commuting route does not match. Because it emerges months later, the work starts with finding where the error was introduced.
Five situations
1. Typos
Three separate entries give you no way to decide which spelling is right. A name may be written one way in the HR list, another in payroll, and in katakana in attendance. All three are the same person, but nothing can match them automatically except the employee number. Without that match, someone checks by eye every time a report is produced.
2. Leavers who are never removed
Payroll is usually the last system to release a leaver, because the final payment has to go out. Delete the HR row first and payroll now holds someone HR has never heard of. Meanwhile, nobody deletes the attendance account at all. A live account that nobody uses skews the headcount and, more importantly, leaves a way into company systems open.
3. Transfers
Five people move in an April reorganisation. HR updates its list on the effective date, while attendance changes departments at month end because that is what suits the reporting cycle. Overtime by department for that month will not reconcile between the two. Neither figure is wrong — they use different effective dates — but someone explains the discrepancy every single time.
4. Pay changes
Raises are easy to apply to the wrong month. Whether the new figure applies from the April period paid in May, or from the May period, changes the amount. The classic mismatch is an approval document that says "revised as of 1 April" and a payroll entry made "from the May payment". Hold the effective month in the HR record and copy it to payroll from there, and there is only one place to check.
5. Access rights
Three separate systems mean three separate permission settings. When an administrator moves to another team, their access to the HR shared folder gets removed, but the payroll login survives. Reviewing rights only works when there is a single list of who can open what.
What this looks like in practice
A company of twenty-five people has one joiner, one leaver and two transfers in September. There are three places to touch: the HR list, attendance, payroll. The work is three registrations for the joiner, three steps for the leaver, and two places each for the two transfers (attendance and HR), four in all. Ten updates in total.
Miss one of those ten and the month-end figures do not line up. To find the cause, the administrator opens three screens side by side and compares twenty-five rows by eye. That reconciliation grows with the company: twice the people, twice the rows to check.
Counted as "time spent typing", the cost of fragmentation looks small. Counted as time spent checking and hunting for causes, it looks large. Measure month-end reconciliation time, not data entry time.
How to fix it
Do not try to integrate everything at once. Start by fixing the order.
- Choose one home for the original employee data — usually the HR record
- Write down the update order for joining, leaving, transferring and pay changes
- Name one person who performs the final check for each of those four processes
- Then automate the handoffs, such as CSV exchange, where they already fit
Skip step three and the order will be agreed but not followed. The checker does not have to be the same person for all four, but each process needs exactly one.
Making integration the goal turns this into a project of several months. The goal is to make each change happen once; simply agreeing the order and the owner already removes most of the misses.
Limits
Connecting systems does not make the numbers agree by itself. If departments interpret effective dates differently, the figures will still differ after integration. Decide how transfer dates and pay revision dates are treated before you connect anything.
For attendance records, Japan's Ministry of Health, Labour and Welfare sets out how start and end times should be confirmed and recorded. Retention periods and the range of documents covered can change, so check the current requirements in the ministry's own guidance. Kintai, APOUL's attendance product, is planned for release and not yet available.
Summary
- The issue is the triple registration, not the separation itself.
- Typos surface months later, so the real cost is the search for the cause.
- Payroll releases leavers last, and attendance accounts tend to survive entirely.
- Transfers and pay changes break reconciliation through mismatched effective dates.
- Agree the update order and the final checker before attempting integration.
APOUL KINTAI