Ecommerce Payout Reconciliation Hub
Browse payout-first workflows for Shopify, Stripe, PayPal, and marketplace deposits before accounting review.
Use a payout-first workflow to explain ecommerce deposits across Shopify, Stripe, PayPal, and marketplace exports before accounting review. This hub groups platform guides, mismatch pages, and handoff workflows.
Ecommerce reconciliation usually fails when teams compare order-level sales directly to a payout-level bank deposit. Orders are gross. The bank deposit is usually net of refunds, fees, chargebacks, reserves, timing differences, and other payout adjustments.
Try with sample files | View sample report
What this hub helps you review
- Shopify, Stripe, PayPal, and WooCommerce exports often describe the same cash movement at different levels of detail.
- Gross sales rarely equal the bank deposit because the bank receives the net payout, not the full customer-payment total.
- Refunds, processing fees, chargebacks, reserves, and payout timing differences can all reduce or delay the final deposit.
- One bank row may cover several orders, several settlement days, or a grouped payout batch.
- If the export does not prove the exact cause of the shortfall, keep amount-difference wording until manual review resolves it.
Numeric example
| Line item | Amount or note |
|---|
| Gross ecommerce payments | $1,000.00 |
| Refunds | -$100.00 |
| Processing fees | -$32.00 |
| Disputes or adjustments | -$15.00 |
| Expected payout | $853.00 |
| Bank deposit | $853.00 |
What files to export
- Orders or charges export with gross sales or charge-level rows, dates, references, customer context, and totals.
- Payout support export with payout IDs, fees, refunds, disputes, reserves, adjustments, and final net payout amounts.
- Bank statement CSV/XLSX with the final deposit date, amount, and bank description for the payout you are reviewing.
Manual workflow
- Start from the bank deposit or payout ID that needs explanation.
- Group source rows by payout where the export supports it.
- Separate gross payments, refunds, fees, chargebacks, reserves, and adjustments.
- Calculate the expected net payout and compare it to the bank deposit.
- Keep grouped payments, timing gaps, and weak-reference cases in review instead of forcing a final match.
How Reconcile Locally helps
- Keeps bank rows, payout rows, and source rows in one local review flow.
- Separates matched rows from amount differences, unknown bank payments, unpaid rows, and duplicate candidates.
- Makes grouped payments and payout-first reasoning visible in the final report instead of burying them in spreadsheet notes.
- Exports a review-ready file before the accounting handoff.
What still needs manual review
- Exact fee, refund, tax, FX, or accounting classifications may still need manual review depending on the exported files.
- Cross-platform workflows still need a human decision when several plausible payout explanations exist.
- Weak bank descriptions and mixed settlement timing can keep a row in review even when the deposit is probably correct.
Platform payout guides
Start with the processor or channel that produced the net bank deposit.
Mismatch and review pages
Use these when the payout looks wrong and you need the explanation path first.
Accounting handoff and proof pages
Move from payout review into bookkeeping only after the file support is clear.