A sales rep enters an order for a customer who's already $40,000 past their credit limit, three invoices overdue. Business Central lets the order through anyway, because nobody configured the system to stop it — the credit limit field on the customer card has been sitting there since implementation, populated with a number, doing nothing.
This is a specific, common gap: companies enter a credit limit because the field exists, without ever configuring the actual enforcement behavior that would make that number mean something at the point an order is placed.
The Credit Limit Field Alone Does Nothing
Entering a value in the Credit Limit (LCY) field on a Customer Card is necessary but not sufficient. Business Central checks credit limit against open balance plus outstanding order value only when credit warnings are actually enabled in Sales & Receivables Setup — and even then, the default behavior is typically a warning a user can click through, not a hard block. Companies that assume entering a limit automatically stops bad orders are trusting a number that isn't actually being enforced anywhere in the transaction flow.
Warning vs. Blocking: A Deliberate Choice
Sales & Receivables Setup lets you configure whether exceeding a credit limit produces a soft warning or genuinely blocks order entry. A soft warning is appropriate for a business that wants sales staff to have visibility and judgment on a case-by-case basis — a longtime customer briefly over limit due to a large, legitimate order might be a fine risk to take. A hard block is appropriate where credit risk needs to be a strict, non-negotiable control rather than left to individual judgment.
Most companies never make this choice deliberately — they inherit whatever the default was set to during implementation, which may not reflect how the business actually wants to manage risk today.
Aging Data Feeds the Real Picture, Not Just the Limit
A credit limit check that only looks at total outstanding balance misses a genuinely important distinction: a customer with $30,000 outstanding, all current, is a very different risk than a customer with $30,000 outstanding, most of it 90+ days overdue. Pairing credit limit enforcement with a routine review of the aging breakdown — not just the total — is what actually protects cash flow, since a customer can sit under their nominal limit while still being a real collection risk.
Credit Holds Need an Actual Owner
When an order does get flagged or blocked, someone specific needs to own the decision to release it — verify payment status, check with the customer, or explicitly approve shipping despite the flag. Without a named owner and a documented process, blocked orders either sit in limbo frustrating sales, or get overridden by whoever hits the block first, defeating the purpose of the control.
Where to Start
Check three things directly: whether credit warnings are actually enabled in Sales & Receivables Setup, whether the warning-vs-block behavior matches how your business genuinely wants to manage risk, and whether someone specific owns the decision when an order gets flagged. A credit limit field with a number in it and nothing enforcing it is a false sense of control.