The offer
Proof first, decision later
Every payroll vendor says their numbers are right. We would rather show you, using your own employees and your own payroll month, before you spend anything.
You already have the two things needed to check a payroll system: the attendance for one month (both cutoffs) and the registers your current system produced for it. A full month matters because SSS, PhilHealth, and Pag-IBIG are monthly amounts, and only a complete month lets us prove them. Give us both (or connect us to your data) and we do the rest. If AppDeep Payroll cannot reproduce your register, you will know exactly where and why, and you have lost nothing.
How it works
Four steps, one month
- Send. You send the data for one closed cutoff — a spreadsheet export is fine — or give us read access to your current system.
- Set up. We load your employees, rates, schedules, and statutory settings into a dedicated AppDeep Payroll instance created for you.
- Compute. We process that cutoff in AppDeep Payroll: DTR, overtime, SSS, PhilHealth, Pag-IBIG, withholding tax, loans, and adjustments.
- Compare. We return a line-by-line comparison against your register and walk your finance team through every discrepancy.
What we need from you
Four files. Any format you already have.
- Employee master. Names, IDs, basic pay, pay class, hire dates, tax status, and statutory numbers.
- One month's DTR or attendance, both cutoffs. Punch logs, timesheets, or the attendance summary your current system used.
- That month's payroll registers. The earnings and deductions per employee as your current system computed them.
- Statutory settings. Your SSS, PhilHealth, Pag-IBIG, and withholding tax setup, plus any company-specific rules (allowances, loan schedules, leave conversion).
Excel, CSV, or PDF exports all work. If you would rather not export anything, we can connect to your data instead.
What you get back
A comparison you can sign off on
- Comparison report. Every employee, every earning and deduction line, side by side: your register versus AppDeep Payroll, with the peso difference.
- Discrepancy list. Each difference explained — a rate we were not given, a rounding rule, a statutory table version, or an error in the source data.
- Payslips and summary. Sample per-employee payslips and the payroll summary for the cutoff, so you can see the output your team would actually use.
- A straight answer. If the match is not exact and the reason is on our side, we say so.
On our first migration, a 580-employee company, 580 of 581 employees matched the incumbent payroll to the peso on the first parallel run. The one exception was a data-entry error in the old system.
Questions
Before you send anything
Is our payroll data kept confidential?
Yes. Your data goes into a dedicated instance with its own database, created for your parallel run and not shared with any other company. We sign an NDA on request before you send anything. When the run is done, we delete the instance or keep it as the start of your migration, whichever you decide.
How long does it take?
Typically within 5 working days of receiving complete data [PLACEHOLDER: confirm turnaround]. Larger headcounts or unusual pay rules can take longer; we tell you the expected date when we confirm receipt.
What does it cost?
Nothing. The parallel run is free and does not commit you to anything. If you decide to move to AppDeep Payroll afterward, the work done for the run becomes the first step of your migration.
What if the numbers differ?
We show you why, line by line. Sometimes it is a rule or rate we were not given, and we fix our setup. Sometimes it is a rounding or table-version difference, and we document it so finance can decide which is correct. And sometimes it is the old system: on our first migration, the single mismatch out of 581 employees turned out to be a data-entry error in the incumbent payroll.
Do we need to install anything?
No. AppDeep Payroll is web-based and runs on the dedicated instance we set up. You send files or grant read access; nothing is installed on your side.
Which month should we send?
Any recently closed month that is typical for you, both cutoffs. A month with overtime, a holiday, and a few loan deductions is a better test than a quiet one. We need the whole month because the SSS, PhilHealth, and Pag-IBIG amounts are monthly, and their split across the two cutoffs is part of what we verify.