AR teams age receivables as a matter of course. Credits sitting in vendor accounts do not get the same discipline at most companies, which is precisely why they accumulate.
An aged supplier credit carries two distinct risks. The vendor side risk is that the credit expires under the vendor's own terms or that the relationship ends before the credit gets applied. The accounting side risk is that the credit sits on the books as an effective receivable that is increasingly unlikely to be collected, which raises a write down question.
Both risks compound silently. By the time someone notices, the recovery options are limited.
Why Credits Age in the First Place
Aging happens for structural reasons, not because of negligence.
No active vendor relationship
The most common reason a credit ages: the vendor was a one time or occasional supplier, and there is no upcoming invoice to apply the credit against. Without a triggering event, the credit sits indefinitely.
Credit volume below approval threshold
Small credits often do not justify the effort of a refund request, but they accumulate. A vendor with twenty $200 credits over four years represents $4,000 that no one bothered to claim individually.
Vendor changes
The vendor was acquired, changed payment systems, or rebranded. The credit on the books references an entity that may no longer exist in the same form, and the cleanup work to follow up never happens.
Vendor master not maintained
The vendor is still active but the contact information is stale. AP does not have a current contact to escalate to. The credit just sits.
Vendor Side Expiration Terms
Many supplier credit notes carry expiration terms, either explicitly stated on the document or in the underlying contract or vendor terms.
Common patterns include 12 month expiration from the credit issue date, expiration at fiscal year end of the vendor, expiration tied to specific contract termination dates, and forfeiture if the credit is not applied within a defined number of subsequent transactions.
Most finance teams do not capture these terms at the point the credit is posted, which means the expiration is not tracked and the credit silently invalidates. By the time someone tries to claim it, the vendor declines.
Recovery at that point requires escalation and depends entirely on the strength of the commercial relationship.
The Accounting Risk Side
From an accounting perspective, an unapplied vendor credit is effectively a receivable from a counterparty. It reduces the gross payable balance and creates an expected future cash benefit, either through application against a future invoice or through a refund.
Standard accounting policy requires periodic assessment of whether that expected benefit is still realizable. If a credit has aged beyond a certain point and there is no realistic path to application or refund, it should be written down.
Most companies do not have a formal supplier credit write down policy, which leaves the credits on the books indefinitely and inflates the reported balance sheet position. This becomes an audit topic when external auditors test vendor balances during year end.
Building an Aging Discipline
The aging discipline mirrors what AR teams do for customer receivables, scaled appropriately for the volume.
Bucket the credits
Standard buckets work well: 0 to 30 days, 31 to 60, 61 to 90, 91 to 180, and 180 plus days. The older buckets get escalating levels of attention.
Define action triggers by bucket
- 0 to 30 days: no action needed unless the vendor has no expected future invoices
- 31 to 60 days: review for application against the next invoice cycle
- 61 to 90 days: explicit follow up with vendor, request application status or refund
- 91 to 180 days: escalate to procurement category owner, consider refund request
- 180 plus days: write down assessment, formal vendor escalation, or recovery audit candidate
Capture expiration dates at posting
When a credit is received, the expiration terms should be captured during the validation step. The expiration date becomes part of the credit record and feeds into the aging review independently of the standard buckets.
Monthly review with a defined owner
AP and controllership jointly review the aging report monthly. The output is a list of credits requiring action in the next 30 days, with the action and the owner specified.
When to Write Down a Credit
Write down decisions that need a defined policy so they are not made arbitrarily. The typical thresholds for considering a write down:
- Credit is more than 180 days old and the vendor has been contacted without response
- Vendor relationship has ended formally
- Vendor has been acquired and the acquiring entity declines to honor the credit
- Credit amount is below the threshold where pursuit cost exceeds the credit value
- Vendor has indicated the credit has expired under their terms and decline to honor
Write downs should be approved at the appropriate authority level depending on amount and documented with supporting evidence of the pursuit attempts and the reason for write down. Without this discipline, write downs become a back door for clearing the aging report rather than a controlled accounting decision.
Start Here
Generate an aging report against your vendor master for all unapplied credit balances. If you have never run this report, the output will likely surprise you. Sort by age and by amount.
Pick the oldest 10 credits and assign each one a specific action: apply, refund, escalate, or write down. The discipline that emerges from working through that initial backlog becomes the basis for the ongoing monthly review.
