Shopify Payout Reconciliation Example
A concrete Shopify walkthrough from gross orders and payout deductions to the final bank deposit review.
Try with sample files | View sample report
Problem statement
A reviewer sees Shopify sales totals that are higher than the bank deposit. The example shows why the right question is not why sales are short, but what deductions and timing sit inside this payout.
Numeric example
| Line item | Amount |
|---|
| Gross Shopify orders | $2,134.24 |
| Refunds | -$120.00 |
| Processing fees | -$64.20 |
| Adjustment | -$15.00 |
| Expected payout | $1,935.04 |
| Bank deposit | $1,935.04 |
Why the numbers do not match
- The bank deposit reflects the net payout, not the gross order total.
- Refunds and adjustments can reduce the payout even when the original orders were paid earlier.
- One payout can group several order dates together, so order timing does not always match bank timing.
- The safest workflow starts from payout ID and net payout before drilling into orders.
What files to export
- Shopify orders export with order references, paid dates, gross totals, and refund-related fields.
- Shopify payout export with payout ID, status, gross activity, deductions, and net payout amount.
- Bank statement export with deposit amount, date, and bank description for the Shopify transfer.
Manual workflow
- Start with payout ID, payout date, and net payout amount.
- Check the payout breakdown before comparing store-wide sales totals to the bank.
- Separate refunds, fees, and adjustments from the gross orders included in the payout.
- Match the expected net payout to the bank deposit by amount, date, and reference.
- Keep any unresolved shortfall as amount difference until the export proves a more exact cause.
Common mistakes
- Comparing one bank deposit directly to the store sales total.
- Ignoring payout status or payout ID when the deposit is delayed or split.
- Calling every shortfall a fee when the exports only prove a broader deduction or adjustment.
How Reconcile Locally helps
- Keeps payout rows, order support, and bank rows in one payout-first review flow.
- Shows matched rows first and keeps unresolved differences visible instead of hiding them in notes.
- Uses conservative wording when the file set proves a deduction but not the final accounting classification.
What still needs manual review
- Grouped gateway flows and weak references can still require another export or manual confirmation.
- This walkthrough explains review logic, not posting policy inside accounting software.
Content review and sources
Written and reviewed by the Reconcile Locally product team. Last reviewed June 7, 2026.
Guidance is checked against current product behavior and first-party documentation where available. Reconciliation results still require human review.
Frequently asked questions
What is the first field to check in a Shopify payout example?
Start with payout ID and net payout amount. Those fields usually explain the bank row better than a store-wide sales total.
Does a matched payout mean every order inside it is fully explained?
Not always. The payout can match the bank while some underlying order-level details still need separate review.