> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Ledger Period Close Past Deadline, Microsoft Dynamics 365 > Ledger Period Close Past Deadline: legal entities whose ledger close is more than 5 days past the internal deadline. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > 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. | | | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | One row per connected legal entity where the current ledger period is past its configured internal close deadline by more than 5 days and is not yet in a Closed (or On hold) state. Reads the F\&O ledger calendar and period-status tables. An entity that completes its close drops off the list. | | **Currency** | The card is a count of entities, so it is currency-agnostic. Blocking items in the drill-down carry their value in the entity's accounting currency. | | **Multi-Company** | This card is inherently multi-company: it ranks every connected legal entity by how far past deadline it is, so the group controller sees the whole tenant's close progress in one view. | | **Time window** | `RT` (real-time, evaluated continuously against the close calendar) | | **Alert trigger** | `close deadline >5d past` (any legal entity more than 5 days past its internal close deadline fires the alert) | | **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 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. | Legal entity | Period | Days overdue | Blocking items | | ------------- | -------- | --------------- | ------------------------------------------------- | | EU Retail BV | Mar 2026 | 5 days | 3 rejected journals, unposted bank reconciliation | | US Retail Inc | Mar 2026 | 4 days | Intercompany leg unmatched with UK Retail Ltd | | CA Retail ULC | Mar 2026 | 2 days | Accrual reversals not yet posted | | UK Retail Ltd | Mar 2026 | 0 days (closed) | none | Four things to notice: 1. **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. 2. **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](/nerve-centre/kpi-cards/microsoft-dynamics/journals-rejected-at-posting-postingstatusrejected) card; clear those and one of the two blockers is gone. The card does not just say "late", it says why. 3. **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. 4. **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. | Card | Why pair it with Ledger Period Close Past Deadline | | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------- | | [Ledger Period Close Status](/nerve-centre/kpi-cards/microsoft-dynamics/ledger-period-close-status) | The full per-entity close status board. This card is its over-deadline exception subset. | | [Period Close On-Time Rate (12mo)](/nerve-centre/kpi-cards/microsoft-dynamics/period-close-on-time-rate-12mo) | The trailing trend. If this card fires every month for the same entity, the on-time rate tells you it is chronic, not a one-off. | | [Open / Not-Posted Journal Entries](/nerve-centre/kpi-cards/microsoft-dynamics/open-not-posted-journal-entries) | A common blocker: unposted journals hold the period open. | | [Accrual Reversals Last Close](/nerve-centre/kpi-cards/microsoft-dynamics/accrual-reversals-last-close) | Accrual reversals that have not posted are a frequent late-close cause, as on CA Retail ULC above. | | [Journals Rejected at Posting (PostingStatus=Rejected)](/nerve-centre/kpi-cards/microsoft-dynamics/journals-rejected-at-posting-postingstatusrejected) | Rejected journals are unbooked entries that block the close until corrected. | | [Intercompany / Operating-Unit Imbalances](/nerve-centre/kpi-cards/microsoft-dynamics/msd-intercompany-balance) | When one entity cannot close because its intercompany leg is unmatched, as on US Retail Inc above. | ## 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:** | Reason | Direction | Why | | ---------------------------------------- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Deadline source** | Either | The 5-day threshold is measured against the internal close deadline configured in the workspace. If your deadline differs from what F\&O's close calendar implies, the days-overdue figure differs. Confirm the configured deadline. | | **Period state vs task state** | Either | F\&O can show a period as Open while the close-task checklist is substantially complete, or On hold during sub-ledger close. The card treats anything not yet Closed and past deadline as overdue; a task-by-task view may read further along. | | **Working-day vs calendar-day counting** | Small | If your deadline is expressed in working days (WD5) and a manual count uses calendar days, the overdue figure shifts around weekends and holidays. The card uses the configured close calendar. | | **Legal-entity scope** | Card more comprehensive | The native workspace is usually opened one legal entity at a time. This card spans every connected entity, so it can show late entities a single-company user would not be watching. | | **Sync lag** | Card up to a few minutes behind | The card polls the period-status tables on a short interval, so an entity that just closed may show as overdue until the next poll. | **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](/nerve-centre/kpi-cards/shopify/total-revenue), [bigcommerce.total\_revenue](/nerve-centre/kpi-cards/bigcommerce/total-revenue), or [adobe\_commerce.total\_revenue](/nerve-centre/kpi-cards/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. ## Known limitations / merchant FAQs **What does "past deadline" mean here?** It means the ledger period is still open more than 5 days after the internal close deadline configured for that legal entity. It is not measured against period-end; it is measured against your own target close date, which is usually a few working days after month-end. **Why 5 days and not at the deadline itself?** A small slip is normal during any close. The 5-day buffer suppresses the noise of an entity that is a day or two behind and is on track, and reserves the alert for genuinely stalled closes that need escalation. The watchlist still shows entities that are late but under the threshold. **An entity is late but I know the close is nearly done. Why is it here?** Because the period is still Open. F\&O can show a period as Open even when most close tasks are complete and only a final review remains. The card reads period state, not checklist percentage, so it stays on the list until the period is actually Closed. Check the blocking-items column to see what is left. **What blocking items does the card show?** The concrete reasons the period cannot close: rejected journals, unposted journals, an unmatched intercompany leg, an unposted bank reconciliation, or accrual reversals not yet posted. Each links to the sibling card that lets you clear it. **Does this span all legal entities?** Yes, and that is the point. The native close workspace is usually viewed one entity at a time, which hides cross-entity dependencies. This card ranks every connected entity in one queue so the group controller sees the whole tenant's close at once. **Can Vortex IQ close the period for me?** No. Closing a period is a deliberate finance action with audit consequences. Vortex IQ surfaces which entities are late and exactly what is blocking them; a human completes the close. Auto-closing would defeat the control the close exists to provide. **How does this relate to the on-time rate card?** This card is the live exception list for the current close. The [Period Close On-Time Rate (12mo)](/nerve-centre/kpi-cards/microsoft-dynamics/period-close-on-time-rate-12mo) card is the trailing trend. If the same entity appears here month after month, the on-time rate confirms the problem is structural and needs a process fix, not just a chase. *** ### Tracked live in Vortex IQ Nerve Centre *Ledger Period Close Past Deadline* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.