Evidence-first exception checklist

Preserve the source trail before fixing QuickBooks or Xero.

When a Shopify accounting sync does not match the payout or bank, first save the native records and locate the earliest broken equality. Do not delete, replay, add, match, or recategorize entries while the evidence is still moving.

Shopify Payments only · One payout and currency · Investigation, not correction

Quick answer

Freeze first. Prove the native payout. Then compare the synced record.

Keep four evidence sets separate: the specific Shopify Payments payout and its included transactions, the Shopify Payments activity report for the relevant period and currency, the actual bank line, and the connector or accounting record as it exists now. Preserve identifiers, timestamps, status, currency, destination account, amounts, and any visible manual changes.

Test the records in order. First, do the proved Shopify rows tie to Shopify's displayed payout total? Second, does that payout tie to the observed bank deposit? Third, do the provider's documented records represent that economic payout exactly once in aggregate? The first failed comparison suggests the next system and owner to investigate; it does not prove why the failure occurred.

Shopify sources: specific payout details and transaction export and the Shopify Payments activity report.

Before changing anything

Capture the exception in its current state.

01

Shopify payout evidence

Save the payout total, currency, status, destination account, transfer reference where available, payout date, and included transactions shown in the payout detail. Use an exported CSV only after the admin or file context uniquely proves which rows belong to that payout; date and currency alone are not enough.

02

Shopify period evidence

Save the activity report for the relevant date range and payout currency. Shopify presents starting balance, gross activity, fees, payouts, net movement, and ending balance; that period view is context, not a substitute for proving one payout's rows. Shopify notes that report data can lag by up to three days, so retain the selected range and currency with the snapshot.

03

Bank evidence

Preserve the actual posted or downloaded bank line, account, currency, amount, posting date, and available reference. A Shopify status is not evidence that the bank received the money.

04

Connector and accounting evidence

First identify the provider's documented posting model. Then save its payout-related records, transaction state, mapped destination where shown, sync time, available source IDs, and related bank-feed records. Note duplicates, exclusions, manual edits, retries, or prior corrections without changing them yet.

Never include passwords, access tokens, or other credentials. Crop bank evidence to the relevant line, redact unrelated activity and full account identifiers, and omit unnecessary personal, customer, and tax data. Send each owner only the minimum packet needed for that system through an approved secure channel.

Failure-localization sequence

Find the first equality that fails.

  1. 01

    Confirm one payout and one currency.

    Start from the specific Shopify Payments payout, not a sales report, an order total, a date-and-currency guess, or a mixed processor batch. Keep PayPal and other third-party payouts in separate source trails.

  2. 02

    Test A: Shopify activity → displayed payout total.

    After confirming export scope and sign conventions, sum the included rows' Net values and compare the result with Shopify's displayed payout total. If the values do not tie, stop at the native payout scope before investigating the connector or bank.

  3. 03

    Test B: Shopify net payout → observed bank deposit.

    Compare the same-currency payout with the actual destination account and bank line. Use the available transfer reference and timing as corroboration. Do not subtract a Shopify fee, refund, dispute, or reserve again after it has already changed the payout's net amount.

  4. 04

    Test C: accounting record → the same payout and bank line.

    Compare the preserved connector or accounting record with the native payout that passed A and B. Under the provider's own posting model, confirm that the available identifiers, currency, amount, and destination represent that economic payout exactly once in aggregate—not a second bank-feed addition or a parallel manual import.

  5. 05

    Check for duplicate routes before replaying anything.

    Search the connector view, accounting register, bank feed, and prior imports for the payout amount and source identifiers. Preserve every candidate. A retry, delete-and-resync, or manual Add can contaminate the evidence or create a duplicate before a missing record has been distinguished from a duplicate one.

  6. 06

    Send the smallest complete packet to the right owner.

    Usually route a native-payout failure to Shopify support, a passed payout with a bank exception to the bank or payments owner, and a connector/accounting mismatch to the app provider and qualified bookkeeper. Send a recipient-specific minimum packet that includes the passing comparisons and first failure.

Synthetic trace

The native payout and bank pass. The accounting record is US$30 short.

Assume the Shopify admin has proved that the invented USD activity below belongs to one payout. The values are illustrative components, not literal CSV Net rows. They demonstrate the sequence; a real payout's own rows, signs, fees, and source identifiers control the real investigation.

Invented Shopify, bank, and accounting amounts used in Tests A–C
Preserved record Invented amount Result
Shopify gross captured amount before fee + US$1,000.00 Native composition
Shopify refund − US$70.00
Shopify processing fee − US$30.00
Shopify displayed payout total US$900.00 Test A passes
Observed bank deposit US$900.00 Test B passes
Preserved accounting-sync record US$870.00 Test C fails by −US$30.00

Test AUS$1,000.00 − US$70.00 − US$30.00 = US$900.00

Test BUS$900.00 bank − US$900.00 payout = US$0.00 variance

Test CUS$870.00 accounting − US$900.00 payout = −US$30.00

This trace localizes the exception after the native payout and bank checks. The repeated US$30 resembles a fee being counted a second time, but the numbers alone do not prove that explanation or identify a connector, setting, mapping, import, or manual edit as the cause. Preserve the record and ask its owner to diagnose it.

Shopify Connector by QuickBooks example

The current Intuit workflow makes its Match-not-Add rule explicit.

For a positive Shopify payout received in the bank, the Shopify Connector by QuickBooks app in QuickBooks Online requires all included transactions to show Categorized, every “Funds in this payout” adjustment to have an account, and Add (or Confirm) to be selected for the Payout transaction before QuickBooks creates a Deposit for the net payout. In Bank transactions, select Match for the Shopify bank deposit and existing Deposit; do not manually Add the deposit in the bank feed. Preserve the current Integration transactions category/action, adjustment mappings, and Deposit before changing either.

Intuit routes a negative payout through the connector's configured Payments account. That is outside this positive-deposit example.

This Intuit-specific example does not establish how another connector or Xero integration records a payout. For any other route, use that provider's current instructions and support channel while keeping the same native Shopify and bank evidence separate.

Source: Intuit's Shopify Connector workflow.

Evidence-preservation rationale

Keep the before-state separate from later troubleshooting changes.

Selected low-star Shopify App Store reviews include merchant reports of substantial monitoring, manual repair, editing, or deletion after unexpected accounting-sync outcomes. Preserving a before-state helps distinguish the original mismatch from later troubleshooting changes. These complaint samples do not establish incident rates, provider defects, causes, or what happened in a different store; vendor replies are not independent verification of the reported events.

Merchant-language sources: selected A2X low-star reviews, selected Synder low-star reviews, and selected Reconcilely low-star reviews. Shopify facts about payout details and activity reports are sourced above. The preservation and triage sequence is this site's conservative investigation method; the QuickBooks-specific behavior is sourced to Intuit.

Related checks

Use the guide for the first comparison that is unclear.

If the native payout composition does not tie, use the payout CSV reconciliation guide. If Shopify's payout ties but the bank deposit is hard to locate, use the bank-reference lookup guide. If the store uses Intuit's Shopify Connector, use the QuickBooks payout-matching guide after preserving the current integration state.

After one native payout is established

Carry the Shopify and bank comparisons into bookkeeper review.

The US$9 Shopify Payout Reconciliation Workbook keeps one verified Shopify payout-composition check separate from the payout-to-bank check and leaves a variance visible. It can organize the native evidence before a connector or accounting exception is handed off.

The ZIP contains one editable .xlsx workbook with worked synthetic examples and a checklist tab. It does not connect to Shopify, QuickBooks, Xero, an app, or a bank; import, sync, repair, delete, match, categorize, or post transactions; diagnose a provider; choose accounts or tax treatment; or replace a bookkeeper.

View the US$9 workbook on Gumroad

Delete the bundled synthetic sample rows before a real handoff. Differences up to 1.00 in the workbook currency stay visible but are labeled Ready. Shopify Payments only. One currency per workbook. Requires an app that can open and recalculate Excel formulas; compatibility with Google Sheets, Apple Numbers, mobile apps, and browser-only editors is not verified.

Boundary

An evidence checklist—not accounting, repair, or provider diagnosis.

This page does not select or change a connector, chart of accounts, accounting basis, tax treatment, ledger entry, mapping, sync setting, or correction. It does not prove a Shopify, Intuit, Xero, app, bank, or bookkeeper defect. Preserve the controlling records and ask the qualified party responsible for each system to diagnose and approve any change in that system.