If your business takes card payments through Stripe and keeps its books in QuickBooks, you have two systems that describe the same money in different ways. Stripe sees individual charges, refunds, disputes and fees. QuickBooks sees a single deposit landing in your bank account a few days later. A Stripe QuickBooks integration is what turns that one deposit back into the sales, fees and refunds behind it, so your books match your bank and your revenue reports are right.
This guide is for founders, finance leads and bookkeepers at SaaS, subscription and e-commerce businesses. It covers what a Stripe QuickBooks integration syncs, the three realistic ways to build one, how to set up the most common path, the problems that show up during reconciliation, what it costs, and when a custom integration is worth it.
What a Stripe QuickBooks Integration Syncs
The core job is reconciliation: matching every Stripe payout to the transactions that make it up. Intuit's own help documentation for its Stripe connector describes the data it moves into QuickBooks Online like this.
Sales. Each Stripe charge arrives as a "Payment received" transaction with the gross amount, the net amount and the fee, plus line item detail. Intuit says the connector syncs "most of the same details for each transaction in QuickBooks that you see in Stripe."
Refunds. Refunds are synced as their own transactions, so a refunded sale does not simply disappear from your revenue.
Payouts. Each Stripe payout is recorded as a bank deposit. Other items that affect a payout, such as holds, disputes, adjustments and Stripe Capital payments, appear inside that deposit.
Fees. Processing fees and other Stripe fees go to a Stripe Fees expense account. They sit inside the compound deposit rather than as separate lines.
Products and customers. When a Stripe product does not match a QuickBooks item, the connector uses a default Stripe Sales item and writes the Stripe item name into the description. You also choose default customer, product and vendor records in the settings.
The direction is one way: Stripe is the source, QuickBooks is the destination. Data does not flow back from QuickBooks to Stripe in the native connector. If you need QuickBooks invoices to create Stripe payment links, or Stripe subscription data to drive revenue recognition schedules in QuickBooks, that is beyond what the connector describes and usually means an app or custom work.
For subscription businesses there is a second layer that a basic sync does not cover: revenue by plan or tier, deferred revenue for prepaid annual plans, chargeback categorization and sales tax by state. Those are accounting decisions, and the integration has to carry enough detail from Stripe for your accountant to make them.
Integration Options
There are three real ways to connect Stripe and QuickBooks.
The native connector. Intuit offers "Stripe Connector by QuickBooks" for QuickBooks Online, installed from the Integrations area inside QuickBooks. It covers sales, refunds, payouts, adjustments and fees, and can import up to two years of history. It is the simplest path for a single Stripe account with ordinary card sales.
Third-party connector apps. Stripe's own documentation points QuickBooks Online users to third-party accounting integrations and to accounting apps in the Stripe App Marketplace that automate bookkeeping. (Stripe also offers an IIF export for QuickBooks Desktop, which QuickBooks Online cannot import.) Depending on the vendor, these apps may add options such as summary versus per-transaction posting, more detailed fee mapping, or support for more than one Stripe account. Features and prices change often, so check each vendor's own page for this exact pair before you commit. General iPaaS tools can also move Stripe events into QuickBooks if you are willing to build and maintain the mapping yourself.
Custom integration through the APIs. Stripe documents payout reconciliation through its API: its itemized payout reconciliation report lists every payment, refund, dispute, fee and other balance transaction in a payout, with optional subscription and invoice IDs and your own metadata, and Stripe sends webhook events when new report data is ready. A custom integration reads that data, applies your own rules, and posts exactly the entries your QuickBooks chart of accounts needs.
| Option | Best for | Limits | Cost basis |
| Native Stripe Connector by QuickBooks | One Stripe account, card sales, small to mid volume | One Stripe account at a time; no on-demand sync; fee detail lives inside deposits | No price listed on Intuit's help page; needs a QuickBooks Online subscription |
| Third-party connector app | More posting options, several accounts, more volume | Fixed mapping logic per vendor; monthly fees that often scale with transactions | Vendor subscription, see each vendor's pricing page |
| Custom API integration | Subscriptions, deferred revenue, multiple entities, high volume | Needs build and maintenance budget | One-time build plus upkeep |
If your QuickBooks file also connects to a store, the Shopify QuickBooks integration and WooCommerce QuickBooks integration guides cover how those payouts interact with Stripe.
How to Set Up the Native Stripe Connector in QuickBooks Online
This is the path most businesses try first. The steps below follow Intuit's own help article.
Before you start
You need an active Stripe account and admin access to QuickBooks Online. Decide which bank account in QuickBooks receives Stripe payouts. Talk to your accountant about the start date: if you already recorded Stripe deposits by hand, overlapping history will create duplicates.
Connect the app
- In QuickBooks Online, go to Integrations, then Find integrations.
- Search for "Stripe Connector by QuickBooks" and select Get integration.
- Log in to Stripe, then select Agree and Connect.
- Choose your Stripe Deposit Account, which is the bank account that receives payouts, and the Stripe locations you want to track.
- Pick a start date (up to two years back) and select Sync Now.
Review the first sync
When the sync finishes, open App Transactions. Intuit's article says transactions usually show up in For Review within about two hours of processing, and you cannot force an update on demand. Confirm "Payment received" transactions before the payout transactions they belong to; Intuit notes that transactions needing individual review cannot be bulk confirmed.
Check the settings
Open App Settings and review the defaults for customer, product, vendor and the Stripe Sales item. If your Stripe products have the same names as QuickBooks items, they can match; otherwise the default item is used. Note that a product category cannot be used as a line item, so a match to a category falls back to the default item.
Match to existing invoices
If you invoice customers in QuickBooks and they pay through Stripe, you can match synced Stripe transactions to existing invoices and sales receipts instead of creating new sales. Do this before confirming, or you will double count revenue.
Reconcile the bank account
Once payouts are recorded as deposits, reconcile the QuickBooks bank account against your bank statement as usual. Each payout deposit should equal what actually arrived, with fees, refunds and adjustments already netted inside it.
Common Problems and Limits
Most Stripe QuickBooks problems are reconciliation problems. These are the ones the official documentation points to, and the ones that follow from how the data is shaped.
Duplicate revenue. The most common mistake is recording a sale twice: once as a QuickBooks invoice or sales receipt, and again as a synced Stripe "Payment received" transaction. Matching to existing invoices before confirming avoids it. The same applies if a bank feed already imported the payout deposits before the connector was turned on.
Fees hidden inside deposits. Intuit says fees are "included in the compound deposit" and go to the Stripe Fees expense account. They do not appear as separate lines in the transaction list until the related sale is added or matched. If you only look at the bank feed, gross revenue looks lower than it is and fees look like zero.
Payouts that do not equal sales. A payout can include refunds from earlier days, dispute amounts, holds, adjustments and Stripe Capital payments. That is why a payout rarely equals one day of sales. A good integration ties each payout to its balance transactions; without that, bookkeepers end up with unexplained differences.
Only one Stripe account. Intuit's article says the connector "does not support multiple Stripe integrations at once." Businesses with several Stripe accounts, for example separate brands or regions, need an app or a custom build.
No on-demand sync. Data arrives on the connector's schedule, typically within about two hours. That is fine for bookkeeping, not for anything that needs real-time figures.
Multi-currency. Intuit's help article does not describe how the connector handles several currencies. If you charge in more than one currency or receive payouts in more than one, test it with your own data before relying on it.
Subscriptions and deferred revenue. The connector records cash events. It does not split a prepaid annual plan into monthly revenue or break revenue out by subscription tier. If you report under accrual accounting, someone has to post those adjustments.
Sales tax. Whether tax collected in Stripe arrives in QuickBooks with enough detail for state filings depends on how your Stripe products and tax settings are set up. Check this early if you sell into several US states.
Chargebacks and disputes. Disputes show up as items in payout deposits. If you want dispute losses and dispute fees in their own accounts for reporting, plan that mapping deliberately.
Costs
Native connector. Intuit's help article for Stripe Connector by QuickBooks does not list a price for the app. You need a QuickBooks Online subscription; check Intuit's current plan pricing, which is not reproduced here.
Stripe. Stripe's processing fees are the fees the integration records. They are set by your Stripe pricing, not by the integration.
Third-party apps. Connector apps publish their own pricing, usually a monthly subscription, often tiered by transaction volume or number of connected accounts. Prices change often, so compare current vendor pages.
Custom integration. There is no list price for a custom build; cost depends on the number of entities, transaction volume and how much accounting logic it carries. For context, Itexus states on its fintech software development page that discovery and prototyping engagements "start from around $30,000", and that enterprise fintech projects "often range from $150,000 to $1,000,000+". A focused Stripe to QuickBooks sync usually sits well inside a larger product build rather than being a project on its own.
When a Custom Integration Makes Sense
The native connector and off-the-shelf apps are the right answer for most small businesses. A custom integration starts to pay off in these situations.
Subscription revenue that needs accrual treatment. If you sell annual plans, offer several tiers, or report deferred revenue, a cash-based sync leaves your finance team posting manual journal entries every month. A custom integration can read Stripe subscription data and post revenue by tier and period.
More than one Stripe account or legal entity. The native connector supports one Stripe account at a time. Groups with several brands, regions or entities often need payouts routed into separate QuickBooks companies or classes with intercompany logic.
High volume and strict reconciliation. When thousands of transactions flow every day, small mismatches compound. A custom job can reconcile Stripe balance transactions against your own product database every night and flag drift before month end.
Your own product logic sits between Stripe and the books. Marketplaces, platforms and fintech products often apply credits, split payments or adjust balances in their own systems. The accounting entries have to reflect that logic, which a generic connector cannot see.
Compliance and audit requirements. Regulated businesses may need an audit trail from every journal entry back to the Stripe event, idempotent processing so retried webhooks never post twice, and card data that never leaves Stripe.
The accounting software integration guide explains these patterns across QuickBooks, Xero, NetSuite and Sage. If you are weighing ledgers, see also the Xero Stripe integration guide.
How Itexus Can Help
Itexus has delivered "120+ integrations delivered for neobanks, payment providers, robo-advisors, and trading systems", and integrates products with Plaid, Yodlee, Stripe, Adyen, Bloomberg and 50+ fintech APIs.
- Stripe to QuickBooks reconciliation. Payout sync that ties every deposit to its charges, fees, refunds and disputes.
- Subscription accounting. Revenue by subscription tier, deferred revenue for prepaid annual plans, and refund and chargeback categorization.
- Reliable event processing. Idempotent webhook handling and nightly reconciliation jobs that flag drift for review.
- Lower PCI scope. Card data kept inside Stripe Elements.
In a wealthtech platform rebuild for a 450K-subscriber investment advisory firm, Stripe payouts reconcile into QuickBooks with revenue recognition by subscription tier and state-level tax handling. Contact us to discuss your integration.
Itexus is a trusted partner
Itexus delivered the app according to the requirements. The team met all development milestones and deliverables. They were efficient, friendly, and cooperative. Itexus team was very timely with updates, a regular meeting cadence, and ad-hoc questions and answers via Slack. The team was very responsive and still is.
Stive Jackson
RMD, Investing Fund
Itexus’ work positions the business well for an imminent launch. They excel at managing their team, presenting frequent product demos to ensure that the project is aligned with development goals. An affordable price structure coupled with remarkable technical skill makes them an attractive partner.
Phill Osolinski
CEO Ryze Rewards
The assigned team was easy to work with and they are especially strong collaborators and communicators. They demonstrated flexibility, professionalism, and trust in everything they did, and completed the work on time and budget.
Sue Wollan Fan
CEO Mango Connects
Itexus excelled at both experimental AI and sprint-oriented UI/UX tasks. Itexus did strong project management work, too, a necessity in such a complicated project.
Jesse Dubin
Senior PM Standard&Poors
They’re a great group of developers who really understand the reality of business.
Andreea Vanacker
CEO SPARKX5
Frequently Asked Questions
Does QuickBooks have a native Stripe integration?
Yes. Intuit offers Stripe Connector by QuickBooks for QuickBooks Online. It syncs Stripe sales, refunds, payouts, adjustments and fees, records payouts as bank deposits, and can import up to two years of history.
How do I record Stripe fees in QuickBooks?
With the native connector, fees are categorized into a Stripe Fees expense account and included in the payout's compound deposit. If you record Stripe payouts by hand, record the gross sale, the fee as an expense, and the net amount as the deposit, so revenue is not understated.
Why doesn't my Stripe payout match my sales in QuickBooks?
A payout can include refunds, disputes, holds, adjustments and Stripe Capital payments as well as sales, and fees are deducted before it reaches your bank. Reconcile each payout against its underlying Stripe transactions rather than against a day of sales.
Can I connect more than one Stripe account to QuickBooks?
Not with the native connector: Intuit's help article says it does not support multiple Stripe integrations at once. For several accounts, use a third-party app that supports them or a custom integration.
What are the main Stripe accounting integrations?
The common options are Intuit's own Stripe connector for QuickBooks Online, accounting apps in the Stripe App Marketplace and other third-party accounting integrations, general iPaaS tools, and custom integrations built on Stripe's API and reports. Xero users have similar choices, covered in our Xero Stripe integration guide.
Is the Stripe connector enough for Stripe bookkeeping on a subscription business?
It handles cash events well: sales, refunds, fees and payouts. It does not split prepaid annual plans into deferred revenue or report revenue by subscription tier. Subscription businesses on accrual accounting usually add manual journal entries, a specialized app, or a custom integration.
