OnPay Payroll: What QuickBooks Users Should Weigh Before Switching
Considering OnPay for payroll while you run QuickBooks? We compare the practical trade-offs, integration, and what to verify before you switch.
OnPay earns a fresh round of review coverage every year, and the headlines usually lead with pricing. If you keep your books in QuickBooks, the subscription fee is only part of the decision. The bigger questions are how pay runs land in your books and what a switch costs you mid-year. Here is how we would think it through.
What is OnPay, and who is it for?
OnPay is a browser-based payroll service sold by an independent company, not by the maker of QuickBooks. It sits in the full-service category: it calculates pay and payroll taxes, files the returns, and produces year-end forms such as W-2s. Nothing installs on your machine.
Its marketing leans on simple, flat pricing, which is why it keeps appearing in comparisons with QuickBooks Payroll. Flat pricing appeals when headcount or pay frequency makes tiered fees hard to predict. Your actual cost still depends on how many people you pay and how often, so price it against your own numbers.
How does payroll reach QuickBooks if OnPay runs it?
Payroll has to land in your books even when a third party calculates it. Two patterns cover most setups. An integration can post the entries into QuickBooks Online for you, or you can record one journal entry per pay run by hand.
OnPay advertises an integration with QuickBooks Online. If you use it, the accounts still need mapping: gross wages to wage expense, employer taxes to payroll tax expense, and withheld amounts to payroll liabilities. When the bank payment clears, it settles those liabilities. Check the mapping after the first live run rather than trusting the defaults.
Desktop editions are the other case. Integrations of this kind usually target the online product, so desktop users commonly post a manual entry per run. It is routine bookkeeping, but it is your bookkeeping, and it deserves a repeatable template.
The pricing in reviews goes stale quickly
Review sites refresh their OnPay write-ups each year, and pricing is usually the headline. Treat those numbers as a snapshot. Payroll vendors change base fees and per-person rates, run promotions, and adjust what is included, and a review can lag by months.
QuickBooks Payroll pricing moves too. If you are comparing, pull both vendors’ current rates the same day and apply them to your real headcount and pay frequency. Also check what each plan includes for state filing and year-end forms, because the real difference tends to hide there.
What should you check before switching?
None of these points appear in a headline price, and every one of them eventually appears in your workload:
- Who files each return, in every state where you have staff, and who is liable if one is late?
- Are W-2 and 1099 filing included, or billed as extras?
- How are contractors paid and reported?
- How do pay runs reach QuickBooks, and who sets up the account mapping?
- What support do you get on payday when something breaks?
Can you switch mid-year without a mess?
Yes, but the new provider has to take over your year-to-date wage and tax balances, so the handover matters. Pull a year-to-date payroll summary before you start, covering gross wages, taxes withheld, and employer taxes by employee. A new year is the cleanest boundary, and a quarter boundary is next best. Keep the final filings from the old provider where you can find them.
Test the first direct deposit run early, not on a tight deadline.
Our take
OnPay is a credible option, and the flat-fee pitch is real. What a review cannot do is price your payroll. Count your people, list your states, and cost both services on those facts before you commit. If you do move, move at a clean boundary and reconcile the first two pay runs line by line. That habit catches mapping errors while they are still small.