Short answer
If you pay a handful of people a fixed monthly salary, have no overtime or night shifts, and one careful person checks every run, a spreadsheet works. Many small companies run this way for years.
It gets risky when the work stops being a copy of last month. Contribution rates and tax tables change. Overtime, night differential and holiday pay enter the sheet. 13th month and final pay need the right months and the right balances. And the person who built the formulas becomes the only one who understands them.
Software does not make payroll correct by itself. It moves the rules, the history and the checking out of one person's head and one file.
When a spreadsheet is fine
A spreadsheet is a reasonable payroll if most of these are true:
- You have a handful of employees, all on fixed monthly pay.
- There is no overtime, night shift or holiday work to compute.
- One person knows every formula, and a second person can still follow them.
- Someone other than the preparer checks every run before payday.
- You keep a dated copy of each run, so you can show what was paid and when.
- You update the rates and tables yourself whenever they change, and you know when that is.
If that describes you, you do not need to switch yet. Use the self-check below to see where the sheet is thin, and the free calculators to test your numbers.
Where it breaks
These are the places a Philippine payroll sheet most often goes wrong. None of them is hard once. The trouble is doing them correctly every pay period, every year, and for every employee.
Contribution tables change
SSS moved to a 15% rate in January 2025, split 5% employee and 10% employer, on a monthly salary credit from ₱5,000 to ₱35,000. Pag-IBIG figures contributions on pay up to ₱10,000. PhilHealth is 5% of basic pay, with a ₱10,000 floor and a ₱100,000 ceiling. Each has its own rounding and its own limits.
In a sheet, a rate change means finding every lookup table and formula that uses it, editing them, and testing again. Miss one cell and every payslip after it is off, usually in small amounts that nobody notices until a remittance does not match. You can see these rules worked out line by line in the salary calculator.
Withholding tax tables
Withholding tax comes from the BIR tables under the TRAIN law (RR 11-2018, Annex E), with different tables for monthly and semi-monthly pay. The tax is figured on pay after the employee's SSS, PhilHealth and Pag-IBIG shares. Then the year-end true-up compares what was withheld against the annual table.
A sheet usually handles the per-payday step and forgets the true-up, or handles it by hand in December. Mid-year hires, raises and leavers all change the answer.
Overtime, night differential and holiday pay
Premium pay depends on the kind of day: an ordinary day, a rest day, a regular holiday or a special non-working day. Overtime and night shift stack on top, and each combination has its own multiplier. One wrong cell reference and the whole column is wrong.
This is the point where many small companies outgrow a spreadsheet. The daily rate, the hours and the day type all have to come from somewhere reliable, and attendance data usually arrives in another file.
13th month pay
13th month pay is the basic salary earned in the calendar year divided by 12, paid on or before December 24. Unpaid absences and leave without pay come off first. New hires and leavers are prorated, and a salary change mid-year changes the base month by month.
Allowances, overtime and similar pay are left out unless your policy says otherwise. The first ₱90,000 of the 13th month and other benefits is tax-free; the rest is taxable. Try your own case in the 13th month pay calculator and compare it to your sheet.
Final pay
Final pay must be released within 30 days of separation (DOLE Labor Advisory No. 06, Series of 2020). It combines unpaid salary, the prorated 13th month, the cash value of unused leave that converts to cash, and separation or retirement pay when it is due, less loans and any tax still owed. It is the computation spreadsheets handle worst, because it is rare, so nobody remembers how it was built last time.
The final pay calculator shows each part separately so you can check the total.
No audit trail
A spreadsheet does not record who changed which cell, when, or why. If an employee asks why last quarter's pay was lower, or an auditor asks what rate you used in March, you are reconstructing it from old copies and memory. A saved file named "payroll FINAL v3" is not a history.
Payslips and government forms
Each employee needs a payslip that matches what was paid. Each month, contributions have to be reported and remitted to SSS, PhilHealth and Pag-IBIG, and each employee needs a BIR Form 2316 by January 31 of the next year, or on their last payday if they leave during the year. In a sheet these are separate exports and copy-paste jobs, each one a chance to make the payslip, the remittance and the bank file disagree.
One-person risk
Most spreadsheet payrolls were built by one person and are understood by one person. If that person is on leave, resigns, or makes an honest mistake the day before payday, the company has a problem that no formula can fix.
A self-check: sheet or software?
Go down the list and ask who does each task today, and how you would know if it went wrong.
| Task | In a spreadsheet | In payroll software |
|---|---|---|
| Update contribution tables | You edit each table and formula, then re-test. | Rules carry their effective dates, so last year's runs keep last year's rates. |
| Withholding tax and the year-end true-up | Built and checked by hand, often only at year end. | Worked out on every payslip, with the annual figure tracked. |
| Overtime, night and holiday pay | Hours are typed in or pasted from another file. | Premium rules apply to the day type, ideally from attendance records. |
| Compute 13th month pay | A formula per employee, adjusted for hires, leavers and absences. | Worked out from the basic pay on record, prorated for hires, leavers and absences. |
| Compute final pay | Rebuilt each time someone leaves. | Assembled from the same records, with each part shown. |
| Keep an audit trail | Saved copies and memory. | A record of who changed what, and when. |
| Payslips to employees | Exported or copied one by one. | Generated from the run, so they match what was paid. |
| Government reports and forms | Retyped into each agency's format. | Prepared from the run, for your team to file. |
| If the builder is away | Payroll waits, or someone guesses. | A second person can run it from the same records. |
If you can answer every row in the spreadsheet column with "we have that covered and tested", your sheet is doing its job. If several rows make you nervous, that is your list of what to fix, with or without software.
What switching takes
Switching is mostly moving data and proving the numbers. With fidera it goes like this:
- Import your employee list from a spreadsheet. Department and branch names that do not quite match are paired with the real ones, and duplicate employees are caught before they are saved. See how the import works.
- Import employees, pay and year-to-date figures, so a mid-year switch carries the history with it.
- Run fidera next to your current payroll. This is a parallel run. Compare every employee, and switch when the numbers match. See how the parallel run works.
Your spreadsheet keeps being the payroll of record until you are satisfied. For plans and rates, see pricing. If you are comparing systems, read how to choose an HRIS and payroll system.
fidera