Stripe QuickBooks integration: how to set it up

Agree the posting rules first

Before choosing a tool, agree with your accountant where each kind of Stripe activity goes. Most setups use a Stripe clearing account: an account in QuickBooks that holds Stripe activity until the payout lands. Payments go in, fees and refunds come out, and each payout moves the balance to your real bank account. When everything is recorded, the clearing balance equals what Stripe still owes you.

Decide as well how sales tax, discounts and other currencies should appear, and how a payment finds its customer. These rules, more than the brand of connector, decide which option can do the job.

The ways to connect them

There are four broad options. Start with the simplest one that posts what your accountant needs.

When Intuit's Stripe Connector is enough

QuickBooks Online has its own Stripe Connector under Integrations. It imports sales, refunds, payouts and adjustments, records fees in a Stripe Fees expense account and can bring in up to two years of history. Transactions arrive in the For Review list, usually about two hours after Stripe finishes processing them, and someone confirms them there.

It suits a single Stripe account with a manageable list of products. Know its limits: it connects one Stripe account at a time, items it can't match go to a default Stripe Sales item, and payments and payouts have to be confirmed in order. If nobody works through the review list every week, the books fall behind.

When a sync app fits better

Apps such as Synder, PayTraQer or Acodei's QuickBooks Sync in the Stripe App Marketplace post transactions automatically and add rules: different income accounts by product, currency or payment method, and a choice between recording each transaction or a daily or per-payout summary. Summary sync keeps QuickBooks lean at high volume; per-transaction sync keeps a detailed trail. Either way, each payout should still match one bank deposit.

They charge a monthly fee that grows with volume, and their mapping only goes so far. Test refunds, partial refunds and disputes on a sandbox or copy company before you rely on them.

When to build a custom sync

A custom integration pays off when the ready-made options can't express how your business works. These are the usual signs:

• Invoices are created in your own app or CRM and must become QuickBooks invoices for the right customer, then be marked paid when Stripe collects.
• You run a Stripe Connect platform or marketplace with many connected accounts.
• Several companies, currencies or Stripe accounts feed one or more QuickBooks companies.
• Deposits, partial payments, credit notes or subscriptions need posting rules the apps don't offer.
• You need to trace each order to its payment, fee and payout.

What a reliable sync does

Whatever you build or buy, check that it handles the cases that cause month-end clean-up:

• Each Stripe event is recorded once, even when Stripe sends the same webhook again.
• It keeps a map from Stripe IDs to QuickBooks IDs, so a refund finds its original sale.
• Failed writes are retried, and anything still failing lands in a list a person can replay.
• A daily check compares Stripe payouts with QuickBooks deposits and reports differences before month end.
• It runs against a sandbox or copy company with a week of real transactions before going live.

Switching on without double counting

The most common mistake is recording the same period twice: once by hand or by an old connector, and again by the new one. Pick a start date, stop the old method from that day, and compare the first few payouts by hand against the bank before you trust the totals.

Frequently asked questions