Most store owners start looking at a Shopify QuickBooks integration for the same reason. Shopify says the business sold a certain amount last month, the bank says a different amount arrived, and QuickBooks Online holds whatever the bookkeeper managed to type in from the payout reports. None of the three figures is wrong, exactly. They measure different things at different moments, and the job of the integration is to translate between them so that the books agree with the store and with the bank without someone rebuilding the month by hand.
That translation is harder than it looks, because Shopify thinks in orders and QuickBooks thinks in transactions, deposits and accounts. In this article I’ll go through what needs to move between the two systems, compare the realistic ways of connecting them (Intuit’s connector and other marketplace apps, an iPaaS such as Zapier, Make or Celigo, and a custom build), and spend most of the time on the accounting traps specific to this pair, since that’s where these projects succeed or fail. I’ll finish with testing and reconciliation, plus short notes on WooCommerce and Xero.
What actually needs to sync, object by object
Before choosing a tool, write down which system owns each kind of record. Much of the trouble in these setups comes from two systems that both believe they own products or customers, and quietly overwrite each other.
| Object | Direction | System of record | Common trap |
|---|---|---|---|
| Orders and sales | Shopify to QuickBooks | Shopify | Posting every order as revenue when the cash arrives later, net, in a payout |
| Payouts and deposits | Shopify to QuickBooks | Shopify Payments, confirmed by the bank | Adding the deposit from the bank feed as well as from the connector, so it lands twice |
| Processing fees | Shopify to QuickBooks | Shopify Payments | Fees buried inside a net deposit, so revenue is understated and no fee expense appears |
| Refunds and disputes | Shopify to QuickBooks | Shopify | Refunds netted out of a later payout, in a different period from the original sale |
| Sales tax | Shopify to QuickBooks | Shopify for the amount collected, QuickBooks for the liability | Taxes that Shopify remits on the merchant’s behalf being booked as payable a second time |
| Products and SKUs | Usually Shopify to QuickBooks | Whichever system the team edits in; pick one | Items matched by name, so a renamed product creates a duplicate |
| Customers | Shopify to QuickBooks, if at all | Shopify | One QuickBooks customer per guest checkout, and the customer list becomes unusable |
| B2B invoices and payment status | Both ways | QuickBooks for the receivable | Payment recorded in one system and never reflected in the other |
| Gift cards | Shopify to QuickBooks | Shopify | Treating a gift card sale as revenue when it’s a liability until redeemed |
It’s also worth asking whether QuickBooks needs every order at all. For many stores, a daily or per-payout summary with fees, refunds and tax broken out is what the accountant actually wants, and it keeps QuickBooks small. Per-order detail earns its place when someone uses it, for instance when B2B customers pay on invoice.
Your options: Intuit’s connector, marketplace apps, iPaaS or a custom build
Intuit builds its own connector. In QuickBooks Online it’s the Shopify Connector by QuickBooks, and on the Shopify App Store it appears as “QuickBooks Online” by Intuit Inc. According to Intuit’s US help article, each Shopify sale comes in as a payment received that becomes a sales receipt once confirmed, fees are recorded as expenses, refunds come in as individual refund transactions, and each Shopify payout becomes a deposit that moves the net amount from Undeposited Funds (or Payments to deposit) into the bank account you choose. B2B orders arrive as invoices linked to the company, and a payment recorded in QuickBooks can mark the Shopify order as paid. Transactions wait in a review queue unless you switch on automatic adding, and you can import up to twelve months of history when you first connect.
The Shopify App Store also carries several third-party accounting connectors, which differ mainly in how they summarize transactions, how much mapping control they give you, and how they handle stores that sell on several channels. Then there’s the iPaaS route. Zapier offers Shopify triggers such as a new paid order or a new refund and QuickBooks Online actions such as creating a sales receipt or invoice, Make publishes Shopify and QuickBooks templates, and Celigo lists a Shopify and QuickBooks integration covering products, orders and billing. Finally, there’s a custom build against the Shopify Admin API and the QuickBooks Online Accounting API, usually as a small service with its own queue and logs.
| Option | When it fits | Where it breaks |
|---|---|---|
| Intuit’s connector | One Shopify store, Shopify Payments, a standard chart of accounts, and a bookkeeper who’s happy reviewing transactions in QuickBooks | Unusual account mapping, several stores or sales channels, payment gateways and cases its documentation doesn’t describe, or anyone who needs the logic changed |
| Third-party marketplace app | You want summarized journal entries per payout, more mapping control, or one tool across Shopify and marketplaces | You inherit the vendor’s data model, and when it disagrees with your accountant’s, you work around it |
| iPaaS (Zapier, Make, Celigo and similar) | A specific gap the apps don’t cover, such as pushing B2B orders as invoices to a particular class, or a team that already runs its other integrations there | Per-order flows rarely handle payouts, fees and refunds as one reconciled unit, and retries can create duplicates unless someone designs for them |
| Custom build | Several stores or currencies, an ERP or 3PL in the middle, non-standard revenue recognition, or volume where you need control over batching and failure handling | It’s software you own, so it needs monitoring, an owner and maintenance when either API changes |
My view is that most single-store merchants should start with a packaged connector and move on only when they can name what it does wrong. A custom build earns its cost when the books depend on rules no product knows about, and even then the hard part is the accounting design.
The accounting traps specific to Shopify and QuickBooks
A payout is a bundle, and it’s net
The central fact of this pair is that Shopify Payments doesn’t deposit each sale. It pays out in batches, and the amount that reaches the bank is what Shopify now labels the payout balance – payments minus refunds, disputes and fees. Shopify’s API documentation also notes that a payout contains only the balance transactions that were available when it was issued, so an order placed late on a given day can land in the next payout. Orders and deposits will never line up one-to-one, and an integration that tries to match them that way will fail daily.
The correct model posts sales to a clearing account (Undeposited Funds or Payments to deposit, in QuickBooks terms), records fees and refunds against that clearing account, and then moves the net payout to the bank as one deposit. Intuit’s connector works this way, and Intuit’s guidance is explicit that you should match the bank feed line to the deposit the connector created, and never add it from the bank feed as well. A deposit recorded twice is one of the commonest reasons a Shopify bank account in QuickBooks won’t reconcile.
Fees, refunds and disputes that cross periods
Because fees are deducted before the money moves, a store that books only deposits understates both revenue and expenses. Refunds create a subtler problem. The refund belongs to the day it was issued, but the cash effect shows up in whatever payout comes next, and a dispute can reduce a payout weeks after the original sale. If the integration posts the refund to the original sale’s date, closed periods change underneath the accountant. Decide in writing which date governs each kind of adjustment, and hold the integration to it.
Sales tax, including tax Shopify remits for you
Sales tax is easy to double-count. Intuit’s documentation distinguishes merchant-liable tax, which goes on the sales receipt and into the liability for your tax agency, from marketplace taxes on certain Shop app sales, which Shopify often remits itself and which the connector books to Sales Tax Payable and then clears when the payout arrives. Whatever the tool, confirm that tax Shopify has already remitted doesn’t also sit in the liability you file.
Gift cards, products and customers
A gift card sold is a liability until it’s redeemed, and the connector records it that way through a gift card account. Custom flows often get this wrong and count the revenue twice. Products and customers are more a data-quality problem. Intuit’s connector matches products by SKU and name and won’t create a missing product automatically so a catalog with inconsistent SKUs will fill the review queue. With customer tracking off, sales post to a default customer, and for direct-to-consumer stores that’s often the better choice. Few accountants want forty thousand one-time buyers in their customer list.
Multiple currencies
Shopify Payments can pay out in a currency other than the one you sell in, and that gap has to be modeled. On the QuickBooks side, Intuit’s help is blunt that once Multicurrency is turned on it can’t be turned off, and the home currency can’t be changed afterward. That makes multi-currency a decision to take with your accountant before go-live, since the integration will be built around it.
History and the first import
Intuit’s connector imports up to a year back, and Shopify itself limits apps to the last 60 days of orders unless the app has been approved for the broader read-all-orders access. If you are cleaning up a long backlog, plan the historical load separately from the ongoing sync, and decide whether old periods should be posted at all or closed with summary journal entries.
A short note on WooCommerce and Xero
A WooCommerce QuickBooks integration raises the same questions with a different payment layer. WooCommerce stores often run more than one gateway, so there’s no single payout feed to anchor reconciliation, and each gateway’s deposits have to be cleared separately. The QuickBooks extension on the WooCommerce marketplace, QuickBooks Sync for WooCommerce by MyWorks Software, works with QuickBooks Online and Desktop and lets you post orders as invoices, sales receipts, sales orders or estimates, a choice that deserves the same thought as summary versus detail.
For a Shopify Xero integration, Xero lists a Shopify app on its own app store as built by Xero, with a choice between a daily summary and one transaction per sale, and automatic matching of payouts to the bank. The traps are the same, because they come from how Shopify pays out.
How to test and reconcile before you trust it
Testing an accounting integration means proving that the numbers tie out, which a sync without errors doesn’t do. I’d test in a sandbox company against orders chosen to be awkward: a normal card sale, a partial refund, a full refund in a later period, a discount code, a gift card sold and later redeemed, a shipping-only charge, a B2B invoice paid late, a dispute, and an order in a second currency if you sell in one. Each should land in QuickBooks exactly once, in the right account, on the date your written rules say.
Then reconcile three ways for at least one full payout cycle, and preferably a full month. Shopify’s payout report should equal the deposits in QuickBooks, payout by payout. The deposits in QuickBooks should match the bank statement with nothing left over in the clearing account except payouts still in transit. And sales, refunds, fees and tax in QuickBooks should agree with Shopify’s own finance reports for the same dates. Trace every difference to a cause before go-live, and write it down.
For a custom build or an iPaaS flow, add two more tests. Send the same Shopify event twice and confirm nothing is posted twice, because Shopify’s documentation warns that an app can receive the same webhook delivery more than once. Then deliberately make QuickBooks fail, since Intuit publishes per-company throttles on its API, and confirm that failed postings wait in a queue where someone can see them, instead of disappearing. After go-live, keep a daily reconciliation comparing payouts and deposits, with an alert on any gap. It’s the cheapest insurance an integration can have.
Related reading
- Integration reconciliation reports: proving two systems agree
- Idempotent webhooks: handling duplicate and out-of-order events
- Shopify ERP integration at peak
How we approach it at eProxim
eProxim has built ecommerce stores for more than 25 years and has engineered integrations between business systems since 1997, so we tend to start a QuickBooks Shopify integration with the accountant’s rules and only then pick the tool. Often the right answer is a packaged connector, carefully set up, and we’ll say so. When the business needs more, because of several stores, currencies, an ERP or a warehouse in the middle, we build the layer between the systems ourselves, with queues, idempotent posting and daily reconciliation as standard.
Small fixed-scope jobs are welcome, from fixing a connector that double-posts deposits to designing a custom payout sync, and we can usually start within a week, on a fixed price, by the hour or as a monthly block of hours. If you’re an agency with a client whose books won’t reconcile, our page for small agencies and dev shops explains how we work behind you. You can see more of our Shopify integration work, or tell us what isn’t reconciling.