What payout reconciliation proves
Payout reconciliation compares the batches reported by a payment processor with the deposits that reached a bank account. The goal is not merely to make two totals look equal. The goal is to explain every difference in a way that supports the ledger. A completed reconciliation should show which payouts cleared, which deposits are still in transit, which fees or refunds changed the net amount, and which items require follow-up.
This is different from reconciling individual customer sales. A processor can collect hundreds of charges, subtract fees, reserve funds, include refunds, and send one net deposit. The bank sees that net deposit, often one or more business days later. Start with payout batches because they provide the bridge between transaction activity and cash.
Useful result: a reviewer can select any processor payout or bank deposit and see its counterpart, timing, amount difference, and documented explanation.
Gather the right source files
Export the processor payout report and the bank statement for an overlapping period. The payout report—your payment reconciliation report—should include a payout date, payout identifier, currency, gross amount when available, fees when available, and net amount. The bank export should include posting date, description, amount, and account currency. Keep the original exports unchanged. If you need a working copy, preserve the source filename and record the export time.
Use enough overlap around month end. A payout initiated on the last day of a month may post to the bank in the next month. Pull several business days before and after the close so those items can be classified as timing differences instead of being treated as missing. If the processor maintains separate balances by currency, reconcile each currency separately. Do not convert amounts simply to force a match.
Check the files before matching
- Confirm the bank account and processor account belong to the entity and period under review.
- Check that debits and credits have the expected signs.
- Look for duplicate header rows, subtotal rows, opening balances, and blank amount cells.
- Confirm the processor column called net really represents the amount expected at the bank.
- Keep currencies separate and note any processor conversion payout explicitly.
Match in a controlled order
Begin with exact net amount matches inside a reasonable posting window. A two or three business day window often captures ordinary settlement timing, but the appropriate range depends on the processor, weekends, holidays, and the merchant agreement. Do not use a wide window without review. The same round amount can occur repeatedly, and a loose date rule can pair the wrong records.
Next, inspect payouts and bank lines that are close but not equal. Determine whether the processor report shows fees, refunds, chargebacks, reserves, currency conversion, or adjustments. A difference is explained only when the source report supports it. Avoid labels such as miscellaneous variance when a specific cause can be identified.
Then review one-to-many and many-to-one situations. Some processors split a payout across bank lines, while some bank feeds combine postings or show a deposit and a separate fee. Preserve the component records and document the relationship. Do not replace the source detail with a manually typed total because that makes later review harder.
Preview free in the browser. $39 once to export.
Classify what remains
After the straightforward matches are removed, the remaining list becomes the exception queue. Common categories include in transit, fee netted, refund or chargeback, reserve movement, duplicate import, wrong account, wrong currency, missing bank line, and missing processor payout. Each category implies a different next action.
An in-transit payout has evidence of processor initiation but no bank posting yet. Carry it to the next period and confirm it clears. A fee-netted difference should tie to processor fee detail and the correct expense account. A missing bank line may require checking another bank account or confirming that the payout failed. A missing processor payout can indicate an unrelated deposit, a manual transfer, or an incomplete export.
Do not force a zero: manual plugs, silent date changes, and combining unrelated amounts can hide the exact issue the reconciliation is meant to reveal.
What a payment reconciliation report contains (template and filled example)
A payment reconciliation report is the page a reviewer reads after the matching is done. One row per payout. Each row carries the processor side (gross, refunds, fees, net), the bank side (date, description, amount), the difference, a status, and a note. Bank lines that belong to no payout get their own rows so nothing drops off the report.
- payment-reconciliation-report-template.csv: header row only. Copy it into your close workbook.
- payment-reconciliation-report-example.csv: the same columns filled from the synthetic Stripe and bank sample files used in the Stripe worked example. Not customer data.
Columns and where each value comes from
| Column | What goes in it | Source |
|---|---|---|
payout_id, payout_date | The processor's payout identifier and date | Processor payout report |
currency | One currency per row. Do not convert to force a match | Processor report |
gross, refunds, fee | What the payout is made of. Refunds and fees as negatives | Itemized payout report |
net | The amount the processor sent. Should equal gross + refunds + fee | Processor report |
bank_date, bank_description, bank_amount | The matched bank line, or blank if none yet | Bank statement CSV |
difference | net minus bank_amount (blank bank amount counts as 0). Left blank on bank-only rows | Calculated |
reconciliation_status, match_reason | matched, ambiguous or unmatched, and why | Your matching output |
reviewer_note | The explanation a second person can check | Preparer |
Keep payout_date and bank_date as separate columns. Stripe's payout reconciliation report groups a payout by its estimated arrival date, not the date your bank posts the deposit (Stripe Docs: Payout reconciliation report, read 2026-10-20). A one or two day gap is normal timing, not an error.
The filled example, row by row
| Payout | Gross | Refunds | Fee | Net | Bank line | Difference | Status |
|---|---|---|---|---|---|---|---|
po_SAMPLE_0924 · 2026-09-24 | 245.00 | -20.00 | -8.01 | 216.99 | 2026-09-25 STRIPE TRANSFER ST-SAMPLE24 216.99 | 0.00 | matched |
po_SAMPLE_0930 · 2026-09-30 | 60.00 | 0.00 | -2.04 | 57.96 | none yet | 57.96 | unmatched |
| no payout | 2026-09-29 MONTHLY SERVICE FEE -15.00 | unmatched |
- po_SAMPLE_0924 ties. Three sales of 120.00, 80.00 and 45.00 make 245.00 gross. A 20.00 refund and 8.01 in fees (3.78 + 2.62 + 1.61) come off. 245.00 - 20.00 - 8.01 = 216.99, which is the bank line one day later. Difference 0.00.
- po_SAMPLE_0930 is open, not wrong. The processor file shows it in transit at month end and the bank sample stops on 2026-09-29. The 57.96 difference is carried to next month and closed when the deposit posts.
- The 15.00 service fee is a bank charge. It belongs to no payout. Book it to bank fees. Do not net it against a payout to make a total look right.
The report ties when every row is either difference 0.00 or carries a note a reviewer can follow. Here: one matched, one in transit, one bank charge.
Check it against ReconcileCSV
Drop stripe-payouts-itemized-sample.csv and bank-statement-sample.csv into the free preview (set the Stripe date column to effective_at). It shows the same result as the example: 1 matched, 2 unmatched, with the same match reasons. The $39 once unlock exports the ledger CSV with these columns: date, source, source_file, source_row, type, currency, gross, fee, net, transaction_id, reference, description, reconciliation_status, matched_to, match_score, match_reason. matched_to names the counterpart as <file> row N, for example bank-statement-sample.csv row 1. Row N is the Nth data row under the header, so it is line N+1 in a spreadsheet. If two loaded files share a name, they are labeled name (1) and name (2), and adding another file with that name can change those labels. The exceptions CSV has the same columns for rows that are not matched. The payout id lands in reference. Refunds and gross by sale come from the processor's itemized report, so add them to the template yourself.
Document the close
Save the original exports, the matching output, the exceptions report, and notes supporting each unresolved item. Record the date completed, preparer, reviewer, period, accounts, and any items carried forward. The final difference should be zero after supported explanations, not necessarily because every payout posted in the same month.
Roll unresolved timing items into the next reconciliation and close them when the bank posting arrives. If an item remains unresolved beyond the normal settlement period, escalate it with the payout identifier, amount, expected bank account, and processor evidence. This makes support conversations faster and gives the reviewer a precise open item.
For processor-specific export paths, see Stripe payout to bank, PayPal, Square, and Shopify Payments. For the unmatched queue after comparison, use the reconciliation exceptions guide.
Where a browser-local tool helps
ReconcileCSV can parse CSV exports, normalize common date and amount layouts, propose deterministic matches, and list exceptions for review. The free preview shows matches and exceptions. A one-time $39 purchase unlocks full ledger, print, exception, and journal-entry CSV exports. Processing occurs in the browser, and the product does not upload CSV contents.
The tool does not post journal entries, connect to bank or processor accounts, decide accounting treatment, or replace reviewer judgment. Column mapping and source quality still matter. Unsupported or unusual exports may need manual mapping, and ambiguous matches should be reviewed rather than accepted automatically.
FAQ
What does payout reconciliation prove?
Payout reconciliation compares processor payout batches with the deposits that reached the bank. The goal is not only equal totals. Explain which payouts cleared, which deposits are still in transit, which fees or refunds changed the net, and which items need follow-up. Start with payout batches because they bridge transaction activity and cash.
Which files do I need for a payment reconciliation report to bank match?
Export the processor payout or payment reconciliation report and the bank statement for an overlapping period. The payout report should include payout date, payout identifier, currency, and net amount, plus gross and fees when available. The bank export should include posting date, description, amount, and account currency. Keep originals unchanged. Confirm the bank account and processor account belong to the entity under review.
How wide should the timing window be around month end?
Pull several business days before and after the close. A payout initiated on the last day of a month may post to the bank in the next month. A two or three business day window often captures ordinary settlement, but weekends, holidays, and processor schedules can extend the delay. Do not use a wide window without review. The same round amount can occur repeatedly, and a loose date rule can pair the wrong records.
Should the bank deposit equal the payout gross or the fee-netted amount?
Match the amount the bank actually received. For many processors, fees are already reflected before the payout net is created, so the bank deposit should equal that net without subtracting fees again. When amounts differ, check fee detail, refunds, chargebacks, reserves, currency conversion, split deposits, or the wrong source column before treating the gap as a processing fee.
What if one payout splits across bank lines, or several payouts land as one deposit?
Preserve the component records. Some processors split a payout across bank lines; some bank feeds combine postings or show a deposit and a separate fee. List every component, confirm the sum by currency using dates and references, and document the one-to-many relationship. Do not replace source detail with a manually typed total.
How should I classify unmatched payout or bank rows?
After straightforward matches are removed, the remaining list is the exception queue. Common categories include in transit, fee netted, refund or chargeback, reserve movement, duplicate import, wrong account, wrong currency, missing bank line, and missing processor payout. Each category implies a different next action. Leave true unknowns open with evidence rather than plugging the difference.
Do my CSV files leave the browser in ReconcileCSV?
No. CSV parsing and matching run in the browser. ReconcileCSV does not connect to your bank or processor, pull live payout status, or upload your files to a matching server. The free preview shows proposed matches and exceptions. A one-time $39 unlock adds full ledger, print, exception, and journal-entry CSV exports. You still review ambiguous rows and support accounting conclusions from the original source reports.
When should I use ReconcileCSV instead of spreadsheet-only matching?
Use ReconcileCSV when you repeatedly compare processor payout CSVs to bank statement CSVs, need deterministic match proposals, and want unmatched and ambiguous rows surfaced without rebuilding the match logic. Spreadsheet-only is fine for a one-off with few rows and clear references. ReconcileCSV does not post to your books, choose fee accounts, or repair incomplete exports; it accelerates the comparison step.
What columns should a payment reconciliation report have?
One row per payout: payout id and date, currency, gross, refunds, fees, net, the matched bank date, description and amount, the difference, a status and a reviewer note. Add rows for bank lines that belong to no payout. Keep the payout date and bank date separate because a payout can post a day or two later. A downloadable template and a filled example from synthetic Stripe and bank samples are on this page.