QuickBooks Online Advanced Payroll: Elite Tier, Workflows, and NYC Compliance

For most NYC small businesses, no. Premium is the right tier and Elite is overkill. The exceptions are real but narrow.

What you actually get for the price step-up. Premium runs roughly $85 per month plus $9 per employee at list price. Elite runs roughly $130 plus $11 per employee. That is a $45 base price increase plus $2 per employee monthly. For a 10-employee NYC business, you are looking at $65 a month more for Elite, or about $780 a year. The question is whether $780 a year of value is what Elite gives you over Premium.

What Elite adds that Premium does not have. Five features in practical terms. (1) Same-day direct deposit instead of next-day. (2) A personal HR advisor on call through Mineral, the HR services partner. (3) Project tracking with QuickBooks Time Elite included rather than the lesser Premium time-tracking. (4) White-glove payroll setup for new clients — an Intuit specialist handles your initial setup and historical data migration. (5) Expanded tax penalty protection: up to $25,000 with broader coverage scope, including some help if the IRS comes calling on a payroll matter even when QBO did not cause the error.

The Premium features that already cover most needs. Premium includes automatic federal and state filings (the big one), next-day direct deposit (24-hour funding which is fine for almost every business), the basic tax penalty protection up to $25,000 for QBO filing errors, expert review of your payroll setup at onboarding, garnishment management, workers comp administration through AP Intego, and QuickBooks Time Premium for time tracking. That is a full payroll product. The auto-filing alone is the feature that justifies paying for Premium over Core, and it is the same on Elite.

Where the Elite features actually deliver. Same-day direct deposit matters in two scenarios. First, when you forget to run payroll until the morning of pay day — same-day saves you. Premium next-day means you missed the cutoff and your team gets paid the day after. Second, when you have hourly employees whose timesheets come in late and you need to cut a same-day check. For salary-only payrolls, same-day direct deposit is rarely the difference. We see it matter most for construction, restaurants, and other industries with hourly or shift-based labor.

The HR advisor is the feature people pay for and rarely use. Elite includes access to Mineral HR advisors for unlimited consults on employee handbook drafting, classification questions, termination guidance, and state-by-state compliance. In theory, this is valuable. In practice, most small business owners do not call. The HR situations that come up are typically handled internally or escalated to outside counsel for anything serious. We have a half-dozen Elite clients who paid for the HR advisor for a year and called once. Not a great return. If you have actual HR needs — high turnover, multi-state employment law questions, complex termination situations — the advisor pays for itself. If you are running a clean small business, it sits on the shelf.

The white-glove onboarding actually matters for some clients. If you are migrating from another payroll system mid-year, the historical data migration is genuinely hard. Wage history, year-to-date taxes, prior W-2s, accrued PTO — all of it has to come over correctly or your first W-2 from the new system will be wrong. Elite includes a setup specialist who does this for you. Premium and Core do not. For mid-year migrations, the white-glove service is the strongest argument for Elite. For new business setup or year-end migrations (which we strongly prefer), white-glove is unnecessary.

The penalty protection difference is smaller than Intuit suggests. Both Premium and Elite cover up to $25,000 in penalties for QBO filing errors. The Elite version includes broader scope — some assistance even when QBO did not cause the error — but the core protection is the same dollar amount. The marketing makes Elite sound like a fundamentally better protection. It is not. The same $25,000 cap applies. We have walked through the fine print with Intuit reps multiple times and the practical difference is modest.

The math for a typical NYC five-person S-corp. Premium: $85 + 5 employees x $9 = $130 a month, or $1,560 a year. Elite: $130 + 5 employees x $11 = $185 a month, or $2,220 a year. Elite costs $660 more annually. For that $660, you get same-day direct deposit (rarely needed for a salaried team), HR advisor access (rarely called), white-glove onboarding (one-time benefit, irrelevant after year one), and expanded penalty scope (marginal). On those facts, Premium is the better value almost every time. The $660 saved goes further if you spend $300 to $500 on annual CPA-led payroll review, which catches more real problems than the Elite HR advisor will.

When Elite is actually worth it. Four scenarios make Elite the right pick. (1) You are mid-year migrating from another payroll system and the historical data migration is complex. (2) You have multi-state employment with real exposure under state employment law — California, New York employment-law complexity, Washington state pay transparency, the kind of thing where one bad termination can cost you. (3) You have already had a costly payroll mistake (a $10,000 misclassification settlement, a six-figure unpaid wage claim, a state audit) and you want the deeper safety net. (4) You have no in-house HR and need a real advisor to call when situations come up.

When Elite is overkill. One- to five-person S-corps with clean payroll, salaried employees, and a CPA already in the picture. The vast majority of our NYC clients fall here. Premium does everything they need at $600 to $800 less per year.

The hybrid we recommend for cost-sensitive clients. Stay on Premium. Add a CPA review of payroll quarterly — the same time the 941 and NYS-45 file. The review costs less than the Elite upgrade and catches more real issues because the CPA is looking at your specific situation rather than a generic HR question. For multi-state or complex situations, layer in an annual employment-law review with an HR consultant on retainer rather than calling Mineral. The total cost is roughly the same and the quality of advice is better. Our payroll services page covers what this looks like in practice.

One last piece of the calculation. If you are reading this because Intuit is pushing you to upgrade to Elite, ignore the sales pressure. The sales team is incentivized to upsell. Look at the features. Look at what you actually use today. If Premium is meeting your needs and you do not have one of the four scenarios above, stay on Premium. Save the money. Spend a fraction of it on a CPA who actually knows your business.

Set the owner up as a regular W-2 employee, pick a reasonable salary, run it through payroll every cycle, and book distributions through a journal entry to the equity distribution account. That is the short version. The longer version covers why each step matters and where most owners get this wrong.

Step one: add yourself as an employee. In QBO Payroll, go to Employees, add new employee, fill in your information just like any other W-2 hire. Use your real name and SSN. Mark the employee type as Officer for the S-corp tax classification, which routes the W-2 correctly at year-end. Set the pay schedule — we recommend semi-monthly (15th and last day) or monthly for owner-only payroll because it cuts the number of pay runs and keeps the workflow simple. Set the salary at your reasonable comp number. Configure withholding using a W-4 just like any employee. Add your direct deposit info if you want the pay to land in a personal account.

Step two: figure out your reasonable salary. This is the decision that matters more than any other in the setup. The IRS rule is that an S-corp owner who works for the business must pay themselves a reasonable salary for the services they provide before taking distributions. Reasonable is not defined as a percentage in the code. It comes from cases like Watson v. United States, where the court used three benchmarks: what comparable employees in the same role would earn, what the owner role actually demands of them, and what the company can support. For NYC-based owners, three data points to work from. (1) Look up Bureau of Labor Statistics wage data for your role in the New York City metro area. (2) Look at what you would pay a non-owner employee to do your job. (3) Look at industry compensation surveys (Robert Half, AICPA, your trade association). The defensible range usually falls between 40 and 60% of total owner compensation, but the right number depends on your facts.

Step three: run payroll for the owner like any employee. Every pay cycle, QBO Payroll prepares the run. The owner gets withholding for federal, state, NYC if a city resident, FICA, Medicare. The employer share of FICA and Medicare comes out of the S-corp. The net amount lands in the owner personal account. The gross goes to the W-2 at year-end. This is the cleanest, most defensible structure. Some owners try to skip the formal payroll mechanics and just write themselves a check labeled wages once a year. Do not do this. Lump-sum wages at year-end look suspicious to the IRS and create cash flow problems — you owe payroll tax deposits and the timing gets messy.

Step four: handle distributions separately, through a journal entry. Distributions are not payroll. They are an equity transaction. When you want to take a distribution, write yourself a check from the business account and book a journal entry: debit Distributions (an equity account), credit Cash. Do not run distributions through QBO Payroll as a special pay type. Do not call distributions a bonus or a reimbursement. The distribution shows up on the K-1 generated when the S-corp files its 1120-S, separate from the W-2.

The W-2 and K-1 at year-end. QBO Payroll generates the W-2 automatically for the owner like any other employee. It shows Box 1 wages, Box 3 Social Security wages, Box 5 Medicare wages, Box 16 New York state wages, Box 18 New York City wages if applicable, and the withholding boxes. The K-1 comes from the S-corp 1120-S return, which you (or your CPA) file separately. The K-1 reports the owner share of pass-through income, separately stated items, and the distributions taken. The two documents flow to your personal Form 1040 in different places: the W-2 income goes on Line 1, the K-1 ordinary income goes on Schedule E. Make sure your CPA receives both at tax time. The S-corp return is due March 15, the 1040 by April 15, and getting the timing right matters because the K-1 has to be issued before the 1040 can be filed.

Common setup mistakes we see. Five errors come up regularly when we onboard a new S-corp client.

Mistake 1: zero salary. The owner sets salary at $0 and takes 100% of compensation as distributions. This is a red flag for IRS review. If the owner works for the business, the IRS expects some salary. Zero is almost never defensible.

Mistake 2: undefensibly low salary. The owner picks a salary like $20,000 or $30,000 when their actual role and the company profits justify $80,000 or $150,000. The IRS recharacterization risk is real. We have seen audits where the IRS reclassifies a large chunk of distributions as wages and adds back payroll tax plus penalties.

Mistake 3: running distributions through payroll. Owner uses QBO Payroll to issue distribution checks coded as some non-taxable pay type. This is wrong on two counts. First, it puts equity transactions in the payroll system, which is the wrong place. Second, it creates W-2 boxes that do not match the K-1. At year-end, the books will not reconcile cleanly.

Mistake 4: irregular payroll runs. Owner pays themselves whenever cash is available rather than on a schedule. The IRS prefers regular, defined payroll. Irregular runs look like distributions disguised as wages and invite scrutiny.

Mistake 5: forgetting to issue the W-2. If the owner is on payroll for the year, the W-2 has to be issued by January 31 like any employee, even though it is going to themselves. QBO Payroll handles this automatically once you set up payroll correctly. The mistake usually comes from owners who set up payroll mid-year and then disabled the auto-W-2 feature without realizing it.

Mistake 6: NYC resident owner and the city tax. If the owner is a New York City resident, NYC tax applies to the W-2 wages just like any city-resident employee. The withholding rate is 3.078 to 3.876 percent. QBO Payroll handles this once you mark the owner address as NYC. Skip the address marker and you under-withhold on the city, which catches up when the owner files their 1040.

How to fix a prior-year split that was wrong. If you discover your salary was too low in a prior year, you have two options. Option A: file an amended W-2 and 1120-S for that year to reclassify some distributions as wages. This requires paying back payroll tax plus interest, but it gets you compliant. Option B: do nothing and hope the statute of limitations runs out before the IRS notices. The statute is generally three years from the return filing date for normal items, six years for substantial understatement. We prefer Option A when the dollar amount is meaningful because the penalty exposure on Option B is significant if the IRS catches it.

The annual review. Every year, reassess the salary based on the prior year results and the projected current year results. If the business grows, the salary probably grows with it. If the business shrinks, the salary might shrink — though the reasonable comp test still applies. The point is that the salary is not a set-and-forget number. It is a live decision that should be revisited at planning time each year. We typically have this conversation with S-corp clients in the November or December planning meeting, set the new salary for the coming year, and adjust QBO Payroll in early January. For NYC-specific tax planning questions, see our business owners page.

QBO Payroll Premium and Elite handle most of the routine filings. A handful still need human review, and a few never get touched by QBO at all. Knowing the line between automatic and manual is the difference between a clean compliance record and a notice in the mail.

What QBO Payroll files automatically (Premium and Elite). The auto-filing list for the 2026 tax year covers the core federal returns and most state returns.

Federal Form 941 (Employer Quarterly Federal Tax Return). Filed quarterly by the last day of the month following the quarter end: April 30, July 31, October 31, January 31. QBO pulls the wage and withholding data from your payroll runs, populates the form, and files electronically through the IRS Modernized e-File system. You get a confirmation when the filing posts.

Federal Form 940 (FUTA). Filed annually by January 31 for the prior year. QBO calculates FUTA at 6.0% on the first $7,000 of wages per employee, applies the standard 5.4% credit for state unemployment paid, and arrives at the typical net 0.6% rate. The filing happens automatically.

Federal Form W-2 and W-3. QBO generates W-2s for every employee by January 31, transmits W-3 to the Social Security Administration, and provides employees with electronic and mailed copies if you opt in. The W-2 reflects every pay run for the calendar year.

State income tax withholding returns. QBO handles auto-filing for the states with electronic filing support, which covers roughly 40 states including New York, California, Texas (no income tax but unemployment), New Jersey, Pennsylvania, Connecticut, and most major business states. For NY specifically, this means the quarterly NYS-45 with income tax withholding included.

State unemployment insurance returns. QBO files the SUI return quarterly in every supported state. For NY, this is part of the NYS-45. For NJ, it is the WR-30. For CA, it is the DE-9. Each state has its own form and QBO handles each one separately.

State new hire reporting. When you add a new employee, QBO reports the new hire to the state new hire registry within the statutory deadline (typically 20 days). This is a federal requirement under PRWORA that every state implements.

Payroll tax deposits. QBO Payroll auto-deposits federal and state payroll taxes on the schedule the IRS assigns to your business (monthly or semi-weekly). Auto-deposit is the default once you turn payroll on. Do not turn it off — the late-deposit penalty under IRC §6656 ranges from 2% to 15% depending on lateness, and the deposit fees you save are not worth the penalty exposure.

What still needs a person. Several filings and decisions never get auto-handled, even on Elite.

Form 1099-NEC for contractors. QBO Payroll does not file 1099-NECs automatically. You need QuickBooks Online Contractor Payments (a separate $15 per month subscription) or you handle 1099 filing manually outside QBO. The 1099-NEC is due January 31 to contractors and to the IRS. Penalties for late filing range from $50 per form (less than 30 days late) to $310 per form (after August 1 or intentional disregard). For a business with 20 contractors, missing the deadline costs $1,000 to $6,200 in penalties.

NYC Metropolitan Commuter Transportation Mobility Tax (MCTMT) standalone filings. If your business qualifies for MCTMT and the NYS-45 inclusion is not how it gets reported in your situation, the MTA-305 quarterly is separate. QBO does not file MTA-305 directly. We typically handle this through the NYS Tax Department portal as a separate step.

Local taxes outside QBO scope. QBO handles federal, state income tax, state unemployment, and a limited set of local taxes in some major metros. It does not handle every local tax. NYC commercial rent tax, Philadelphia wage tax, San Francisco gross receipts — these and similar municipal taxes are filed outside QBO.

Multi-state nexus and registration. QBO calculates the right withholding once you tell it where each employee works, but it does not register your business with each state. When you add a remote employee in a new state, you have to register with that state revenue department and unemployment agency before payroll can be processed correctly. Skip the registration and you accumulate back-tax exposure that has to be cleaned up later.

S-corp officer reasonable compensation. QBO calculates payroll on whatever salary you enter. It does not tell you whether that salary is defensible. The reasonable comp decision sits entirely with you (or your CPA). Wrong number, audit risk.

Year-end W-2 corrections. Once W-2s issue on January 31, corrections require Form W-2c, which QBO supports but does not automatically generate. If an employee SSN is wrong or wages were misstated, you have to initiate the correction yourself.

State-specific filings outside the auto-filing list. Some states are not in the QBO auto-filing program. For those states, QBO calculates the tax but you file the returns manually. Check the QBO Payroll state list before you assume auto-filing covers your situation.

The manual review steps we run every quarter for our payroll clients.

Step 1: pull the 941 preview before it auto-files. QBO gives you a 24 to 48 hour window to review the 941 before it submits. Check wage totals against the QBO payroll register. Confirm the federal tax liability matches the deposits made during the quarter. Verify the employee count is reasonable. Catch errors before the filing posts to the IRS.

Step 2: pull the NYS-45 preview. Same exercise for New York. The wage detail section is the most error-prone — every employee gets a line, and a wrong SSN, address, or job title can flag the return for state review.

Step 3: reconcile YTD wages to the books. Pull the YTD payroll summary report from QBO and compare to the wages expense on the P&L. The two should tie out. If they do not, something is wrong — usually a journal entry posted to wages that should have gone somewhere else, or a payroll run booked to the wrong account.

Step 4: confirm payroll tax deposits cleared the bank. Pull the bank reconciliation and confirm every federal and state payroll tax deposit cleared. If a deposit is stuck in pending status with the IRS or state, you want to know before the filing deadline.

Step 5: review the contractor list for 1099 readiness. Every quarter, pull the contractor payment list. Confirm every contractor has a current W-9 on file. Flag any contractor approaching $600 in cumulative payments who might trigger 1099 issuance at year-end.

Step 6: confirm new hire and termination data is current. Cross-check the QBO employee list against the HR list. Catch any new hires not yet onboarded and any terminations not yet processed.

Step 7: confirm multi-state registrations are current. For any business with employees in more than one state, confirm each state registration is active and current. State filing requirements change and a registration that was current last year may not be this year.

The year-end review checklist. A separate review runs in December before W-2s go out. Confirm employee addresses are current. Confirm SSNs match Social Security Administration records (use the SSA verification service for free). Confirm wages tie to the books. Confirm tax classifications match the W-2 type. Confirm any benefits, retirement contributions, and pre-tax deductions are reported correctly in the appropriate W-2 boxes. Issue the W-2s. Then run the same review against contractor payments before the 1099s issue.

The pattern. QBO does the mechanical work. The decisions, the inputs, and the review still need a person. Lean on auto-filing for what it does well. Build a review process around the parts the engine cannot make decisions for. Our bookkeeping service includes a quarterly payroll review as part of the standard scope for clients running payroll inside QBO.

The protection is real, the cap is $25,000 per year on both Premium and Elite, and the scope is narrower than the marketing suggests. Here is what is covered, what is not, and what happens when you actually need to file a claim.

What is covered. Intuit pays the IRS or state penalty plus interest, up to the $25,000 annual cap, when QBO Payroll causes the error that triggered the penalty. The standard examples are when QBO miscalculates a withholding amount, files a return with the wrong wage detail because of a system bug, files a return late because of a QBO system outage, or applies an incorrect tax rate that resulted in an underpayment.

What is not covered. The bigger list. Penalties caused by your inputs, your decisions, or your inactions are on you. Specifically.

Incorrect employee classification. If you set up a 1099 contractor in QBO who turns out to be a W-2 employee under IRS classification rules, QBO calculated payroll correctly based on the inputs you gave it. The penalty for misclassification is yours.

Missing state registrations. If you have an employee in a state where you have not registered, QBO will calculate the withholding but the back-registration penalty is yours.

Failure to register for local taxes. NYC MCTMT, NYC commercial rent tax, Philadelphia wage tax, San Francisco payroll expense tax, and similar local taxes. If you have local exposure that QBO does not track and you miss the filing, the penalty is yours.

Multi-state errors caused by employees you did not flag as remote. If an employee moves to a new state and you do not update QBO Payroll to reflect the new work location, QBO continues withholding for the old state. When the employee files in the new state, they will not have proper withholding, and the employer may owe back tax to the new state. That penalty is yours.

S-corp reasonable compensation issues. If the IRS recharacterizes a portion of distributions as wages and assesses back payroll tax with penalties, none of that is covered. The decision on what counts as reasonable comp was yours.

Data entry errors. If you typed in the wrong SSN, the wrong wage rate, or the wrong filing status, and QBO calculated payroll based on that wrong data, the penalty is yours. The protection covers Intuit mistakes, not yours.

Cancellations and lapses. If your QBO Payroll subscription was cancelled or lapsed and an auto-filing did not happen as a result, the penalty is yours. The protection only applies when QBO was actively running and made the mistake.

Cases over the $25,000 cap. Anything above the cap is yours. For most small businesses this is irrelevant — payroll penalties rarely exceed $25,000 in a year on Intuit-caused errors. For larger employers or for serial misfilings, the cap can be a real limitation.

How a claim actually works. The process is structured but not always fast.

Step 1: receive a notice from the IRS or state. Penalty notices come on a specific form — CP504 for the IRS, similar formats for states — with the penalty amount, the issue, and a payment deadline. Open the notice immediately. Do not let it sit.

Step 2: review the notice and determine if QBO was at fault. Most penalty notices come from missed deposits, wrong tax amounts, or late filings. Trace the issue back to its source. If the underlying data in QBO was correct and the auto-filing or auto-deposit happened on time, the system is probably at fault. If your inputs were wrong, the penalty is yours.

Step 3: contact QBO Payroll support and open a tax penalty claim. The phone number is on the back of your QBO account. Open a ticket. Provide the notice, the underlying QBO payroll records, and a brief description of what went wrong. The support rep will assign a case number and route the claim to the payroll resolution team.

Step 4: provide supporting documentation. QBO will ask for the notice, the QBO payroll register for the period in question, the bank statements showing deposits, and proof of the filing or attempted filing. Be ready to send these as PDFs through their secure portal.

Step 5: wait for the resolution. Most claims resolve in 14 to 45 days depending on complexity. Simple cases (a clear QBO system error that caused a missed deposit) resolve faster. Complex cases (a state filing that QBO claims was sent but the state claims was not received) take longer.

Step 6: receive the payment or denial. If approved, Intuit pays the penalty and interest directly to the taxing authority or reimburses you if you already paid. If denied, you get a letter explaining why. The most common denial reason: the underlying data was wrong, so QBO did not cause the error.

Step 7: appeal if denied. The appeals process inside Intuit is informal. You can escalate to a supervisor or to the QBO Payroll customer success team. If the denial is wrong, persistence usually gets results. If the denial is correct (your data caused the error), no appeal will change that.

Cases where the protection has worked for us. Two we can name from the last two years. A client on Premium had a federal payroll tax deposit fail to clear because of a QBO bank connection bug that did not retry the deposit after a temporary IRS portal outage. The IRS assessed a 5% late deposit penalty of about $1,200 on a $24,000 deposit. We filed the claim, provided the supporting docs showing the QBO retry log, and Intuit paid the full $1,200 within three weeks.

A different client had QBO file the NYS-45 with a stale employee address that resulted in the state flagging the return and assessing a $250 wage detail error penalty. We filed the claim, Intuit took responsibility because the QBO system had not pushed an employee address change through to the filing module, and paid the penalty.

Cases where the protection did not work. Three we have seen.

A client misclassified a worker as a 1099 contractor for two years. When the IRS audited and reclassified the worker as a W-2 employee, the back tax plus penalties came to about $18,000. QBO denied the claim. The penalty came from a classification decision the client made, not from a QBO system error. The denial was correct.

A client had a remote employee move from New Jersey to Pennsylvania and did not update QBO. QBO continued withholding NJ tax instead of PA tax. When the employee filed their 1040, they owed back tax to PA, and the state assessed an employer penalty for the missed withholding. QBO denied the claim because the underlying issue was the employer failing to update the employee work location in QBO.

A client had a registered state that lapsed because the annual registration renewal was missed. QBO continued filing returns to the state, but the state rejected them because the registration was inactive. The penalty for late filing came in, and QBO denied the claim because the underlying registration failure was the client responsibility.

The honest assessment of the protection. It covers what it says it covers, which is QBO system errors causing penalties. It does not cover what marketing sometimes implies, which is broad payroll-tax protection. The $25,000 cap is generous for most small businesses and adequate even for some mid-sized employers. The Elite-tier expanded scope adds some help with IRS-side negotiation even when QBO is not at fault, but does not change the dollar cap or the coverage scope materially. Treat the protection as a real safety net against system errors and not as a substitute for clean inputs and periodic review. The right way to use it: configure payroll correctly, review the auto-files before they post, audit the deposits monthly, and trust the protection to handle the occasional system mistake. The wrong way: assume the protection covers everything and skip the review steps. The wrong way is how penalties end up not covered.

Leave QBO Payroll when the friction starts to cost more than the integration saves. Each alternative has a specific sweet spot. Picking the right one matters because moving payroll providers is painful enough that you want to do it once, not twice.

Stay with QBO Payroll when. Your books are already in QBO and the integration matters. Your team is under 25 employees. Your payroll is fundamentally simple — one or two states, salaried staff, no complex benefits. The auto-filing and the QBO integration save you enough time that the friction points are tolerable.

Leave for Gusto when. You want a cleaner UX, better contractor management, and integrated benefits administration. Gusto wins on three specific dimensions over QBO Payroll for the 5- to 50-employee range.

User experience. The Gusto interface is meaningfully more polished than QBO Payroll. New users get through onboarding faster. The dashboard is cleaner. The mobile experience is better for employees who want to check pay stubs and W-2s on the go. We have seen clients who switched to Gusto report that their team complaints about payroll dropped to near zero within two months.

Contractor payments. Gusto handles contractor payments natively as part of the platform. You add a contractor, run payments on the same schedule as employees, and Gusto handles 1099-NEC generation automatically at year-end. QBO Payroll separates contractor payments into a different product (Contractor Payments at $15 per month) and the experience is less integrated. If you have 10+ contractors, Gusto is significantly easier.

Benefits administration. Gusto includes health insurance, dental, vision, life insurance, 401(k) integration, FSA, HSA, and commuter benefits administration as part of the platform. You can enroll employees, manage open enrollment, and handle benefits changes through one interface. QBO Payroll does not have an integrated benefits product — you bolt on third-party tools and reconcile manually. For an employer with full benefits, the Gusto consolidation saves time and reduces error.

Pricing for Gusto is similar to QBO Payroll Premium — the Plus tier runs $80 per month plus $12 per employee. The Premium tier (with HR resources and dedicated support) runs $135 plus $16.50 per employee. For a 10-person company, Gusto Plus comes in at about $200 per month versus QBO Premium at $175. Slightly more expensive but a noticeably better product for most situations. The catch: Gusto syncs to QBO for the GL entries but the sync is one-way and less direct than the QBO Payroll native integration. If your bookkeeper is heavily dependent on the QBO Payroll integration, that friction matters.

Move to Rippling when. Your needs go beyond payroll into IT provisioning, device management, app access, and global hiring. Rippling is the unified platform that handles HRIS, payroll, IT (laptops, software access, single sign-on), and global employer-of-record services from one interface.

The sweet spot for Rippling is technology companies in the 20- to 500-employee range that hire fast, have a mix of US and international employees, and want one system for both HR and IT. The argument is consolidation: one platform that provisions a new hire laptop, sets up their software access, processes payroll, handles benefits, manages PTO, and tracks performance reviews. For a tech startup growing from 30 to 100 people in 18 months, Rippling can replace four or five separate tools.

The cost structure is modular. The HRIS base runs around $8 per employee per month. Payroll is an add-on at around $8 per employee. The IT modules add more. A full Rippling stack typically runs $35 to $60 per employee per month, which is more than QBO Payroll or Gusto but spread across more functionality. For a 50-person tech company replacing five tools, Rippling can come out cheaper in total than the alternatives.

Where Rippling is overkill. Small businesses (under 20 employees) where the integration with QBO matters and the IT side is not relevant. Service businesses where benefits administration is the main need (Gusto is better for that). Companies with simple payroll that just need it to work (QBO Payroll Premium handles this fine).

Move to ADP when. You cross 100 employees, have complex multi-state operations, need PEO services, or have HR compliance requirements that demand a dedicated representative on speed dial. ADP RUN (their small business product) and ADP Workforce Now (their mid-market product) are the alternatives.

ADP RUN is comparable to Gusto and QBO Payroll Premium in feature scope, sometimes slightly less polished but with a larger compliance team behind it. Pricing is opaque (you have to call for a quote) and usually runs more than Gusto on a per-employee basis. The argument for ADP RUN over Gusto: if you need real human support on a regular basis, ADP has more support staff and longer hours. If you do not, Gusto is usually a better product.

ADP Workforce Now is the mid-market product, suited for businesses with 50 to 1,000 employees. It includes full HRIS, payroll, benefits, talent management, and compliance modules. The implementation is more involved than QBO Payroll or Gusto — expect 8 to 12 weeks for a clean rollout with data migration, configuration, and training. The pricing is six figures annually for many configurations. The argument for ADP at this scale is the compliance backbone — ADP has been doing payroll for 75 years and has a deep bench on multi-state, multi-jurisdiction, and complex compensation arrangements.

Where ADP is overkill. Anyone under 100 employees in a single state running simple payroll. The cost and complexity are not justified.

The decision framework we use. Walk through these in order with a client considering a switch.

Question 1: how many employees do you have today and where will you be in 24 months? Under 25 stable, stay with QBO. 25 to 100 growing, consider Gusto or Rippling. 100+ and complex, ADP or Rippling depending on the use case.

Question 2: do you have international or remote employees in states where you are not yet registered? If yes, the complexity changes the answer. Rippling handles global employer-of-record services natively. Gusto handles US multi-state well. QBO Payroll handles US multi-state but the registration is manual and slow. ADP handles everything but at a higher cost.

Question 3: how important is the QBO integration? If your bookkeeper depends on it, QBO Payroll has the cleanest integration with QBO. Gusto integrates well but it is not native. Rippling and ADP both integrate but the depth varies. Test the integration with sample data before you commit.

Question 4: do you have an IT or HR consolidation case? If your goal is one platform for HRIS, IT, and payroll, Rippling is the answer. If your goal is just payroll, Rippling is overkill.

Question 5: how much do you spend on the current payroll setup and how much can you afford? Run the numbers for each alternative based on your actual employee count and modules. The total cost of ownership often surprises people — the headline per-employee fee is not the whole story once you add benefits administration, contractor payments, and integration fees.

The migration itself. Switching payroll providers mid-year is painful. Year-end is the cleanest cutover — you finish the year on the old provider, issue W-2s from the old provider, and start January on the new provider. Mid-year migrations require importing year-to-date wage history into the new provider so the W-2s at year-end add up correctly across both systems. This is doable but error-prone. We strongly recommend year-end migrations unless the current provider is failing badly enough that waiting is worse than the migration friction.

Our default recommendation for NYC clients. Stay with QBO Payroll Premium until you hit one of three triggers. (1) You grow past 25 employees and the friction starts to add up. (2) You need real benefits administration and the patchwork bolt-on is breaking. (3) You have multi-state remote employees and the registration friction is causing notices. At any of those three points, evaluate Gusto first, Rippling if your team has IT consolidation needs, and ADP if you need a heavyweight compliance backbone. Skip the evaluation if QBO Payroll Premium is working — the switching cost is real and you want a real reason before you commit. Our client accounting services engagement includes payroll-provider evaluation as part of the standard scope for clients in transition.