The short answer

To stop reps selling past credit limits, set each limit from the customer’s monthly purchases and payment term, and check every order against what they have been invoiced less what they have paid, plus the new order. Hold orders over the limit for a few named people in finance or management to release, never the rep. The same check must run in the van and hold when the rep works without signal.

Key takeaways

  • A customer on 30-day terms usually owes about a month’s purchases; add around 25% headroom for a busy month.
  • Count payments the moment they are recorded, so a collection on the visit frees credit on the same visit.
  • If the same customer is released every month, raise the limit or stop the releases.
  • Give the rep a way to keep the sale: collect on old invoices first, or sell the excess for cash.
  • Read the aging alongside the limit; invoices more than 60 days past due deserve a conversation before the next order.

Why reps sell past the limit

Reps are usually measured on sales, and a customer who wants another delivery is a sale today. The cost of the unpaid balance arrives months later and lands on someone else. Add a long relationship, an owner who promises to pay next week, and a rep who cannot see the balance anyway, and the limit becomes a suggestion.

None of that is solved by asking reps to be careful. It is solved by a limit the system checks on every order, the same way for everyone.

Set limits that mean something

Start from what the customer buys and how long they take to pay. A customer on 30-day terms who buys about the same each month will normally owe around one month’s purchases. Add a margin for a busy month, and you have a limit you can defend.

New customers start low and earn more by paying on time. Review every limit at least twice a year, and whenever a customer’s buying or paying changes.

TipNever set a limit you would not defend to the customer’s face; a number nobody believes gets overridden.

Check the right balance

The figure to compare is what the customer owes now plus what they are about to take: everything invoiced, less everything paid, plus the new order. Checking only overdue invoices, or only last month’s, lets a customer pile up current debt until it all falls due at once.

Payments should count the moment they are recorded. A rep who collects on the visit should be able to sell on the same visit, because the collection has freed the credit.

Decide: hold or refuse, and who releases

An order over the limit can be held for someone to decide, or refused outright. Holding suits most distributors: the order is not lost, and someone with authority looks at it. Refusing suits businesses that want no exceptions at all.

Whoever releases, it is not the rep and not the rep’s sales target. Give release rights to a few people in finance or management, and agree what they look at.

  • Is any invoice overdue, and by how long?
  • Has the customer paid on time over recent months?
  • Is the excess small against the limit?
  • Is a payment promised, and by when?
  • Should the limit itself be raised?

TipIf the same customer is released every month, raise the limit or stop the releases; a limit that is always overridden is no limit.

Make the rule hold in the van

The office is not where most credit is given away; the van is. The check has to run on the rep’s orders and invoices too, at the moment they are saved, and it has to hold when the rep is working without signal. A rule that only the office follows teaches reps to sell first and explain later.

Give the rep a way out that keeps the sale: collect on the old invoices first, or sell the order for cash. Both keep the customer stocked without adding to the debt.

  1. Show the rep the customer’s balance before the visit
  2. Collect on open invoices first
  3. Raise the order; if it is over the limit, it waits
  4. Offer a cash sale for the excess
  5. Leave held orders for the office to decide

Watch age as well as amount

A customer can be under the limit and still be a problem, if part of the balance is months past due. Read the aging alongside the limit: an account with invoices more than 60 days past due deserves a conversation before the next order, whatever the limit says.

Credit control is a conversation with the customer as much as a rule in the system. Tell customers their limit and their terms, so a held order is never a surprise.

TipTell the rep why an order was held the same day; a rep who hears it first from the customer looks foolish and stops trusting the rule.

Checklist: Credit control for field sales

  • Give every credit customer a limit and terms
  • Base each limit on purchases and payment term
  • Check invoiced less paid, plus the new order
  • Count payments as soon as they are recorded
  • Hold orders over the limit; do not just warn
  • Give release rights to a few named people
  • Make the same check run in the rep app
  • Read the aging alongside the limit
  • Review limits twice a year

In Axon Suite

How Axon Suite handles it

In Axon Suite every order is checked against the customer’s credit limit when it is saved, in the office and in the rep app: what the customer has been invoiced less what they have paid, plus the new order. An order over the limit is held or refused as your sales settings say, an invoice over the limit is refused, and only a user whose role holds the Approve level on sales orders can release a hold. Documents made offline are checked when they reach the server, the same as online.

Feature

Credit limits on every order

Every order is checked against the customer’s limit the moment it is saved, in the office and in the rep’s app. Over the limit, it is held for someone with approval rights or refused, as your settings say.

Open: Credit limits on every order
Feature

Selling from the van with no signal

Check-ins, orders, invoices, payments and returns are saved on the phone when there is no signal, then sent once it returns. Each one keeps the day of the sale and is sent only once, however often it has to retry.

Open: Selling from the van with no signal
Feature

Roles that decide who does what

Every user holds one role, and every role holds a level per area: View, Create, Edit, Full or Approve. Without the level, the screen turns read-only and the server refuses the change all the same.

Open: Roles that decide who does what
Feature

Aging and party statements

Aging buckets every open invoice and bill by its due date. A statement gives one customer or vendor their running balance with the same aging beneath it, printed in Arabic or English.

Open: Aging and party statements
Feature

Payment terms and due dates

Set each term once: net days, end of this month or the next plus days, or a fixed day of the month. Every customer and vendor carries a term, and each document’s due date is calculated from its date and that term.

Open: Payment terms and due dates

Before you go

Questions owners ask

Does a limit of zero mean no credit?

Decide what zero means and write it down, because systems differ. In Axon Suite a limit of zero means no limit, so enter a figure for every customer whose orders should be checked.

Can a rep get round the limit by working offline?

They should not be able to. In Axon Suite the credit check runs on the server when the document arrives, so an order made offline is held or refused just as it would be online.

Who should be allowed to release a held order?

A few people in finance or management who can see the customer’s full history, never the rep who raised the order. A release should be a deliberate decision with a reason, not a click to clear a queue.

Glossary

Terms in this guide

Open the glossary

See your own van sale reach the ledger in 30 minutes.

Chat on WhatsApp