Credit Exceptions Need an Exit

Opening Ledger

I am less interested in whether a business ever makes a credit exception than in what happens after it does. Commercial judgment requires room to accommodate an unusual order, a seasonal requirement or a customer whose circumstances deserve closer examination. I would not replace that judgment with an inflexible rulebook. But I would insist that the approval describe its own boundaries. What exactly has been authorized? What evidence supports it? What ends it? This week, I want to examine the architecture of a useful exception: permission that remains specific, visible and subject to a deliberate exit. The objective is not to eliminate flexibility. It is to keep flexibility from becoming an unexamined commitment.

Main Feature

Permission is not a permanent credit decision

Consider an illustrative approval: a customer needs an order released above its normal credit limit. The commercial rationale is credible. Management authorizes the release. The order ships.

The important question is what that authorization means for the next order.

I would draw a firm distinction between approving a transaction and changing the standing credit decision. The former permits a defined departure. The latter establishes a different basis for future business. An exception process should make that distinction explicit rather than leave the next employee to interpret an old email.

NACM distinguishes credit policy, which establishes the governing framework, from credit procedures, which specify the steps used to carry it out. Its discussion includes account monitoring, approval procedures and communication of decisions among the components of a credit policy. That distinction provides a useful foundation for designing exception controls. (bcm.nacm.org)

My proposed standard is straightforward: an exception should describe both the permission being granted and the decision that must follow it.

Name the departure precisely

Do not begin the approval record with the importance of the customer. Begin with the requirement being changed.

Is management authorizing exposure above an established limit? Accepting a longer payment period? Proceeding without information normally required? These are different decisions. I would record them separately, even when they concern the same order.

This is not an argument that every departure is unsound. The OCC's bank-supervision handbook expressly recognizes that an exception does not automatically constitute excessive risk-taking. That guidance concerns banking; I am using it here as a management analogy, not presenting it as a rule governing ordinary trade suppliers. (occ.treas.gov)

For trade-credit decisions, I would write the exception narrowly enough that another authorized employee could determine whether a later request falls inside or outside it. Name the customer entity, the covered transaction, the permitted exposure and the specific requirement being relaxed.

Avoid a general instruction to support the account. Require an authorization that can be applied without guessing what its author intended.

Separate the commercial reason from the risk response

A persuasive commercial reason answers why the business wants to proceed. A risk response answers how the business intends to address the additional uncertainty.

Keep those explanations separate in the approval record.

For example, preserving a valuable relationship may explain the commercial objective. It does not explain why an enlarged balance is acceptable. Ask the decision-maker to identify the evidence supporting payment expectations and the limits placed on the authorization.

The OCC's handbook describes documenting underwriting exceptions with their justification or mitigating factors and obtaining approval through the appropriate authority. That is the narrower principle worth borrowing: record the reasoning, not merely the permission. (occ.treas.gov)

I would also distinguish an assumption from a completed action. If an approval depends on receipt of a customer payment, the record should identify who verifies receipt. Do not allow a statement that payment is expected to satisfy a condition requiring payment to have arrived.

An executive should be able to read the file and identify what was known, what remained uncertain and what management chose to accept.

Design the exit before the release

My recommendation is to give each temporary exception a defined endpoint and a named reviewer.

The endpoint might be completion of the specified transaction, receipt of requested information or a scheduled reassessment. Choose an event that matches the reason for the exception. A seasonal accommodation should not quietly become a standing authorization for unrelated orders.

Specify the next decision as well. At the endpoint, the reviewer should close the exception, recommend a formal change to the standing credit terms or request a newly justified exception.

Do not make renewal an administrative copy of the original approval. Require the reviewer to explain what has changed and what remains unresolved. Repeated authorization should be visible as repeated authorization.

Treat expiration as an internal approval boundary, not an instruction to disregard an existing customer commitment. This is an educational management framework, not legal advice. Contractual questions require separate review; applicable legal rules vary by state.

Review the accumulated exceptions

The OCC cautions that exceptions which appear manageable individually can increase portfolio risk in aggregate. It also describes comparing the performance of loans with exceptions against those without them. The lesson I draw for trade credit is to review the pattern as well as the individual approval. (occ.treas.gov)

I would ask management to examine the exposure covered by active exceptions, the reasons for renewal and the assumptions shared across approvals. Are separate customers all receiving accommodations based on the same expectation about future business? Are the same missing documents repeatedly deferred?

Use that review to decide whether the company needs different account decisions or a better policy. Do not assume the correct answer is always tighter control. A recurring, well-supported need may justify a formally designed credit arrangement rather than an endless sequence of temporary approvals.

NACM's credit-decision education emphasizes finding ways to approve business with a reasonable expectation of payment, including alternatives acceptable to credit, sales and the customer. Flexibility belongs in the process. (clc2.nacm.org)

Make the final status explicit

I would consider an exception unfinished until its disposition is recorded.

Document whether it ended as intended, required another approval or led to a revised standing decision. Preserve the original rationale alongside the outcome so the next reviewer can compare expectation with experience.

The governing question is not whether management was willing to say yes. It is whether the business can still explain the scope of that yes—and identify the point at which another decision is required.

Field Note

Illustrative scenario—not a real case.

A distributor receives an unusually large order from an established customer. The order would exceed the customer's normal credit limit. Sales requests an accommodation because the order supports a specific installation project.

Rather than increasing the standing limit, management approves only the identified order. The record names the approving executive, specifies the permitted exposure and assigns a credit manager to review the account after the expected payment is received. It also states that later orders are not covered by this authorization.

Before that review, the customer submits another large order. The credit manager treats it as a new request, not as an extension of the earlier permission. Management must assess the updated account position and make a separate decision, subject to any existing contractual commitments.

The educational point is the boundary. The original approval remains useful without becoming an indefinite instruction to keep extending credit.

What This Means

• Distinguish a transaction-specific exception from a change to the standing credit decision.
• Document the commercial objective separately from the evidence and conditions supporting approval.
• Give temporary permission a defined endpoint, a responsible reviewer and an explicit disposition.
• Review repeated exceptions together before deciding whether to revise account terms or the underlying policy.

From the Library

Insights — Insights is the companion reading destination for this edition's management questions: what to authorize, what to document and what to revisit.

Related Reading

• Portfolio Analysis
• Books by Chris Eaton — free PDF library

Closing Ledger

For this week's management discussion, I would bring an active exception to the table—not the most troubled account, just an ordinary accommodation. Ask someone who did not approve it to explain its scope, its conditions and its endpoint. If the file cannot answer those questions, improve the record before debating whether the original decision was right. I want credit judgment to remain commercially useful. That requires a clear distinction between a decision made for a particular circumstance and permission that the organization can continue using indefinitely.

A credit exception should carry its boundaries as clearly as its approval.

Sources

• NACM — Building a Credit Policy from Scratch
• OCC Comptroller's Handbook — Lending and Loan Portfolio Risk Management
• NACM Learning — Making Credit Decisions

About Chris Eaton

Chris Eaton is the author of The Black Ledger and writes on commercial recovery, credit, judgment intelligence and the systems that protect earned capital.

Educational content only — not legal advice.