Last reviewed: 10 October 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
Editorial ink illustration: Several payment-related records sit beside a clock and an open report.
A customer says an invoice has been paid, yet NetSuite still shows an amount due. Before sending another reminder, separate two questions: was money received, and was the corresponding payment applied to this invoice? The answers may be different.
A payment record captures information about a customer payment. Its application connects the appropriate amount to a particular invoice. Credits and deposits can also help settle an invoice, but they are separate sources with their own records and conditions.
This lesson helps accounts-receivable and customer-service users trace those relationships. It uses a simplified, single-currency example and focuses on reading and verifying records. It is not an instruction to move money, issue a refund, or change live payment information.
An invoice records a billed amount. Receiving money is a later event, and deciding which invoice that money settles is another part of the process. Keep the invoice identifier, customer, currency, original amount, and current amount due together when investigating.
An invoice balance is also different from the customer's overall position. A customer may have several open invoices and an unapplied payment at the same time. A customer-level total can hide the fact that a particular invoice has not been settled as intended.
Begin with the invoice the customer is asking about. Ask what date the balance refers to and whether the comparison is with a current record, an earlier statement, or a report run for a particular date. Two correct views can differ when they describe different moments.
For the earlier billing stages, the lesson on sales orders, fulfillment, and invoices provides related context. Here, the invoice already exists and the question is what reduces its remaining balance.
A customer payment can be recorded and applied to eligible open invoices. The amount applied to an invoice reduces its amount due. A payment can also remain unapplied rather than immediately being assigned to an invoice.
Think of the payment record as the source of an amount available for settlement, and the application as the connection to the intended invoice. One source may need to be allocated across several eligible invoices. A payment's total and the amount assigned to one invoice therefore need not be equal.
For a review, identify the payment record and inspect which invoices received amounts. Compare that allocation with the customer's remittance information and the organization's agreed process. A matching customer name and payment total do not, by themselves, establish the correct allocation.
Also distinguish the recorded payment from independent evidence that funds were received or cleared. Depending on the method and process, banking or payment-processing evidence may require separate review. Do not declare a receipt settled solely because someone entered a record.
Suppose a fictional customer has invoice TEST-INV-410 for 1,000 currency units. The amount is already the invoice total. We will ignore tax changes, discounts, exchange differences, write-offs, and any other adjustments so that the relationship is easy to see.
First, a customer payment of 600 is recorded and the full 600 is applied to this invoice. The remaining invoice balance becomes 400. To verify that result, the reviewer needs both the payment record and its application to TEST-INV-410.
Next, an approved credit memo of 100 is applied to the same invoice. The remaining balance becomes 300. The calculation is 1,000 less 600 less 100. The result depends on both amounts actually being applied to this invoice.
Notice what the calculation does not say. It does not say the customer sent 700 in cash. Only 600 came from the payment in this example. The other 100 came from a credit memo, which represents a different financial event.
It also does not establish that the customer is overdue by 300. To answer that question, inspect the invoice's due date, the reporting date, and any relevant agreement or dispute. Amount due and amount overdue answer different questions.
The example's final check is simple: the invoice shows 300 remaining, the related payment accounts for 600, and the applied credit accounts for 100. All three records must refer to the intended customer and invoice context.
Now suppose the 600 payment exists but has not been applied to TEST-INV-410. The invoice does not receive the 600 reduction merely because a payment is present on the customer account. If the 100 credit has been applied, the invoice would still show 900 under the simplified assumptions.
Alternatively, suppose the 600 payment was applied correctly but the 100 credit is still unused. The invoice would show 400. An approved credit waiting to be applied is different from an applied credit already reducing this invoice.
These variations are useful training cases because they keep the amounts constant while changing the relationship. The issue is not arithmetic. It is identifying which record is connected to which invoice, for how much.
Before correcting an allocation, confirm the customer's instructions and the organization's authorization requirements. Another invoice may legitimately have received the money. A balance investigation should establish the facts before changing them.
A credit memo can reduce the amount a customer owes and can be applied to an open or future invoice. It may arise from an approved return or another authorized billing correction. A credit memo does not, by itself, mean money was returned to the customer.
A customer deposit represents another source that may be available for application under the relevant conditions. Do not substitute the word payment for every customer balance item. The record type helps explain how the amount arose and which processing rules apply.
Availability can depend on the source transaction's state. For example, a deposit associated with a sales order has conditions affecting when an unapplied portion can be used through a customer payment. Investigate the source relationship if the expected deposit is not available, rather than creating another receipt.
For the distinction between a customer credit and a refund, continue with authorization, receipt, credit, and refund in customer returns. Keep the source amounts separate in your reconciliation even when they all help settle one invoice.
If an expected invoice does not appear, check the transaction context before assuming it has disappeared. The selected accounts-receivable account can limit which invoices are shown. With multiple currencies, currency selection also affects the available invoices, credits, and deposits.
In a multi-subsidiary account, confirm the relevant customer and subsidiary relationship. A familiar customer name does not remove the need to verify the correct subsidiary and currency. Use the actual record identifiers when asking finance or the administrator to investigate.
Parent and subcustomer relationships matter too. Consolidated Payments changes whether eligible payments, credits, and deposits can be applied across a top-level customer and its subcustomers. Without that feature, customers and subcustomers apply payments to their own invoices.
Do not enable a feature or alter an entity relationship merely to make one invoice appear. Those changes have a broader effect. Ask the owner to confirm whether the existing configuration and intended application are consistent.
Build a short evidence trail for the disputed invoice. Record the invoice amount, each applied payment, each applied credit or deposit, and the remaining balance. Keep unapplied amounts in a separate part of the review so that they are visible without being deducted twice.
Then inspect the timing. A statement generated before the payment application can show a different balance from the current invoice. Record the dates of the payment, application-related activity where available, and the statement or report being discussed.
If amounts still differ, look for adjustments outside the simplified example: discounts, currency effects, reversals, or another application. Have finance interpret any accounting treatment. Do not force a complex transaction into the simple 1,000-minus-600-minus-100 model.
A useful internal finding might say: “The payment is recorded, but only 400 of it is applied to this invoice. The remaining allocation needs review against the remittance.” That statement is more helpful than either “the customer has not paid” or “the invoice is wrong.”
Customer-service users may have enough access to identify the issue without having permission to change the financial records. Preserve that boundary. Provide the invoice and payment references to the authorized accounts-receivable owner.
An invoice is evidence of billing, not of money received. A payment record is not proof that a particular invoice was settled. A credit memo is not a cash refund. A customer total is not a substitute for checking an individual invoice's remaining amount.
A partial payment can be entirely correct. The key question is whether the allocation agrees with the customer's instructions and the approved business process. Do not treat every open invoice with a payment as an error.
Similarly, a zero amount due needs context. It may result from several settlement sources rather than a single cash receipt. Keep the explanation precise when reporting cash collection or answering a customer.
The strongest explanation follows the money and the records without collapsing them into one fact. Once you know which amounts were applied to the invoice, its remaining balance becomes much easier to explain.
For help improving the surrounding receivables process, explore CuriousRubik's NetSuite optimization services.