Employee Records: A Single Source of Truth for HR

Ask three people in the same company for one employee's hire date and you can easily get three answers. HR has a spreadsheet, the payroll officer keeps a working file they trust because it is the one they use every cutoff, and the 201 file in the cabinet holds the signed contract nobody has opened since onboarding. No one is careless here. The record simply exists in three places, and copies drift. Everything HR does afterwards inherits that drift.

What belongs in the employee master record

A master record is the one authoritative description of a person's employment. It carries identity details and the government numbers that follow the employee everywhere — SSS, PhilHealth, Pag-IBIG and TIN — plus the employment terms that everything downstream computes against: date hired, employment status, position, department, pay basis, assigned schedule and leave entitlements.

It helps to separate the fields that almost never change from the ones that change on a known event. Date of birth and government numbers are captured once and corrected only when they were wrong. Position, status, schedule and rate change on promotion, regularisation, transfer or a salary adjustment — each of which has a date attached, and that date matters as much as the new value.

In ERPat, the Human Resource module is that system of record. Profiles, schedules, attendance, leaves and holidays sit together rather than in separate files maintained by separate people, which is what makes it possible to answer "what was true for this employee in March?" without reconstructing it from memory.

What happens when the same person exists in three files

The cost of duplicate records is rarely dramatic. It shows up as small corrections that arrive after the fact, and each one costs someone an afternoon.

Consider a hire date that is off by a few weeks. Under Article 95 of the Labor Code, an employee who has rendered at least one year of service is entitled to five days of paid service incentive leave, subject to the exemptions in the same article. If the date in the leave tracker disagrees with the date in the 201 file, the entitlement opens on the wrong day and someone has to argue about it later. The same field drives seniority questions, probationary end dates and the pro-rating of 13th month pay, which Presidential Decree No. 851 requires employers to pay not later than December 24 each year and defines as one-twelfth of the basic salary earned within the calendar year.

Identity fields carry the same weight. The certificate of compensation payment and tax withheld that every employer must furnish each employee on or before January 31 of the following year is only as correct as the name and TIN the record holds. Fixing that in January, for dozens of employees at once, is the most expensive possible time to find out.

Schedules, attendance and leave read from the same profile

Attendance data means very little on its own. A time record only becomes late, undertime or overtime once you know which schedule the employee was assigned to on that day, and whether that day was a holiday. That is why keeping schedules, attendance, leaves and holidays with the profile — rather than in a separate timekeeping file — removes a whole class of disputes: the schedule that was used to evaluate the day is the schedule the record says applied.

Leave works the same way. Eligibility is a question about the record, not about the leave form. Service incentive leave depends on length of service. The seven working days of paid parental leave granted to solo parent employees under Republic Act No. 11861, which lapsed into law in June of this year, depends on the employee having rendered at least six months of service and on their status being documented. Maternity leave under Republic Act No. 11210 depends on facts that were recorded well before the application arrived.

Work arrangements now belong in the record too. Under the revised implementing rules of the Telecommuting Act issued by DOLE in September, work performed in an alternative workplace is treated as work performed in the regular workplace and all time on duty counts as hours worked — so who is on a telecommuting arrangement, and since when, is an employment fact, not an informal understanding.

Documents that live with the record, not beside it

Every employment fact has paper behind it: the signed contract, the government IDs, the regularisation letter, the salary adjustment memo, the acknowledged company policies. When those live in a shared drive organised by whoever created the folder, the record and its evidence slowly separate.

The Documents module keeps that storage centralised with role-based access controls and version tracking. Version tracking is the part people underestimate. When a contract has been amended twice, "which version is current" is a real question with a real answer, and a filename ending in -final-v2 is not it. Role-based access is the other half: employee files contain sensitive personal information, and under National Privacy Commission Circular No. 16-03 a personal information controller must notify the Commission within 72 hours of knowing, or reasonably believing, that a personal data breach has occurred. A folder everyone in the office can open is difficult to secure and even harder to account for afterwards.

Retention also needs a home. The revised telecommuting rules, for instance, require employers to keep the documents proving voluntary adoption of the arrangement for at least three years.

Keeping the record accurate through the employment lifecycle

A master record is not something you set up once. It is maintained across a sequence of events — hiring, regularisation, transfer, promotion, rate change, leave of absence, return, resignation — and the discipline that makes it trustworthy is simple: each event is entered once, in the record, with the date it took effect.

Offboarding deserves particular attention because it is when accuracy stops being recoverable. Final pay, the release of the certificate of compensation payment and tax withheld on the day the last payment of compensation is made, and the clearance trail all depend on a record that is complete on the employee's last day, not reconstructed a month later from whatever people still remember.

Where to start

You do not need a full data cleanup before any of this pays off. Start with the handful of fields that payroll and compliance actually depend on — date hired, employment status, pay basis, schedule, government numbers — and reconcile those against the signed documents rather than against another spreadsheet. Then retire the side copies, because a second file that is still being updated is a second source of truth by definition. Once the profile is the place everyone looks, the questions that used to take an afternoon to settle take a minute, and the corrections stop arriving in January.