Credit Hold

A seller that offers payment terms takes credit risk until the customer pays, and a credit hold pauses further exposure when a balance becomes overdue, exceeds a limit or triggers another risk rule. The hold should prompt review, not replace it, so finance must check the facts before stopping an important shipment or releasing more goods.

A hold can apply to the whole account or a specific sales order, and Microsoft Dynamics documentation describes configurable credit-management holds for orders. Oracle NetSuite documentation likewise explains customer limits and holds, but these are software behaviours, not universal legal rights to suspend performance, so read the contract and system configuration.

Set clear triggers: a company might flag an account when invoices are more than a defined number of days overdue or when open orders plus receivables exceed the approved limit. A threshold should reflect the customer's history, margin and exposure, since an arbitrary single rule may be too strict for some buyers and too lax for others.

Calculate exposure consistently by including unpaid invoices and the value of orders not yet paid, avoiding double count, and consider credit notes, cleared payments and deposits. If a customer owes $80,000 and has a new $30,000 order against a $100,000 limit, projected exposure is $110,000 before other adjustments, so the $10,000 excess needs a decision.

A disputed invoice changes the conversation, because a customer may have reported damaged goods or a pricing error, so investigate the dispute rather than treat silence as refusal to pay, record the undisputed balance separately, and ensure staff know the issue and the contract's dispute process even where a hold remains justified. Payment promises are not cash: a customer may say it initiated a bank transfer, but the seller should verify receipt and settlement status under its own policy.

A screenshot can be altered or a transfer recalled, so for urgent orders a deposit or narrower shipment may be safer than removing every restriction. Assign release authority, since a credit manager might approve a small temporary exception while a large exposure needs a director, and require a reason, amount and expiry date, because the system should show who released the hold and an override that remains indefinitely defeats the control.

Sales needs a practical path, since a salesperson may have a valued customer waiting for parts but should not promise dispatch until finance has reviewed credit status. Give the team a clear response time and escalation contact, because an unexplained "computer says no" can damage a relationship and conceal an accounting error.

Communicate clearly with the customer by stating which invoices are overdue, the amount and how to raise a dispute or send payment evidence, avoiding accusations and checking notice terms and obligations already accepted if the seller plans to stop future deliveries; a polite, specific message can speed resolution without giving up credit control. A hold can expose process problems inside the seller, as the customer may have paid but cash was posted to the wrong account, or a credit note may be waiting for approval, so reconcile the ledger before drawing conclusions because a mistaken hold can disrupt operations and make the seller look unreliable.

Credit limits should be reviewed as the relationship changes, since a customer doubling its orders might need a fresh assessment and a larger approved limit, and more sales are not always profitable if receivables stretch or defaults rise, so use payment history, available financial information and commercial context. A credit hold is a pause to make a considered decision about further credit: define triggers, verify the ledger and contract, give staff an approval route and explain the issue to the customer, recording the release or continued restriction with its reason so that the control protects cash without surprising the wrong customer.