A real-time alert list of legal entities whose ledger period close is more than 5 days past the internal close deadline. Each row is a company that is late closing its books.
At a glance
A live alert list of every connected legal entity whose ledger period close is still open more than 5 days after the internal close deadline. A late close means the period’s numbers are not yet final: revenue, AR, and the trial balance can still move, so any report run against that entity is provisional. Each row shows the entity, the period in question, how many days overdue it is, and the items blocking the close. This is the controller’s escalation queue during the month-end close, surfaced in real time rather than discovered after the fact.
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 group retailer on Finance & Operations with four legal entities and an internal close deadline of working day 5 (WD5) after month-end. The snapshot is taken on 12 Apr 26, with the March 2026 period due closed by 07 Apr 26.
Four things to notice:
- Only EU Retail BV crosses the 5-day threshold. The deadline was 07 Apr 26; it is now 12 Apr 26 and the period is still open, so it is 5 days overdue and the alert fired. US Retail Inc at 4 days and CA Retail ULC at 2 days are late against the internal target but below the alert line, so they appear on the watchlist without triggering an escalation.
- EU Retail BV’s blocking items are concrete and actionable. Three rejected journals and an unposted bank reconciliation. The rejected journals tie straight back to the Journals Rejected at Posting card; clear those and one of the two blockers is gone. The card does not just say “late”, it says why.
- US Retail Inc is blocked by an intercompany leg, not its own books. Its close cannot complete until the matching entry in UK Retail Ltd is reconciled. This is the dependency that month-end checklists routinely miss, because each controller looks only at their own entity. The cross-entity view is what makes the dependency visible.
- UK Retail Ltd closed on time and is off the list. The card shows it at 0 days as context in this example, but in the live view it simply does not appear once Closed. The list is an exception queue: the shorter it is, the cleaner the close.
Sibling cards merchants should reference together
This alert list is the escalation layer of the period-close cluster. Pair it with these to clear each blocker and track the trend.Reconciling against Microsoft Dynamics 365
Where to look in Business Central / Finance & Operations:Finance & Operations: General ledger > Ledger setup > Ledger calendars (period status per legal entity) Finance & Operations: General ledger > Period close > Financial period close workspace (close task progress and assignees) Finance & Operations: General ledger > Period close > Ledger calendar (Open vs On hold vs Closed per period) Business Central: Finance > Accounting Periods and the Close Income Statement batch (the closest BC equivalent)F&O exposes period status through the ledger calendar and the financial period close workspace. The native screens tell you whether a period is Open or Closed; what they do not do natively is compare the open period against your internal close deadline and rank entities by how far past it they are. This card adds the deadline and the days-overdue calculation, and it presents every entity in one ranked queue. Why our number may legitimately differ:
Cross-connector reconciliation:
A late close has no commerce-platform equivalent, but it has a direct commerce consequence: any revenue figure for an entity whose period is still open is provisional. If you are reconciling D365 GL revenue against shopify.total_revenue, bigcommerce.total_revenue, or adobe_commerce.total_revenue, an entity on this list will keep moving as late journals post, so treat its gap as unsettled until the close completes.