Where customer credit processing breaks

Customer credit usually breaks at handoffs: sales passing incomplete applications to credit, and order holds released by people who never tell the credit team. Stale scores and late adjustments cause most of the remaining rework. Each failure leaves traces in work queues and order notes, where anyone can find them.

New applications arrive half finished

Sales wants the account open before the first order ships. The application reaches credit missing trade references, a signed agreement, or a legal entity name that matches the bank account. Credit chases the salesperson. The salesperson chases the customer. The order waits.

How to spot it: look at applications that were returned or reopened. If the same missing fields come up again and again, the intake form is the problem, not the analysts. Another sign is a cluster of accounts opened on a 'temporary' limit that nobody ever revisited.

Scores that nobody refreshes

Policy often says existing accounts are reviewed on a cycle. In practice, review happens when something goes wrong. The score from the original application stays on file while the customer's payment behaviour changes underneath it.

The evidence: compare each account's last review date against its current payment pattern. Late payers with untouched limits give it away. So does a forecast of scoring needs that was written once and then copied forward each period.

Holds that leak

Suspending an account is a credit decision, but the hold lives in the order system, which someone else owns. Customer service or a regional manager can push an order through to keep a shipment moving. Sometimes that is the right call. The trouble starts when the release never gets recorded against the credit file, so the next reviewer sees a clean account.

Reinstatement fails the opposite way. Payment arrives and collections marks the debt cleared, but the block stays on. The customer calls sales, sales escalates, and someone lifts it by hand.

What to check: pull orders released from hold and see who released them and whether they entered a reason. Blank reason codes, or releases by staff outside credit, point to an informal approval path. Complaints from customers who have already paid and still cannot order point to a missing reinstatement signal between collections and credit.

Credit memos and adjustments that lag

A disputed invoice, a pricing error or a return should produce a credit memo. Until it posts, the customer looks more exposed than they are and may be suspended over a balance they do not owe. Disputes settled by phone or email often reach the ledger late, or not at all.

Warning signs: accounts on hold where the disputed amount roughly equals the overdue amount. Collectors keeping private notes of agreed adjustments outside the system. That side spreadsheet is the real dispute log, and whoever redesigns the process should ask to see it.

Reports built for the wrong reader

Credit and collection reports tend to grow by addition. Each request adds a column and nobody removes one. The result satisfies auditors but helps nobody decide on a limit. Where delinquent balances go to outside credit bureaus, mistakes are harder to undo. Correcting the ledger does not, by itself, correct the external record.

A quick test: ask who reads each report and what they did after the last one. A shrug means the report is ritual. If customers dispute bureau entries, trace whether adjustments flow through to external reporting or stop at the ledger.

Policy that drifted from practice

Written credit policy sets limits, approval levels and payment terms. Over time, exceptions accumulate. A strategic customer gets special terms. A region starts approving its own increases. None of these is wrong on its own. Together they mean the document describes a process that no longer runs.

Finding the gap: sample recent approvals and match each one against the authority level in the policy. Notice how often an approval sits outside it, and whether anyone signed off on that exception.

Questions to ask the people who run it

The documented process and the working one rarely match. These questions tend to surface the difference:

• When an application comes in incomplete, what is the first thing you do, and who do you call?
• Who can release an order from credit hold today, whether or not the policy allows it?
• How do you learn that a customer has paid and should be unblocked?
• Where do you note an adjustment agreed with a customer before the credit memo posts?
• Which accounts do you review unprompted, and which only when they cause trouble?
• Which report do you actually open, and what do you use in place of the others?
• If nobody checked, what part of this job would you stop doing?

The answers to the last two often show which controls are real and which exist only on paper.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.