The policies and operating controls a business uses to approve customer credit, set limits and terms, monitor receivables, resolve disputes, and collect amounts due.
Credit control is the set of policies and operating controls a business uses to decide which customers may buy on credit, set limits and payment terms, issue accurate invoices, monitor receivables, resolve disputes, and collect amounts due. Its purpose is to support profitable sales without allowing receivables, bad debt, or collection delays to create unacceptable cash-flow risk.
In some banking and macroeconomic writing, credit control can have broader meanings. This page uses the common business and trade-credit meaning.
| Stage | Control question | Typical evidence |
|---|---|---|
| Customer onboarding | Is the customer legitimate and able to pay? | Identity, registration, financials, references, credit reports |
| Credit decision | What exposure and terms are acceptable? | Approved limit, payment terms, security, authority record |
| Order release | Will this order exceed the available limit or violate a hold? | Open orders, invoices, payments, disputes, current limit |
| Invoicing | Is the invoice complete, accurate, and sent promptly? | Purchase order, delivery evidence, invoice, tax details |
| Monitoring | Which balances are due, disputed, or deteriorating? | Aging, DSO, utilization, dispute log, promise-to-pay history |
| Collection | What follow-up is appropriate and authorized? | Reminders, contact notes, statements, escalation record |
| Remediation | Should terms, limits, security, or supply change? | Updated review, approval, payment plan, hold or limit decision |
| Write-off or recovery | Is the accounting and legal treatment supportable? | Collection evidence, approval, legal advice, recovery record |
Credit control should coordinate sales, customer service, billing, treasury, accounting, and legal functions. Sales incentives should not permit unauthorized limits or terms.
Assume a business reports:
$12 million;$1.5 million; andA simplified DSO calculation is:
DSO = ($1.5 million / $12 million) x 365 = 45.6 days
If standard terms are 30 days, 45.6 days may justify investigation. It does not prove every customer is 15.6 days late. The result can reflect sales growth, seasonality, billing timing, disputes, customer mix, or a few large past-due accounts.
Now assume the closing aging is:
| Aging bucket | Balance |
|---|---|
| Current | $850,000 |
| 1-30 days past due | $300,000 |
| 31-60 days past due | $150,000 |
| More than 60 days past due | $200,000 |
| Total | $1,500,000 |
The $200,000 oldest bucket deserves account-level review even if aggregate DSO later improves. The controller should identify disputes, collectability, concentration, promises to pay, credit holds, and allowance implications rather than relying on one average.
A customer limit should reflect more than annual sales. Relevant factors can include:
Terms should state when payment is due, applicable discounts, billing and dispute procedures, and consequences of default. Enforceability and late-payment rights vary by jurisdiction; template language should not replace legal review.
An aging report groups open invoices by due status. It is useful only if payments, credits, disputes, and unapplied cash are posted accurately.
DSO relates receivables to credit sales. It is a trend measure, not a contractual delinquency calculation. Use consistent sales and receivables definitions when comparing periods.
Utilization compares current exposure with the approved limit. The exposure definition may include invoiced balances, unbilled deliveries, open orders, accrued charges, and related entities.
Late payment can arise from price, quantity, quality, delivery, tax, or documentation disputes. Collection pressure will not fix a valid billing error.
Repeated missed promises can reveal deterioration earlier than a formal default. Contact notes should record who promised what amount by which date.
A documented escalation path can move from reminder to direct contact, account hold, revised terms, payment plan, collection agency, formal demand, or legal action. The correct sequence depends on amount, age, dispute status, customer importance, recoverability, contract, and law.
Before escalation, confirm:
The United Kingdom, for example, has statutory late-payment rules, but those rules should not be generalized to another jurisdiction or transaction.
| Mitigant | Potential benefit | Important limitation |
|---|---|---|
| Deposit or advance payment | Reduces unsecured exposure | May affect competitiveness and customer cash flow |
| Parent guarantee | Adds another repayment source | Value depends on enforceability and guarantor capacity |
| Letter of credit | Adds a bank undertaking under stated terms | Documentary compliance and fees matter |
| Trade credit insurance | Covers specified insured losses | Limits, exclusions, retention, reporting, and claims conditions apply |
| Factoring | Converts or finances receivables | Cost and recourse terms vary |
| Credit hold | Prevents additional exposure | Does not collect the existing balance |
Credit control cannot eliminate customer insolvency, fraud, operational errors, legal disputes, or economic shocks. Aggressive controls can also damage valid customer relationships or suppress profitable sales. The objective is documented, risk-based control rather than maximum collection pressure or zero receivables.
This page is educational and is not legal, accounting, tax, collection, or personalized financial advice.