Payroll-ready employee data without duplicate people records

One employee record that two departments depend on

Payroll-ready employee data comes from a single people record that HR maintains and finance trusts, with a clear owner for every field payroll uses. Duplicates appear when finance keeps its own spreadsheet of bank accounts and salaries because the HR record is incomplete, and the cure is to close those gaps rather than tolerate a second list.

The second list always starts for a sensible reason. A payroll officer could not find a tax reference in the HR file, so they kept one. A new bank account was emailed straight to payroll, so it went into the spreadsheet. A year later the two sources disagree on dozens of small points and nobody knows which one is right.

Field ownership between HR and finance

Ownership answers one question per field: who may change it, and who must be told. Agree it field by field.

• Legal name, identity or passport number and date of birth: owned by HR and verified against documents at onboarding
• Start date, job grade, department and cost centre: owned by HR, with finance told of every cost centre change
• Basic salary and fixed allowances: changed by HR on an approved letter, reviewed by finance before the next pay run
• Bank name and account number: submitted by the employee, recorded by HR, checked by finance for a matching account name
• EPF, SOCSO, EIS and income tax reference numbers: recorded by HR at onboarding, confirmed by finance against statutory submissions
• Overtime, variable pay and claims for the period: prepared by the approving department and checked by finance
• Last working day and exit type: owned by HR and sent to finance as soon as the exit is confirmed

Changes that need approval before they touch payroll

Finance should be able to read every one of these fields and change none of the HR-owned ones directly. When finance spots an error, it raises it with HR, and HR corrects the source.

Salary, allowance and bank changes are where payroll fraud and payroll mistakes both begin. Require an approval for each and keep the evidence: a signed increment letter, a bank statement header or a form completed by the employee.

Bank account changes deserve extra caution. A request to switch accounts that arrives by email, especially close to pay day, should be confirmed with the employee through a separate channel before HR updates anything. That single habit stops a common payment diversion scam.

Set a cut-off for each payroll period after which changes roll into the next one, and publish it so managers stop sending late adjustments.

The reconciliation HR and finance run before every pay run

Before payroll is processed, HR and finance compare a handful of lists: new joiners in the period, leavers in the period, approved salary changes, cost centre transfers and recorded unpaid leave. Each list from HR should match what finance is about to pay.

Differences are the point of the exercise. Investigate each one, correct the HR record if it is the source, and note the reason. Over time the differences shrink and the check becomes a quick sign-off.

Keep evidence of each reconciliation. Auditors and your accountant will ask how you know the payroll matches the people on the books, and a dated record answers that far better than confidence.

Retiring the duplicate list you already have

If finance already runs a parallel spreadsheet, do not delete it on day one. Compare it field by field with the HR record, resolve each mismatch with evidence, and decide which source is correct. Then freeze the spreadsheet, keep it for reference, and route every future change through HR.

Expect some resistance from whoever maintains the spreadsheet. It is often the most accurate record in the company, built by someone careful. Ask that person to lead the comparison, because their knowledge of the exceptions is what makes the cleanup work.

Payroll data includes identity numbers and bank details, so limit who can see the full record during and after the cleanup, and check your handling against PDPA obligations with your adviser.

Holding people records and finance records in their own places

When people records, approvals and exits sit in BukuHR and bills, payments and period reporting sit in BukuCloud, each team works from its own system and the ownership model above decides who changes what. How payroll-relevant fields should travel between the two, whether by export, a review step or an integration, is worked out with Fasttrade against your payroll process and your accountant's needs.

Frequently asked questions