Payout reconciliation: match the payment report to the bank deposit

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.

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.

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.

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.