Semi-monthly Philippine payroll for accounting firms
Payroll for the firms that run payroll for everyone else.
One subscription, any number of client companies, each an isolated payroll. Every peso is computed from the timesheet. SSS, PhilHealth, Pag-IBIG and BIR withholding are built in and dated, so recomputing an old cutoff uses that year’s tables.
No email inbox needed for staff or employees. Temporary passwords are handed over directly.
Payslip
June 1–15 · 10 of 11 days worked
EMP-011 · monthly-rated rider
Basic pay
₱11,990 ÷ 2
₱5,995.00
Meal allowance
10 days × ₱50
₱500.00
Motorcycle rental
10 days × ₱50
₱500.00
Change oil
₱87.50 ÷ 12 × 10, short cutoff
₱72.92
Gross pay
₱7,067.92
SSS salary loan
amortization, capped at balance
−₱830.61
Net pay
₱6,237.31
Statutory shares are taken on the 16–30 cutoff for this client, so none appear here. Each line is rounded to the centavo as it is computed; net is gross less deductions.
SSS2025 table, MSC ₱5k–₱35k
PhilHealth5% on basic
Pag-IBIG₱200 cap
BIR withholdingsemi-monthly TRAIN table
Form 2316per-employee PDF
Alphalist1604-C .DAT, checked before download
13th monthRA 851, ₱90k cap
RA 10173platform is a processor, not a controller
Why firms switch
Built from a working register, not a feature list.
The engine was written against a real firm’s payroll workbook and is tested against its rows to the centavo. What the spreadsheet did by hand, the app does structurally.
Your workbook, made structural
The 26-day divisor, prorated allowances, monthly-rated and daily-rated employees in one register, statutory taken on the cutoff you choose. Payslips render from the run and are never re-keyed, so the payslip-versus-register check cannot fail.
Four eyes on every cutoff
Once your firm has a second staff login, preparer, checker and approver must be different people: a preparer cannot check their own run, and neither can approve it. A one-person firm runs every step itself. Finalize posts loan payments, statutory bases, year-to-date totals and a balanced journal in one transaction. Void reverses every bit of it.
Even we cannot see your clients’ payroll
The platform console shows head counts and plan status. Employee names, salaries and government IDs are invisible above your firm by design, not by policy.
How a cutoff runs
Seven steps, three people, one balanced journal.
Each step is a distinct status in the app. Roles are enforced on the request, not hidden in the interface. A firm of one runs all seven; add a colleague and the separation switches on.
1Open the periodPayroll admin
Step 1 of 7
OPEN
A 1–15 or 16–end cutoff. Which statutory deductions this cutoff carries is frozen into the period when it is created, so a policy change later never rewrites history.
Period June 16–30
Deducts SSS · PhilHealth · Pag-IBIG · tax
Flags frozen at creation
2Build the timesheetsHR, or the client’s own HR seat
Step 2 of 7
OPEN
Aggregate from daily attendance, import a biometric CSV, or key the days. Overtime, night differential, rest-day and holiday hours land in their own buckets.
21 employees · 21 timesheets
Source: attendance + 1 import
OT 14h · ND 6h · holiday 1d
3Compute the runPreparer
Step 3 of 7
CALCULATED
Every line per employee: basic, premiums at Labor Code multipliers, allowances by method, statutory from the dated tables, withholding from the BIR table, loans and standing deductions. Overrides need a reason and keep the engine’s figure beside them.
Gross ₱412,318.50
Deductions ₱61,904.12
Net ₱350,414.38
4CheckChecker, not the preparer
Step 4 of 7
CHECKED
The checker sees each override next to the original. A negative net blocks the run and names who, and by how much.
2 overrides, both with reasons
Negative net: none
Checked by M. Reyes
5ApproveApprover, neither of the two
Step 5 of 7
APPROVED
Once the firm has more than one staff login, neither the preparer nor the checker can approve. Self-approval is refused by the API, not just hidden.
Approved by A. Santos
Preparer ≠ checker ≠ approver
6FinalizeApprover
Step 6 of 7
FINALIZED
One transaction posts loan payments, monthly statutory bases, year-to-date totals, a balanced journal entry on the client’s ledger, and the payslips. Void reverses all of it.
Journal: debits = credits
9 loan payments posted
21 payslips created
7ReleasePayroll admin
Step 7 of 7
RELEASED
Bulk release makes payslips visible in the employee portal with PDF on demand. The firm sees who has acknowledged theirs.
21 released · 17 acknowledged
PDF per payslip
Statutory report ready
Everything around the engine
The whole year, not just the cutoff.
Each module feeds the run or reads from it. Nothing is re-typed between them.
Employees
Effective-dated compensation. A raise closes the old rate and starts a new one, so recomputing an old period still pays the old rate.
Client HR seats
Seat a login at the client company to encode their own people, attendance and leave. They read the payroll; they cannot prepare, check or approve it.
Pay items
A per-client catalog of earnings and deductions with tax treatment and ledger mapping. Add a rice subsidy and it flows through payroll, payslips and journals.
Attendance
Holiday calendar, daily grid, biometric CSV import that never overwrites a manual fix, and portal clock-in with capped hours.
Leave
Employees file from the portal. Approval writes the days into attendance, so leave pay needs no re-typing.
Loans and advances
SSS salary and calamity, Pag-IBIG MPL, calamity and housing, company advances. Collected each cutoff from the start date, capped at the balance, reversed on void.
Payslips
Created at finalize, released in bulk, printed or downloaded as PDF, acknowledged by the employee.
Reports
Monthly SSS, PhilHealth and Pag-IBIG remittance summaries with employee and employer shares, 13th-month accrual, the payroll register and the general ledger. Each downloads as CSV.
Year-end for BIR
December annualization with refunds and collections written onto the final payslip. Form 2316 PDFs and the 1604-C alphalist as the BIR .DAT file, from the same computation.
Employee portal
Own payslips, own attendance, clock in and out, file leave, change password. Nothing of anyone else, enforced server-side.
Privacy by architecture
Even we cannot see your clients’ payroll.
Firms are trusted with salaries, government IDs and home addresses. The platform console can list your firm, your clients and your head counts. It cannot open a payslip, an employee, or a run. That is how the data is scoped, not a setting someone could flip.
Every query is scoped to the firm and the client company at the request selector.
A Client HR seat is confined to one company. Any other client is refused outright.
Permissions resolve from the database on every request. Revoking a seat takes effect on the next call.
Under the Data Privacy Act (RA 10173) the platform acts as a processor. Your firm and its clients remain the controllers.
Pricing
A small base fee, then pay per client company.
One subscription per firm. Each client company you run payroll for is charged by how many of its employees were paid that month. A client with no run that month costs nothing.
Free
One client company, up to ten employees. No card, no time limit.
Headcount is employees with a payslip on a finalized run in the month. Nothing else counts.
A client is billed only in months it was paid on the platform.
Volume discount on client lines: 10% from 51 clients, 20% from 151.
Invoiced monthly, due in 15 days. VAT added where applicable.
What typical firms pay per month
Solo accountant, own company, 6 employees
₱0
3 clients, about 8 employees each
₱1,546
6 clients, four small and two mid-sized
₱3,693
12 clients: eight small, three mid-sized, one of about 100
₱8,287
A client near the top of its band costs roughly ₱15 to ₱35 per employee, so a firm can charge its clients well under what retail payroll vendors ask, which is the point of buying wholesale.
Prices in Philippine pesos, VAT not included.
Questions accountants ask
The details that decide it.
Which cutoff takes SSS, PhilHealth and Pag-IBIG?
Set per client: second cutoff only, first cutoff only, split evenly, or the last cutoff of the month. The choice is frozen into each period when it is created, so changing the policy later never rewrites an old run.
How is withholding tax computed?
From the BIR semi-monthly table on taxable earnings minus the employee’s statutory shares for the cutoff. December annualization recomputes the year on actual compensation and writes the refund or collection onto the final payslip. A manual override with a reason is always available. When BIR, SSS, PhilHealth or Pag-IBIG publish a new table, Payzone adds it as a dated version, and every run records which tables it used.
Where does rounding happen?
On each line, once. Rates are kept to four decimals; every earning and deduction is rounded to the centavo as it is computed, and net is simply gross less deductions, so the payslip always adds up. The number of decimals and the rounding mode are client settings.
Can monthly-rated and daily-rated employees sit in one register?
Yes. Monthly-rated get half their monthly rate with absences and late minutes deducted. Daily-rated get rate times days worked, with paid leave and unworked regular holidays added as their own lines.
Can our clients encode their own attendance?
Yes. Seat a Client HR login at the company. They manage their own people, attendance and leave and read the payroll you built from it. They cannot prepare, check, approve, finalize or release.
What if a finalized payroll was wrong, or someone resigns?
Run an adjustment for just the people affected: it pays or recovers only the difference against the finalized run, with the reason on every line. A resignation gets a final-pay run covering the last cutoff, leave conversion, prorated 13th month, open loans and the year’s tax. A 13th-month run pays year-to-date basic ÷ 12.
Do employees or staff need a working email address?
No. Accounts are created with a one-time temporary password you hand over directly. Nothing in the product depends on receiving mail.
What happens at year-end?
Annualization per employee with the ₱90,000 benefits cap applied. Form 2316 as a one-page PDF per employee, and the 1604-C alphalist as the .DAT file the BIR module reads, checked against BIR’s published layout before it downloads (schedule CSVs too). Both come from one computation, so a certificate can never disagree with its alphalist line. Minimum wage earners (Schedule 2) are not in the .DAT yet.
How is the bill worked out?
Monthly, after the month ends: the base fee, plus one charge for each client company that had a finalized run that month, priced by how many of its employees were paid. A client with no run costs nothing that month, and voided runs never count. The Billing page in the app shows the month so far, so nothing on the invoice is a surprise.
Is our clients’ data separated from other firms’?
Every query is scoped to the firm and the client company. The platform itself sees head counts and plan status only. Voided runs are reversed, never deleted, and finalized runs snapshot their lines.
See a cutoff run end to end.
A 30-minute walkthrough on a synthetic firm with three clients: run a cutoff, trip the negative-net guard, close a BIR year, seat a client’s HR.