How to Connect Stripe to QuickBooks Online (UK Guide)

If you take card payments through Stripe and keep your books in QuickBooks Online (QBO), the aim is simple to state and surprisingly fiddly to get right: every charge, fee, refund and payout should land in QuickBooks cleanly, with the correct VAT, and your Stripe deposits should reconcile against your bank to the penny. Done well, your monthly close takes minutes. Done badly, you end up with unmatched transactions, double-counted income and a VAT return you cannot fully trust.

This guide sets out the realistic ways to connect Stripe to QuickBooks Online for a UK business: what actually needs to flow between the two, how to handle fees, refunds and payouts, the VAT points that catch people out, and when an off-the-shelf tool is enough versus when a custom integration earns its keep.

The short answer

There are three broad routes:

• A connector app — Stripe's own "Connect to QuickBooks" app, or a dedicated tool such as Synder or Bridge by Commerce Sync. Best for most small UK businesses: quick to set up and good at the common cases.
• Zapier or Make — useful for light glue and edge workflows, but weak as your primary accounting sync because they tend to fire one action per charge and do not reconcile payouts.
• A custom integration against the Stripe and QuickBooks APIs — worth it at volume, with unusual revenue recognition, or when Stripe feeds more than just your ledger.

Whichever you choose, the single most important decision is what you sync and at what level of detail — because syncing every individual charge is the classic mistake.

What "connecting Stripe to QuickBooks" actually means

Stripe and QuickBooks describe money differently, so before picking a tool, get clear on which jobs you need it to do:

• Charges — the gross amounts customers pay you.
• Fees — what Stripe deducts before paying you (its standard UK rate for domestic cards is published on Stripe's pricing page; international and currency-conversion fees are higher). Fees are a business expense and must be recorded, not netted away and forgotten.
• Refunds and disputes — money going back out, which has to reduce income and reverse VAT, plus any dispute (chargeback) fees.
• Payouts — the actual lump sums Stripe transfers to your bank, which almost never match a single day's charges.
• Customers and invoices — optional, and usually best left summarised on a high-volume account.

The crucial insight: the money that hits your bank is not the same as your sales. When a customer pays £100, you do not receive £100, and you do not receive it immediately. You receive £100 minus Stripe's fee, batched into a payout that lands a day or several days later, usually combined with other charges, refunds and adjustments. A clean sync reconstructs that.

Per-charge vs summarised: pick the right granularity

There are two models for getting Stripe income into QuickBooks:

1. Per-charge transactions. Each Stripe charge becomes a QuickBooks sales receipt or invoice. This suits low-volume, high-value businesses (B2B services, bespoke work) that genuinely want transaction-level detail in the ledger.
2. Summarised entries. Stripe activity is grouped — usually per payout — into a single entry with lines for gross sales, fees, refunds and tax. The total matches the bank deposit. This is right for the large majority of businesses with any real volume.

If you process more than a handful of charges a day, summarised is almost always the correct choice. It keeps QuickBooks clean and turns reconciliation into a one-click match.

The ways to connect, compared

There is no universally "best" tool — it depends on volume, complexity, and how much you care about clean reconciliation.

Approach	Best for	Strengths	Weaknesses
Stripe's native QuickBooks app	Simple, low-volume accounts	Free; quick; official	Limited control; can create per-charge clutter; weak on payout matching
Dedicated apps (Synder, Bridge/Commerce Sync, etc.)	Most SMBs	Payout-level reconciliation; fees and VAT handled; multi-channel	Monthly fee scales with volume; ceiling on custom logic
Zapier / Make	Light glue, alerts, edge cases	Flexible; no code; connects many apps	Per-charge by default; hard to reconcile payouts; costs climb at volume
Custom integration	High volume, complex, multi-system	Exactly your logic; full control; scales	Build cost; needs maintenance; only worth it past a threshold

Option 1: Stripe's native QuickBooks app

Stripe publishes an official app in the QuickBooks app store that pulls your Stripe activity across. It is free and fast to switch on, which makes it tempting. For a small, single-currency UK business with simple VAT it can be perfectly fine. The catch is that the default behaviour often creates a transaction per charge and leaves you to match payouts manually, with limited control over fee and tax mapping. Before relying on it, test exactly how it records fees and payouts — that is where the simple options usually fall short.

Option 2: Dedicated connector apps

Tools such as Synder and Bridge by Commerce Sync are purpose-built for this job. Rather than dumping individual charges, the good ones group Stripe activity by payout and post a summarised entry into QuickBooks, breaking out gross sales, Stripe fees, refunds and tax, with a total that equals the deposit in your bank. That last point is the whole game: when the QuickBooks entry matches the bank line, reconciliation becomes one click. The trade-off is a monthly fee that scales with volume, and a limit on how much unusual logic you can apply.

Option 3: Zapier or Make

Zapier and Make both have Stripe and QuickBooks connectors and are excellent for lightweight automation — creating a draft invoice for a B2B charge, posting an alert on large payments, or handling a specific edge case. Where they struggle is the core accounting job: out of the box they fire one action per charge, which recreates the per-charge problem and does not reconcile against payouts. You can build payout-aware logic in Make, but you are effectively rebuilding what a dedicated app already does, and the task pricing climbs at volume. Use them as glue, not as your primary ledger sync.

Option 4: Custom integration

A custom build talks directly to the Stripe and QuickBooks APIs, applying exactly your mapping and reconciliation rules. More on when that is worth it below.

Reconciling payouts: the part everyone underestimates

This is the heart of a good Stripe-to-QuickBooks setup. For each Stripe payout, you need to reconstruct:

• Gross charges for the transactions included
• Less Stripe processing fees
• Less refunds and dispute amounts settled in that batch
• Plus or minus any adjustments

…to arrive at the net payout that matches your bank line in QuickBooks.

The robust pattern is a Stripe clearing (holding) account in QuickBooks. Sales and fees post to the clearing account; each payout moves the net amount from the clearing account to the bank. At any moment, the clearing account balance represents money earned but not yet paid out. If it drifts to a strange figure, something is wrong — which makes it a useful early-warning signal. Stripe exposes the underlying detail through its balance-transaction and payout objects, so a well-built sync can reconstruct every payout precisely.

VAT and multi-currency: the UK gotchas

This is where well-meaning setups quietly go wrong.

VAT

• Stripe fees and VAT. Treat Stripe's UK card processing fees as outside the scope of VAT — do not reclaim input VAT on them, and check how your tool codes the fee line. If in doubt, confirm the correct treatment with your accountant.
• Tax rates must map correctly. Standard-rated, zero-rated and exempt sales must hit the correct QuickBooks VAT codes. A summarised entry that lumps everything into one rate will misstate your return.
• Refunds reverse VAT. A refund is not just negative income — it reverses the output VAT too. Make sure your tool handles this automatically.
• Output VAT belongs to you. For direct sales, Stripe is a payment processor, not a marketplace facilitator, so you account for the VAT yourself. The amount QuickBooks records as VAT must agree with what your checkout actually charged.

Multi-currency

• If you sell in more than one currency, decide whether you record in the presentment currency or your settlement currency, and stay consistent — mixing them creates phantom gains and losses.
• Stripe applies its own FX rates, which will not match QuickBooks' daily rate. Those differences are real realised FX gains and losses and need an account to land in.
• QuickBooks multi-currency has to be switched on deliberately, and it cannot be turned off afterwards, so plan before you enable it.

Common pitfalls to avoid

• Syncing every charge as its own transaction. At any volume this floods QuickBooks and nothing matches your bank.
• Ignoring fees. Under-recording expenses overstates profit and distorts your VAT picture.
• No clearing account. Without one, payouts and sales fight each other and reconciliation never balances.
• Double-counting. If QuickBooks already imports your bank feed, make sure the sync is not also creating a separate deposit for the same money.
• Backdating a connection. Turning a tool on mid-period without handling historic transactions creates gaps or duplicates. Pick a clean cut-over date.
• Trusting it on day one. Run a parallel month against your old process before you rely on it.

When is a custom integration worth it?

Off-the-shelf tools cover the common cases well. A custom build earns its keep when you outgrow them. Signs it is time:

• High volume, where per-charge or tiered app pricing has become painful.
• Unusual revenue recognition — subscriptions, deposits, deferred revenue, usage-based billing — that standard summaries cannot express.
• Multiple systems — Stripe feeding not just QuickBooks but a CRM, a data warehouse or a fulfilment process from one pipeline.
• Bespoke tax logic across regions and schemes that no single connector maps correctly.

A custom build writes clean, payout-matched entries on your exact rules. The cost is real — design, build and maintenance — so it makes sense once the cost of getting it wrong (misstated VAT, hours of manual reconciliation, profit you cannot see) clearly exceeds the build. As an indicative UK market guide, a focused Stripe-to-QuickBooks build commonly sits in the low-to-mid four figures for a clean single flow, rising into five figures with multiple systems or complex tax logic — treat that as a range to sanity-check quotes against, not a quote in itself. There is often a sensible middle path: a dedicated app for the standard flow, plus a small custom piece for the edge case it cannot handle. That kind of pragmatic, vendor-neutral call is exactly what our API integration work is built around, tied into your wider data integration where reporting matters.

How APIwise can help

Getting Stripe and QuickBooks talking is rarely the hard part — getting them to reconcile cleanly, with the right VAT treatment and payouts that match your bank to the penny, is. As the UK's API and AI integration specialists, we are vendor-neutral: if a connector app plus a small tweak is right for you, that is what we will recommend. If your volume, systems or tax rules genuinely call for a custom build, we will scope and price it up front, fixed.

The simplest next step is our fixed-price Integration Health Check: we review how your systems connect today, find the gaps and risks, and give you a clear, costed plan. The fee is credited against any build that follows. You can also see how we work in detail on our API integration page.