Your AP Team Is Probably Overpaying Vendors — And Credit Notes Are Why

A silent cash risk that hides in plain sight until month-end

There is a mistake that AP teams make every single week, across every ERP system, in every industry. It does not show up in the invoice queue. It does not trigger a duplicate payment alert. It does not get caught by three-way matching.

It hides inside a due date field that almost nobody checks on credit notes.

The problem nobody documents

Most AP procedures cover invoice processing in detail. Three-way match, PO tolerances, approval matrices, reason codes — all documented, trained, and audited.

Credit notes? Usually a paragraph. “Book it, set the terms, move on.”

That gap is where money leaks out.

Here is what actually happens when a credit note lands in your inbox:

A vendor issues a credit for £4,200. The processor opens it in the system, books it against the vendor account, and saves it. The vendor has Net 30 payment terms. The system — helpfully, automatically — calculates the due date: 30 days from the document date.

The next payment run is in four days. The credit note is not due yet. It does not appear in the proposal. The matching open invoice gets paid in full.

Four weeks later, the credit note finally surfaces in the payment proposal — but by then, the invoice it was meant to offset is long gone. The vendor has been overpaid by £4,200.

Nobody notices until reconciliation. Sometimes not even then.

This is not a rare edge case

I have seen this happen with a single credit note worth a few hundred. I have also seen it with a reversal entry worth six figures that sat with a future due date for three months while the vendor balance ballooned silently.

The error is not carelessness. It is a documentation failure. The rule — set every credit note due date to immediate — is either not written down anywhere, or it is buried in an onboarding document nobody reads after week one.

And when temporary cover steps in, or a new starter joins mid-month, the rule disappears entirely.

Why the system cannot save you here

ERP systems do exactly what they are configured to do. If the vendor has Net 30 terms, the system applies Net 30 to everything — including credits. That is logical from a system design perspective.

It is catastrophic from a cash management perspective.

The fix is not a system change. It is a process rule, applied manually and consistently:

Every credit note — vendor-issued or internal correction — gets its due date set to the document date.

Not the vendor’s standard terms. Not whatever the system defaults to. The document date. Immediate.

This applies to:

• Vendor credit notes for returned goods or billing errors
• Credit notes against invoices still in process
• Internal reversal and correction entries
• Foreign currency credit notes (with an additional FX monitoring flag)

The four situations you will encounter

After fifteen years of AP processing, these are the four credit note scenarios that come up repeatedly — and what to do with each:

1. Credit note for an already-paid invoice. Book it, set the due date to immediate. If the vendor has other open invoices, it offsets in the next run. If not, flag it for manual review — you may be able to request a cash refund if the amount is material.

2. Credit note for an invoice still in process. Book both, pair them manually, confirm the net amount with the buyer before the payment proposal. This prevents a situation where the invoice gets approved and paid while the credit note waits.

3. Internal reversal or correction entry. Same rule, no exceptions. A reversal entry with a future due date will distort the vendor balance and can cause the next payment run to propose the wrong amount.

4. Foreign currency credit note. Apply the due date rule, then add a flag for treasury or financial accounting. The exchange rate at booking versus the rate at offset can create a small FX variance that needs to be recorded correctly.

A 15-minute check that pays for itself

Even with the rule in place, credits accumulate — especially in high-volume teams processing hundreds of invoices per week. A monthly health check catches what slips through:

1. Pull the open vendor transaction list, filtered for credit balances only
2. For each vendor showing a credit, check whether there is a matching open debit
3. If yes — look at the due date on the credit note. Future date? Correct it to today
4. If no matching invoice — the credit is sitting as a debit balance. Flag for reconciliation; if the amount is material, initiate a refund request
5. Document what you found and what you did. That documentation is audit evidence

Run this on WD-3 or WD-2. Anything corrected before WD-1 can still make the final payment proposal and close cleanly.

The SOP language that makes the rule stick

Knowing the rule yourself is not enough. The rule needs to be written down in a form that a temporary processor on their third day can follow without asking anyone.

Here is language you can drop directly into your team’s SOP or payment proposal checklist:

All credit notes — whether vendor-issued or generated as an internal correction or reversal — must be booked with the due date set to the document date (immediate payment terms). This applies regardless of the vendor’s standard payment terms. The processor and reviewer must both confirm the due date before saving or approving the entry. Any credit note with a future due date will be returned for correction before the next payment run.

Short. Unambiguous. Auditable.

Why this matters beyond the money

Overpayments are recoverable — usually. What is harder to recover is the time spent investigating, the awkward conversation with the vendor, the audit finding that questions your controls, and the reconciliation that does not close cleanly at month-end.

Credit note due date errors are also one of those process failures that look embarrassing in hindsight. Not because they are complicated — the rule is genuinely simple. But because they are preventable, and the only thing standing between you and the error is a documented, enforced standard.

That is the whole point of SOP work in AP. Not to document the obvious, but to make the non-obvious obvious — and then make it stick.

This article is based on real AP process experience across manufacturing, financial services, and professional services environments. For a full practical guide including decision trees, a printable checklist, and an SOP template, see the Credit Note Management guide in the AP Specialist Guide Series.

Tags: accounts payable · AP specialist · SSC · shared service centre · credit notes · invoice processing · month-end close · finance operations · ERP · SAP · Dynamics · Oracle · Basware