PayPal Withdrawal Reconciliation Example
A PayPal walkthrough showing how activity rows, fees, FX, and the withdrawal batch map to the bank deposit.
Try with sample files | View sample report
Problem statement
PayPal mixes customer payments, fees, refunds, FX rows, and withdrawals in one activity export. The example shows why the bank match starts from the withdrawal batch, not from the raw payment total.
Numeric example
| Line item | Amount |
|---|
| Customer payments | $3,440.00 |
| Refunds | -$180.00 |
| Processing fees | -$101.40 |
| Currency adjustment | -$24.60 |
| Expected withdrawal | $3,134.00 |
| Bank deposit | $3,134.00 |
Why the numbers do not match
- Customer payments increase the PayPal balance, but the bank receives only the later withdrawal.
- Fees, refunds, and FX rows reduce the amount available for withdrawal before cash hits the bank.
- Withdrawal date and original payment date usually do not match.
- The withdrawal reference is stronger evidence than trying to match individual payments directly to the bank.
What files to export
- PayPal Activity export with payments, refunds, fees, FX rows, withdrawals, statuses, and transaction references.
- Bank statement export with deposit amount, date, and bank description for the PayPal withdrawal.
- Order or invoice export when customer-facing references are needed behind the PayPal activity rows.
Manual workflow
- Separate the Activity export by transaction type before any bank match.
- Group the rows that support the withdrawal batch you are reviewing.
- Keep FX rows, holds, and reversals separate from ordinary processing fees.
- Match the expected withdrawal to the bank deposit by amount, date, and reference.
- Leave unsupported differences in review until another export confirms them.
Common mistakes
- Matching customer payments directly to the bank before isolating the withdrawal batch.
- Treating FX rows and holds as if they were ordinary fees.
- Closing the review before the withdrawal reference and net movement agree with the bank row.
How Reconcile Locally helps
- Keeps withdrawal-support rows and bank rows visible in one local workflow.
- Separates matched withdrawals from unresolved amount differences and unknown deposits.
- Preserves unresolved PayPal review states instead of collapsing them into generic notes.
What still needs manual review
- Mixed-currency and weak-reference PayPal flows can still require manual confirmation.
- The example explains review logic, not the accounting treatment of each PayPal subcategory.
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
Why is the PayPal withdrawal batch the main match point?
Because that is the cash movement that actually reaches the bank. The customer payments only explain what sits behind the withdrawal.
Should FX rows be merged into fees in the example?
No. It is safer to keep FX-related rows separate unless the exports clearly support a narrower conclusion.