PH-compliant payroll that calculates every peso — and books the journal
Run Philippine payroll end-to-end — SSS, PhilHealth, Pag-IBIG, and BIR withholding from live statutory tables, posted straight to your GL.
Everything Payroll & HR handles
A real PH statutory engine
SSS, PhilHealth, Pag-IBIG, and BIR withholding are computed against effective-dated tables in the database — the 2024 authority values, not constants hardcoded in code.
Governed rate changes
Statutory rates are staged, approved by a second person, and published with effective dates and an audit log, so no payroll run ever splits across two rate versions.
Runs that post a balanced journal
Posting an approved run writes a real multi-line entry — salary and employer contributions on the debit side, each statutory deduction and salaries payable on the credit — balance-checked and marked posted.
Segregation of duties across the run
Create, calculate, approve, post, and disburse are distinct actions with row-locking against double-posting; the poster and disburser must differ from the creator and approver.
Employees, compensation, and org
A full directory with hires, transfers, and terminations, versioned compensation with pending-change approval, and departments, positions, and an org chart.
Attendance, timesheets, and leave
Clock in and out with overtime and late tracking, timesheets routed through approval with a double-pay guard, and leave types, balances, requests, and an approver inbox.
From action to ledger, in four steps
- 1Set up
Add employees, assign compensation and shifts, and record and approve attendance.
- 2Calculate
The engine snapshots the current statutory tables once, then computes gross, each contribution, withholding, and net pay per employee.
- 3Approve & post
A second user approves and a third posts; the run becomes one balanced, period-guarded journal and payslips capture a rate snapshot.
- 4Disburse
Mark the run disbursed — employee rows and the covered timesheets flip to paid and settled.
Real screens, real data
PH statutory coverage that’s current and governed
SSS, PhilHealth, Pag-IBIG, and BIR withholding are seeded with 2024 authority values and governed through versioned, effective-dated tables — so every run computes to the rules in force, and every payslip retains a forensic snapshot of the rates used.
What you get
- Statutory contributions and withholding computed to PH rules on every run.
- Every run lands in the ledger as a balanced, auditable journal automatically.
- Rate updates are controlled and traceable: two-person approval, effective dates, change log.
- Built-in segregation of duties plus double-post and double-pay guards.
- Ask Sebee about pay and leave in plain language, on a PII-tiered read surface.
Frequently asked questions
Which Philippine statutory contributions does LedgerQ compute?
SSS, PhilHealth, Pag-IBIG, and BIR withholding, computed against effective-dated tables in the database — seeded with the 2024 authority values, not constants hardcoded in code.
Does a payroll run post to the GL?
Yes. Posting an approved run writes a real multi-line entry — salary and employer contributions on the debit side, each statutory deduction and salaries payable on the credit — balance-checked and marked posted.
What controls are there over a payroll run?
Create, calculate, approve, post, and disburse are distinct actions with row-locking against double-posting; the poster and disburser must differ from the creator and approver, with a double-pay guard on timesheets.
How are statutory rate changes governed?
Rates are staged, approved by a second person, and published with effective dates and an audit log, so no payroll run ever splits across two rate versions — and every payslip retains a snapshot of the rates used.