Why a customer overpayment creates a problem
The money has arrived, so the account looks settled. But the excess does not belong to the company that received it yet: until it is assigned, it sits in the customer ledger as credit no invoice has claimed.
An unapplied credit can coexist with invoices that still appear open, so the customer statement may show both a debit and a credit that need allocation. The excess itself does not increase the amount owed. Keeping its origin, owner and agreed treatment visible prevents the team from chasing a settled invoice or applying the credit to the wrong one.
What causes the excess
- A price list the customer has not updated, so the payment goes out at the previous rate while the invoice was issued at a newer one.
- A duplicate payment of the same invoice, sent twice by two people or by two payment runs.
- A wrong exchange rate, or an amount keyed in wrong.
- An agreed early payment discount the customer did not take, despite meeting its conditions.
- One transfer covering several invoices that adds up above the open balance.
- Rounding on a converted amount, or an advance sent before an invoice exists.
How the excess is handled
- Detect the excess against the invoice. The payment is matched to the invoice it was meant to settle, and what remains after the invoice is covered is the excess. Cash posting is the process that surfaces it, and a remittance detail arriving with the payment makes the match possible.
- Record it as an unapplied credit. The excess is booked as a credit on the customer account that no invoice has consumed, which makes it neither revenue nor a discount.
- Carry it as a liability. The money was received without being earned, so the excess stays a liability until it is used or returned.
- Apply it to another invoice or return it. The usual outcome is applying the credit against another invoice pending from the same customer, or as an advance against a future one. The alternative is a refund.
Example: a payment made from the previous price list
Merchausen Supplies sells packaging to Brightline Grocers and has lowered its price per case from USD 19.50 to USD 19.00. Invoice INV-4820 goes out at the new rate for 250 cases, which is 250 times USD 19.00 = USD 4,750, and the customer pays at the previous rate of 250 times USD 19.50 = USD 4,875. The figures are illustrative.
The invoice is covered and the excess remains: USD 4,875 minus USD 4,750 = USD 125. That amount is recorded as an unapplied credit.
In the same period Merchausen issues INV-4863 to Brightline for USD 2,340. The credit goes against it, and the amount left to collect is USD 2,340 minus USD 125 = USD 2,215, which leaves the account with no open excess.
How an overpayment differs from neighboring terms
A short payment runs the opposite way: the customer pays less than the invoice and leaves a balance open. An unapplied payment is the accounting state the excess is recorded in, and this article stops at naming it. Invoice matching is the control that compares invoice, order and receipt before money leaves, so it happens before an excess can exist.
Payment terms set when payment is due and whether a discount applies. Accounts receivable is the object an unresolved excess distorts. The mirror case belongs to the paying company: a business that overpays a supplier chases the return.
Following the excess after the invoice is settled
Once the invoice is covered, the excess needs its own record: payer, source payment, amount, reason and agreed destination. Simetrik’s receipt and settlement controls can expose amount differences through configured comparisons. The team must still follow the excess even if the bank and ledger totals agree.
If it remains an unapplied customer credit, preserve the allocation evidence and its age. Applying it to a later invoice or authorizing a refund requires a documented decision, so the original invoice is not reopened or settled a second time by mistake.