EventDiscover the Future of Automated HR Management with WORKSPHR — A free seminar on turning manual HR work into connected, automated processes. Reserve a seat

HR software built on one employee record and 201 file.

Government numbers, contracts, org chart and contact details all live on one encrypted record. Update it once, and every other module reads the same information.

The Philippine 201 file, handled properly.

A 201 file is a legal record before it is a convenience. It has to hold a TIN without exposing it to every user, and it has to be produced in full when a labor inspector asks.

WORKSPHR keeps government numbers, employment history, position, department, branch, contact details and emergency contacts on a single record that every other module reads.

  • SSS, PhilHealth, Pag-IBIG and TIN stored once
  • Employment history with effective dates
  • Position, department, branch and client account
  • Contact and emergency contact details

How the process works.

Step
1

Import your records

Bring employees, departments and positions across from your current system. WORKSPHR validates the file before it writes anything.

Step
2

Set access by role

Assign roles once. Payroll and HR Admin see the full record, managers see their team, and employees see their own. Government numbers are masked by default.

Step
3

Every module reads the same record

Payroll, leave, attendance, documents and the org chart all draw from the same record, so a transfer or promotion is one update, not several.

One record, not three that disagree.

The directory, the org chart and the document vault show the same data three ways. Storing it once is what turns an employee transfer into a single update instead of three.

Sensitive numbers stay useful without being exposed.

A TIN has to be readable by payroll and unreadable to almost everyone else, which is why storing it in a shared document fails a privacy review. Holding it on the record with field-level masking lets statutory reporting draw on it while keeping it out of view for roles that have no reason to see it.

Learn more about government compliance

Fields your industry needs, behaving like the rest.

A seat ID kept in a notes field cannot be filtered, reported on or used to build a roster. Defined as a custom field it becomes part of the record, which is the difference between recording something and being able to act on it.

An audit trail that answers who saw what.

The question after an incident is rarely who edited a record, it is who looked at one. Every view, download and export is written with a timestamp, user and IP address, and the log itself exports for inspection alongside the records.

A migration that cannot half-succeed.

The risk in moving systems is not a failed import, it is a partial one that nobody notices until payroll runs. Every import validates as a dry run first and returns failing rows for correction, so live records are only written once the whole file is sound.

The employee record, the directory, role-based access and the audit trail are included on every plan. The number of custom fields scales by plan.

Book a 30-min demo
  • What does an employee record hold?
    Government numbers (SSS, PhilHealth, Pag-IBIG, TIN), employment history with effective dates, position, department, branch and client account, contact and emergency contact details, plus any custom fields your organization defines.
  • Who can view an employee's record?
    Access is role-based down to field level. Payroll and HR Admin see the complete record, line managers see their team's non-salary data, and employees see their own. SSS and TIN are masked for every other role.
  • Can we add fields specific to our industry?
    Yes. Custom fields sit on the record and work like standard fields, so they are searchable, filterable, reportable and included in exports. BPO teams commonly add seat ID, retail adds branch code, and manufacturing adds shift assignment.
  • Is every access to a record logged?
    Yes. WORKSPHR writes each view, download and export to an immutable audit trail with a timestamp, user and IP address, and you can export that log for inspection alongside the records themselves.
  • How do we migrate from our current system?
    We import employees, departments and positions from Excel, Google Sheets, Sprout, ZipHR or another HRIS. Every import runs as a dry-run validation first, with failing rows exported for correction, so nothing partial reaches your live records.
  • Does the directory update when someone transfers?
    Yes, immediately. WORKSPHR generates the directory and the org chart from the record itself, so a transfer or promotion is one update rather than three. Learn more about the org chart →

See your own records brought across.

Book 30 minutes with our Pampanga-based team. Send a sample of your current records and we will show you how they look once consolidated.