Zoho Books: one bank deposit, several customer payments
Updated · 2 min read
When one Zoho Books US bank deposit covers several customer payments, first determine whether those payments already exist in Zoho. Match the bank movement to the supported existing records; if payments have not been recorded, Zoho can instead offer the corresponding invoices. These are different starting states, and creating another receipt can repeat income already recorded.
This is a grouped-receipt investigation, not a CSV join. If the bank evidence is available only as PDF, LocalExtract can prepare a local transaction CSV; customer and invoice relationships need separate evidence.
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.
Open the deposit in its bank account
The official multiple-customer-payment instructions start at Banking, then the bank account and its Uncategorized Transactions. Select the deposit and inspect the possible matches on the right.
Read the object type as well as the amount. With customer payments already recorded, inspect those payment records. Without recorded payments, the right-hand side can list invoices. Check the customers, invoice references and remittance information before selecting the supported transactions and using Match.
A proposed match is not proof that the deposit belongs to the displayed customer. An equal total can describe a different collection of invoices. Retain the remittance or settlement detail that establishes which payments make up this bank movement.
Separate a grouped receipt from an unexplained shortfall
This invented single-currency USD exercise defines a deposit of 460.00 and two supported customer payments: 180.00 for C-A and 280.00 for C-B. The two existing payments total 460.00, so the workpaper points to existing payment records, not another 460.00 income transaction.
| Evidence state | Matching preparation |
|---|---|
| Both customer payment records exist and explain the deposit | Review their references as the existing matches |
| Payments are not recorded, but invoice/remittance evidence identifies them | Review the invoice path Zoho documents |
| Bank shows 455.00 while remittance totals 460.00 | Retain the 5.00 difference as unresolved until independently explained |
Do not assume the last row represents fees. Zoho has a separate bank-charge workflow, but a numerical difference alone does not justify using it. Likewise, recording an additional receipt does not fix a missing or incorrect customer allocation.
The synthetic grouped-payment worksheet records payment existence separately from amount agreement, with the short-deposit control. Python checks the defined sums only; no Zoho matching or invoice settlement has been executed.
Retain the association after review
Keep the bank reference, selected payment or invoice references, remittance and any unresolved difference together. Confirm the resulting records under your authorized accounting process, then perform the separate statement reconciliation when the period is ready.
The Power Query invoice-merge guide addresses repeated amounts caused by expanding joined tables. It does not decide which Zoho payment records are real. LocalExtract prepares date,description,amount from one PDF at a time and does not create customer payments. Download for a PDF source.
Official Zoho Books US sources checked October 16, 2026.
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy