Grouped Payout Reconciliation - Review One-to-Many Deposits Safely
Review grouped payout deposits when one bank row covers several orders, refunds, deductions, or payout components.
Try with sample files | View sample report
Problem statement
Grouped payouts are one of the main reasons a bank deposit does not line up cleanly with one order, one invoice, or one payment row. The bank only shows the final deposit, while the supporting payout detail may span several source rows and deduction types.
Numeric example
| Line item | Amount |
|---|
| Grouped source rows | $2,410.00 |
| Refunds and deductions | -$224.80 |
| Expected grouped payout | $2,185.20 |
| Bank deposit under review | $2,145.20 |
Why the numbers do not match
- One bank deposit can represent many orders or charges from the same payout batch.
- Refunds, reserves, and other deductions can be mixed into the same grouped payout.
- The payout report and bank export may use different dates and identifiers.
- Repeated values can make amount-only matching look safer than it really is.
- A grouped payout often needs a report-first workflow before any accounting handoff is safe.
What files to export
- Payout export with payout ID, batch date, deductions, and net payout amount.
- Orders or invoice export with source rows that can explain what belongs inside the grouped payout.
- Bank statement export with deposit date, amount, and description for the grouped bank row.
Manual workflow
- Start from the payout batch or grouped bank deposit rather than from one individual order.
- Pull all source rows that belong to the same payout window or payout ID.
- Separate the gross source total from refunds, reserves, and other deductions.
- Compare the expected grouped payout to the bank row and keep any open remainder in review.
- Export the final report with matched rows first and grouped-payment review rows kept separate.
Common mistakes
- Forcing a one-to-one match when the deposit clearly belongs to several source rows.
- Calling the remaining gap a fee without enough source-row evidence.
- Using amount-only matching as final proof when several source rows share similar totals.
- Collapsing grouped payouts into one unexplained net line before review is complete.
How Reconcile Locally helps
- Keeps grouped payout support rows visible together instead of splitting them across several spreadsheet tabs.
- Separates exact matches from possible grouped payments and other review rows.
- Exports a report that makes one-to-many matching easier to explain later.
What still needs manual review
- A possible grouped payment still needs reviewer confirmation before final acceptance.
- Some grouped batches need another export or a broader payout window before the last open amount is fully explained.
- Grouped payouts should stay in review when the support is close but not yet strong enough to defend.
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 one bank row match several source rows?
Yes. That is a common grouped-payout case. Keep it in review until the supporting rows and deductions are visible together.
Should I mark a grouped payout as matched when the totals are only close?
No. Leave it as a possible grouped payment or amount difference until the support is strong enough to defend.