Skip to main content

Perspectives · Guide

Credit limits and agents: who approves the override?

In distribution, margins live in exceptions: a dealer's limit stretched on a phone call, a discount above authority. Agents can handle the routine, but every override needs a named person behind it, and the rules for who that is should be written down before the agent starts.

Author
M. K. Elango · Founder, elan1
Published
Reading time
4 min read
On the desk phone, a credit manager makes notes on a printed report.

Ask the owner of any FMCG distributor how credit really works and you will hear two answers. There is the policy: limits set by outstanding, history and season. Then there is the practice: a trusted dealer calls the salesman, the salesman calls the credit manager, and a truck leaves with stock worth more than the limit allows.

Neither answer is wrong. The practice exists because rigid limits lose good business. The trouble starts when an agent is put in the middle of that practice without anyone deciding which part of it the agent is allowed to perform.

Three kinds of credit decision

It helps to separate the decisions an agent will meet, because each needs a different answer.

  1. Within the limit: an order that fits the dealer's existing limit. The agent can process it, and the action is recorded.
  2. Above the limit, inside a band: an override that is normal for this dealer and this season. A named person decides, quickly, with the history in front of them.
  3. Outside the band, or a change to the limit itself: a decision about the relationship, not the order. It needs the credit manager, and sometimes the owner.

The mistake is to let an agent treat the second kind as the first because "we always approve Kumar Traders". That habit is exactly what a written rule should capture, with a ceiling, so the agent cannot stretch it further than a person would.

Who approves is a design decision

In elan1, overrides above your line wait for the person you name, usually the credit manager. They see the order, the outstanding, the ageing and the reason the agent gave, and they answer in the console or with one tap on their phone. An unanswered request expires after 24 hours and is refused, so a truck never leaves because nobody replied.

Some changes should never be automated at all. A request to change a dealer's or supplier's bank details is refused by default, however it arrives, because it is the most common route to payment fraud.

Discount authority works the same way

Salespeople carry discount authority in their heads: five per cent on their own, more with the area manager's nod. When an agent drafts quotes or updates the CRM, that authority has to be explicit. elan1 Work checks that no discount is committed beyond the seller's authority, however the request arrives, and that the price list still agrees with the e-invoice and the books.

Write the rules before the agent starts

Before switching anything on, sit down with the owner and the credit manager and write four things on one page:

  • The band within which an override is routine, by dealer tier.
  • The person who approves inside the band, and their deputy.
  • What counts as outside the band, and who decides then.
  • The changes that are always refused, starting with bank details.

That page becomes the rule set. The agent handles the routine, the people keep the exceptions, and the record shows who decided each one. When the season turns and the band needs to move, you change one rule and the record shows that too.

Key takeaways

  1. Separate orders within the limit, routine overrides and relationship decisions; each needs a different route.
  2. Overrides wait for a named person; unanswered requests expire after 24 hours and are refused.
  3. Bank-detail changes are refused by default, because they are the commonest route to payment fraud.

Product capabilities named here carry their current status (available, in pilot or designed) on each product page and in Trust and security. Figures marked “Design target” are specifications, not measurements.

About the author

M. K. Elango

Founder, elan1

M. K. Elango founded elan1 in Chennai to put AI agents to work inside regulated businesses, with a named person answerable for every action that commits them. He writes about pricing, approvals and what it takes for an auditor to trust an agent.

Meet the leadership team : M. K. Elango

Intelligence you can answer for.

Start with one process. Add the next when it holds.