Shopify Failed Payout Reconciliation - Review Status, Support and Bank Timing
Review Shopify payout status, exported payout support, and bank timing when an expected payout is delayed or marked as failed.
Try with sample files | View sample report
Problem statement
A failed or delayed payout creates confusion because the orders may look paid, the payout may exist in Shopify, and the bank still shows no matching cash movement. The reconciliation job becomes a status-and-support workflow before it becomes a bank match.
Numeric example
| Line item | Amount |
|---|
| Expected payout support | $1,846.40 |
| Payout status | Failed / delayed |
| Bank movement found | $0.00 |
| Rows still needing review | Payout batch and bank status |
Why the numbers do not match
- The payout can be delayed or failed before any bank movement happens.
- Orders and refunds may still be visible in Shopify even though the payout status changed.
- A bank row may be missing simply because the payout has not arrived yet.
- Grouped payout support can make it hard to isolate which orders belong to the affected payout.
- Reviewer language needs to distinguish a status issue from a final cash mismatch.
What files to export
- Shopify payout export with payout ID, status, payout dates, and net payout amount.
- Shopify orders export with orders and refunds tied to the affected payout period.
- Bank statement export for the period where the payout was expected to arrive.
Manual workflow
- Confirm the payout status in the payout export before assuming the bank is wrong.
- Match the affected order and refund rows to the payout support batch.
- Check whether the issue is a failed payout, a delayed payout, or a bank identification problem.
- Keep the payout in review until the bank movement exists or the payout status is resolved.
- Export the report with the payout still flagged as review or unresolved if the bank movement is not yet present.
Common mistakes
- Treating a failed or delayed payout as an unexplained bank mismatch without checking payout status first.
- Posting accounting entries before the payout movement is actually confirmed.
- Mixing unresolved payout-status cases with normal matched payout rows.
How Reconcile Locally helps
- Keeps payout support and bank review together when the payout status is unclear.
- Shows which rows are already explained and which remain blocked by payout status rather than matching logic.
- Prevents delayed or failed payouts from being forced into false final matches.
What still needs manual review
- This page is a review workflow, not a payout-recovery or support workflow.
- A failed payout may still require platform support or bank-side action outside the reconciliation report.
- Keep the bank side unresolved until the payout movement exists or the platform status is resolved.
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
Can I reconcile a failed payout if no bank deposit exists yet?
You can review the payout support and status, but the final bank match should stay unresolved until the movement exists or the payout issue is fixed.
What should I export first for a failed payout?
Start with the Shopify payout export so you can confirm the payout ID, status, and expected net amount before reviewing the bank period.