
Payroll Software Demo Checklist for Philippine Owners: 8 Tests to Run Live
Eight live tests for any payroll software demo in the Philippines, run on your own data: trace a payslip, try to approve your own run, pull the log, export everything.
Run a payroll demo as a test, not a tour. Give every vendor the same script and your own last cutoff, with names removed, then make them show eight things live: your numbers reproduced, a payslip traced, a correction, an approval block, the log, the files you submit, a full export, and the AI's limits.
Every vendor will say "yes, we do that." The useful question is "show me where I can see it." Each test below has something to ask for and a rule for passing, so a quiet owner can run it and a talkative salesperson cannot talk past it.
Set Up the Payroll Software Demo So Every Vendor Takes the Same Test
Put three people in the room: the owner or executive, the payroll lead and the accountant. A week before, send each vendor the same script and the same anonymized file. Insist on their live product, not slides, and score every vendor on one sheet.
Use your last closed cutoff as the file: the payroll register with employee numbers in place of names. Add five hard cases from your own payroll, for example a hire in the middle of a cutoff, a resignee, someone with a loan, a branch transfer, and someone who worked overtime on a holiday.
Each person watches for something different. The owner asks "can I see it?" The payroll lead checks the work. The accountant checks what leaves the system and goes to the bank and the government.
The 8 Tests for a Payroll Software Demo
A test passes only when the answer appears on screen, computed from your data. "Let me follow up," "that is on the roadmap" and "it is configurable" are misses for the demo, even if they are honest. Run the tests in this order, because the later ones depend on the earlier ones.
Test 1: Reproduce Your Last Cutoff
Ask the vendor to load your file and produce net pay for your five hard cases. Compare each figure with what you actually paid. A difference is not automatically the vendor's error, because it may be yours, but every difference must trace to a line the vendor can name.
Ask to see: net pay for each of the five employees, side by side with your own figures.
Passes if: the figures match, or each gap is explained by one named line.
Test 2: Trace One Net Pay Back to Its Inputs
Pick one payslip and ask the vendor to click from net pay to gross pay, to each deduction, and to the attendance and rate behind it. You will be the one explaining a disputed payslip.
DOLE's rules already expect a payroll that shows, for each employee, the time paid, the rate, regular pay, overtime pay, deductions and the amount actually paid (Rule X, Sec. 6).
Ask to see: one payslip opened up to its attendance, rate and each deduction.
Passes if: nobody leaves the screen, opens a spreadsheet or asks a developer.
Test 3: Correct a Closed Cutoff
Say one employee was overpaid by two days in a cutoff that is already approved. Ask the vendor to fix it. A good system shows the fix as a visible adjustment, or reopens the run with a record, and leaves the original figures viewable.
Ask to see: the correction, then the original and the adjusted figures together.
Passes if: the original is still visible and the change is recorded, not silently overwritten.
Test 4: Try to Approve Your Own Run
Log in as the person who prepared the run and try to approve it. Whoever can add an employee, change a rate and approve the run can pay anyone anything without a second pair of eyes. This is a control, not a feature, so ask how approval rights are set by role.
Ask to see: the preparer's login trying to approve, and the role settings.
Passes if: the system blocks it or requires a second person.
Test 5: Pull the Log for One Salary Change
Pick one employee whose salary changed last month. Ask who changed it, when, what the old value was and what the new one is, and ask for the log as a file your auditor can open.
Salary data is personal data, and the Data Privacy Act expects reasonable organizational, physical and technical measures against unlawful access and alteration (Sec. 20). Whether a given log meets that standard is for your counsel.
Ask to see: the log entry, then the export of it, then who can switch logging off.
Passes if: it shows who, when, old value and new value, the export carries all four, and switching logging off is itself recorded.
Test 6: Produce the Files You Submit
Ask for the bank payment file for your bank, plus the government files and forms your accountant prepares from payroll, generated from this cutoff while you watch. "Available on request" does not count.
Ask which version of each form the system uses, whether the payment file goes to the bank directly or is uploaded by you, and whether a second person approves the payout.
Ask to see: each file, opened, with your accountant checking the format.
Passes if: your accountant confirms they can use each file as it is.
Test 7: Export Everything
Ask the vendor to export your full payroll history: every cutoff, every employee, every adjustment, in a file you can open without the vendor. Ask where the data is hosted, which subcontractors process it, what the export costs, and how long you keep access after you cancel.
You need this for two reasons. DOLE requires employment records to be preserved for at least three years from the last entry (Rule X, Sec. 12), so you must be able to produce them after you leave. And you stay responsible for personal data when processing is subcontracted (Data Privacy Act, Sec. 14). Employees can also ask for a copy of their data in a structured, commonly used format (Sec. 18). The Tax Code separately requires books of accounts and other accounting records to be kept for five years, counted from the filing deadline for the year of the last entry (Sec. 235, as amended by RA 11976). Your accountant can say which payroll records count as part of your books.
Ask to see: a real export of your test file, opened.
Passes if: it is complete, readable without the vendor, and the terms for hosting, fees and access after cancellation are in writing.
Test 8: Make the AI Show Its Limits
If the product has an AI assistant, ask seven things: what it can read, what it can change, who approves a change, whether every action is logged, which model runs it and where your data is processed, how long data is kept and whether it trains anything, and whether you can turn it off.
Then ask it one question about your own payroll. NPC Advisory No. 2024-04 says a controller stays accountable when AI processing is subcontracted, expects ways for people to intervene in automated decisions and warns against overstating AI's role, which it calls AI washing. For the difference between grounded AI and a chatbot, see What "AI-Native" Payroll Actually Means.
Ask to see: the seven answers in writing, then the AI answering from your data.
Passes if: the answers are specific, and the AI's reply cites figures you can find on screen.
Score the Demo With One Table
Score each test 2 if shown live on your data, 1 if shown only on sample data or in part, and 0 if promised or deferred. Compare vendors on one sheet. The zeros matter more than the total, because a zero on test 4, 5 or 7 is a risk, not a missing feature.
Table: The eight tests, what to ask for, and what a pass looks like
| # | Test | Ask to see | It passes if | A common miss |
|---|---|---|---|---|
| 1 | Reproduce your cutoff | Net pay for five hard cases | Matches yours, or each gap is named | "The sample data is similar" |
| 2 | Trace a net pay | One payslip opened to its inputs | No one leaves the screen | "Let me pull a report" |
| 3 | Correct a closed cutoff | Fix, original and adjusted figures | Original visible, change recorded | The fix overwrites the record |
| 4 | Approve your own run | Preparer trying to approve | Blocked or needs a second person | "You can set that up later" |
| 5 | Salary-change log | Who, when, old and new value; who can switch it off | All four, in an export | The export drops the old value |
| 6 | Files you submit | Bank and government files, opened | Your accountant can use them | "Available on request" |
| 7 | Export everything | Full history in an open file | Complete, readable, terms in writing | "We can arrange that" |
| 8 | AI limits | Seven answers in writing | Specific, and cites your figures | "It is secure and compliant" |
Before You Sign: Four Checks Beyond the Demo
A demo shows capability. Before signing, run one cutoff in parallel, call a customer of your size, get the full price in writing and put the export terms in the contract. Each check closes a gap the demo cannot.
- Run a parallel cutoff. Ask for a trial or paid pilot on one real cutoff, run beside your current process, and compare every payslip. See How to Switch Payroll Providers Mid-Year for the cutover mechanics.
- Call a reference of your size. Ask for a customer with a similar headcount and industry, and ask what went wrong in their first two cutoffs.
- Get the price in writing. Ask what is per employee and what is flat, whether there is a setup fee, whether VAT is included, and what happens at renewal. Cost by headcount shows how published prices compare at 10 to 500 employees.
- Write the export into the contract. Test 7 is only a promise until the terms for your data, fees and access after cancellation are in the agreement.
What YAHSHUA One Payroll Shows Today
YAHSHUA One Payroll does not pass tests 4 and 5 in full today. One person can create, approve and post the same payroll run, and the audit log's Excel and PDF exports leave out old and new values. Here is the detail, so you can check us.
Test 4. The default Admin role can create, approve and post a run, and nothing checks that these are different people. You can split those permissions across custom roles, but the system does not require it. There is one approval step.
Test 5. Changes to rates, formulas and income and deduction setup, and edits to an employee's pay profile, are logged on screen with old and new values. The Excel and PDF exports leave those values out. Entries in Salary History record that a change was made, without the amounts. A company can also switch logging off for most modules, so check that setting.
It does compare two payroll runs, which helps with test 3. Run all eight tests on every vendor on your shortlist, including us. See pricing for what it costs.
Related reading
- Payroll Software in the Philippines: What Actually Matters Before You Switch, the buying guide these tests fit into
- Multi-Branch Payroll in the Philippines: 7 Controls for Owners With 5 or More Locations, ten-minute tests for companies with several sites
- Can AI Replace a Payroll Officer in the Philippines?, what to hand over and what to keep human
- Excel vs. Payroll Software in the Philippines, when a spreadsheet stops being enough
- YAHSHUA One Payroll, the product to run the eight tests on
Frequently Asked Questions
What should I ask in a payroll software demo? Ask the vendor to show, live and on your own data, how it reproduces your last cutoff, traces one net pay back to its inputs, corrects a closed cutoff, blocks you from approving your own run, shows who changed a salary and when, produces the files you submit, and exports your full history. Answers that arrive as "yes, we do that" are not tests.
How long should a payroll software demo take? Plan about 90 minutes for the eight tests with the owner, the payroll lead and the accountant in the room. If a vendor says a test needs a separate session to prepare, treat that as a result and score it as a miss for the demo, then ask when it can be shown.
Should I give a vendor my real payroll data before I sign? Send only what the test needs: salary figures and employee numbers, with names, addresses and government ID numbers removed. Under the Data Privacy Act you remain responsible for personal data you hand to a processor (Sec. 14), and a test of the math does not need anyone's identity.
How do I test AI in payroll software during a demo? Ask what it can read, what it can change, who approves a change, whether every action is logged, which model runs it and where your data is processed, how long data is kept, and whether you can turn it off. Then ask it a question about your own payroll. NPC Advisory No. 2024-04 says you stay accountable for AI processing you subcontract.
What payroll records must I be able to get out of a payroll system? DOLE's rules require a payroll that shows, for each employee, the time paid, the rate, regular pay, overtime pay, deductions and the amount actually paid, and require employment records to be preserved for at least three years from the last entry (Omnibus Rules, Book III, Rule X, Sec. 6 and 12). Ask the vendor to export all of it, including adjustments.
Bring your own cutoff. Run the eight tests on us.
Book a free demo and bring your last cutoff's payroll register with the names removed. We'll tell you up front which two tests we don't pass in full.
Book a Free Demo →Sources
- Omnibus Rules Implementing the Labor Code, Book III, Rule X, Sec. 6 (Payrolls) and Sec. 12 (Preservation of records), Supreme Court E-Library, elibrary.judiciary.gov.ph/thebookshelf/showdocs/2/85819 (accessed November 2026)
- Republic Act No. 10173 (Data Privacy Act of 2012), Sec. 14 (Subcontract of personal information), Sec. 18 (Right to data portability) and Sec. 20 (Security of personal information), lawphil.net/statutes/repacts/ra2012/ra_10173_2012.html (accessed November 2026)
- Republic Act No. 11976 (Ease of Paying Taxes Act), Sec. 33, amending Sec. 235 of the National Internal Revenue Code (Preservation of books of accounts and other accounting records), lawphil.net/statutes/repacts/ra2024/ra_11976_2024.html (accessed November 2026)
- National Privacy Commission, NPC Advisory No. 2024-04, "Guidelines on the Application of the Data Privacy Act of 2012 to Artificial Intelligence Systems Processing Personal Data," December 19, 2024, privacy.gov.ph (accessed November 2026)
- YAHSHUA One, Payroll product page, yahshua.one/payroll (accessed November 2026)
Written and reviewed by the YAHSHUA One editorial team, part of The ABBA Initiative (OPC). Published November 5, 2026.