Statutory payroll, and attendance you can trust.
SSS, PhilHealth, Pag-IBIG, withholding, 13th month and final pay — on current tables, held centrally, with a register that ties to the journal by construction.
| Gross pay | basic, OT, night diff | ₱4,182,400 | |
| SSS | employee share | ₱186,200 | current table |
| PhilHealth | 5% · shared | ₱104,560 | current table |
| Pag-IBIG | capped | ₱56,800 | current table |
| Withholding tax | TRAIN table | ₱308,240 | current table |
| Net pay | to 3 banks | ₱3,526,600 | balanced |
Philippine payroll with statutory contributions, a parallel run against your previous books, and attendance from your biometric readers, checked before anyone is paid.
What it actually does.
The register and the journal are the same number
Not two numbers that are reconciled afterwards. Payroll posts once, and the register is a reading of that posting rather than a separate document that can drift.
- Current SSS, PhilHealth, Pag-IBIG and withholding tables, updated centrally.
- 13th month, final pay and separation computed rather than worked out by hand.
- A run with blockers will not produce payslips — the exceptions are cleared first.
Split to the site the hours were actually worked at, which for 27 of these 142 people is not the branch they are rostered to.
People who move are handled
Somebody covering another branch this cutoff is paid against where they actually worked, not where they are rostered. If a site’s labor cost looks odd, that is usually why — and it is correct.
- Attendance from your biometric readers at every branch, checked against the roster each cutoff.
- Unworked days are visible, not invisible — a salary paid by the day is a real risk.
- Loans and deductions with a balance, so nothing amortises to zero silently.
Checked against a real payroll register supplied by the client, not against itself.
A parallel run you can actually trust
Against whatever kept payroll before this, line by line, until the difference is explained rather than tolerated. Going live on a payroll you have not proved is how an ERP loses a client in month one.
- Every difference listed per employee, per component.
- Rate history kept, so a change is dated and attributable.
- Labor against sales by hour, so cover and cost can be judged together.
The ones people ask about this.
Do you update the statutory tables?
Yes, centrally, for every client at once. A revision reaches you the day it lands and you do not pay for it.
Can it read our biometric devices?
Yes. Today each reader’s export is imported and checked against the roster before payroll runs. A direct cloud connection for supported readers is being built, so punches arrive without anybody exporting them.
How long does a parallel run take?
One cutoff, usually. We run both and work the differences until each one has a reason.
What about staff who work at more than one branch?
They are paid against where they actually worked, and the cost lands on that branch.
Nothing here is a separate product.
Time & attendance
From your biometric readers, checked before anyone is paid
See the pageAccounting
Multi-entity double-entry, consolidation, intercompany
See the pageReporting & analytics
190 reports, each opening the rows behind it
See the pageSecurity & access
Enforced in the database, down to the action
See the pageSee it on your own figures.
Bring one ordinary day from your business and we will run it through in front of you, on your own items and your own prices.