Customer Paid, Invoice Still Open? Review Unapplied Payments

A customer says, “We already paid,” but the invoice still appears on your collections list. Before sending another reminder, investigate the payment. The receipt may be missing, recorded twice, assigned to another customer, or waiting for enough information to identify the correct invoices.

Want receivables reviewed and maintained? Summer Peaks can handle all accounting, accounts receivable as one function, or a single payment-matching project. Tell us what you want handled.

What an unapplied payment means

In this guide, an unapplied payment is a recorded customer receipt that has not been assigned to the intended invoice or invoices. An unidentified receipt may need a separate investigation before the customer is known. Systems use different labels and accounting treatments for these situations. Do not assume that an open invoice proves the customer has not paid, or that a bank receipt proves an invoice has been cleared.

Build a short investigation list

For each exception, collect the payment amount and date, payer name, method, bank or processor reference, customer account, and any remittance details. Then record the proposed invoice match, evidence, person responsible, and next action. Use only the details needed for the review and keep sensitive payment records in a controlled system.

The University of Michigan's incoming payment process asks for the issuer, date, amount and payment method when investigating missing or unallocated payments. Its payment notification process also collects customer and invoice identifiers. Those are useful examples of the information that makes matching possible; its account codes and internal forms are specific to the university.

Review the receipt before changing an invoice

1. Confirm whether the money arrived. Check the bank or payment processor record. A customer's payment notice can start an investigation, but it does not establish that funds settled in your account.
2. Search existing records. Look for the amount, reference and payer in recorded receipts, unapplied payments and related customer accounts. Check for duplicate entries before adding another receipt.
3. Match the instruction. Compare remittance advice with invoice numbers and amounts. Request clarification when a payment covers several invoices, comes from a related company, or lacks a usable reference.
4. Document differences. Identify a short payment, disputed charge, approved credit, discount or processor fee separately. Do not erase a remaining balance just to make the records agree.
5. Apply and review. Use the system's appropriate payment-application process, retain the supporting record, and recheck the customer balance and open-invoice list. Keep bank matching and invoice matching consistent without recording the same cash twice.

Example: one receipt, two invoices

This is an invented example, not a client result. A customer owes $1,200 on invoice A and $800 on invoice B. A $2,000 receipt is recorded, but neither invoice was selected. The customer sends remittance advice naming both invoices. After confirming the receipt and checking for an earlier application, the reviewer applies $1,200 to A and $800 to B. Both invoices then show no remaining balance. The application assigns an existing receipt; it does not represent another $2,000 arriving in the bank.

If the customer paid $1,900 instead, the reviewer would investigate the $100 difference rather than silently close both invoices. A discount, credit, fee, dispute or unpaid balance requires its own evidence and treatment. Ask the accountant responsible for the records when classification is uncertain.

Keep collections connected to the review

Before contacting a customer about an invoice flagged as unpaid, check for a documented payment exception. Tell the person managing collections what is being investigated and when to follow up. A pending match should be visible, with an owner and a next review date; it should not disappear indefinitely from attention.

For a recurring review, track the number and value of unresolved receipts, the age of each exception, and the reason it remains open. Start with a simple list that someone can maintain. Automation can suggest matches, but ambiguous receipts and adjustments still need review.

Sources and factual boundaries

The University of Michigan Shared Services Center's Incoming Payment Processing explains its unallocated-payment process and the identifying information it requests. Its Accounts Receivable policy states the university's responsibility for timely receipt and proper recording. These are primary sources describing university operations, not rules imposed on small businesses. The checklist and numerical example above are original Summer Peaks workflow recommendations. Source links reviewed October 3, 2026. Correct entries depend on your accounting system, accounting basis and underlying facts; this article does not prescribe a universal journal entry.

Continue with an accounts receivable workflow or a clear transaction audit trail.