How to Connect Shopify to QuickBooks Online (UK Guide)

If you sell through Shopify and keep your books in QuickBooks Online (QBO), the goal is easy to state and fiddly to deliver: every order, fee, refund and payout should land in QuickBooks with the right VAT, and your Shopify Payments deposits should reconcile against your bank to the penny. Done well, your monthly close takes minutes. Done badly, you get a pile of unmatched transactions, double-counted income and a VAT return you cannot fully trust.

This guide sets out the realistic ways to connect Shopify to QuickBooks Online for a UK business: what actually needs to flow between them, how to handle fees, refunds, payouts and VAT, the summarised-versus-per-order decision that makes or breaks the setup, and when an off-the-shelf app is enough versus when middleware or a custom build earns its keep.

The short answer

For most UK stores, the right approach is a dedicated connector app that posts summarised entries grouped per payout into QuickBooks, so each entry matches a bank deposit exactly. The main routes are:

• A connector app — QuickBooks Connector (the tool formerly known as OneSaas), or a payout-aware specialist such as A2X or Link My Books. Best for the large majority of stores.
• Middleware (Zapier, Make) — useful glue for alerts and edge workflows, but weak as your primary accounting sync because it fires one action per order and ignores payouts.
• A custom integration against the Shopify and QuickBooks APIs — worth it at high volume, across multiple channels, or with unusual revenue recognition.

Whichever you pick, the decisive choice is what you sync and at what level of detail. Pushing every order in individually is the classic mistake.

What "connecting Shopify to QuickBooks" actually means

Shopify and QuickBooks describe money differently, so before choosing a tool, get clear on the jobs you need it to do:

• Orders / sales revenue — your takings, ideally split by product type, region or tax rate.
• Payment fees — what Shopify Payments (or Stripe/PayPal as a separate gateway) deducts before paying you. A real expense, not something to net away and forget.
• Refunds and chargebacks — money going back out, which must reduce income and reverse output VAT.
• Payouts — the actual lump sums that hit your bank, which rarely match a single day's orders.
• Customers and contacts — usually best left out of QuickBooks on a high-volume store.

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

Summarised vs per-order: pick the right granularity

There are two models for getting Shopify income into QuickBooks:

1. Per-order transactions. Each Shopify order becomes a QuickBooks sales receipt or invoice. This suits low-volume, high-value businesses (bespoke work, B2B wholesale) that genuinely want order-level detail in the ledger.
2. Summarised entries. Shopify activity is grouped — usually per payout — into one entry with lines for gross sales, shipping, discounts, fees, refunds and tax. The total matches the bank deposit.

If you process more than a handful of orders a day, summarised is almost always correct. Syncing per-order quickly buries QuickBooks under hundreds of entries a month, none of which line up with your bank deposits. Summarising keeps the ledger 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
QuickBooks Connector (OneSaas)	Simple, low-volume stores	Bundled with QBO; quick; official	Often per-order; weaker on payout matching and fee detail
A2X / Link My Books	Most ecommerce stores	Payout-level reconciliation; fees and VAT handled; accountant-friendly	Monthly fee scales with volume; ceiling on custom logic
Middleware (Zapier / Make)	Light glue, alerts, edge cases	Flexible; no code; connects many apps	Per-order by default; hard to reconcile payouts; cost climbs at volume
Custom integration	High volume, multi-channel, complex	Exactly your logic; full control; scales	Build cost; needs maintenance; only worth it past a threshold

Option 1: QuickBooks Connector (OneSaas)

QuickBooks Online ships with QuickBooks Connector (the former OneSaas), which can link Shopify and other apps to QBO. For a small, single-currency UK store with straightforward VAT it can be fine, and there is no extra subscription to find. The catch: it tends toward per-order syncing and is weaker on payout-level reconciliation and fee breakdown. Before relying on it, test exactly how it records payouts and payment fees — that is where the bundled option usually falls short.

Option 2: A2X and Link My Books

Tools such as A2X and Link My Books are purpose-built for ecommerce accounting. Rather than dumping individual orders, they group Shopify activity by payout and post a summarised entry into QuickBooks, breaking out gross sales, discounts, shipping, gift cards, payment 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. Link My Books leans into UK VAT logic; A2X is strong on multi-channel. The trade-off is a monthly fee that scales with volume, and a limit on how much unusual logic you can apply.

Option 3: Middleware (Zapier or Make)

Zapier and Make both have Shopify and QuickBooks connectors and are excellent for lightweight automation — drafting an invoice for a B2B order, posting an alert on large orders, or handling a specific edge case. Where they struggle is the core accounting job: out of the box they fire one action per order, recreating the per-order problem and not reconciling against payouts. You can build payout-aware logic in Make, but you are effectively rebuilding what A2X already does, and task pricing climbs at volume. Use them as glue, not as your primary ledger sync. We cover where these tools genuinely shine on our AI automation page.

Option 4: Custom integration

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

Reconciling Shopify Payments and Stripe payouts

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

• Gross sales for the orders included
• Less payment processing fees
• Less refunds and chargebacks settled in that batch
• Plus or minus any adjustments

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

Each gateway behaves differently:

• Shopify Payments exposes payout and balance-transaction data, so fees and timing can be reconstructed cleanly. This is the easiest case, and what dedicated apps handle best.
• Stripe (if used as a separate gateway) pays out on its own schedule with its own fee structure, reported through Stripe's payout and balance objects — a separate reconciliation stream. The same clearing-account discipline applies; our Stripe-to-QuickBooks guide goes deeper on that flow.
• PayPal is the classic headache: funds sit in a PayPal balance, fees are per-transaction, currency conversions happen inside PayPal, and bank withdrawals are separate events. It usually needs its own clearing account.

The robust pattern is a clearing (holding) account per payment method 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 balance represents money earned but not yet paid out. If it drifts to a strange figure, something is wrong — a useful early-warning signal.

VAT and multi-currency: the UK gotchas

This is where well-meaning setups quietly go wrong.

VAT

• 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.
• Payment fees and VAT. UK card processing fees are generally outside the scope of VAT, so there is normally no input VAT to reclaim on them; check how your tool codes the fee line, and confirm the treatment with your accountant if unsure.
• Cross-border rules. Sales to EU consumers and the OSS/IOSS schemes carry different VAT treatment; international sales need deliberate mapping, not a default.
• Marketplace facilitator rules. If you also sell via Amazon or eBay, the platform may account for VAT on certain sales, so those amounts must be treated differently from direct Shopify sales.

A good principle: your Shopify tax settings and your QuickBooks tax mapping have to agree. Most VAT errors come from a mismatch between what Shopify charged and what the sync recorded.

Multi-currency

• Decide whether you record in the presentment currency or your settlement currency, and stay consistent — mixing them creates phantom gains and losses.
• Gateways apply their 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 must be switched on deliberately and cannot be turned off afterwards, so plan before you enable it.

Common pitfalls to avoid

• Syncing every order as its own transaction. At any real 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 orders 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-order app pricing has become painful or summarisation needs to be smarter than the standard tools allow.
• Multiple stores or channels (Shopify plus Amazon, eBay, a B2B portal, EPOS) needing consolidated, consistent posting into one QuickBooks file.
• Unusual revenue recognition — subscriptions, deposits, deferred revenue, bundles — that standard summaries cannot express.
• Operational coupling — the same pipeline also updating a warehouse system, triggering fulfilment, or feeding a data warehouse for reporting.

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 reconciliation, margin you cannot see) clearly exceeds the build. As an indicative UK market guide, a focused Shopify-to-QuickBooks build commonly sits in the low-to-mid five figures depending on channels and complexity; treat that as a range to sanity-check quotes against, not a quote. 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 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 Shopify 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 such as A2X or Link My Books plus a small tweak is right for you, that is what we will recommend. If your volume, channels 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.