Contributions
SSS, PhilHealth, Pag-IBIG
Contribution tables built in, employee and employer share, computed every cutoff and carried straight through to the monthly remittance.
Talaan · HR & payroll for the Philippines
Payroll, timekeeping and HR in one system. SSS, PhilHealth, Pag-IBIG and withholding computed every cutoff, and 13th month per PD 851 from what each employee actually earned.
| Employee | Basic | SSS | PhilHealth | Pag-IBIG | W-Tax | Net pay |
|---|---|---|---|---|---|---|
| Alonzo, M. | 12,500.00 | 625.00 | 312.50 | 50.00 | 520.83 | 10,991.67 |
| Bautista, R. | 9,000.00 | 450.00 | 225.00 | 50.00 | — | 8,275.00 |
| Carpio, J. | 18,750.00 | 900.00 | 468.75 | 50.00 | 1,437.50 | 15,893.75 |
| Dimaculangan, A. | 15,000.00 | 750.00 | 375.00 | 50.00 | 895.83 | 12,929.17 |
| Estrella, K. | 11,250.00 | 562.50 | 281.25 | 50.00 | 364.58 | 9,991.67 |
| 5 employees | 66,500.00 | 3,287.50 | 1,662.50 | 250.00 | 3,218.74 | 58,081.26 |
Deductions in redNet in greenFigures illustrative
01
Computed for the Philippines
Not a global payroll engine with a Philippine setting bolted to the side. The statutory tables, the premiums and the deadlines are the system's first-class citizens.
Contributions
Contribution tables built in, employee and employer share, computed every cutoff and carried straight through to the monthly remittance.
Withholding
Withholding computed per period against the graduated table, with the taxable and non-taxable split kept on every payslip line.
PD 851
Total basic salary actually earned in the calendar year ÷ 12, taken from released runs. A mid-year hire pro-rates itself; somebody who left in September still gets their share.
Labor Code
Regular holiday worked at 200%, special non-working at 130%, rest day at 130%, and 10% night differential for hours inside 22:00–06:00.
Leave
Credits accrue monthly against each contract's entitlement, with conversion to cash and a trail that says where every credit came from.
Separation
Clearance, final pay and the employee's own access all move together. The day a separation completes, the login stops working.
02
What's inside
01
Employees, contracts, government numbers, dependents, education and work history. One record per person, with every change kept.
02
Facial clock-in in the browser, published schedules, holidays, overtime filings and daily time records that close themselves each night.
03
Filing, approval, monthly accrual and conversion. An approved leave writes the days it covers, so payroll sees them.
04
Semi-monthly or monthly runs, statutory deductions, premiums, allowances and payslips, reviewable and approvable before a peso moves.
05
Amortisation schedules built at filing and collected automatically on the cutoffs you nominate, with the balance kept honest.
06
Violations, notice to explain, notice of decision and the sanction that follows, with suspensions that start and end by themselves.
07
Job openings, applicants, interview schedules and offers, with the hiring decision gated by approval and kept on the applicant's own record.
08
The employee's own payslips, leave balance, filings and clearance, so HR stops being a lookup service.
03
What you actually get
One employee, one fortnight, four screens. The overtime on her time record is what produces the overtime line on her payslip, and the leave she filed on 10 June is the day the ledger spends. Do the arithmetic yourself; that is why it is here.
01
One record per person, with the contract in force, the government numbers and every change kept. Not four spreadsheets keyed to a surname.
Every change keptGovernment numbers illustrative
02
Facial clock-in in the browser, against the schedule they were actually published. Nobody scheduled who left no record survives the night unmarked, and a worked regular holiday is recognised as one.
| Date | In | Out | Late | OT |
|---|---|---|---|---|
| 08 JunMonPresent | 08:05 | 17:00 | 5m | — |
| 09 JunTuePresent | 07:58 | 19:30 | — | 2.5h |
| 10 JunWedOn leave | — | — | — | — |
| 11 JunThuPresent | 08:00 | 17:00 | — | — |
| 12 JunFriHoliday | 08:00 | 17:00 | — | — |
| 13 JunSatRest day | — | — | — | — |
| 14 JunSunRest day | — | — | — | — |
| 4 days worked · 1 on leave | 5m | 2.5h | ||
Absences booked overnightApproved leave writes its own day
03
What the employee receives, and what they will ask you about. A premium that does not apply is not printed as zero, so nothing on it needs explaining.
Premiums computed from the record aboveFigures illustrative
04
A balance is a ledger, not a cell somebody edits. Credits accrue monthly against the contract's entitlement, and each line says what moved it.
| Particular | Days | Balance |
|---|---|---|
| Opening balance carried forward01 Jan 2026 | +6.25 | 6.25 |
| Accrual, Jan to Mar31 Mar 2026 | +3.75 | 10 |
| Vacation leave, 22 Apr22 Apr 2026 | -1 | 9 |
| Accrual, April30 Apr 2026 | +1.25 | 10.25 |
| Accrual, May31 May 2026 | +1.25 | 11.5 |
| Vacation leave, 10 Jun10 Jun 2026 | -1 | 10.5 |
| Balance as at 15 Jun 2026 | 10.5 | |
Accrues monthlyEvery credit says where it came from
04
A cutoff, end to end
Most of what goes wrong in payroll goes wrong quietly, days before anyone runs it. Talaan closes each day as it happens.
Step 01
By face in the browser, or keyed by HR, against the schedule they were actually published.
Step 02
Anyone scheduled who left no record is marked absent overnight, not discovered on payday.
Step 03
Overtime, leave and corrections go through approval, and approved leave writes its own days.
Step 04
Basic, premiums, allowances, statutory deductions and loan instalments, per employee.
Step 05
Review, approve, release. Payslips to the employees, remittance schedules to the agencies.
05
Before you hand it over
Payroll is every salary, every government number and every address you hold. These are the mechanisms, not adjectives, and the list of what the system will not do for you is on the same page as the rest.
01
One append-only entry per create, edit and delete, holding what changed, from what, to what, by whom. Passwords and keys are redacted by shape, so a secret cannot reach the trail even by accident.
02
Visibility is set per role: everything, a unit and the units under it, or only their own. A unit is a tree and it resolves at read time, so moving somebody moves what they can see. Somebody with no unit sees nothing rather than everything.
03
Approvals are configured per action, and a decision and what it triggers are one transaction. If the thing it triggers fails, the approval is rolled back with it rather than left recorded against work that never happened.
04
Password rules, two-factor, lockout, idle and absolute session limits, and an optional list of countries an account may be used from, set per role and merged strictest-wins. The breached-password list is held offline; no password or fragment of one is ever sent to a third party.
05
The day a separation completes, the login is revoked and the sessions already open are ended. It is not a task on somebody's list.
06
A full snapshot of your database on a schedule, with retention that never removes the newest. Whether a good backup exists is answered by looking at the backups, not by reading a status column that says it should be there.
05.1
What it does not do
Clock-in is by face in the browser, or keyed by HR against a published schedule. Talaan does not ingest the logs of a fingerprint or RFID device you already own.
Recruitment carries an applicant through openings, interviews and the offer, and marking them hired records that decision. Opening their 201 file is still a deliberate act.
There is no recycle bin and no restore, by design. What protects you instead is that nothing can be deleted while another record still points at it, and the deletion itself is on the trail.
SSS, PhilHealth, Pag-IBIG, BIR withholding, PD 851 and the Labor Code premiums. If you need to pay staff in another country, this is the wrong system and we will say so on the call.
06
Start here
The fastest way to judge a payroll system is to give it a fortnight you already know the answer to. Send us one and we will run it live against your headcount, your schedules and your deductions.