Summary
- Microsoft Dynamics 365 Business Central warns when a customer passes its credit limit or has an overdue balance, but it doesn’t stop the sale. Microsoft’s guide says you can still post when the limit is exceeded.
- The Blocked field on the customer card is what stops documents. Ship stops new orders and shipments, Invoice also stops invoicing, and All stops every transaction, including payments.
- Ship is usually the right setting for putting a customer on stop. It stops new supply while you can still invoice goods that have already gone out, and Microsoft lists payments as stopped only under All.
- Approval workflows can hold an over-limit sales order for a named approver. The order stays locked at Pending Approval until it’s approved.
- Agree who can set and lift a block before you need one, and tell the account manager first. A key account shouldn’t find out from a rejected order.
- Trove is credit control software that connects two-way with Business Central on the Advanced plan. It chases the overdue balance and keeps the decision on the customer’s record, while the block itself stays in Business Central.
What Business Central does when a customer goes over its credit limit
Business Central shows a warning and lets the user carry on. The Credit Limit field on the customer card sets the balance at which warnings start, and Microsoft’s customer guide says Business Central tests the header and lines of journals, quotes, orders and invoices against it. The same guide is clear about the result: you can post even if the limit is exceeded. A blank field means the customer has no credit limit.
The same guide explains how to choose which warnings people see, in the Credit Warnings field on the General FastTab of Sales & Receivables Setup:
- Both Warnings: checks the credit limit and the balance due, and warns on either.
- Credit Limit: warns when the customer’s balance is above its limit.
- Overdue Balance: warns when the customer has an overdue balance.
- No Warning: shows nothing.
For most finance teams, Both Warnings is the useful setting. A customer can be well inside its limit and still be 60 days late, and that’s often the account you most want the person taking the order to know about.
A warning only helps if someone acts on it, and the person who sees it is usually entering an order with a customer waiting. If you want a sale to stop, you need one of the two controls below.
Blocking a customer: Ship, Invoice and All
The Blocked field on the customer card stops transactions, and each option goes further than the last. To set it, search for Customers, select the customer, choose Edit and pick a value in Blocked. These are the effects Microsoft lists for blocking a customer:
| Blocked value | What it stops | What still works | When to use it |
|---|---|---|---|
| Ship | New orders and new shipments | Shipments already made can still be invoiced | The normal choice for putting an overdue customer on stop |
| Invoice | New orders, new shipments and new invoices. Shipments not yet invoiced can't be invoiced either | Reminders and finance charge memos can still be sent | When nothing more should be billed until the account is reviewed |
| All | Every transaction, including payments | Nothing can be posted for the customer | Insolvency, or an account you're closing |
Two details matter more than they look. Invoice stops you billing goods you’ve already delivered, so it can delay the very money you’re trying to collect. All stops payments too, so if a blocked customer pays, you’ll need to lift the block before you can post the receipt.
If a customer has gone into administration, All is usually the right starting point, and our guide to what to do with unpaid invoices when a customer enters administration covers the next steps.
Routing over-limit orders for approval
An approval workflow sits between a warning and a block: the order waits for a named person instead of going through or being refused. Microsoft’s Workflow Setup reference lists credit limit approval workflows for both sales orders and sales invoices, and its workflow events include a customer’s credit limit being exceeded.
To set one up:
- Search for Workflows and choose New Workflow from Template, as described in Microsoft’s guide to workflow templates.
- Pick the sales order credit limit approval template, one of the credit limit workflows in Microsoft’s Workflow Setup reference. Use the sales invoice version if you invoice without orders.
- Name the approver in the workflow response, and add them in Approval User Setup, as described in Microsoft’s guide to setting up approval users.
- Enable the workflow, then test it with a real over-limit order, from entering the order through to requesting approval, so you can see where the check happens in your process.
Once a request is sent, the record moves to Pending Approval and stays locked for processing until every required approver has approved it. Approvers work from the Requests to Approve page and can approve, reject or delegate.
Approval can also cover the limit itself. Microsoft’s approval workflow guide gives changes to a customer’s credit limit as an example, with the new value applying only once the last approval is in. Temporary limits aren’t part of the setup Microsoft describes here, but partner add-ons offer them, including Rand Group’s Credit Manager.
Who should set and lift a block
Finance should own the block, with a clear sign-off for each type of customer. Business Central will record whatever value someone enters, so the rule has to come from you. Write it down once, and restrict who can edit the field if your permissions allow it.
| Customer | Who proposes the block | Who signs it off | Who is told first | Who lifts it |
|---|---|---|---|---|
| Key account | Credit controller | Finance director, after speaking to the sales lead | Account manager, at least a day ahead | Credit controller, once the agreed amount is paid and the finance director confirms |
| Long-tail account | Credit controller | Finance manager, or a standing rule such as 45 days overdue | Account manager, same day | Credit controller, once the overdue balance is cleared |
| New customer | Credit controller | Finance manager | Salesperson who opened the account | Finance manager, after a payment or a fresh credit check |
| Customer with a genuine dispute | Don't block yet | Finance manager decides once the query is understood | Account manager, who helps settle it | Finance manager, when the undisputed balance is paid |
The thresholds here are a starting point, so change them to fit your terms and margins. Disputed invoices need different handling from slow payers, and our guide to invoice dispute management sets out who answers the query and who approves the credit note. For a new or worrying customer, checking their payment record gives the sign-off something firmer to rest on.
Telling sales before the buyer finds out
A block on a key account stops shipments the account manager may already have promised, so they should hear about it from finance first. The account manager owns the relationship with the buyer and the credit controller owns the ledger, and a stop works best when each does their part. Before the Blocked field changes, Priya the credit controller sends Tom the account manager the overdue total, the oldest invoice and the time the block will go on, so he can call the buyer that day. This fits the wider rules for handing an overdue account to the account manager, and sales teams working in HubSpot can see overdue Business Central customers there too.
How chasing and the block work together
A block stops the debt growing, and chasing is what gets it paid, so keep both running with one person in charge of each. Agree what the customer needs to do to come off stop, then put that in the chaser: pay the overdue balance, or give a date you accept.
If you use Business Central’s own reminders, Microsoft confirms they can still be sent with Blocked set to Invoice. It doesn’t say the same for Ship or All, so test your reminder run on a blocked customer before you rely on it. We’ve covered setting up reminder terms and levels separately.
Lift the block as soon as the agreed condition is met. A customer who has paid and still can’t order will ring the account manager, and the goodwill you kept by warning them goes quickly. Check the balance against the credit limit first, because clearing the overdue invoices doesn’t always bring the customer back under it.
A worked example: Example UK Ltd puts a wholesaler on stop for a week
Example UK Ltd supplies food and drink to Example Wholesale Ltd, a key account with a £40,000 credit limit. The balance has reached £52,300, and £18,600 of that is 34 days overdue after three chasers with no reply.
| Day | What happens | Who |
|---|---|---|
| Monday | A new order triggers the credit warning. Priya checks the account and recommends a stop. Rachel, the finance director, agrees after speaking to the sales lead, and Priya tells Tom the block goes on at 10am tomorrow | Priya, Rachel |
| Monday afternoon | Tom calls the buyer, explains the position and asks for a payment date | Tom |
| Tuesday | No date arrives. Priya sets Blocked to Ship and notes the reason. A £4,200 delivery from last week can still be invoiced | Priya |
| Wednesday | Chasing continues, with the condition spelled out: pay the £18,600 and supply restarts | Priya |
| Thursday | The buyer promises payment on Friday. Priya records the date, and Rachel confirms the block stays until the money lands | Priya, Rachel |
| Friday | The £18,600 arrives and is posted, taking the balance to £33,700, under the limit. Rachel confirms, Priya clears the Blocked field and tells Tom, who confirms the held order with the buyer | Priya, Rachel, Tom |
Ship did the job here. Example UK Ltd stopped adding to the debt and still billed what it had delivered. Had Priya chosen All, she’d have had to clear the block before posting the receipt.
Where Trove fits
Trove handles the chasing and the record around a block, while the Blocked field and credit limit stay in Business Central. Trove’s ERP integration syncs two-way with Business Central on the Advanced plan, at £300 a month. It reads customers, invoices and payments, writes notes, emails, payment dates and contacts back, and uses webhooks to stop chasing when a payment is reconciled.
- Chase the overdue balance. Trove runs the sequence to the customer and keeps every email and reply on the account, so the person deciding on a block can see what’s already been tried.
- Keep the decision with the account. Notes stay on the customer in Trove, so the reason for a stop, who agreed it and the condition for lifting it are there for the next person.
- Approve sensitive chasers. Team approvals hold a chaser until the right person has said yes, and each decision is stored in the customer’s notes. Tom can approve the firmer message to a key account before it goes.
- Keep the account manager informed. Slack and Teams alerts can tell the account manager by direct message when their customer replies or pays, which is often the moment to talk about lifting a stop.
- Check the risk. The credit and risk checks add-on brings Creditsafe or Atradius checks into Trove. Both are add-ons on the Advanced plan.
Trove is listed on Microsoft Marketplace, where every app is reviewed against Microsoft’s marketplace certification policies before it’s published. If you’re comparing options, we’ve reviewed credit control software for Business Central, and our guide to credit control team roles covers who does what beyond the block.
FAQs
Does Business Central block sales orders over the credit limit?
Not by default. Business Central shows a warning and you can still post. To stop the order, set the customer’s Blocked field or use an approval workflow.
How do I block a customer in Business Central?
Search for Customers, select the customer, choose Edit and set the Blocked field to Ship, Invoice or All. Microsoft’s page on blocking customers explains what each value stops.
How do I set a credit limit in Business Central?
Enter the amount in the Credit Limit field on the customer card. Then choose which warnings people see in the Credit Warnings field in Sales & Receivables Setup, as Microsoft’s customer guide describes.
Can a blocked customer still pay?
Microsoft lists payments as stopped only under All, where no transaction is allowed, including payments. If a customer on All pays, change the field before posting the receipt.
How does the account manager find out when a customer on stop pays?
Finance can tell them directly, or a tool can do it. Trove’s Slack and Teams alerts can send the account manager a direct message when their customer pays, with a link to the customer in Trove.
Trove runs a free 30-day trial. You can start a free trial here or book a demo if you’d like to see it working with your Business Central data first.