In this article
Keep the amount billed, payments applied and remaining balance connected when deposits, credits or multiple payment attempts are involved.
An invoice is a request for payment and a business record. It is not the same object as a transaction or a bank deposit. One invoice can involve a deposit, a later balance payment and a correction. One customer can also have several invoices for identical amounts. A reliable balance review preserves those relationships rather than matching by name and amount alone.
Use the invoice identifier as the starting point
Helcim’s invoice creation guide describes invoice numbers, dates, payment terms and editable status fields. Its invoice transaction guide shows where to inspect linked payment details. The Virtual Terminal guide describes partial payments attached to an existing invoice. These features make it possible to review a balance from its underlying activity instead of relying solely on a display label.
A useful worksheet separates four categories: the current billed amount, documented credits or changes, successful payments applied to that obligation, and unresolved payment attempts. The last category stays visible without being automatically counted as collected money. A pending attempt may deserve follow-up, but it should not be silently promoted into a completed payment in your explanation.
Work a deposit and change-order example
A fictional sign shop issues invoice S-420 for $1,800. The customer makes a $450 deposit. Before production, the parties approve removing an item worth $90, so the documented amount due for the work becomes $1,710. The shop later receives a $1,260 balance payment. The arithmetic is $1,800 minus $90 minus $450 minus $1,260, leaving zero.
This example assumes the approved change is properly reflected in the business’s records. It does not prescribe how to issue a credit document or record revenue for your accounting and tax situation. The lesson is that the $90 change and the $450 payment have different meanings. Combining them into one unexplained “discount/payment” line makes later questions harder to answer.
Now imagine the $1,260 payment was attempted twice: the first was declined and the second succeeded. Counting both attempts as money received would produce a false overpayment. Counting neither because one line says Declined would leave a false balance. Review the distinct transaction records and identify which one actually paid the invoice.
Check what the customer was sent
Helcim distinguishes sending a PDF invoice copy from sending a Pay Now email with a payment link. A customer who received a bill without a payment link may need a different explanation from a customer whose payment failed. Verify the communication’s purpose and destination before concluding that an unpaid invoice indicates a processing problem.
For internal coordination, use a short factual note: “Invoice S-420 total is $1,710 after the approved $90 change; deposit and balance payments total $1,710.” Keep private commentary out of customer-facing invoice notes. If the evidence is incomplete, say which payment or change remains unverified instead of marking the invoice settled for convenience.
Run a final balance check
- Confirm the correct invoice number and currency.
- Reconcile the current total to its documented changes.
- Identify each applied payment once, including partial payments.
- Separate declined, pending, returned and refunded activity.
- Check whether another employee has already requested the remaining balance.
A zero balance is only as good as those inputs. It can arise from two errors that offset, such as an omitted credit and an extra payment entry. Trace the links, not just the final number. For a real customer inquiry, send only the relevant invoice and payment explanation through the merchant’s approved channel; this publication does not collect or review private invoices.