Recovery playbooks · Prevention

Month-end AP checks for overpayments

A short set of checks at each month end keeps duplicates and unused credits from building up between larger reviews.

In short

  • List vendors with debit balances and new unapplied credits.
  • Run a duplicate check on the month's payments by vendor, amount and normalized invoice number.
  • Review payments to new vendors and changed bank details.
  • Check the AP subledger agrees with the general ledger.
  • Record what was found and recovered so trends show.

What the check does

Month-end AP checks for overpayments are a small, repeated set of tests you run before you close the period. They are not a full review of every payment. They target the places where money tends to leak: vendors sitting in a debit balance, credits that arrived and never got used, payments that look like each other, and new payees or changed bank details. Done every month, they stop small problems from stacking up until someone has to spend a week digging them out.

The checks matter because AP work is repetitive and fast. A packaging supplier gets paid twice because the second invoice arrived with a different number format. A credit note for damaged goods lands in the inbox and never reaches the vendor record. A new supplier is set up in a hurry and the bank details are typed from an email. None of these is dramatic on its own. All of them cost cash, and most of them are easy to spot if you look on a schedule.

The scope is deliberately narrow. You are looking for overpayments you can still recover and credits you can still apply, not re-examining every transaction. That keeps the check to a few hours at close rather than a project. The larger reconciliation and the vendor statement work still happen, but they happen with a cleaner starting point.

What you get out of it is a short list: vendors with debit balances, new unapplied credits, suspected duplicates for the month, payments to new vendors and changed bank details, and a note of what the subledger says against the general ledger. Each item has an owner and a next step before the period closes.

Setting it up

Start with the vendor list. Pull every vendor with a debit balance and every vendor with a new unapplied credit during the month. A debit balance in accounts payable means you have paid more than you owe, or a credit has not been matched. Sort the list by size and work down it. A supplier you have traded with for years with a small debit balance may just be an invoice posted late. A new supplier with a debit balance deserves a look at the payment history.

Next, run a duplicate check on the month's payments. Match on vendor, amount and a normalized invoice number. Normalized means you strip the spaces, dashes and leading zeros so INV-00457 and inv 457 land in the same bucket. Also check payments in the same amount to the same vendor within a few days of each other. Some duplicates hide behind two invoice numbers for the same delivery, so look at the amount and date pattern, not just the number.

Review payments to new vendors and any vendor whose bank details changed during the month. Confirm the change came through a channel you trust and that someone other than the person who entered it has seen it. Then agree the AP subledger to the general ledger. If the two differ, find out why before you close: a posting to the wrong period, a payment recorded twice, or a credit sitting in the wrong place will all show up here.

Finally, record what you found and what you recovered. A simple log with the vendor, the issue, the amount and the outcome is enough. After a few months it shows whether duplicates cluster around certain suppliers or certain times of the month, which tells you where to tighten the process. Keep the log where the whole team can see it, and review it at the start of the next month-end check.

Where it falls short

The check only sees what is in your records. If a duplicate payment went to a supplier who has not issued a statement or raised it, the payment match may catch it, but a credit you never received will not appear. Vendor statements and confirmations still do the work of finding what your own data cannot show. Month-end checks reduce the pile; they do not replace those conversations.

The duplicate test depends on the quality of your invoice numbers. If suppliers send invoices with no number, or your team keys the same invoice under two references, the match will miss it. Amount and date matching helps, but it can also raise false positives, for example two genuine orders of the same size from the same supplier in one week. Plan for someone to review the hits rather than treat every match as a recovery.

The subledger to general ledger check tells you the two agree, not that both are right. A duplicate posted consistently in both will pass the test. So will a credit applied to the wrong invoice. Treat agreement as a starting point and look at the ageing of debit balances over several months; a balance that never moves is usually a real problem, not a timing difference.

Recovery depends on the supplier and the contract. Whether you can net a credit against a future invoice, how long a supplier will hold a refund open, and what happens if the overpayment crosses a period all depend on the agreement and the jurisdiction. Where those questions matter, get an adviser involved. The check finds the money; collecting it is a separate job with its own rules.

Checking that it works

Measure the check by what it turns up and what gets closed. Each month, count the items found, the value recovered and the items still open from prior months. If the open list keeps growing, the check is finding problems faster than the team can resolve them, and you need to decide whether to add resource or tighten the upstream process.

Track where each item came from. If most duplicates trace back to one supplier or one buyer, the fix is at the source: a clearer purchase order reference, or a supplier told to quote the PO on every invoice. If most credits come from a single vendor, ask why the credit note is not being applied when it arrives. The log should point to a cause, not just a count.

Sample the results. Take a handful of recovered items and confirm the correction actually happened: the credit applied, the refund received, the duplicate reversed in the ledger. A recovery noted but not posted is worse than no note, because it hides the problem. Spot-check a few payments that the duplicate test passed, to see whether the test is missing obvious pairs.

Review the check itself once a quarter. Is the vendor debit list getting shorter? Are new vendors being paid correctly the first time? If the answers are yes, keep the routine and adjust the thresholds. If not, change what you test. The point is a habit that runs every month and gets a little sharper each time, not a one-off clean-up.

Questions

How do I find duplicate payments at month end?

Match the month's payments by vendor, amount and a normalized invoice number, and also look for same-amount payments to the same vendor within a few days. Review the hits by hand, because some are genuine repeat orders. Record what you confirm so the pattern is visible next month.

What is a debit balance in accounts payable?

It means you have paid a vendor more than you currently owe, or a credit has not been matched against an invoice. List every vendor with a debit balance at month end and work down the list by size. A balance that does not move over several months usually needs a refund or a credit applied.

Why does the AP subledger need to agree with the general ledger?

A difference between the two points to a posting problem: a payment recorded twice, a credit in the wrong place, or an invoice in the wrong period. Agreement does not prove everything is right, so also look at how debit balances age and at the duplicate results.

How do I handle a supplier credit that was never applied?

Find it on the new unapplied credits list, match it to the invoice it relates to and apply it or request a refund. Whether you can net it against a future invoice depends on the contract and the jurisdiction, so check the agreement or ask an adviser where it matters.

Updated Nov 17, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.