How do I set and enforce customer credit limits and credit holds?

A credit limit caps how much open AR a customer can carry before new orders require review. A credit hold is the enforcement mechanism: once open AR (or open AR plus a pending order) would exceed the limit, the order is blocked until a credit manager reviews and either releases it or requires action first. The hold is a control, not a collections tool on its own.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 16, 2026Last reviewed September 16, 2026Editorial policy

Part of the accounts receivable and collections guide.

What a credit limit is	The maximum open AR balance a customer is approved to carry
What a credit hold does	Blocks a new order or shipment once the limit would be exceeded, pending manual review
Who resolves a hold	A credit manager — release with an exception, require partial payment first, or deny the order
Not the same control	A credit hold is not a dunning or collections action — it prevents new exposure, it doesn't recover past-due balances
Common trigger definition	Open AR + value of the pending order > approved credit limit

Why a credit hold isn't a collections action

A credit hold and a dunning sequence solve different problems. Dunning chases a balance that's already past due. A credit hold prevents new exposure before it's created — it fires the moment a new order would push a customer's open AR past their approved limit, regardless of whether any existing balance is actually late. A customer with a perfect payment history can still hit a credit hold simply by ordering enough, on-time balances included, if the new order would put total open AR over the ceiling.

What actually goes into setting the limit

NACM's guidance on credit policy treats the limit as a deliberate risk decision, not a default — set from a credit application, trade references, and payment history, and revisited periodically rather than fixed at onboarding and never touched again. The specific number matters less than having a documented, repeatable process behind it: a limit nobody can explain the basis for is a limit nobody can defend when a customer disputes being held.

What should trigger a hold vs. just a warning

Not every approach to the limit should stop an order cold. A hard hold that blocks every order the moment a customer is anywhere near their limit creates friction on accounts that are otherwise perfectly healthy — a customer running close to their limit but with a clean payment history is a different risk than one running close to their limit with two invoices already 60 days past due. Distinguishing the two in the rule itself, rather than treating every near-limit order identically, is what keeps the hold from becoming a blunt instrument that annoys good customers as often as it catches bad ones.

What happens after an order is held

A held order needs an actual resolution path, not just a flag someone eventually notices. NACM's guidance frames the credit manager's options as: release the order as an approved exception (a project-related or temporary circumstance), require a partial payment or deposit before releasing it, or deny it until the underlying balance is addressed. Whichever path is taken, it should be logged against that customer's credit file — an exception granted once without a record becomes the default the next time, quietly eroding the limit the policy was supposed to enforce.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Checklist

Hold vs. warning vs. no action, by account condition

Account condition	New order pushes over limit?	Any balance past due?	Action
Healthy, near limit	No	No	No action — order proceeds normally
Healthy, at limit	Yes	No	Soft hold — notify the account owner, fast-track review; likely a quick exception approval
Past due, within limit	No	Yes	Warning to the credit manager, but not an automatic order hold — this is a collections issue, not a limit issue
Past due, over limit	Yes	Yes	Hard hold — require payment on the past-due balance before releasing any new order

Frequently Asked Questions

No — NACM's guidance treats the limit as a per-customer risk decision based on that customer's credit application, trade references, and payment history, not a single company-wide number applied uniformly.

Yes — a hold triggers on open AR (including current, not-yet-due balances) exceeding the approved limit, not on delinquency specifically. A customer who pays on time every month can still hit their limit purely on order volume.

Periodically, not just at onboarding — a limit set when an account was new and small can become stale as the relationship grows, in either direction: too low for a customer who's proven reliable, or too high for one whose payment behavior has deteriorated.

Sources

Topic

AR & Collections

Accounts receivable is the money customers owe a business for goods or services already delivered on credit — a current asset on the balance sheet until it's collected. AR and collections, as a practi…

Definition

What is an AR aging report and how do I read it?

An AR aging report lists every open invoice grouped by how long it's been outstanding — current, 1-30, 31-60, 61-90, and 90+ days past due. Read it by tracking the bucket distribution over time, not just the total; a shrinking current bucket and growing 90+ bucket signal a collections problem before it shows up in a blended DSO figure.

How-to

How do I automate dunning and collections reminders?

Schedule reminders relative to the due date (a few days before, then at set intervals after), with escalating tone and channel, and add a suppression check before each send confirming the invoice is still genuinely open and undisputed. Most accounting systems support scheduling this natively; the suppression check is what prevents the most damaging automation failure.

Diagnostic

How do I handle a customer short-payment, deduction, or chargeback on an invoice?

First classify the deduction — valid claim (damaged goods, pricing error, an agreed promotion) versus unauthorized short-pay. Valid claims get coded to the right expense/contra-revenue account and closed out; unauthorized ones get disputed and either recovered or written off. Applying the payment before classifying the gap creates unapplied-cash and aging problems downstream.