Payments & bookkeeping
Plumbing Payment Reconciliation Checklist: Invoice to Bank
Reconcile payments in layers: verify the customer transaction, allocate it to the correct invoice, and then explain the bank settlement. A paid label, a payment message, and a bank deposit are not interchangeable pieces of evidence.
In this guide
Define the records being reconciled
Start with the customer invoice, payment transaction, allocation, and bank entry. Add processor payout records when the payment method creates a separate settlement stage.
Use a consistent reporting date and account scope. A report for one date range should not be compared with a bank list covering a different period without accounting for the timing difference.
This checklist supports operational review. Your accountant should determine the ledger classifications, adjustment treatment, and formal reconciliation process.
Use the checklist in order
PAYMENT RECONCILIATION
[ ] Invoice and customer identity verified
[ ] Original charge and approved adjustments checked
[ ] Actual payment reference and status verified
[ ] Payment allocated to the correct invoice(s)
[ ] Partial payments and unallocated amounts identified
[ ] Refunds or reversals traced to original records
[ ] Processor fees and other batch adjustments identified
[ ] Payout or deposit reference matched where relevant
[ ] Bank amount and posting date reviewed
[ ] Existing accounting entries checked for duplicates
[ ] Differences assigned to an owner, not silently removed
[ ] Resolution evidence and review date retained
Do not skip directly from a bank amount to an invoice status when the intervening records are unclear.
Check allocations before settlements
Suppose a fictional payment of $700 covers invoice A for $400 and invoice B for $300. The allocation should total $700 across both invoices, not $700 on each.
If only invoice A is identified, the remaining $300 is an unresolved allocation—not automatically new revenue or an overpayment. Investigate the customer's remittance information and the business record.
Similarly, a payment of $200 toward a $600 invoice leaves $400 due only when the payment is verified and no other relevant adjustments apply.
Explain differences without guessing
A net bank amount can differ from customer payments because of fees, refunds, timing, or other actual adjustments. Record the specific evidence for the difference.
Do not use a general “miscellaneous fee” line to force the reconciliation to balance. An unexplained difference is a question to resolve, not an invitation to invent a category.
| Difference | Review question |
|---|---|
| Payment not in the bank yet | Is settlement still pending or in another batch? |
| Bank amount lower than payments | Which documented adjustments explain it? |
| Duplicate-looking payment | Are the references identical or merely the amounts? |
| Customer reports payment | Can the transaction be located and verified? |
| Invoice still open | Was the payment allocated to the right record? |
Keep an exception queue
For each unresolved item, record the amount, identifiers, evidence checked, owner, and next action date. Do not let unmatched items disappear from the totals without explanation.
If a correction affects posted or reconciled accounting records, involve the accountant before changing them. Preserve the original record and correction trail.
Review the process, not just the balance
After resolving exceptions, look for recurring causes: missing invoice references, duplicate manual entry, unclear multi-invoice allocations, or incomplete integration handling.
Fixing the source of repeated differences can make the next reconciliation simpler. The objective is an evidence-supported connection between what the customer owed, what they paid, and what reached the bank—not merely a spreadsheet that reaches zero by the end of the day.
Sources and editorial notes
Product and documentation references checked September 29, 2026. GoPlumber publishes this guide about its own product category. Examples and templates are original illustrative material, not customer case studies or market benchmarks. Confirm current vendor terms before acting.