Gusto and QuickBooks Online: payroll entries

The Gusto QuickBooks integration does one thing: after each payroll, it writes a journal entry into QuickBooks Online. It does not record Gusto’s own invoice or the payments you make to benefit providers. That entry is complete and correct only if every Gusto category is mapped to the right account, and it stays correct only if nobody also adds the same payroll from the bank feed. Most Gusto files that need fixing have payroll in the books twice.

This post covers connecting Gusto, the mapping table, a full payroll entry worked through with the bank debits it has to match, and the settings that decide how it looks in QuickBooks. It is the payroll page in a series on apps that feed QuickBooks Online, alongside recording payment processor payouts in QuickBooks Online.

Connecting Gusto to QuickBooks Online

The connection starts in Gusto, not in QuickBooks. Gusto’s steps (Gusto, Integrate with QuickBooks Online, read October 22, 2026):

1. In Gusto, go to the App directory, search for QuickBooks Online, and select Connect.
2. Sign in to QuickBooks Online and select Authorize. You need admin permissions in both Gusto and QuickBooks. An accounting firm picks the firm first, then the client company.
3. Review the settings Gusto recommends.
4. Map every Gusto category to a QuickBooks account.
5. Optionally, choose QuickBooks classes for the entries.
6. Select which payrolls already run this year to sync.

Gusto pulls the chart of accounts from QuickBooks Online, so an account has to exist in QuickBooks before it can be mapped. If one is missing, create it in QuickBooks, then select Refresh accounts in Gusto.

Step 6 is where a file most often gets doubled. Gusto offers to sync the W-2 and 1099 payrolls already run in the fiscal year. If those months were already entered by hand or from the bank feed, syncing them again records payroll twice. Gusto itself says it does not recommend syncing a payroll for a period where the books are already closed.

The mapping table

Every Gusto category must be mapped, even one that does not apply yet; Gusto leaves an unused category off the entry. These are Gusto’s category groups and the account type it says each one typically maps to (Gusto, Account mapping types), with the QuickBooks account names used in this post:

Gusto category	What it holds	Account type	Account in this post
Bank Account	The money Gusto debits	Bank	Operating Checking
Wages and Salaries	Gross pay: net pay plus employee taxes and deductions, by earning type	Expense	Wages and Salaries
Employer Taxes	The company’s payroll taxes	Expense	Employer Payroll Taxes
Benefit Expenses	Employer contributions to a benefit	Expense	Employee Benefits
Benefit Liabilities	Employee and employer contributions owed to the provider	Liability	401(k) Payable
Deductions and Garnishments	Post-tax amounts withheld from pay	Liability	Payroll Deductions Payable
Reimbursements	Expenses repaid to employees	Expense	Auto and Mileage
Taxes Payable	Taxes Gusto records but does not pay, such as NY SDI	Liability	Payroll Taxes Payable
Taxes Receivable	Refunds an agency owes the company	Asset	Payroll Tax Refunds Receivable

Gusto does not support Accounts Receivable or Accounts Payable accounts in the mapping, because those need a customer or vendor on each line.

Two lines in that table surprise people:

• Wages and Salaries is gross pay. Gusto puts net pay, employee taxes and employee benefit contributions all into Wages and Salaries, so the expense is what the employees earned, not what they took home. There is no line for employee tax withholding as a liability, because Gusto takes those taxes out of the bank on the debit date.
• Benefits and deductions stay in your bank. Gusto says “we do not take any money for benefits or deductions.” It records what is owed as a liability, and you pay the provider yourself. The liability clears when that payment is recorded against it.

Set default mappings too. When you add a deduction, an earnings type, a benefit or a new state, Gusto creates new categories, and an unmapped one stops the sync until someone maps it.

A Gusto payroll, from the register to the bank

A four-person design studio pays semi-monthly through Gusto on 2-day processing. The payroll for the October 16, 2026 check date, from Gusto’s payroll register:

Gusto payroll, check date October 16	Amount
Gross wages, 4 employees	12,000.00
Federal income tax withheld	−1,150.00
Social Security withheld, 6.2%	−744.00
Medicare withheld, 1.45%	−174.00
State income tax withheld	−480.00
401(k) deferrals, 5%	−600.00
Net pay	8,852.00
Employer Social Security and Medicare	918.00
Employer 401(k) match, 3%	360.00
Mileage reimbursement	85.00

Employer taxes are only the 6.2% and 1.45% matches because, by October, all four employees have passed the $7,000 federal unemployment wage base, and in this example the state’s base too. Earlier in the year the same entry carries federal and state unemployment tax as well.

On 2-day processing, Gusto debits the bank two business days before payday, Wednesday, October 14, in three separate debits: “one for employee pay,” “one for employee reimbursements” and “one for all payroll taxes” (Gusto, Processing payroll overview). The tax debit is the employee taxes withheld plus the employer’s share: $1,150.00, $744.00, $174.00 and $480.00, plus $918.00, for $3,466.00.

The entry Gusto syncs, dated on the debit date:

Date	Account	Debit	Credit
Oct 14	Wages and Salaries	12,000.00
Oct 14	Employer Payroll Taxes	918.00
Oct 14	Employee Benefits	360.00
Oct 14	Auto and Mileage	85.00
Oct 14	Operating Checking		8,852.00
Oct 14	Operating Checking		85.00
Oct 14	Operating Checking		3,466.00
Oct 14	401(k) Payable		960.00

Debits and credits are $13,363.00 each. The bank is down $12,403.00 in the three amounts it will show, and 401(k) Payable holds $960.00, the employees’ $600.00 plus the $360.00 match, until the studio pays the plan provider. When it does, that withdrawal is categorized from the bank feed to 401(k) Payable, not to an expense, which brings the liability back to zero.

Matching the three debits

On the bank statement, Gusto’s debits carry codes: NET for net pay and TAX for taxes, among others. When the three withdrawals of $8,852.00, $85.00 and $3,466.00 appear under Transactions, then Bank transactions, each one is already in the books through the synced entry. Match each to the entry. Do not add it.

Adding them is the duplicate-payroll error. If the $8,852.00 and $3,466.00 withdrawals are added as payroll expense on top of the synced entry, the profit and loss shows $12,318.00 of payroll that never happened. The bank reconciliation still balances, because the added withdrawals are the ones ticked off; the synced entry’s bank lines just sit uncleared, month after month. Old uncleared Gusto lines on the reconciliation are the sign to look for. A bank rule that auto-adds anything from “Gusto” to payroll expense does this every payroll without anyone seeing it. The general fix is in duplicate transactions in the bank feed.

Two kinds of payroll withdrawal are not in the synced entry and are added from the bank feed: the monthly Gusto invoice, which Gusto says it cannot sync, and payments to benefit providers. The invoice is a Payroll Service Fees expense. The benefit payments go to their liability accounts.

Gusto settings that change the entry

Four settings in Gusto’s Manage tab decide how the entry looks in QuickBooks, and the entry date is the one to set first:

Setting	Options	What to pick
Entry date	Check date, debit date, or end of pay period	Debit date, so the entry and the bank withdrawals land on the same day
Employer tax consolidation	One payroll tax amount, or each tax separately	Separate if you want FUTA, state unemployment, Social Security and Medicare on their own lines
Journal entry consolidation	One entry, or split by employee, department, job or Gusto project	Split by department or job only if the profit and loss is reported that way
Contractor payments	Each as its own entry, or batched per pay date	Batched past about 30 contractor payments; Gusto syncs batches at 5 PM PT on the processing date

Classes can be added to a split entry, one class per employee, department, job or project grouping. Gusto does not split an employee’s wages across several classes, and it does not integrate with QuickBooks Projects, so job costing by QuickBooks project needs a separate entry.

A payroll that is already matched or reconciled cannot be re-synced from Gusto until its bank matches are undone in QuickBooks. If a mapping changes after a reconciled month, fix the past entries by hand, not by re-syncing.

Owner salary and S corporations

An S corporation owner who works in the business is paid through Gusto like any other employee, and the synced entry posts that salary to Wages and Salaries or a separate Officer Compensation account if you map one. Distributions are not payroll and never go through Gusto. How much salary is reasonable, and how distributions are recorded alongside it, is in S corp reasonable salary.

Gusto vs QuickBooks Payroll

Both run payroll and work with QuickBooks Online; the difference for the books is where payroll lives. Gusto is a separate system that sends a journal entry per payroll, so the mapping above has to be kept up as benefits and deductions change. QuickBooks Payroll runs inside QuickBooks Online, so there is no sync to set up. On price, Gusto listed its Simple plan at $49 a month plus $6 per person, Plus at $80 plus $12 and Premium at $180 plus $22 (Gusto pricing), with QuickBooks Online billed separately. Intuit sells payroll as a bundle with QuickBooks Online, listed from $88 a month plus $7 per employee for payroll with Simple Start before promotions (QuickBooks payroll pricing). Both pages were read October 22, 2026. The cost comparison depends on headcount and on which QuickBooks plan the business needs anyway.

Common questions about Gusto and QuickBooks

Can you do bookkeeping with Gusto?

No. Gusto keeps payroll records: pay stubs, tax filings, benefits and the payroll register. It has no record of sales, bills, other bank accounts or loans, so the books still live in QuickBooks Online, and Gusto’s entry is one input to them.

Is Gusto cheaper than QuickBooks Payroll?

It depends on headcount and on the QuickBooks plan. At the list prices above, four employees on Gusto Simple cost $73 a month ($49 plus 4 × $6), with QuickBooks Online paid on top. Intuit’s bundle for the same four costs $116 ($88 plus 4 × $7), and it includes QuickBooks Online Simple Start. Gusto is cheaper only when the QuickBooks plan the business would pay for anyway costs less than the $43 difference.

Does Gusto pay payroll taxes to the IRS?

Yes. The tax debit Gusto takes from your bank covers the employee taxes it withheld and the employer’s share, and Gusto says “tax amounts go to the applicable state and federal agencies.” The exceptions it records as Taxes Payable, such as NY SDI, are ones it does not pay, so those stay with the business.

Does Gusto work with QuickBooks Desktop?

Yes, through a separate Gusto integration. You upload your chart of accounts from Desktop as an IIF file, map it in Gusto, and Gusto exports each payroll’s journal entry as an IIF file to import into QuickBooks Desktop (Gusto, Integrate with QuickBooks Desktop).

What happens if I set up the integration mid-year?

Gusto lists the payrolls already run this fiscal year and lets you choose which to sync. Sync only the ones not already in the books. If earlier payrolls were entered from the bank feed as a single expense, either leave them and start the sync from the next payroll, or remove those entries first and sync the year, never both.

Payroll in the monthly close

A Gusto file stays right when someone checks each payroll the month it runs: the synced entry against Gusto’s register, the three debits matched, the benefit liabilities back to zero after each provider payment, and payroll expense against the prior month. That is part of a monthly bookkeeping close, with every account reconciled each month.

$99per file, per month

When to hand this off: if payroll has been both synced from Gusto and added from the bank feed, or the benefit liabilities have grown for months without coming back to zero, the payroll months have to be rebuilt against Gusto’s registers before the profit and loss is right. A free file review counts the months first.