Customers carrying aged AR (over 60 days) in D365 who are still placing new ecom orders. Each row is more exposure to a customer who is already late.
At a glance
The killer cross-channel table. It joins the D365 customer ledger against live commerce order feeds and lists every customer who has an open AR balance more than 60 days old AND has placed new ecom orders in the trailing 30 days. Each row is a customer who is extending your working-capital exposure while already failing to pay for what they bought last quarter. When a row crosses the alert threshold, Vortex IQ can fire a Power Automate flow that sets the D365 customer credit-hold flag (IsCreditHold = true) so the next ecom order routes to manual review instead of straight to fulfilment.
| What it counts | One row per customer where SUM(Customer Ledger Entry.Remaining Amount) in the over-60-day aging bucket is greater than zero AND that customer placed at least one new ecom order (Shopify, BigCommerce, Adobe Commerce) in the last 30 days. Rows are joined on the field-mapped link between the commerce customer and the D365 Customer No. Cancelled commerce orders and fully-settled invoices are excluded. |
| Currency | Each row shows aged AR and new ecom order value in the customer’s transaction currency plus the Reporting Currency equivalent (parent legal entity Local Currency, typically GBP, USD, or EUR). FX uses the D365 Currency Exchange Rate table at transaction date. |
| Multi-Company | A customer may carry AR in more than one legal entity. The card rolls aged AR across every connected legal entity the customer appears in and notes the entity holding the largest overdue balance. New ecom orders map to the expected legal entity via the field map. |
| Time window | 30D vsP (new ecom order value measured over the last 30 days vs the prior 30 days; AR aging is a live snapshot) |
| Alert trigger | any customer >60d AR with new ecom orders (any customer with an over-60-day AR balance who places a new ecom order fires the alert, and can auto-set the credit-hold flag via Power Automate) |
| Roles | owner, finance |
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 UK building-supplies merchant on Business Central plus a BigCommerce B2B storefront and a Shopify Plus DTC site, two legal entities (UK Trade Ltd, GBP, and IE Trade Ltd, EUR). The aging snapshot is taken on 12 Apr 26; the new-ecom-order column covers 14 Mar 26 to 12 Apr 26.| Customer | Aged AR (over 60d) | Oldest bucket | New ecom order value (30d) | Suggested action |
|---|---|---|---|---|
| Riverside Contractors | £41,800 | 91 to 120 days | £18,400 | Auto-set credit hold, call before next dispatch |
| Newcorp Trading | £22,600 | 61 to 90 days | £9,200 | Credit hold, request payment plan |
| Distrib-Z (IE) | €14,900 | 61 to 90 days | €6,400 | Credit hold, FX-aware AR review |
| Acme Tech | £8,400 | 91 to 120 days | £3,100 | Watchlist, manual release per order |
| Harbour & Sons | £6,200 | 61 to 90 days | £1,950 | Manual review, soft-hold |
| Top 5 total | £93,900 (GBP equiv) | £39,050 (GBP equiv) |
- Riverside Contractors is the textbook case. They owe £41,800 that is now 91 to 120 days old, and in the last 30 days they placed £18,400 of fresh orders that were heading straight to fulfilment. Without this card, the warehouse ships the new pallets while the old invoices quietly age into the doubtful-debt provision. The alert fired and the Power Automate flow set
IsCreditHold = trueon the D365 customer, so the next BigCommerce order routed to manual review instead of dispatch. - The over-60-day total is £93,900 but the new exposure is £39,050. The card is not just an aging report. It is a forward-looking exposure tracker: it tells Finance exactly how much extra credit is about to be extended to customers who are already late, before the goods leave the building.
- Distrib-Z carries its AR in the IE legal entity in EUR. The card rolls the EUR balance into the GBP Reporting Currency for the total but keeps the native EUR figure on the row so the AR clerk reconciling IE Trade Ltd sees the number they expect. A single-entity aging report would have missed this customer entirely if the clerk was only looking at UK Trade Ltd.
- Acme Tech and Harbour & Sons are watchlist, not hold. Their new-order values are small relative to the aged balance, so the suggested action is manual review rather than an automatic credit hold. The card does not force a binary; it ranks by combined risk so Finance triages from the top.
Sibling cards merchants should reference together
This card is the cross-channel apex of the credit-and-collections cluster. Pair it with these to act on each row.| Card | Why pair it with AR Aging on Customers with Active Ecom Orders |
|---|---|
| Customers on Credit Hold (IsCreditHold=true) | The downstream list once this card’s Power Automate flow has set the flag. Confirms the hold actually applied. |
| Customer Credit Utilisation | Shows how close each customer is to their D365 credit limit, so you can tell a slow-payer from one who is also over-limit. |
| AR Aging 60+ Days | The pure aging view without the ecom-order join. This card adds the forward exposure dimension on top. |
| Orders on Credit Hold | The order-level result once the hold is set: which new ecom orders are now blocked from dispatch. |
| High-Value Overdue Invoices | The invoice-level detail behind the aged AR balances on each row here. |
| Sales Orders Blocked on Inventory or Credit | The operational backlog this card creates: held SOs that need a Finance release decision. |
Reconciling against Microsoft Dynamics 365
Where to look in Business Central / Finance & Operations:Business Central: Customer > Aged Accounts Receivable report (the over-60-day columns) Business Central: Customer Ledger Entries filtered to Open = Yes, Remaining Amount > 0 Finance & Operations: Accounts receivable > Inquiries and reports > Customer aging report Finance & Operations: Credit and collections > Customers on credit hold (the result after the flow runs)No native D365 report joins the AR aging table to the live commerce order feed. The Aged Accounts Receivable report tells you who is late; it cannot tell you who is late AND still buying, because the new orders may not yet be D365 Sales Orders. This card performs that join across the connector boundary. Why our number may legitimately differ:
| Reason | Direction | Why |
|---|---|---|
| Aging snapshot timing | Either | The D365 Aged AR report is run as-of a chosen date. This card snapshots aging live, so a payment that posted an hour ago lowers our number before the next scheduled D365 report run. |
| New orders not yet a D365 Sales Order | Card more inclusive | The new-ecom-order column reads the commerce platform directly. Those orders may still be in Awaiting Sync and have no D365 Sales Header yet, so a D365-only query would not see them. |
| Multi-entity AR roll-up | Card higher per customer | The Aged AR report is usually run one legal entity at a time. This card sums a customer’s overdue balance across every connected entity. |
| Currency translation | Small | The card rolls non-Reporting-Currency balances into the Reporting Currency at the D365 exchange-rate table; a manual aging export left in transaction currency will not match the consolidated total. |
| Credit-memo and unapplied-payment timing | Either | An unapplied payment or an open credit memo changes Remaining Amount. The card and the D365 report apply the same convention, but a manual filter on one document type can miss the offsetting entry. |
Known limitations / merchant FAQs
Does this card automatically put customers on credit hold? Only if you enable the Power Automate flow. When a row crosses the alert threshold, the flow can setIsCreditHold = true on the D365 customer so the next ecom order routes to manual review. Vortex IQ flags and triggers the flow; the flow is what writes back to D365, and you control whether it runs automatically or proposes the action for human approval.
What counts as “active ecom orders”?
Any non-cancelled commerce order placed in the trailing 30 days on a connected platform (Shopify, BigCommerce, Adobe Commerce) that maps to the customer’s D365 Customer No. via the field map. An abandoned cart or a quote does not count.
Why does a customer appear here who I know paid last week?
The aged balance is the over-60-day bucket only. A recent payment may have cleared a newer invoice while the genuinely old invoices remain open. Check the oldest-bucket column: if it still shows a balance, the old debt is unpaid regardless of recent activity.
A customer carries AR in two legal entities. How is that shown?
The row rolls the overdue balance across every connected legal entity and notes which entity holds the largest share. The new-ecom-order value maps to the expected entity via the field map. This is why a multi-entity customer can show a higher total here than in any single-entity aging report.
Can the credit-hold flow be reversed automatically when the customer pays?
A second Power Automate flow can clear IsCreditHold once the over-60-day balance drops to zero, but most Finance teams prefer a manual release so a human confirms the payment cleared and the credit terms still apply. Vortex IQ supports either pattern.
Why is the over-60-day threshold fixed at 60 days?
60 days is the default because most B2B terms are Net-30 and a balance past 60 days is two cycles late, which is the point most credit policies treat as a genuine risk. The aging buckets (61 to 90, 91 to 120, 120+) are shown per row so you can apply a stricter internal policy when triaging.
Does this work for DTC customers or only B2B?
Both, but it is most actionable for B2B where customers buy on terms and carry an AR balance. DTC customers usually pay at checkout, so they rarely carry over-60-day AR; when they do (a chargeback reversal, a manual invoice), they appear here too.
Can I export this list?
Yes, sorted by combined risk descending. The export is the credit controller’s call list: aged balance, oldest bucket, new exposure, and suggested action per customer.