Ecommerce Month-End Payout Reconciliation Checklist
A practical month-end checklist for reviewing ecommerce payouts, deposits, reserves, refunds, and unresolved differences before the accounting handoff.
Try with sample files | View sample report
Problem statement
Month-end payout reconciliation breaks when teams compare monthly sales totals directly to the bank, forget cross-period refunds, or close the period before unresolved payout differences are preserved.
Numeric example
| Line item | Amount |
|---|
| June gross orders | $18,440.00 |
| June net payouts received by June 30 | $17,880.00 |
| In-transit payout arriving in July | $420.00 |
| Open review remainder | $140.00 |
Why the numbers do not match
- Payouts can land after the sales period closes.
- Refunds, disputes, reserves, and adjustments may reduce a later deposit.
- Grouped payouts can mix several sales days or order batches.
- Unreleased balances and weak-reference deposits must stay visible across periods.
What files to export
- Platform or processor payout exports with payout IDs, net payouts, statuses, and dates.
- Component exports with fees, refunds, disputes, reserves, adjustments, and other rows behind the net payout.
- Bank statement export with month-end deposits, descriptions, and signed amounts.
- Optional orders or ledger export when gross activity or carry-forward support still needs explanation.
Manual workflow
- Freeze the month-end date range and pull payout, component, and bank exports for the same cut-off.
- Separate payouts received by month-end from payouts still in transit.
- Group deductions such as fees, refunds, disputes, reserves, and adjustments by payout cycle.
- Match supported net payouts to bank deposits by payout ID, amount, date, and reference.
- Carry open reserves, in-transit payouts, and unresolved differences into a visible next-period schedule.
- Export the final matched, review, and carry-forward package before accounting entries are approved.
Month-end review checks
- A payout arriving next month was forced into the current month as matched cash.
- Refunds or disputes from a later payout cycle were ignored.
- Open payout differences were collapsed into a fee without supporting export evidence.
- Reserve balances were not carried forward explicitly.
How Reconcile Locally helps
- Keeps month-end payout support and bank rows in one local review flow.
- Separates matched deposits from in-transit, reserve, and unresolved review items.
- Produces a report that is easier to hand off than a workbook with hidden netting logic.
What still needs manual review
- Final period-close and accounting decisions remain separate from the reconciliation review itself.
- Cross-period, reserve, multi-currency, and grouped-settlement cases may still require another export or reviewer decision.
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 month-end sales equal month-end cash deposits?
Usually no. Month-end sales are gross activity, while cash deposits reflect net payouts, timing differences, and deductions that may cross into another payout cycle.
What should stay open at month-end?
In-transit payouts, reserves, weak-reference deposits, and unsupported differences should stay visible as carry-forward items instead of being forced closed.