E-commerce
Connect Shopify and QuickBooks
Books that reconcile to the payout, not just to the order total.
- Connects
- Shopify and QuickBooks
- Data flows
- 4 automated, two-way where safe
- Built with
- Shopify Admin API, Shopify Payments payouts, QuickBooks Online API
- Timeline
- Live in 3 to 5 business days from scope
- Owned by
- You. Accounts, credentials and code in your name.
In short
Connecting Shopify to QuickBooks means posting sales, fees, refunds and payouts so the ledger reconciles against money received. Most integrations post the order total and ignore payment processing fees and payout batching, which is why the bank line never matches. SBD builds it around the payout, not the order.
The workflows
What runs between Shopify and QuickBooks.
Each line is one automated workflow. An event in one tool, the checks and mapping in between, the action in the other, and the person who hears about it.
-
Bank reconciliation that matches without manual adjustment
WhenShopify payout batch closes
Automation- Verify and validate
- Map and normalise
- Upsert by key
ThenPost a journal splitting gross sales, processing fees and net deposit
And- Audit log entry
- Alert if it fails or goes quiet
- Review queue if unsure
-
Accurate margin reporting net of processing fees
WhenOrder paid
Automation- Verify and validate
- Map and normalise
- Upsert by key
ThenRecord the sale against the correct income account and tax code
And- Audit log entry
- Alert if it fails or goes quiet
- Review queue if unsure
-
Refunds and chargebacks reflected correctly in the ledger
WhenRefund issued
Automation- Verify and validate
- Map and normalise
- Upsert by key
ThenPost a linked credit note allocated across the original line items
And- Audit log entry
- Alert if it fails or goes quiet
- Review queue if unsure
-
Summarised journals instead of thousands of individual invoices
WhenReconciliation mismatch detected
Automation- Verify and validate
- Map and normalise
- Upsert by key
ThenFlag for review rather than forcing a balancing entry
And- Audit log entry
- Alert if it fails or goes quiet
- Review queue if unsure
Every record passes through the same stages
- 1Receive
Webhook or polling from the source tool, with a signed payload and a replay log.
- 2Validate
Required fields present, types right, record key found. Anything else goes to the review queue.
- 3Map
Fields translated to the destination schema. Enumerations, currencies and dates normalised.
- 4Upsert
Written against the record key, so a retry updates rather than duplicates.
- 5Confirm
Outcome logged. Alert if the count goes quiet. Reconciliation run nightly.
Read this first
Why the obvious route breaks.
A one-step Zap connects Shopify and QuickBooks in an afternoon. This is what goes wrong once real volume and real edge cases arrive.
The order total is not what hits the bank
Shopify Payments deducts fees and batches many orders into one payout. If you post gross order totals, every payout line has to be reconciled by hand forever. The payout is the unit that has to be modelled.
Refunds and partial refunds post as new events
A refund is not a deleted order. It needs its own credit entry linked to the original, and partial refunds need to allocate correctly across line items and tax.
Tax handling is not a single field
Multi-jurisdiction tax, and GST in India, do not map to one QuickBooks tax code. Getting this wrong is worse than no integration, because the books look reconciled while being wrong.
High order volume needs summarisation
Thousands of individual invoices will bloat QuickBooks and slow it down. Most businesses want daily or payout-level summary journals, with detail retained elsewhere for drill-down.
What it costs today
The gap, as the team feels it and as the engineer sees it.
In the team
- The bank line never matches the sales total
- Fees and refunds are adjusted by hand at month end
- Thousands of tiny invoices clog the books
- Tax collected is a guess until the accountant fixes it
- Margin reports are wrong by the processing fee
Under the hood
- Order totals are not what lands in the bank
- Payouts batch many orders, fees and refunds together
- Multi-currency orders settle in one currency
- Tax codes map differently per region
- Per-order invoices hit QuickBooks limits and slow the file
What we wire up
The data flows.
- 01 When
Shopify payout batch closes
ThenPost a journal splitting gross sales, processing fees and net deposit
- 02 When
Order paid
ThenRecord the sale against the correct income account and tax code
- 03 When
Refund issued
ThenPost a linked credit note allocated across the original line items
- 04 When
Reconciliation mismatch detected
ThenFlag for review rather than forcing a balancing entry
Used for
- Bank reconciliation that matches without manual adjustment
- Accurate margin reporting net of processing fees
- Refunds and chargebacks reflected correctly in the ledger
- Summarised journals instead of thousands of individual invoices
- Shopify payouts to QuickBooks
- Shopify to QuickBooks reconciliation
- E-commerce bookkeeping automation
- Shopify fees and refunds in QuickBooks
- Summary journals per payout
- Shopify sales tax in QuickBooks
Built with
Data map
What becomes what, and what it is keyed on.
| In Shopify | In QuickBooks | Matched on | Direction |
|---|---|---|---|
| Payouts | Deposit with fees as a line | Payout ID | one-way |
| Orders, refunds, discounts | Summary sales receipt or journal per payout | Payout ID | one-way |
| Taxes collected | Tax liability line | Payout and tax code | one-way |
| Products | Items, where line-level posting is used | SKU | one-way |
Field-level mapping is agreed in the blueprint and written into the runbook. Two-way rows carry loop protection so a write from the sync never re-triggers the sync.
In every build
What you get with the sync, whichever pair.
Under the hood
- Upserts keyed on the record
Every write is matched on the source ID. A retry or a re-fire updates the existing record instead of creating a second one.
- Retries with backoff
Rate limits and timeouts are retried with increasing delays, then parked for review, never dropped.
- Idempotent, loop-safe writes
Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.
- Reconciliation
A nightly job compares counts and totals on both sides and lists any record that differs.
- Audit log
Every run records input, mapping result, action taken and who or what triggered it. Searchable by record.
- Error monitoring
Loud failures alert within minutes. Quiet ones are caught by an outcome count that alerts when it stops moving.
- Review queue
Records the sync is not sure about land in a screen a person can read, correct and release.
- Scoped credentials
One credential per connection, limited to the objects it needs, stored encrypted, in your account.
For the team
- Slack or email notifications
The alerts go to a named person, not a channel nobody reads. You choose Slack, email, WhatsApp or all three.
- A runbook
One document per integration: what it does, what each alert means, and what to do in the first ten minutes.
- Training
A live session with the people who will use the review queue, recorded for whoever joins later.
- Handover
Admin access, billing and code sit in accounts in your name from day one. If we leave, it keeps running.
- Sixty days of hypercare
The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.
- A monthly report
Runs, records synced, exceptions handled, and what changed. Plain language, one page.
Security and your data
Where the data goes, and who holds the keys.
- Accounts
- Every platform account is created in your name. We work through managed access you can revoke.
- Credentials
- Stored encrypted in the orchestration layer. Scoped per connection. Rotated on handover.
- Data in transit
- TLS everywhere. Webhooks verified by signature before anything is processed.
- Data at rest
- Only what the sync needs. No copies of your customer data on our machines.
- AI steps
- Where an integration uses a model, it is through a business API that does not train on your data.
- Retention
- Run logs kept 90 days by default, adjustable. Payloads redacted of card and ID numbers.
- Agreements
- DPA and NDA on request. Regional rules covered in our privacy policy.
Keys and sensitive data
How API keys, tokens and personal data are handled.
- Keys live in a vault, never in code
API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.
- One credential per connection
Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.
- Service accounts, not personal logins
Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.
- Two-factor on every account
Every platform account we set up has two-factor authentication on, with recovery codes handed to you, not kept by us.
- Rotation on handover and on request
Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.
- Secrets never reach the logs
Audit logs redact tokens, card numbers, government IDs and anything you flag as sensitive before a line is written.
- Webhooks verified before processing
Inbound calls are checked against the sending tool's signature. Unsigned or stale payloads are dropped and counted.
- Access you can see and revoke
Our access is through managed roles in your accounts. You can list it, limit it, and remove it in one click without touching the build.
Engineering decisions
Decided before the first workflow is written.
- Rate limits and backoff
Every API has a ceiling. Calls are batched, queued and retried with increasing delays so a busy hour does not become a failed one.
- Backfill and pagination
The first run has to load history, not just new events. Backfills page through the source in order, resume after interruption, and never double-write.
- Out-of-order and duplicate events
Webhooks arrive twice and out of sequence. Each event carries a version or timestamp, and older versions never overwrite newer state.
- Schema changes
A renamed field or a new dropdown value is the most common silent failure. Payloads are validated against a contract, and a mismatch stops the run and raises a flag.
- Time zones, currencies, units
Dates are stored in UTC and shown local. Money carries its currency. Quantities carry their unit. Conversions happen once, in the map step.
- Sandbox first
Builds run against sandbox or test accounts with seeded data before they touch production. Go-live is a switch, not a rewrite.
- Versioned and reversible
Workflows and code are version-controlled. A release can be rolled back in minutes without losing the records processed since.
- API deprecations watched
Tools retire API versions on a schedule. We track the dates for every connection in the runbook and upgrade before the cut-off.
- Cost per run known
Each workflow has a cost per execution, including any model calls, logged alongside the run. You see the bill before it arrives.
- Metrics, not just errors
Runs per hour, records in and out, exception rate and latency are charted. Trends show a problem before an alert does.
The offer
Hire SBD to connect Shopify and QuickBooks.
A fixed scope, agreed in a thirty-minute call, and live in three to five business days. Accounts in your name. The engineers who built it on call for sixty days after.
- ScopeThirty minutes to agree the flows, the fields and the owner. Written up the same day.
- Build4 workflows, the data map above, validation, upserts, retries and reconciliation.
- Go-liveSandbox first, then a switch. Day three to five from scope for most pairs; longer only if a tool needs approval, such as WhatsApp templates.
- HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
- AfterSixty days of hypercare, then a care plan or run it yourself.
Questions
What people ask about this pair.
Should every order become an invoice in QuickBooks?
Usually not. Past a few hundred orders a month, per-order invoices bloat the file and slow everything down without adding insight. We typically post summary journals per payout or per day, and keep line-level detail in the operational system where drill-down happens.
Can you handle tax correctly?
Yes. Tax mapping, whether GST, VAT or sales tax, is part of scoping rather than an afterthought, because tax posted to the wrong code is worse than not posting it at all. We confirm the treatment with your accountant before anything goes live.
What about historical orders?
We usually start the sync from an agreed cutover date rather than backfilling years of history, since backfilled entries can conflict with periods already closed and filed. Historical backfill is possible if your accountant wants it.
Related
-
Shopify and Airtable
Not a one-way order dump. A synced operational base that survives refunds, partial fulfilment and edits.
-
Tally and Airtable
Tally stays the book of record. Your team finally gets to see what is in it without asking.
-
Zoho Books and Airtable
Invoice from the event that earned it, and see what is outstanding without opening Books.
- Solution
Finance and accounting
Every workflow we automate for this kind of team.
Shopify and QuickBooks
Books that reconcile to the bank, every payout.
Payouts, fees, refunds and taxes posted to QuickBooks so the deposit matches to the cent, with summary journals instead of invoice clutter, built in three to five business days.
Start with a thirty-minute call