Payout Reconciliation Workbook
Free workbook to review payout totals, deductions, expected net deposits, and bank rows in one layout.
Try with sample files | View sample report
Download the working files
Problem statement
Payout review usually spans several exports: payout totals, component rows, and bank deposits. A safe workbook keeps deductions, expected net payouts, and unresolved shortfalls visible in one layout.
Workbook example
| Line item | Amount |
|---|
| Stripe payout PO_4319 | $853.00 expected net |
| Shopify payout SP-1041 | $1,935.04 matched |
| PayPal withdrawal PP-WD-1041 | $24.00 needs review |
Why the numbers do not match
- Gross activity and the final bank deposit are different stages of the payout workflow.
- Fees, refunds, disputes, FX, reserves, and adjustments can reduce the bank amount.
- One workbook needs both payout-level summary rows and component-level support.
- Weak references and grouped deposits should stay open instead of being forced into a final classification.
What files to export
- Payout export with payout IDs, dates, status, gross activity, and net payout amount.
- Component export with fees, refunds, disputes, adjustments, reserves, or withdrawal rows.
- Bank statement CSV/XLSX with deposit date, signed amount, and transfer description.
Manual workflow
- Export the payout report.
- Export fees, refunds, and adjustments.
- Export the bank statement.
- Build one payout summary row.
- Keep unclear shortfalls open.
- Export the review package.
Common mistakes
- Starting from gross sales totals instead of payout IDs and expected net deposits.
- Mixing payout summary rows and component rows without a stable review structure.
- Calling every shortfall a fee when the export only proves a broader amount difference.
- Dropping open payout differences from the final handoff package.
How Reconcile Locally helps
- Turns cleaned payout exports into one local review workflow.
- Separates matched payouts, open amount differences, and unresolved bank rows.
- Preserves conservative wording when the files do not yet prove the exact cause of a shortfall.
What still needs manual review
- Mixed-currency, reserve, and grouped-settlement workflows may still require another export.
- Weak bank descriptions can still require a human to confirm the final payout match.
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
Should the workbook start from gross sales or from the payout ID?
Start from the payout ID and expected net payout. Gross sales are supporting context, but the bank deposit usually matches the net payout after deductions.
When should I use amount difference instead of fee?
Use amount difference whenever the payout export does not explicitly prove the cause. Keep the row in review until the files confirm whether it is a fee, refund, tax, FX, reserve, or another adjustment.