Customers on Credit Hold (IsCreditHold=true), Microsoft Dynamics 365

Customers on Credit Hold: customer records flagged on hold at master level, distinct from order holds. How to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Ecommerce Platform

How many customer accounts carry a master-level credit hold right now, each one silently blocking new orders from invoicing.

At a glance

The count of customer master records currently flagged on credit hold at the account level, the customer-wide hold flag in Dynamics, distinct from a hold placed on an individual order. A customer-level hold is the heavier lever: while it is on, every new and existing order for that customer is blocked from invoicing, not just one document. A rising count is a direct working-capital drag, since revenue that should be booking sits frozen behind the flag.

What it counts	Customer master records where the account-level credit-hold flag is set. In F&O this is the customer hold / IsCreditHold style flag on the customer record (account-wide blocking); in Business Central it is the customer Blocked status set to a value that stops sales or invoicing at the account level.
What it is not	Not order-level holds. An order placed on hold while the customer account is otherwise clear belongs on the order-hold card, not here. This card counts the customer flag, which is broader and more severe.
Currency	Count metric, currency-independent. The frozen exposure value is read from sibling AR and order cards.
Multi-Company	Aggregated across the selected legal entities. The same customer held in two entities counts per entity unless de-duplicated by a shared identifier.
Time window	RT (real-time snapshot of currently held customers)
Alert trigger	>5 customers on account-level credit hold
Roles	owner, finance, operations

Calculation

Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A B2B trade-supplies merchant on F&O, single legal entity, snapshot 14 Apr 26. Finance places account-level holds when a customer breaches its credit limit or runs badly overdue.

Held customer	Reason for hold	Open orders blocked	Frozen order value
Harborview Trade	Over credit limit	3	£84,000
Pennine Supplies	90+ days overdue	2	£41,000
Castle Builders	Disputed invoice	1	£12,500
Oakfield M&E	Over credit limit	4	£103,000
Riverside Plant	Returned payment	1	£7,800
Delta Fit-Out	90+ days overdue	2	£29,000
Customers on Credit Hold (this card)		13 orders	£277,300

Four things to notice:

1. Six customers on hold is above the >5 threshold, so the card alerts. The count, not the value, drives the alert, but the £277,300 of frozen orders is the business consequence.
2. Two customers (Oakfield, Harborview) carry two thirds of the frozen value. As with most credit problems, exposure is concentrated. Resolving the two largest holds clears most of the working-capital drag.
3. Reasons split between credit-limit breaches and overdue balances. That distinction matters: a limit breach may clear with a single payment or a temporary limit increase, while a 90+ overdue hold needs collections to actually land cash.
4. Each held customer blocks all their orders, not one. Oakfield alone has four orders frozen behind a single flag. That is the multiplier effect that makes account-level holds more damaging than order-level ones.

Sibling cards merchants should reference together

Account-level holds sit at the centre of the credit-risk cluster. Pair this card with the order-level, utilisation, and blocked-order views to see cause, value, and consequence together.

Card	Why pair
Orders on Credit Hold	The order-level counterpart. This card is the customer flag; that one is the document flag.
Customer Credit Utilisation	Shows which customers are near their limit and about to trip into a hold.
Credit Hold Spike	The trend alert. A sudden rise in holds is the acute version of this snapshot count.
Sales Orders Blocked on Inventory or Credit	Quantifies the revenue frozen behind these holds.
AR Aging ≥ 60+ Days	The overdue balances that usually trigger the holds in the first place.

Reconciling against Microsoft Dynamics 365

Where to look in Business Central / Finance & Operations:

F&O: Accounts receivable > Customers > All customers (filter on the customer hold / credit-hold flag) F&O: Credit and collections > Customers > Customers on hold (the dedicated hold list) BC: Sales > Customers (filter Blocked status to the value that stops sales or invoicing) BC: Customer Card > Blocked field (per-customer view of the account flag)

To match this card, filter the customer master to records where the account-level hold flag is set, and count distinct customers. The card counts the flag itself, so it lines up with the native customers-on-hold list when scoped to the same legal entities.

Why our number may legitimately differ:

Reason	Direction	Why
Customer hold vs order hold	Card lower	The card counts only account-level holds. Orders held individually while the customer is otherwise clear are excluded and belong on the order-hold card.
Blocked-status granularity	Either	BC’s Blocked field has values (Ship, Invoice, All). The card treats invoicing-blocking values as a hold; a ship-only block may be classed differently in your field map.
Manual vs automatic holds	Either	Holds set automatically by a credit-limit rule and holds set manually by Finance both count, but a workflow-pending hold not yet committed does not.
Multi-company replication	Card higher	The same customer held in several legal entities counts per entity unless de-duplicated.
OData / Dataverse sync lag	Card up to 15 min behind	A hold placed or released in D365 reflects on the card within the cache window.

Cross-connector note: Credit hold is a finance-control concept internal to Microsoft Dynamics 365. The storefront has no equivalent flag, so there is no Shopify, BigCommerce, or Adobe Commerce number to reconcile against directly. The connection to commerce is indirect: a held customer in D365 can still place orders on the storefront, which then stall at invoicing. That blocked-revenue link is surfaced on the sales-orders-blocked sibling card.

Known limitations / merchant FAQs

How is this different from Orders on Credit Hold? This card counts the customer-level flag, which blocks every order for that account. The order card counts individual documents placed on hold while the account itself may be clear. The customer flag is the broader, more damaging lever.

What puts a customer on account-level hold? Typically a credit-limit breach, a badly overdue balance, a returned or failed payment, or a manual hold set by Finance during a dispute. The card counts the flag regardless of why it was set.

Why does one held customer matter so much? Because the hold blocks all of that customer’s orders from invoicing at once. A single flag can freeze several orders and a large slice of bookable revenue, which is why the worked example shows the multiplier effect.

Does a held customer still place storefront orders? Yes. The hold lives in D365, so a customer can keep ordering on Shopify, BigCommerce, or Adobe Commerce. Those orders then stall when they reach invoicing in D365, which is exactly the working-capital trap to watch for.

Can the storefront see the hold? Usually not by default. The hold is an ERP control, so most storefronts will keep accepting orders unless an integration explicitly gates checkout on D365 credit status. This mismatch is why the count matters operationally.

How do I clear a held customer? Resolve the underlying cause (collect the overdue balance, raise or reset the credit limit, or settle the dispute), then release the flag. The frozen orders can then post as invoices and book revenue.

Does multi-company inflate the count? It can. A customer held across several legal entities counts per entity unless your field map de-duplicates on a shared customer identifier.

---

Tracked live in Vortex IQ Nerve Centre

Customers on Credit Hold (IsCreditHold=true) is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Dynamics 365 and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.