5 min read Customer credit

The credit limit: what it does, what it doesn't, and why it's nearly always bypassed

A limit you can bypass without leaving a trace isn't a limit. How to set one that works without blocking legitimate sales.

What it's really for

A credit limit isn't there to say no. It's there to force someone to decide when a figure is exceeded, instead of letting exposure grow without anyone noticing.

That's the difference between a useful limit and a decorative one: the useful one interrupts. If the system warns but lets you carry on, and nobody reviews those warnings, the limit doesn't exist.

How it gets bypassed in practice

From what we've seen implementing this, the ways around it are always the same:

  • You invoice some other way. A manual invoice, another point of sale, another company in the group.
  • The limit gets raised «temporarily» and nobody lowers it. Six months on, the limit is a history of overruns.
  • The limit doesn't count pending orders. The customer is at 90% of the limit and has three orders still to deliver that will push them over. The system lets them through because they aren't invoices yet.
  • It's compared against today's balance, not the overdue one. A customer can be within the limit and have everything overdue: the number says yes and reality says no.

The check that reveals whether your limit works: find out how many sales were approved over the limit last quarter, and who approved them. If you can't answer, you don't have a limit: you have a field.

How to set it so it doesn't block sales

The risk on the other side is real: a control that's too rigid turns every sale into paperwork and ends up switched off. What works:

  • Make approval fast and on the record. One manager, from a phone, in a minute — with a trail of who approved what.
  • Make the block distinguish reasons. Going over the limit isn't the same as having overdue invoices. The second is more serious and should stop things sooner.
  • Make it count the total commitment: invoiced plus orders still to deliver.
  • Review the limit with data. A customer who's paid on time for two years deserves a higher limit; one who's started stretching, a lower one.

And one implementation detail that matters more than it looks: the limit has to live in a single field. We've seen systems with two credit-limit fields inherited from different eras, where one was displayed and the other was validated. The result is a control that looks active and isn't.

Collections and customer credit

On the same topic

A limit that actually stops things

In Zyntello the limit counts invoiced and ordered, distinguishes over-limit from overdue, and approval leaves a trail of who gave it.