Payment reconciliation guide
How Do I Reconcile Batches to Bank Deposits?
Reconciliation connects the transactions captured by your payment system with the transfers recorded by your provider and the deposits posted by your bank. A clean process preserves each source record, matches reference IDs, and sends only genuine exceptions for research.
Use three record layers
Keep sales, provider transfers, and bank activity separate
Start with the transaction or batch report from the payment system, the payout or disbursement detail from the provider, and the matching bank statement. Current PayPal documentation describes reports that connect payments, refunds, disputes, withdrawals, and other balance activity to payouts and bank deposits. Report names and fields vary, so use the documentation for your own provider.
Reconciliation sequence
Work from source transactions to the bank
1. Preserve the source reports
Save unedited transaction, batch, payout, and bank files for the same review period. Note the account, location, currency, time zone, and date basis shown by each report.
2. Identify each transfer
List every payout or disbursement with its amount, status, transfer date, destination, and provider reference. Keep pending or failed transfers out of completed-deposit totals.
3. Map included activity
Use the provider's transfer detail to identify the sales, refunds, disputes, adjustments, and other entries contributing to each transfer. Keep provider labels intact.
4. Match the bank posting
Pair the transfer with the bank deposit using the amount, date, and available reference. Record unmatched items in an exception log instead of changing source data.
Difference analysis
Trace common mismatches without guessing
The batch total differs from the transfer
- Confirm whether more than one batch feeds the transfer.
- Look for refunds, disputes, adjustments, or other balance activity.
- Check whether the reports use different date boundaries or time zones.
- Verify that only completed activity is included.
The transfer differs from the bank deposit
- Confirm the destination bank account and currency.
- Check the provider status for failed or returned transfers.
- Compare the provider reference with the bank description.
- Escalate unexplained differences through a verified support channel.
Exception log
Document what remains unresolved
Expected record
Record the source report, expected amount, reporting period, and reason you expected a match.
Observed record
Capture the actual amount, status, posting date, and exact provider or bank label.
Safe references
Keep sanitized transaction, batch, transfer, and support-case references. Do not place full card or bank account numbers in a general worksheet.
Resolution
Assign an owner and record the provider response, accounting action, and completion date so the item is not researched twice.
Controls that scale
Make the process repeatable across reporting periods
Use consistent identifiers
Retain provider transaction and transfer IDs in the reconciliation file. PayPal's current disbursement documentation specifically describes using Transfer IDs to connect transaction-level activity with bank records.
Lock completed periods
Preserve final exports and document later corrections separately. This maintains an audit trail without overwriting the evidence used for the original match.
Separate status from date
A created, pending, completed, failed, or returned transfer should not be treated as the same event. Record status alongside provider and bank dates.
Review access
Limit report and bank-data access to authorized staff. Share sanitized references through approved support channels when help is needed.
Related resources
Connect reconciliation to payment operations
Common questions
Batch and deposit reconciliation FAQ
Should every batch equal one deposit?
Not necessarily. Transfer grouping depends on the provider's reporting and payout workflow. Use the transfer detail to see which entries contribute to the bank deposit.
Which date should control the match?
Keep transaction, batch, transfer, and bank-posting dates in separate fields. Follow the date basis used by your accounting policy and provider reports.
What if the provider report is incomplete?
Check the provider's official status and reporting guidance, regenerate the report when supported, and contact verified support with the report period and sanitized references.
What should never go in a general support form?
Do not submit full card numbers, security codes, passwords, bank credentials, complete account numbers, or secret API keys.
Last editorial review: August 12, 2026. Sources reviewed: current official PayPal reporting, monthly statement, and disbursement reconciliation documentation.
Next step
Reconcile one completed transfer end to end
Preserve the source reports, map the included activity, match the bank posting, and document any remaining difference with sanitized references.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US