WooPayments deposit differs from WooCommerce sales: check scope
Updated · 2 min read
WooCommerce order sales and a WooPayments payout are different populations. WooPayments transaction records cover orders paid through WooPayments, not every gateway. Start by excluding other gateways, then inspect the actual payout’s status and members.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Separate gateway scope from payout direction
- Identify the WooPayments transaction population first; keep other gateways outside this reconciliation.
- In Payments → Payouts, select Date and Status, open the identified payout and retain its included transactions/CSV.
- Keep Completed Paid as a sent incoming candidate and Completed Deducted as a separate outgoing withdrawal. Do not convert either status into observed bank arrival.
- Compare available bank reference, actual destination, currency and signed movement. Keep missing identifiers and the documented regional/date exceptions visible.
What the downloaded teaching files demonstrate
Our fictional CSV has WooPayments orders 100 EUR, another gateway 50, a stipulated WooPayments fee−10, Completed Paid 90 and a separate Completed Deducted 20. Reading and filtering the file gives an eligible payout 90 and a separate outgoing 20. Summing 90+20 as 110 incoming is wrong. A 70 net account movement would require both bank observations and would still not be the amount of one incoming payout. The 150 all-gateway sales population answers another question.
Fictional CSV: tp-231-scope-direction
Executed worksheet results. These local checks read only constructed files. They do not test vendor accounts, bank receipt, actual fee rates, imports or native report formats.
| Object | EUR | Evidence boundary |
|---|---|---|
| WooPayments | 90 | Sent incoming candidate |
| Deducted | 20 | Separate outgoing |
| Other gateway | 50 | Excluded from WooPayments |
Use available bank evidence, not assumed identifiers
The money-management documentation describes bank references, but they are unavailable for Japan payout accounts and payouts before December 2024. The TAN last four digits used for some Chase, PNC and U.S. Bank accounts may differ from the bank account number. A last-digit mismatch alone does not settle identity.
Retain actual reference, destination context and bank observation. The payout email’s Fees and adjustments can combine deductions and credits, such as dispute fees or capital repayment; it is not simply a processing-rate calculation.
A scope error can look like a missing payout
The example does not prescribe current rates or reproduce a live plugin. Reconstruct the actual payout from its report and keep unmatched gateways, adjustments and bank receipt evidence separate. Do not change payout settings or initiate a refund to make a comparison balance.
For a bank source available only as PDF, download LocalExtract. It processes one PDF locally into date,description,amount CSV; check the extracted rows against the issued statement before using them.
Related guide: Bank statement reconciliation: balances, matches and exceptions.
Documentation for the added task checked October 17, 2026.
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy