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.
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 | 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". |
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. |
Settings & permissions
- Module
module.creditcontrol. creditcontrol.profile.view/.managefor profiles,creditcontrol.limit.overridefor
releasing beyond the limit.
- 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.
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.