Periodic Credit Limit Reviews: How to Structure Them

A granted limit is a decision made with one day's information. Twelve months later that information is stale: the customer grew, shrank, changed owners or started paying late. Periodic review is what keeps the portfolio aligned to current risk — and it is also the cheapest way to grow sales, because it frees room for accounts that have proven themselves.

Frequency by exposure

Reviews for small accounts have to be automatic. If the team must manually review 2,000 customers a year, the review does not happen — it gets postponed until it becomes a problem.

What to analyze in each review

1. Internal behavior — average lateness, worst lateness, restructurings, utilization
2. Current external status — derogatories, filings, entity status, score
3. Volume and trend — growth, decline, seasonality
4. Consolidated corporate family exposure
5. Existing security — still valid, still perfected, still worth something
6. Concentration — what share of receivables this account represents

Triggers for an increase

Increase on evidence, not on request. The triggers that support it:

• On-time payment history for a defined period (six months, for example)
• Consistent utilization above 70% of the current limit
• No new derogatory marks
• Documented revenue growth
• No restructuring in the period

An increase granted under month-end sales pressure, with none of those elements, is an exception — and should be logged as one.

Triggers for a reduction

• Recurring lateness, even with full payment
• A new derogatory filing
• A material, unexplained drop in purchases
• Ownership change without notice
• Deteriorating financial ratios
• Recent restructuring

How to communicate a reduction

Communication decides whether the customer understands the decision or ends the relationship. Four practical rules:

1. Tell them before the next order, never at the counter
2. Sales communicates it, not collections
3. Explain what changes, not the detailed reasoning
4. Offer an alternative: deposit, shorter terms, security

A customer told in advance usually adjusts their buying. A customer who discovers the cut through a blocked order treats it as a breach of trust.

Automating reviews for small accounts

For the low-exposure base, the review can run on its own with simple rules: no lateness and no new derogatory in the period moves the limit up one step; lateness beyond tolerance moves it down; a new derogatory triggers a hold and opens a task. Same logic as automated decisioning, applied to the existing book.

Record keeping

Every review needs a record: previous limit, new limit, basis for the decision, owner and date. Without that history, there is no way to answer the question that always comes after a loss — was this limit ever reviewed after approval?

Process metrics

• Share of the portfolio reviewed on schedule
• Share of reviews that changed a limit
• Idle limit: how much of the granted total is never used
• Delinquency of accounts with overdue reviews versus current ones

The last metric usually justifies the whole process on its own.

What to take from this

Set frequency by exposure tier, automate reviews for the small base, and tie increases and reductions to objective triggers. Communicate cuts early, through sales, and log every review — including the ones that changed nothing.