Credit memos and dilution: the rule that punishes messy billing

A lender advancing 85 percent against an invoice is betting the invoice turns into cash at close to face value. Dilution is everything that erodes face value without a customer defaulting: returns, volume rebates, promotional allowances, pricing errors, short shipment credits, and write-offs of small balances. A pool with 8 percent dilution is simply worth less per invoice than a pool with 2 percent, even if every customer pays.

Dilution is also a data quality signal. High dilution usually means billing is generated before orders are truly final, or pricing masters are stale, or rebate accruals live in a spreadsheet. Lenders read a rising dilution trend as an early warning about operations, which is why the ratio is monitored monthly in most facilities rather than tested once at closing.

The dilution ratio is credit memos and other non-cash adjustments divided by gross sales over the measurement period, commonly the trailing twelve months. Most agreements then size a dilution reserve from the ratio, often applying a stress multiple, and deduct the reserve from availability. Here is a common formulation with a stress multiple of 2.0 applied to the ratio.

That $2,000,000 comes straight off availability. Constructions vary: many ABL agreements instead set a dilution threshold, commonly 5 percent, and add ineligibles or reserves point for point above it, while securitizations build the ratio into a dynamic reserve formula alongside loss reserves. Either way, the lever is the same. Cut the credit memo rate in half and the reserve in this example drops by $1,000,000.

You need every credit memo with its issue date, amount, obligor id, and ideally a reason code, plus gross sales for the same period. The classic break is the numerator: credit memos issued as rebills net out in the AR balance but still count as dilution if you only capture the credit side, which overstates the ratio. The opposite error is worse: netting credits into sales before reporting, which understates dilution and gets found in the first field exam that samples memos.

Reason codes are where the leverage is. A credit for a genuine return is dilution; a credit reversing a duplicate invoice may be excludable as a billing correction under some agreements. If the ERP has three reason codes and one of them is Other, you cannot make that argument, and the whole credit population gets treated as dilutive.

• Dilution is computed deterministically from the full credit memo population and the matching sales period, so the ratio is the same no matter who runs it.
• The measurement window, stress multiple, thresholds, and any excludable credit categories are configured per facility to mirror the agreement's reserve formula.
• Reason code mappings are explicit, so the split between dilutive credits and billing corrections is a documented rule, not a monthly judgment call.
• Every point of the ratio traces to the specific memos behind it, by obligor and reason, which turns a reserve argument with your lender into a data review.