← All support guides

Troubleshooting

How to investigate a Shopify payout variance

Identify whether a difference comes from payout activity, Shopify settlement timing, account mapping, or the bank deposit.

7 minute read

Identify which comparison is different

Vatteo separates two questions: whether the underlying activity reconstructs the Shopify payout, and whether the Shopify payout matches the bank deposit. Keeping those checks separate narrows the investigation.

  • Payout variance: Shopify payout minus reconstructed payout activity
  • Bank variance: bank deposit minus Shopify payout

Check payout identity before the amount

Confirm the payout ID, settlement status, currency, destination bank account, and date. A bank transaction date can fall after the Shopify settlement date, and comparing the wrong deposit creates a false variance.

Common payout-activity causes

  • A refund, dispute, reserve, or adjustment arrived after an earlier import
  • The payout was still scheduled or in transit
  • A fee or transaction was incomplete in the provider response
  • External-payment activity was mixed into the review period
  • A category was mapped or classified incorrectly
  • A payout or correction was imported twice

Common bank-match causes

  • The bank transaction is still pending
  • The wrong destination account or deposit was selected
  • The bank grouped or split transactions
  • A currency conversion changed the received amount
  • The bank feed entry was manually categorized as new income

Refresh evidence before changing accounting

Refresh the Shopify evidence and confirm the payout has reached a final paid state. Then review mappings and the proposed journal again. Avoid deleting or rewriting a posted QuickBooks entry without preserving a correction trail.

When to contact support

Contact support when the same final payout remains different after refresh or when a posted journal no longer matches its approved evidence. Include the payout ID, visible variance, currency, and the step that failed—never credentials or customer personal data.