Skip to content

Credit Limits and Auto-topups

Five worklists in the Credit Control menu watch the exposure that builds up between invoices: two for credit limits, three for automatic topups.

They share a shape. Each is a filtered list with a search box and an Export CSV button, a Showing picker for team or personal scope, and an Add TODO button on every row so nothing is worked twice.

Credit Limits Reached lists customers who have hit one of their credit limits. Credit Limits Approaching lists those within 20% of one.

Columns are the customer, which limit, the current amount against the limit, the usage as a percentage, and whether a relevant TODO already exists.

Filters: a customer search, the limit type (Customer credit, Prepaid credit, Unsent credit, Calls credit or Overdue credit) and whether the customer already has a relevant TODO.

Add TODO opens a short form with the subject pre-filled, for example “Customer credit limit reached - Acme Ltd”, a due date and optional details. It is raised under the Credit Limit Check type and assigned to you.

Things to know:

  • Only active customers appear, and never one marked Do Not Chase.
  • The overdue-credit view also excludes customers on a final-invoice status.
  • A limit type your Form Fields configuration hides is never even queried. It cannot appear in the list, the CSV or the menu badge. Two colleagues with different field permissions therefore see different lists, which is intended.
  • The pages need list access to both customers and invoices, plus at least one visible limit field. Without that the menu entry disappears.

For the limits themselves, see Customers.

These three appear only where the auto-topup module is switched on.

What the topup engine actually did. Columns are the customer, when, the outcome with its reason, the amount, the basis against the trigger, and the TODO state.

Filters: the period (last 7, 30 or 90 days, or all history), the outcome (payment created, expected payment only, or cooldown suppressed) and the method (card or Direct Debit).

Needs list access to payments and expected payments as well.

Customers whose basis amount is within 20% of their trigger, so you can see a topup coming.

Configuration or payment-method faults that would stop an enabled profile collecting. The specific reason is shown for each customer:

IssueMeaning
Automatic collection is disabledThe customer is not set to collect automatically
Payment method is not enabled for auto-topupsThe chosen method is not available for topups
No valid payment card is availableThere is no usable card
Payment-card topup timing is not configuredThe card topup timing settings are missing
No valid Direct Debit is availableThere is no usable mandate
Direct Debit topup timing is not configuredThe Direct Debit topup timing settings are missing
Waiting for the minimum interval between topupsThe last topup was too recent
Collection setup requires attentionSomething else about the setup needs looking at

Filter by reason to work one class of problem at a time.

TODOs raised from the auto-topup pages use the Payment type.

For the profiles themselves, see Auto-topup Profiles.