Accounts Payable Overpayment Journal Entry: How to Record

When you pay a vendor more than you owe, the extra money does not disappear into a rounding error. It sits in accounts payable as a debit balance against that vendor, which is the opposite of what a payables account is supposed to hold. Recording it correctly matters for three reasons: an unreclassified debit balance understates both your payables and your assets, a forgotten one eventually becomes unclaimed property you owe the state, and the amount is real cash you can get back.

Here are the entries, in the order they actually happen, with the period end treatment most teams get wrong.

What is the journal entry for an overpayment to a vendor?

There is no special entry at the moment of overpayment. You debit accounts payable for the full amount you paid and credit cash, exactly as you would for a correct payment. The overpayment shows up as a consequence: accounts payable for that vendor is now debited by more than it was credited, leaving a debit balance equal to the excess.

Take a $1,000 invoice paid at $1,200.

The vendor's subledger account now carries a $200 debit balance. Nothing is misstated yet. What happens next determines whether it stays clean.

Why an overpayment creates a debit balance in accounts payable

Accounts payable is a liability, so it normally carries a credit balance. A debit balance means the vendor owes you rather than the other way around, which makes it an asset sitting in a liability account.

That is fine day to day, and every AP subledger has a few of them at any moment. It stops being fine at period end, because you cannot offset a vendor debit balance against unrelated vendor credit balances when you present the total. Doing so understates accounts payable and understates current assets by the same amount. If the balance is material, reclassify it:

Reverse it at the start of the next period so the subledger and the general ledger stay in agreement, and let the balance clear naturally when the refund or the next invoice arrives. Auditors ask for a listing of debit balances in AP as a standard procedure, so having this reclass done and documented saves a round of questions during the accounts payable audit.

How do you record a vendor refund of an overpayment?

When the vendor sends the money back, you debit cash and credit accounts payable. That credit clears the debit balance and returns the vendor account to zero.

Two practical notes. If you reclassified the balance to a vendor receivable at period end and reversed the reclass, the credit still goes to accounts payable and everything nets. If you did not reverse it, credit the vendor receivable account instead, or you will end up with the same $200 recorded in two places.

The refund also has to be matched to the right vendor when it clears the bank. Refunds arrive as ACH credits or checks that rarely reference the original invoice number, so they are among the easiest deposits to miscode. If you are working from a statement to find them, it is worth being able to turn the PDF statement into a spreadsheet you can filter rather than reading line by line, because an unidentified refund credited to miscellaneous income leaves the debit balance sitting open in AP anyway.

How do you apply an overpayment to a future invoice?

Most vendors would rather hold the credit than cut a check, and most AP systems handle this without a separate journal entry. The existing debit balance simply offsets the credit created by the next invoice, and the net is what you pay.

The next $500 invoice from the same vendor posts as a normal $500 credit to accounts payable. The vendor account now nets to a $300 credit balance, which is what you remit. No manual entry is required in a system that applies open items against each other. The risk is procedural rather than accounting: if nobody links the debit balance to the payment run, you pay the full $500 and the overpayment grows to $200 that is still outstanding.

This is also why vendor credits and overpayments should live in the same queue as invoices. A credit that only exists in someone's inbox never gets applied.

How do you record a duplicate payment?

A duplicate is an overpayment with a specific shape: the invoice was recorded once and paid twice. The accounting is the same, and the resulting debit balance equals the full invoice amount rather than a partial excess.

The harder case is when the duplicate invoice was entered twice as well, because then both payments have a matching credit and there is no debit balance to flag. The vendor account looks perfectly reconciled while $1,000 of expense has been recorded twice. Nothing in the ledger will surface that. It gets caught by comparing invoice amounts and dates across the payment history, which is what duplicate invoice detection software does, or by reconciling the supplier statement against your ledger and finding the balance does not agree.

How do you record a recovery audit credit for a prior year overpayment?

Overpayments found by an outside firm years after the fact do not fit the tidy version above, because the period they belong to is closed.

If the original overpayment left a debit balance in accounts payable, the recovery clears it: debit cash, credit accounts payable, same as any refund. If the overpayment was charged to expense instead, which is common for duplicate payments that were coded rather than matched, the credit has nowhere to go in the closed period. Standard practice is to credit the same expense account in the current period. Recording the recovery as other income is also seen, and materiality is what decides whether either treatment is acceptable. A recovery large enough to distort the current period's expense line usually warrants a conversation with your auditors rather than a judgment call in the close.

Record the recovery gross and the firm's fee separately. An accounts payable recovery audit is priced on contingency, commonly 20% to 30% of what is recovered, and the fee is a professional services expense:

Netting the fee against the recovery and booking $75,000 is the shortcut to avoid. It hides both the size of the leak and what you paid to recover it, and those are the two numbers a CFO needs to decide whether to keep running audits or fix the controls.

What happens to an overpayment nobody ever claims?

Unclaimed vendor credits do not stay yours. After a dormancy period set by state law, typically three to five years for business to business credits depending on the state, an unclaimed credit balance becomes unclaimed property that must be reported and remitted. Writing an aged debit or credit balance off to income because it has been sitting there a long time is a common practice and a common finding in escheatment audits.

The practical rule is to work vendor balances while the relationship is live. A credit with a supplier you still buy from is easy to apply. A credit with a supplier you stopped using in 2023 is a collection effort, and eventually a filing obligation.

Which controls actually stop overpayments?

Every entry above exists because a control was missing when the payment was approved. In order of how much leakage they prevent:

• Duplicate checking that does not rely on invoice numbers. Suppliers reformat invoice numbers constantly. Matching on vendor, amount, and date within a window catches what an exact string comparison misses.
• A deduplicated vendor master. The same supplier set up twice is how two payments for one invoice pass every same vendor check, because they are not the same vendor as far as the system is concerned.
• Line level matching to the purchase order and receipt. Header total matching approves a price variance that a line comparison would reject.
• Monthly supplier statement reconciliation. This is the one that finds the credits and double payments the ledger cannot show you, and it is the routine most teams drop first when they are short staffed. It is worth protecting. See the vendor statement reconciliation process for how to run it.
• A debit balance report reviewed every month. Not at year end, when the balances are old and the vendor contacts have moved on.

None of these are exotic. They are the same controls an external reviewer tests, and keeping the evidence for them in one place is most of the value of accounts payable audit software: the entries above stop being a reconstruction exercise and become an export.

The short version

Pay a vendor too much and accounts payable carries a debit balance for the excess. Reclassify it to a receivable at period end if it is material, then reverse. A refund is debit cash, credit accounts payable. An overpayment applied to the next invoice needs no entry, only someone linking the two before the payment run. A recovery on a prior year overpayment credits the original expense account in the current period, recorded gross with the contingency fee expensed separately. And an overpayment nobody claims becomes unclaimed property, not income.