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 |
- 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.
- 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.
- 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.
- 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. |