Credit control
Overview
Credit control limits how much outstanding balance a customer may accumulate. The application states what matters itself: without a stored limit nothing takes effect — the module only works once a profile exists.
That is the most important sentence on this page. An enabled module without profiles protects against nothing while looking as though it does.
Core tasks
Create a profile. A profile carries the credit limit and the rules for when it applies. Without a profile no limit applies.
Decide on an override. When the limit is reached, the process requires a deliberate decision — overriding is its own permission, not the same authority as managing the profiles. You grant the single release with a mandatory reason in the Credit release card on the order — or on a draft invoice created without an order (free-text, recurring, billing). An invoice from an order is released by the order.
Get notified when the limit is reached. When a customer's open balance rises above the warning threshold (default 90 % of the limit) or above the limit itself, everyone with creditcontrol.profile.manage receives a notification — in the bell and on the channels chosen in their notification settings. Each level notifies only once per customer: once the balance drops below the threshold again, the notification is reset and only a new rise notifies again. You set the threshold at the top of the Credit control page. The check runs on every balance change (invoice, credit note, cancellation, payment, order confirmed or cancelled) and when you change a limit.
Open a profile. A click on the customer in the list — or Open profile in the credit card on the customer — shows the profile with three tabs: Overview (limit, balance, dunning level, alert level), Limit history and Suggestion.
Read the limit history. Every change of the limit is a row: before, after, source (Created, Manual, Suggestion accepted), reason, who and when. Saving without a changed limit writes no row. Enter the reason when changing the limit in the field Reason for the limit change.
Review and accept a suggested limit. The Suggestion tab calculates from the last twelve months: revenue per month, the customer's payment term, the usual delay (paid amounts and amounts overdue today) and the dunning level. The suggestion is one month of ongoing business plus the time until payment arrives, weighted by payment behaviour (on time 100 %, late or dunning level 1 75 %, clearly late or dunned 50 % — you set the three factors at the top of the page), rounded to full 100 €; a factor of 0 % suggests "no credit". The limit only changes once you confirm Accept suggestion — with exactly the amount shown. If the suggestion has changed in the meantime, nothing is accepted and the card recalculates. An automation cannot accept a suggestion.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Credit profile
| Field | Required | Values / format | What it does |
|---|---|---|---|
Customer customerId | yes | an existing customer | Who the profile applies to. One per customer. |
Credit limit limitAmount | no | amount, 0 or more; empty = no limit | How much may be outstanding. On exceeding it the order warns or is blocked — depending on the risk class. 0 explicitly means no credit, not "unlimited". Clearing the field removes the limit — then no limit applies to the customer. |
Reason for the limit change limitChangeReason | no | text, up to 500 characters | Recorded with the change in the limit history. Only shown when the limit changes; without a change nothing is recorded. |
Count open orders includeOpenOrders | no | yes/no | Whether orders not yet invoiced count against the limit. On is the cautious setting: otherwise the limit is only breached once the invoice has long been written. |
Block from dunning level blockFromDunningLevel | no | 0 or more | From which dunning level to block regardless of the limit. Whoever reaches the second reminder gets no new goods — that is the point. 0 means no block via dunning. |
Risk class riskClass | no | low, normal, high | How strictly the check applies. High blocks where normal only warns. |
Note note | no | text | Why the profile looks the way it does. It is shown on a block — which is why a sentence sales can understand belongs here. |
Active active | no | yes/no | Off means no credit check for this customer. |
Alert and suggestion
| Field | Required | Values / format | What it does |
|---|---|---|---|
Warning threshold alertThresholdPercent | yes | 1 to 100 (%), default 90 | From which share of the limit the credit managers are notified. Exceeding the limit notifies in addition. Takes effect on the next balance change. |
Factor on time behaviorOnTimePercent | yes | 0 to 100 (%), default 100 | How much of the calculated limit the suggestion proposes for on-time payment (up to 7 days, no dunning). |
Factor late behaviorLatePercent | yes | 0 to 100 (%), default 75 | The same for up to 30 days of delay or dunning level 1. |
Factor poor behaviorPoorPercent | yes | 0 to 100 (%), default 50 | The same for more than 30 days of delay or from dunning level 2. 0 % suggests "no credit" (prepayment). |
Accept suggestion
| Field | Required | Values / format | What it does |
|---|---|---|---|
Suggestion shown expectedAmount | yes | amount | The amount you confirm. If the suggestion calculated right now differs, nothing is accepted. The interface sets it itself. |
Reason note | no | text, up to 500 characters | Recorded in the limit history with the accepted change, together with the calculation basis. |
Settings & permissions
- Module
module.creditcontrol. creditcontrol.profile.view/.managefor profiles,creditcontrol.limit.overridefor
releasing beyond the limit.
- Notifications to everyone with
creditcontrol.profile.manage(brand of the customer or across
brands); types Credit limit: warning threshold reached and Credit limit exceeded, each can be switched off in the notification settings.
- Read history and suggestion with
creditcontrol.profile.view, **accept a suggestion and set the
threshold** with creditcontrol.profile.manage.
- The separation is deliberate: whoever maintains limits should not casually override them.
- The outstanding balance comes from invoicing — the limit is measured
against what is actually outstanding.
FAQ & troubleshooting
A customer exceeds the limit and nothing happens. Check whether a profile exists for them. Without a profile no limit applies.
I cannot release an override. Then creditcontrol.limit.override is missing.
The outstanding balance looks too high. It follows the open invoices. Check recorded incoming payments in invoicing.
I get no notification although the limit is exceeded. Only the rise notifies: if the level was already reached, it does not notify again. Also check whether you hold creditcontrol.profile.manage and whether the type is switched off in your notification settings.
The Suggestion tab shows nothing. Without an invoice in the last twelve months there is no basis for a suggestion.
We only want to observe, not block. Create a limit serving observation and grant the override permission generously — the warning remains, the block does not bite.