A customer pays the same invoice twice. The first payment is allocated, the second creates a credit balance and the customer calls to ask what will happen next. Customer service says accounts will refund it. Accounts assumes the customer wants the amount used against next month’s invoice. A week later, neither action has happened and two teams believe the other owns the answer.
An overpayment is not only a number on a statement. It is a decision that affects cash, the customer relationship and the accuracy of the account. The handover needs evidence, authority, a named owner and a clear outcome. Without those elements, a valid credit can sit unresolved, be allocated incorrectly or be refunded without the right checks.
Confirm that it really is an overpayment
Start with the bank receipt and the customer account. Confirm the payer, amount, value date, reference and payment method. Check whether the money belongs to another customer, a different invoice, a related company or an invoice that has not yet been raised. An unidentified receipt is not automatically an overpayment, and a credit balance does not explain its cause.
Record which invoices were due and how existing payments were allocated. Preserve the original payment reference and any remittance advice. If the balance is disputed or the evidence is incomplete, keep the case in investigation rather than forcing a tidy conclusion.
Identify how the credit arose
The cause shapes the next action. A customer may have duplicated an electronic transfer, paid an old statement total, ignored a credit note, used the wrong currency or included an amount intended for another account. Internal processing can also create the appearance of an overpayment if a receipt was captured twice.
Write a short factual explanation and link the supporting records. Avoid vague notes such as “customer paid too much”. A useful note might say that two separate bank receipts with different transaction references were received for the same invoice on consecutive days. That gives the reviewer evidence rather than a conclusion to re-investigate.
Obtain a clear customer instruction
Contact the customer through an agreed channel and explain the confirmed balance in plain language. Ask whether they want the credit applied to a specific open item or future invoice, or whether they are requesting a refund. Do not promise the outcome before the required review and approval are complete.
Record the instruction, the person who gave it and the date. If the customer has not responded, set a follow-up owner and due date. Silence should not be converted into an assumed refund or allocation merely to close the case.
Control the allocation or refund decision
For an allocation, identify the exact invoice or approved future treatment and check that the customer’s instruction matches the account. For a refund, follow the organisation’s authority and verification process. Confirm the legitimate recipient and the approved destination using reliable records; do not accept a new bank account from an unverified email as sufficient evidence.
Separate preparation from approval where your controls require it. Record the approver, decision, amount and date. If fees, currency differences or other adjustments affect the balance, explain them before processing so the customer and reviewer can reconcile the final result.
Keep the accounting record and customer message aligned
The operational case and the customer account should tell the same story. Attach or reference the bank evidence, remittance, customer instruction, approval and processing result. Update the credit or allocation status once the action is completed, not when it is merely requested.
Send a concise customer update that states what was done, the amount, the relevant account or invoice and any expected timing. If the action is delayed, give the customer an honest status and the next review point. A clear update prevents repeated enquiries and contradictory answers from different teams.
A practical example
A services company receives two electronic payments for one monthly invoice. The first is matched normally. The second appears two days later with the same invoice number, creating a confirmed credit. Customer service logs the call but writes only “refund requested”, while accounts plans to carry the credit forward.
During review, the accounts coordinator links both bank receipts, confirms that they are separate transactions and checks the customer’s account. The coordinator contacts the authorised customer representative, who asks for the balance to be applied to the next monthly invoice rather than refunded. The instruction is recorded, an accounts manager approves the treatment and one person owns the future allocation.
When the next invoice is raised, the credit is applied, the account is checked and the customer receives a statement showing the result. The case closes with evidence of the original payment, the customer’s decision, the approval and the final allocation. Nobody needs to reconstruct the story from emails.
Use a visible overpayment path
A practical status path is receipt identified, overpayment confirmed, cause recorded, customer instruction requested, decision approved, refund or allocation processed, customer updated and case complete. Give each open stage one owner and one due date. If responsibility moves between customer service, accounts and a manager, make the handover explicit.
Before closure, reconcile the final account balance to the approved action. Check that no duplicate task or refund request remains open and that the customer-facing record agrees with the ledger. Review recurring causes too: repeated overpayments may point to unclear statements, stale customer information or a process that needs correction.
MyTalent MT Accounts focuses on business accounts, financial overview and daily workflows. Explore MT Accounts or talk to our team about the capabilities available for your business.
An overpayment is resolved when the money has an evidenced, approved destination and the customer can see what happened. Until then, the credit is still an open responsibility.
