Three weeks of "We are urgently working on this" from a pharma customer's accounts payable team ended with a small manufacturer's owner writing back: "There is a shipping freeze on all product until payment is made full stop." An order was due to ship that Monday. The owner posted the exchange on X on 8 November 2026 and added: "Nobody cares about the flow of money / working capital like an owner, especially one that came from finance." Your Business Central credit limit never makes that call.
At a 500-person distributor the owner is not reading accounts payable email, but someone still decides whether Monday's order ships. We follow one such order below, then read what Business Central does at each step.
A Business Central credit limit is the Credit Limit field on a customer card: the balance a customer may reach before Business Central issues warnings on journals, quotes, orders and invoices. Microsoft's documentation says "You can post even if the credit limit exceeds." The control that stops transactions is the separate Blocked field, which a user sets on each customer card.
This is analysis from sources, not a client deployment. We read the Business Central behaviour on Microsoft Learn on November 21, 2026 and did not test it in a live tenant. The credit-management evidence comes from NACM and the Federal Reserve, dated where quoted. The 500-person distributor below is an illustration, and its figures are arithmetic, not data.
Monday's order at a customer that is past terms
Take a 500-person distributor with one customer 38 days past terms on a $180,000 balance. The days and dollars are illustrative arithmetic, not data from any company. We walk the next order forward from Thursday.
Thursday. The customer's buyer sends a $60,000 order for Monday shipment. The order taker keys it in. Business Central checks the Balance Due field on the customer card when a sales order is entered and, if Credit Warnings includes Overdue Balance, shows a warning. The order taker, who does not chase invoices, sees it and keys the order anyway.
Friday. The customer's accounts payable team tells your collector what the pharma customer's team told the owner by email: they are urgently working on it. The rep who owns the account wants the order out, because the customer is one of the rep's biggest. The credit manager wants it held until cash arrives. Each has a reason, and neither can overrule the other, because nobody wrote down who can.
Monday. The ship date arrives with the order still open, the rep expecting it to leave and the collector expecting it held. If the location ships through warehouse shipments, the order cannot ship until someone releases it to the warehouse, so that release is the real decision point. The first mover decides: whoever releases the order, or the credit manager who calls the rep first. Nobody was named to make that call, so the first move stands.
Putting a customer on credit hold once an account runs past terms: credit and sales
From the first day past terms, the Overdue Balance warning shows on new orders for that customer, provided Credit Warnings includes it. Putting a customer on credit hold is a separate step that a person takes, and nothing in Business Central says when. The choice between a reminder and a hold has a ship date on it whenever the customer has an open order.
We read what credit managers report about customers like the one above. NACM's Credit Managers' Index, a monthly poll of US trade credit managers, described "persistent weakness in Accounts Placed for Collection" in its October 2026 write-up (NACM News, 5 November 2026), and one respondent wrote: "Customers are trying to push back on payment terms." Andrew Perry, senior director of credit and collections at Clean Harbors, a large public company, put the drift in a number: "Customers that used to pay us in 30 days start taking 45 days" (NACM News, 24 September 2026). The Federal Reserve's October 2026 Beige Book (14 October 2026), Chicago district, reports small business contacts looking for ways to cover operating expenses as higher costs, "late payments from clients," and lower discretionary spending by customers eroded margins.
The picture is not uniformly worse. The same NACM write-up reports the combined Credit Managers' Index improving 0.5 points to 55.2, and the respondent who wrote about past dues put them down to "a hand full of companies." A hand full of accounts is enough to produce Monday: it takes one customer and one open order.
Monday lands where credit and sales disagree. In an NACM eNews poll, 39% of credit professionals said the handling of past-due accounts causes the most friction between credit and sales, ahead of who receives credit (26%), how much credit to extend (24%) and payment terms (11%). NACM does not publish the poll's sample size, so read the 39% as direction. Nikki Wilkins, credit manager at Lodge Lumber Co. in Houston, said of the two functions' different incentives: "That difference can create tension, especially when placing accounts on hold or limiting credit exposure" (NACM News, 19 November 2026). Perry describes the same pull when terms are granted: "Our sales and operations teams may push to accept the deal but sometimes they don't see the risk."
One credit manager settled that friction up front. In a May 2025 NRLA column on building-materials dealers, Mike McDole of Firing Line LBM Advisors described a credit manager who made it clear that salespeople could "appeal" her decision to the owner, who had the final say on questionable accounts, and asked only for a heads-up first. That is a tie-break someone declared before the argument. Monday's order had none, so whoever moved first settled it.
Back to Monday's $60,000. The customer already owed $180,000, and that money was exposure before anyone keyed the order. If the order ships, the account stands at $240,000, and $60,000 of it is exposure the company added after the warning had already appeared. The two figures answer different questions. The $180,000 is a collections problem. The $60,000 is a decision someone made.
You can measure your own two figures. Ask whoever runs your Business Central reporting for every shipment posted in the last 90 days to a customer with an overdue balance on the ship date. Each one was a decision to ship. Check how many have a name and a reason recorded against them. Then record two figures for each customer on the list: the overdue balance already held on the first ship date in the window, which is exposure you already had, and the total value of the shipments made while that balance was overdue, which is exposure you added. Total each column across customers and keep the two apart. Take both to your bad-debt reserve review.
What a Business Central credit limit warning does, and what it lets through
Business Central did what it is built to do on Thursday. We read the Microsoft pages behind that screen to see what that is. The assumption to drop is that a limit in the ERP is a policy the ERP enforces. Microsoft's customer card page (updated 16 November 2026) says "Credit limits, balance amounts, and payment terms make it possible for Business Central to issue a credit and an overdue balance warning when you enter a sales order." Business Central "tests the header and lines" of journals, quotes, orders and invoices against the limit. Then the page states the consequence: "You can post even if the credit limit exceeds." A blank limit means no limit.
Which warnings appear is one company-wide choice. In Sales & Receivables Setup, the Credit Warnings field takes four values: Both Warnings, Credit Limit, Overdue Balance and No Warning. Overdue Balance checks the Balance Due field on the customer card and shows a warning when the customer has an overdue balance, so it is the value that watches for past-terms money. With No Warning, nobody sees anything.
The warning appears on the screen of whoever is entering the order. That person is not necessarily the one chasing the invoice, and the page describes no step after the warning: no approver, no stop, no notice to credit.
Compare an ERP that does stop. Asha Weekes of Gildan, a large apparel manufacturer, told NACM News in May 2024 that her ERP automatically places orders on hold when a customer exceeds its credit limit, and customer service gets the alert and contacts credit. Business Central's limit warns and lets the order post.
How the customer Blocked field stops new orders and shipments in Business Central
The Blocked field on the customer card is the control that stops transactions. Microsoft's page on blocking sales to customers (updated 16 November 2026) gives four values. The table sets them beside the warnings, with the part each one leaves to a person.
| Control | What Business Central does (Microsoft Learn, 16 Nov 2026) | What still needs a person |
|---|---|---|
| Credit Limit warning | Tests journals, quotes, orders and invoices against the limit and warns. "You can post even if the credit limit exceeds." | Someone sets a limit on each customer, and the person typing the order decides what to do with the warning. |
| Overdue Balance warning | Checks the Balance Due field and shows a warning if the customer has an overdue balance. | Someone decides what an overdue balance means: how late, how much, which customers. |
| Blocked = Ship | "New orders and new shipments can't be created for this customer. Existing shipments not yet invoiced can be invoiced." | A person decides the account is on hold, then sets the field on that customer. |
| Blocked = Invoice | "New orders, new shipments, and new invoices can't be created for this customer. Existing shipments not yet invoiced can't be invoiced." Reminders and finance charge memos can still be sent. | A person decides, and then owns invoicing the shipments that were already out. |
| Blocked = All | "No transaction is allowed for this customer, including payments." | A person decides, and checks that blocking payments is what they meant. |
Two details decide which value fits a past-due account. All blocks payments, so setting it on a customer you are chasing blocks payments against the account you want paid. Invoice leaves shipped goods uninvoiced: anything you shipped before the hold and had not yet invoiced waits until someone releases it. Ship is the gentler value. It stops new orders and shipments, and existing shipments can still be invoiced. Each value moves a different amount of money, and each is set by hand: select a customer, choose Edit, and change Blocked, one customer at a time.
The credit limit informs whoever types the order. The Blocked field waits for someone to set it. The decision between them is a person's, and the two pages that describe them give it no name.
The credit managers who spoke to NACM do not describe an ownerless decision. In May 2024, the practitioners NACM quoted had credit reviewing and releasing holds, and Chelsea Hirn of KGP Companies described where sales fits: "For each of the accounts that go on hold, there is a sales rep to review it." Monday's order had no such owner. So the question for your company is who plays credit's role, what that person can do without sales' agreement, and what happens when neither answers by the ship date. The credit limit and the Blocked field hold none of those answers.
Business Central credit limit workflow approval: write the rule before the flow
Business Central already has an approval engine for sales documents and for changes to customer fields, which is more than the credit limit and Blocked pages suggest. Microsoft's page on approval workflows (October 2025) lists "Sales documents" and changes to fields holding sensitive information, "such as Vendor Bank Account No. or Customer Credit Limit," and says "The new value won't be implemented until the last request is approved." Its page on approving documents (updated March 2026) says core workflows for sales documents and customer cards are "ready to start as guides," and that a record in Pending Approval "remains locked for processing until all approvers approve the record." The page on creating workflows (October 2026) sets a Due Date Formula for the days an approver has, an Approver Limit Type such as Approver Chain, and Delegate After one, two or five days.
What those pages do not describe is a rule that starts an approval from the Credit Limit or Overdue Balance warning. In a February 2024 DynamicsUser.net thread, a Business Central reseller replied that Credit Limit "is not a standard field on the Sales Order" and told the user to reach out to their partner. That is one 2024 forum reply, not a statement of current behaviour. Learn does not list Microsoft's workflow templates either, so the list in your own tenant is the one to trust. Whether the approval is built in Business Central's workflow engine, in Power Automate (see why neither can approve anything alone) or in code, the hold needs a written answer for each of the five stages of decision infrastructure first. Monday's order had an answer for none of them. The workflow engine can hold some of them and not others:
- Signal: the trigger. The Credit Limit warning and the Overdue Balance warning are different triggers. Pick one: a limit crossed, a number of days past terms, or a dollar amount past terms. In Business Central: policy first. Check your tenant's Workflow Templates page (Microsoft's templates start with MS-) for a sales-order credit-limit template before scoping anything. Learn does not list the templates, and a sandbox test confirms whether one covers credit limits.
- Route: the approver, the cover and the tie-break. Name the person who approves a hold or a release and the person who covers when that one is out. Then name who decides when credit says hold and sales says ship, and up to what amount. Write the appeal path down. McDole's credit manager named hers: salespeople could appeal to the owner, and she asked for a heads-up first. In Business Central: the approver chain and the substitute are configurable in an approval workflow. The tie-break is policy.
- Approve: the clock and the default. Set how long the approver has before the order's ship date, and write what happens if nobody answers. In Business Central: the clock is configurable (Due Date Formula, overdue approval notifications). A sales document in Pending Approval stays locked until the approvers approve it or someone cancels the request, so an unanswered request holds the order. Whether a customer three days late with a Monday shipment should wait is the policy call.
- Execute: the action and the customer message. Choose which Blocked value the hold sets (Ship, Invoice or All), and who sets it. Remember that All blocks payments. Name who tells the customer, and who tells the sales rep before the customer calls them. In Business Central: a person sets Blocked on the customer card. Whether a change to the Blocked field can be routed through an approval the way Customer Credit Limit can needs a sandbox test before you rely on it.
- Audit: the record and the release test. Record who held or released the account, when, on what overdue balance and for what reason, and what evidence released it: applied cash, a promise-to-pay date, a partial payment. That record is what turns the 90-day test above from a reconstruction into a report. Andrew Perry of Clean Harbors describes granting terms against conditions such as partial prepayment, cash in advance or a standby letter of credit (NACM News, 24 September 2026), and the same conditions can serve as release tests. In Business Central: policy.
The Decision Latency Diagnostic scores where a decision like this one stalls: who sees the past-due account, who approves the hold, who acts in Business Central and where the record sits.
Releasing a credit hold without losing the order
Release is the mirror decision and gets less attention. Setting Blocked back to Blank restores transactions: Microsoft's description of Blank is "Transactions are allowed for this customer." The leftovers differ by value. Under Invoice, goods that shipped before the hold and had not been invoiced stay uninvoiced until release, so a slow release delays the very invoice the customer owes. Under Ship, existing shipments could be invoiced all along.
A release that waits for sales to ask costs the order. A release that credit makes alone costs the relationship, which is Wilkins' tension again. Write the release test next to the hold trigger: what payment evidence counts, who can release alone, and up to what amount.
What we are taking from this into OpsGrid
The Business Central pieces above need no extra software: a limit, a warning setting, a Blocked value and a written rule. We follow how credit managers, controllers and sales leaders talk about this call in their own forums, trade press and association surveys, the same sources this article cites. Across them, credit and sales clash at the hold, and the warning in Business Central does not settle it. We are using that pattern to shape what OpsGrid, our decision infrastructure for Business Central, does next. What OpsGrid runs today in its beta, and what is on its roadmap, is listed on the OpsGrid page.
Frequently asked questions
How do you block a customer in Business Central?
Open the Customers page, select the customer, choose Edit, and set the Blocked field to Ship, Invoice or All. Ship stops new orders and new shipments but lets existing uninvoiced shipments be invoiced. Invoice also stops new invoices and the invoicing of existing shipments, though reminders and finance charge memos can still go out. All stops every transaction, including payments. Blank allows everything. Microsoft Learn, updated November 16, 2026, describes the field, and a person sets it by hand on each customer card.
Does a Business Central credit limit block a sales order?
Microsoft Learn describes the credit limit as a warning. Business Central tests journals, quotes, orders and invoices against it, issues a warning when a document exceeds it, and says 'You can post even if the credit limit exceeds.' The Credit Warnings setting in Sales & Receivables Setup chooses which warnings appear, and a blank limit means no limit. This article did not test whether an exceeded limit affects releasing a sales order, so it makes no claim there. To stop transactions for a customer, use the Blocked field.
What does it mean when a customer is on credit hold?
In B2B terms, a customer on credit hold owes a past-due balance or has passed its credit limit, and the seller has stopped new shipments, and sometimes new orders, until the balance is paid or a payment plan is agreed. A person makes that decision. In Business Central the control that stops new transactions for a customer is the Blocked field, which a user sets to Ship, Invoice or All. The credit limit only warns. A customer ledger entry also has an On Hold field, but Microsoft Learn describes it in connection with reminders: an entry on hold does not prompt a reminder by itself, so it is not a credit hold.
Who releases a customer credit hold in Business Central?
Whoever your permissions allow to edit the customer card changes the Blocked field back to Blank, which Microsoft describes as 'Transactions are allowed for this customer.' The Learn page names no role for that step, so the company has to name one. Learn does document approval workflows for changes to customer fields, with Customer Credit Limit as its example, so an administrator can set up a workflow that requires approval on some customer field changes. This article has not tested whether the Blocked field can be routed through that approval, so test it in a sandbox before relying on it. Credit managers quoted by NACM News in May 2024 describe credit reviewing and releasing held accounts, with a sales rep reviewing each one.