The distance between a sanctioned limit and a usable rupee

A business owner can leave a lending conversation believing that a sanctioned amount is money available for tomorrow's payroll. The lender may believe something narrower: a limit has been approved, subject to evidence, review conditions and a particular draw process. Neither party needs to be deliberately misleading for that difference to become serious. I have seen an internal distinction that was obvious to a credit team disappear in a branch conversation. By the time servicing explains it, the customer has made plans. The resulting disagreement is often described as a service delay when the original problem was an unclear commitment.

What the customer believes has been agreed

I first encountered this problem after moving from trade services into lending. In trade services, our work concerned the records behind commercial transactions. Inside a lender, an explanation could influence a customer's decision to place an order, pay a subcontractor or accept another contract. That made the language around availability more consequential. I could not assume that a customer would interpret an internal status label as we did. Nor could I ask a servicing colleague to repair a promise made elsewhere without giving them a clear account of the actual approval and the remaining conditions.

The answer was not to make every conversation longer. It was to identify the few distinctions that changed what the customer could do. We separated the sanctioned limit from the amount currently drawable, recorded the conditions still outstanding and named the person responsible for assessing them. A review date also needed an explanation: did it mean a routine update, a fresh lending decision or the expiry of the current availability? Those questions belonged in the product and operating design before they became an argument at the counter. The same words had to mean the same thing in the sales discussion and the service record.

I do not regard a signed document as evidence that the explanation succeeded. The document matters, and legal colleagues determine its proper form. But a service organisation also needs to know whether its own people can explain the commitment consistently. I have asked managers to describe a facility using an actual customer situation: an invoice has been disputed, a buyer has changed its payment date or a required item has not arrived. The exercise often reveals a gap that a general presentation misses. It shows where colleagues are relying on an assumption rather than an agreed decision path.

Where an explanation becomes a commitment

There is a difficult boundary between helping a customer understand a condition and implying that the condition will be waived. A colleague may say that a document is usually accepted, or that a review normally takes a few days, intending to be helpful. The customer may hear an assurance about this case. I ask our managers to distinguish the process we can describe from an outcome that remains subject to assessment. This does not require cold or evasive language. It requires enough precision to preserve the decision that still has to be made, while giving the customer a useful next step and an accountable contact.

The lending relationship is also affected by what we omit. If one condition is likely to determine whether funds can be drawn, it should not be buried beneath a long list of routine requirements. In the maintenance-contractor case, evidence of accepted work mattered because some invoices were disputed. The important question was not whether the borrower could supply another copy of an invoice. It was what the wider evidence established about the obligation behind it. A request for more paperwork would have been a poor substitute for explaining that distinction. It could create activity without moving the decision any closer to resolution.

I have sometimes been told that this approach makes a lender less competitive. A more confident conversation may win the customer's attention, while a careful explanation exposes uncertainty. That is a commercial tension worth acknowledging. My response is to ask whether we are comparing the same promises. If a competitor offers genuinely different terms, we should understand them. If the difference is merely that our unresolved condition has not yet been mentioned, the apparent advantage is fragile. It will surface when the customer attempts to use the facility. Growth built on that gap also places a cost on the colleagues asked to explain it later.

The internal incentive can make the problem harder. A team measured only on sanctions or disbursements may treat the service handover as someone else's work. I want business development to remain responsible for the accuracy of the proposition it presents, without making it the judge of every subsequent credit question. That requires a handover both teams can inspect. It also requires managers to recognise that a smaller, usable commitment may serve the business better than a larger headline amount whose conditions have not been understood. I would not translate that judgement into a universal rule about facility size; the evidence and customer context still matter.

Making the handover inspectable

A useful handover record is shorter than a complete credit file but more specific than a status update. It should identify the current decision, the remaining conditions, the next review and the owner of an unresolved issue. I also want it to show when the explanation changed. A customer who heard one thing last week should not be told a different thing without an account of the new fact or decision. The history protects the quality of the conversation. It allows a manager to examine whether the delay arose from a missing item, an unclear instruction or a legitimate reassessment.

Technology can make that record accessible, but the software does not settle the meaning of its fields. A label such as approved can conceal several operating states unless the organisation agrees what it permits. I ask product, credit and servicing colleagues to test those labels against difficult cases before asking technology teams to automate them. Otherwise the system can distribute an ambiguity more quickly. The useful measure is whether the person answering the customer can identify the actual position and the next responsible decision, rather than whether every screen contains a completed field.

At board level, I would expect a concise account of recurring failures in that handover, not a tour of individual account screens. Directors need to know whether the company repeatedly makes promises that its process cannot support and whether management is addressing the cause. They should also see the commercial cost of a more precise proposition when it affects planned growth. My experience has made me cautious about treating customer explanation as a finishing layer applied after product approval. For a working-capital lender, the explanation is part of the product. It determines whether a commitment approved in one room can be understood and carried out in another.