The Stripe QuickBooks integration most small businesses use is the Stripe Connector by QuickBooks, which Intuit offers inside QuickBooks Online. It pulls in your Stripe sales, fees, refunds and payouts, and records each payout as a bank deposit linked to the sales and fees inside it. A second route is a Stripe app from a third-party developer, and a custom connection is the third.
This article follows Intuit’s and Stripe’s own pages as read in November 2026. Check their pages for current details and prices before you decide.
How the Stripe QuickBooks integration works
Stripe pays you in batches called payouts, usually one per business day, and takes its fees out before it pays. Your bank statement therefore shows one deposit that is smaller than the sales it covers. A good integration keeps the individual sales, the fees and the deposit together so the bank feed can be matched.
Intuit’s connector does this with three kinds of record. Each sale appears as a “Payment received” transaction with its gross amount, net amount and fees. Fees are recorded as an expense tied to the sales receipt and categorised to a Stripe Fees account. When you add a payout, QuickBooks records a bank deposit linked to the sales and fees that make it up. Holds, disputes, adjustments and Stripe Capital payments show in a section of the deposit for adding funds (Intuit: connect and manage Stripe transactions).
Setting up the Stripe Connector by QuickBooks
Intuit lists the steps. You need an active Stripe account and QuickBooks Online.
- In QuickBooks Online, go to Integrations, then Find integrations, and search for “Stripe Connector by QuickBooks”.
- Select Get integration, sign in to Stripe and choose Agree and Connect.
- In the app settings, pick the bank account where Stripe pays your payouts and the Stripe locations to track.
- Choose a start date for importing transactions. Intuit says you can go back up to two years.
- Select Sync Now. Imported items appear under App Transactions within a few minutes.
Intuit recommends keeping the default app settings. Pick the start date with your bookkeeper: if last year’s Stripe sales are already in the books, starting before that date creates duplicates.
What the connector cannot do
These limits are all from Intuit’s help article, and they decide whether the connector is enough for you.
- Only one Stripe integration can be connected at a time.
- You cannot run a sync on demand. Completed transactions usually appear within about two hours.
- If a Stripe item does not match a QuickBooks product or service, the sale uses a default “Stripe Sales” item and the Stripe item name goes in the description.
- Product categories cannot be used as items on sales.
- Some transactions need a manual review before you can add them, and when you confirm in bulk, payments have to be confirmed before payouts.
The connector also puts each transaction in a review queue first. That is a feature for a careful bookkeeper and a chore for a business with hundreds of small payments a week.
The other route: a third-party Stripe app
Stripe’s documentation lists QuickBooks Sync by Acodei, a Stripe app built by a third-party developer. Stripe says it syncs sales, fees, payouts, refunds, invoices, customers, products and taxes, in real time per transaction or as a daily total for large volumes. It can also map product types to QuickBooks accounts. Stripe describes a free user tier and a free trial for paid tiers, and points to the developer’s pricing page for the tiers (Stripe: accounting software integrations).
The difference to weigh is how much sits between the sale and the books. The Intuit connector queues items for your review. The third-party app offers mapping rules and a daily summary option, which suits volume but needs someone to set the rules once and check them regularly.
How to record payouts and fees so the bank feed matches
This is where most books go wrong, so agree it before connecting anything. Here is a worked example with made-up numbers: a customer pays $500, Stripe takes $15.20 in fees, and $484.80 arrives in your bank on the next business day. The books should show a $500 sale, a $15.20 fee expense and a $484.80 deposit. If the sale is booked at $484.80 instead, income is understated and the fee is invisible.
Questions to settle with your bookkeeper:
- Which bank account receives Stripe payouts, and is it the one selected in the connector?
- Do you book sales at the gross amount with fees as an expense? This is how Intuit’s connector behaves.
- Who handles refunds and disputes, and where do they show?
- Do you also take payments outside Stripe, such as cheques or bank transfers, that need matching to invoices?
- Do you add transactions through the app first and match the bank feed second, or the reverse? Mixing the two is a common cause of doubled deposits.
If you already create invoices in QuickBooks and let customers pay them by card, check which invoice and payment records the connector creates before you turn it on. Run it for a week on a start date of today, compare it with the bank, then go back in time.
What to check in the first month
A new connection looks fine on day one and goes wrong quietly. Set a short routine for the first month so a problem is caught while it is small.
- Week one. Compare one Stripe payout with the matching bank deposit and the deposit record in QuickBooks. The three amounts should agree to the cent.
- End of the first month. Add up the Stripe Fees account and compare it with the fees total in the Stripe dashboard. A gap usually means refunds, disputes or an item that was never added from the review queue.
- Any month. Look for sales booked to the default “Stripe Sales” item. Each one is a product that has no match in QuickBooks, so reports by product will be wrong until you add or rename it.
- Quarter end. Confirm nothing from before your start date was imported twice, and that payments taken outside Stripe are matched to their invoices.
If a number does not agree, fix the cause rather than the symptom. Editing a deposit to make it balance hides the problem and returns it next month.
When a custom connection is worth it
The two off-the-shelf routes cover the common case. A custom connection is worth a conversation when your payments carry rules the apps do not know about: a deposit that must be applied to a specific job, a subscription that needs revenue split across months, tips or tax that go to different accounts, or Stripe sitting alongside a booking or CRM system that should create the invoice. CentriWeb builds these in n8n for clients and looks after them, as part of its run with less admin service. We build custom, so weigh our view with that in mind.
It does not suit a business with a few payments a week and a bookkeeper who is happy to review each one. The free connector is the right answer there. For related set-ups see Square and QuickBooks, HubSpot and QuickBooks, and for the payments side of the business our payments work.