Customer Credit Reviews: How AR Teams Re-Check Existing Accounts Before Risk Grows
A working guide for a 3 to 5 person AR team: which existing customers to review and how often, the signals to check, how to run the review in your ERP, and what to do with the result.
Sia Ghazvinian
Co-Founder & CEO
Table of contents
Share
Most bad debt does not come from the new customer you vetted last month. It comes from a customer you approved three years ago, on a limit nobody has looked at since, whose business changed while your team was busy chasing this week's invoices.
The pressure behind that is real. In the 2026 Atradius Payment Practices Barometer for North America, companies sold 43% of their B2B volume on credit, overdue invoices averaged 23% of receivables, and customer liquidity constraints were the leading cause of late payment. A customer short on cash does not announce it. It shows up first as small changes on your own ledger.
This guide is for controllers and AR managers running a 3 to 5 person collections team. It covers which existing customers to review and how often, what to look at, how to run the review in your ERP, and what to do with the answer.
What Is a Customer Credit Review?
A customer credit review is a scheduled re-check of an existing customer's credit limit and terms, based on how the account pays today rather than how it looked when you approved it. The output is a decision: keep the limit, raise it, lower it, or change the terms.
A credit review exists because a credit decision starts to go stale the day you make it. The customer's cash position, ownership, order size and payment habits all move, and the limit in your ERP does not move with them unless someone moves it.
Credit review versus a new-customer credit check
A new-customer check works with outside information because you have no history yet. The process for vetting a customer before extending terms leans on trade references, bureau reports and the application. A review of an existing customer has something better: months or years of real payment data on your own books. Use it first.
Why existing accounts drift
Accounts drift in three ways. Exposure grows because the customer orders more and nobody revisits the limit. Payment speed slows a few days at a time, so no single invoice looks alarming. And the business itself changes, through new ownership, a lost major contract or a move into a new market. The five Cs of credit still apply; they just need fresh inputs.
Which Customers Should You Review, and How Often?
Review every customer with an open credit line at least once a year, and review your largest and riskiest accounts more often. A small team cannot give every account the same attention, so sort them by what they could cost you.
Sort accounts into review tiers
Tier accounts by exposure (open balance plus open orders) and by recent payment behavior. A simple four-tier model covers most AR teams:
Tier | Who belongs | How often to review | Who signs off |
|---|---|---|---|
Tier 1: largest exposure | Top accounts that together make up most of open AR | Every three months | Controller |
Tier 2: mid-size | Steady accounts with meaningful balances | Every six months | AR manager |
Tier 3: small | Low balances and low order volume | Once a year | Assigned collector |
Watch list | Any account that hit a trigger below | Monthly until it clears | Controller |
Your Tier 1 list is where a single failure hurts most, so it gets the most frequent review. If a handful of customers make up most of your open balance, read up on AR concentration risk before you set the tiers.
Set event triggers that force an early review
The calendar catches slow drift. Triggers catch sudden change. Move an account to the watch list and review it right away when any of these happen:
Average days to pay rises by 10 or more days compared with the prior six months
The customer breaks a payment promise, or breaks two in a row
An order would push the balance over the credit limit
A check bounces or a payment is reversed
The customer asks for longer terms or a payment plan
Your AP contact changes suddenly, or ownership changes
Sales asks for a higher limit to close a large order
Write the triggers down so every collector applies them the same way. Promise-to-pay tracking makes the broken-promise trigger easy to see, because the promises are already logged.
What Should a Credit Review Look At?
Look at four things, in this order: payment behavior on your own ledger, exposure against the limit, outside signals, and what your collectors have heard. The first two come straight from your ERP and should take minutes per account.
Payment behavior on your own ledger
Pull the last 12 months of invoices and payments. Check average days to pay against your terms, the trend over the last six months, the share of invoices paid late, and any short payments or deductions. An AR aging report analysis gives you the same picture across the whole book, so you can see which accounts are moving into older buckets.
A trend matters more than a single number. A customer that always pays at 45 days on net 30 terms is predictable. A customer that moved from 32 days to 44 days over six months is telling you something.
Exposure versus the credit limit
Compare the current balance plus open orders with the approved limit. A customer running at 95% of its limit every month is either a growing account that deserves a review upward or a stretched account that deserves a closer look. The review tells you which.
Outside signals
For Tier 1 and watch-list accounts, refresh the outside view: a current business credit report, news about the customer and its industry, and any change in ownership or key people. You do not need this for every Tier 3 account every year.
Relationship notes from the collectors
Your collectors hear things before the numbers show them: a new AP clerk who cannot find invoices, a controller who mentions a slow season, a site manager who says a large job was cancelled. Ask for those notes in the review, and write them on the account.
How Do You Run the Review in NetSuite, QuickBooks or Business Central?
Run it from a saved report or search that lists every customer with its limit, balance, open orders and average days to pay, sorted by tier. The goal is one list your team works through, not a separate hunt for each account.
NetSuite
In NetSuite, the Credit Limit and Hold fields sit on the Financial subtab of the customer record. Hold can be set to Auto, On or Off, and NetSuite can place a customer on hold when it reaches its limit or when its overdue balance passes the Days Overdue for Warning/Hold setting. One detail matters for reviews: per NetSuite's guide to customer credit limits and holds, a parent's limit does not include its subcustomers, so review child accounts too.
QuickBooks
In QuickBooks, start by exporting the A/R aging report from QuickBooks and adding columns for each customer's limit and tier in a spreadsheet. Keep the approved limit and the review date in one place your whole team can see, so a collector can check them before releasing an order.
Business Central
In Business Central, the limit sits in the Credit Limit (LCY) field on the customer card. Pair the customer list with a Business Central aging export so the review shows the limit, the balance and the overdue amount side by side.
What Do You Do With the Result?
Every review ends with one of four decisions, recorded on the account with the date and the person who made it: keep the limit, raise it, lower it, or change the terms.
Raise, keep or lower the limit
Raise the limit when the customer pays on time and keeps bumping against it. That is a growing account, and holding it back costs you sales. Keep the limit when nothing has changed. Lower it when the payment trend is slowing or exposure has grown faster than the customer's ability to pay.
Lowering a limit is a business decision, not a punishment, and it is easier to make before the account is badly overdue. The guide to extending credit to customers covers how to set the starting number; the review is how you keep it honest.
Change the terms instead
Sometimes the limit is fine and the terms are the problem. Options include shorter terms on new orders, a deposit on large orders, staged delivery or progress billing on long jobs, or moving the account to a faster payment method. Match the change to the risk you found.
Tell the customer and the sales team
Tell the customer directly, before the next order is affected, and explain what would change the decision. Tell the account owner in sales at the same time. If a lower limit means the next order would be blocked, your credit hold policy should already say what happens and who can approve an exception.
How Do You Keep Credit Reviews From Slipping?
Credit reviews slip because they are important but never urgent. Three habits keep them on the calendar.
Put the schedule in writing
Add the tiers, review frequencies and triggers to your collections policy, with a named owner for each tier. A review that belongs to "the team" belongs to nobody.
Batch the work
Review Tier 1 accounts in one sitting every three months and Tier 2 in one sitting every six months, rather than one account at a time. Batching makes it easier to compare accounts and spot patterns across the book.
Free up collector time for it
Most small AR teams skip reviews because the week is full of routine follow-up. Every hour saved on reminder emails and status calls is an hour available for the judgment work a credit review needs.
Where Does Abivo Fit?
Abivo's AI collections agent, Kate, handles routine follow-up across every account: reminders, payment-status calls and promise tracking, logged back to the account. That gives your team a cleaner record of how each customer actually pays, and more of the week for decisions like credit reviews, disputes and key accounts. You can see how Kate works on the product page.
Practical Takeaways for Controllers and AR Managers
Review every customer with a credit line at least once a year, and your largest accounts every three months
Sort accounts into tiers by exposure and payment behavior, and give each tier a named owner
Use event triggers to pull an account into review early, rather than waiting for the calendar
Start with your own ledger: payment trend and exposure against the limit come first
Record every decision with a date, a reason and a name
Tell the customer and sales before a lower limit affects the next order
Frequently Asked Questions
How often should you review customer credit limits?
Review every account with a credit line at least once a year. Review the largest accounts every three months and any account on the watch list monthly until it clears.
What triggers a customer credit review outside the normal schedule?
Common triggers are a jump in average days to pay, a broken payment promise, an order that would exceed the limit, a bounced payment, a request for longer terms, and a change in ownership or AP contact.
What is the difference between a credit check and a credit review?
A credit check is done before you extend terms to a new customer, mostly with outside information. A credit review re-checks an existing customer, mostly with its payment history on your own books.
Should a credit review always lower a limit when payments slow?
No. Look at the reason first. A short delay with a clear cause and a kept promise may only need closer follow-up. A steady slowdown with growing exposure is the case for a lower limit or tighter terms.
Who should approve a change to a credit limit?
Set approval by size. A collector can confirm an unchanged limit on a small account, the AR manager can approve mid-size changes, and the controller signs off on the largest accounts and on any exception.
If you want routine follow-up handled so your team has time for credit reviews, Get Started with Abivo.
