Customer credit limits and blocking in Business Central

For B2B businesses selling on credit, controlling customer exposure is operationally critical — too much credit means bad debt risk; too little means lost sales. Business Central's credit limit and blocking features structure both sides: limiting how much each customer can owe, and stopping new business when policy demands.

Credit limit setup. Each customer carries a Credit Limit (LCY) field — the maximum balance you'll permit before warning or blocking. The setup is per customer on the card; templates can default credit limits per customer template.

Credit Warnings. Three options for what happens when a new sales document would push the customer over their limit:

• Both — show warning AND show overdue balance.
• Credit Limit — only warn when over credit limit.
• Overdue Balance — only warn when overdue balance exists.
• No Warning — proceed without warning (rare; disables the protection).

The warning surfaces during sales document entry, before posting. The user sees the customer's outstanding balance, the proposed addition, and the credit limit. They can accept the warning (post anyway), close the document, or escalate to a credit manager.

Hard vs soft enforcement. By default, the warning is soft — the user can override and continue. For hard enforcement (block posting until override), customise the response through workflow:

• Add a workflow rule that requires approval before posting if the customer is over limit.
• The credit manager is the approver; only their approval releases the document.
• The approval is auditable.

Customer blocking. Beyond credit limits, customers can be blocked entirely:

• Ship blocked — no new sales orders can ship; existing orders can post.
• Invoice blocked — no new invoices can post.
• All blocked — no sales activity at all.

Blocking is a binary setting on the customer card; the system enforces immediately at order entry. Use cases:

• Customer disputes; freeze further sales until resolved.
• Customer in collection; no new credit extension.
• Customer ceased operations; archive the relationship.
• Compliance reasons (sanctions list, fraud investigation).

Vendor blocking works the mirror image — blocking purchases from a specific vendor.

Item blocking. Beyond customer / vendor, individual items can be blocked:

• Blocked — no sales of this item.
• Sales Blocked — block on sales only (purchases allowed for run-down).
• Purchase Blocked — block on purchases (sell-down inventory).
• Production Blocked — block production of this item.

Useful for items being phased out, recalled, or under quality hold.

Integration with collections. Customers entering serious overdue states can be auto-blocked via workflow:

• Reminder level reaches 3 → workflow auto-sets Block = Ship.
• AR ageing exceeds N days → workflow notifies credit manager.
• Customer's account moved to collections → manual block applied.

These workflows don't ship out of the box but are easily built in Power Automate.

Credit limit utilisation reporting. Reports show:

• Customer balance vs credit limit per customer.
• Percentage utilisation.
• Customers approaching limit.
• Customers over limit.

Useful for credit managers' daily / weekly review.

Limits.

• No multi-currency credit limits — credit limit is in LCY only. Multi-currency customers have FX implications.
• No graduated tiers out of the box — over 80% might warn, over 100% might block. Use workflow for tiered behaviour.
• No external credit-bureau integration — for automated risk-score-driven limit adjustments, integrate via Power Automate.

Operational reality. Credit-limit and blocking are operational tools — they only work if someone actively manages them. Schedule quarterly credit reviews. Adjust limits as customers grow or shrink. Investigate every over-limit warning. Without active management, limits become folklore that everyone ignores.