> ## 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 Status, Microsoft Dynamics 365 > Ledger Period Close Status: the open/close state of the active ledger period across legal entities, flagging overdue closes. How to read it, why it matters, and how to act. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > The live open/close state of the active ledger period across every legal entity, flagging any entity whose close is running overdue. ## At a glance > A live status board for period close. For each legal entity it shows whether the current ledger period is Open, On Hold, or Closed, and flags any entity whose close has slipped past its deadline. In a multi-entity group, close is only as done as the slowest entity, so this card is the one-glance answer to "are we closed yet, and who is holding us up?" | | | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The close state of the active ledger period per legal entity. In Finance & Operations this reads the period status on the Ledger calendar / Ledger periods (Open, On hold, Permanently closed) and the module access set on the period. In Business Central it reads the Accounting Periods table and the Allow Posting From / Allow Posting To range that controls whether the period is effectively open or closed. | | **States** | Open (posting allowed), On Hold (restricted posting, often closed to operations but open to Finance), Closed (no posting). The card flags any entity whose close is overdue against its deadline. | | **Unit** | A live status per entity, with a count of entities overdue. | | **Currency** | Not applicable; this is a status card, not a value card. | | **Multi-Company** | This card exists for multi-entity groups. It shows every selected legal entity side by side and highlights the laggards. | | **Time window** | `RT` (real-time live status) | | **Alert trigger** | `overdue >5d` (an entity whose close is more than 5 days past its deadline) | | **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-headquartered group on Finance & Operations with four legal entities, snapshot 12 Jun 26 (live). The internal deadline for closing the May period is the 6th working day of June, which fell on 09 Jun 26. | Legal entity | Period (May 26) | State | Days vs deadline | | ------------- | --------------- | ------- | ---------------- | | UK HoldCo | May 26 | Closed | on time | | UK Retail Ltd | May 26 | Closed | on time | | US Retail Inc | May 26 | On Hold | +1d late | | EU DTC BV | May 26 | Open | +3d late | The card flags **2 entities not yet closed**, with EU DTC BV the furthest behind at 3 days past deadline. Four things to notice: 1. **The group is not closed until all four are.** Two entities being done is not "closed". The consolidated view depends on the slowest entity, EU DTC BV, which is still Open. 2. **EU DTC BV at +3d is a watch-item, not yet an alert.** The `overdue >5d` alert has not fired, but the trend is the wrong way. Acting at +3d is how you avoid the +6d alert. 3. **US Retail Inc is On Hold, not Closed.** On Hold usually means operations are locked out but Finance is still posting adjustments. It is one step from done, so a quick check of its [Open (Not Posted) Journal Entries](/nerve-centre/kpi-cards/microsoft-dynamics/open-not-posted-journal-entries) tells you what is left. 4. **The two laggards likely share a root cause.** Smaller overseas entities often slip because of intercompany reconciliations. Cross-check [Intercompany / Operating-Unit Imbalances](/nerve-centre/kpi-cards/microsoft-dynamics/msd-intercompany-balance) before assuming it is just slow data entry. ## Sibling cards merchants should reference together Ledger Period Close Status is the live close scoreboard. Pair it with these to see why an entity is behind and how it trends. | Card | Why pair | | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | [Ledger Period Close Past Deadline](/nerve-centre/kpi-cards/microsoft-dynamics/ledger-period-close-past-deadline) | The focused overdue view. This card shows all states; that one zeroes in on the breaches driving the alert. | | [Period Close On-Time Rate (12mo)](/nerve-centre/kpi-cards/microsoft-dynamics/period-close-on-time-rate-12mo) | The trailing trend. Today's status vs the 12-month track record tells you if this month is a blip or a pattern. | | [Open (Not Posted) Journal Entries](/nerve-centre/kpi-cards/microsoft-dynamics/open-not-posted-journal-entries) | The work blocking close. An entity stuck Open usually has unposted lines for the period. | | [Accrual Reversals (last close)](/nerve-centre/kpi-cards/microsoft-dynamics/accrual-reversals-last-close) | Accrual processing is a common close bottleneck. Noisy reversals point at where time is going. | | [Intercompany / Operating-Unit Imbalances](/nerve-centre/kpi-cards/microsoft-dynamics/msd-intercompany-balance) | Intercompany reconciliation is the classic reason an overseas entity closes late. | ## 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 > Ledger periods** (Open / On hold / Permanently closed, plus module access) > **Finance & Operations: General ledger > Period close > Financial period close workspace** (task progress against the close schedule) > **Business Central: Finance > Accounting Periods** (and the General Ledger Setup Allow Posting From / Allow Posting To range) To reconcile: for each legal entity, the native period status (and in BC the Allow Posting range) is what this card reflects. The card matches the live state subject to the sync window. **Why our number may legitimately differ:** | Reason | Direction | Why | | ------------------------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Open vs effectively-open (BC)** | Either | Business Central has no hard "closed" flag in the same way as F\&O; closure is enforced via the Allow Posting range. The card interprets a period outside that range as Closed, which may differ from how a user reads the Accounting Periods list. | | **Module-level period access (F\&O)** | Either | F\&O can hold a period open for one module (say GL) while closed to others. The card reports the overall state; a native check on a single module may read differently. | | **Deadline definition** | Either | The overdue flag uses your configured internal deadline. If a native report uses the statutory filing date instead, the "late" count will differ. | | **On Hold interpretation** | Either | On Hold is treated as not-yet-closed for the alert. A team that considers On Hold "done for operations" may count it as closed. | | **OData / DMF sync lag** | Card up to 15 min behind | A period just closed in F\&O / BC may still show Open on the card until the next refresh. | This card has no commerce-side counterpart; period close is entirely an ERP concept. The indirect link is that a late close delays trustworthy reconciliation of commerce revenue against the GL, which is why a slipping close here can hold up the [Revenue Gap vs Commerce](/nerve-centre/kpi-cards/microsoft-dynamics/revenue-gap-vs-commerce) analysis. ## Known limitations / merchant FAQs **What is the difference between Open, On Hold, and Closed?** Open means posting is allowed. On Hold (F\&O) means posting is restricted, typically locked to operations but still open to Finance for adjustments. Closed means no posting at all for that period. The card flags anything not yet Closed against its deadline. **How does Business Central represent a "closed" period?** BC does not use a hard closed state the way F\&O does. Closure is enforced through the General Ledger Setup Allow Posting From / Allow Posting To range. The card reads a period outside that range as effectively Closed. **What sets the deadline the overdue flag uses?** Your configured internal close deadline (for example the 6th working day). It is set in card configuration during onboarding. The default is your internal target, not the statutory filing date, because the internal deadline is the one that matters operationally. **Why is "the group isn't closed until the last entity is" so important?** Consolidated reporting depends on every entity being closed. A single laggard entity blocks group close, board reporting, and clean revenue reconciliation. This card surfaces that laggard immediately rather than at the consolidation step. **Can a period be closed for one module but open for another?** In F\&O, yes. A period can be closed to operations while still open to GL for late adjustments. This card reports the overall state; use the native Ledger periods screen to see module-level access. **Does reopening a closed period show here?** Yes. If a closed period is reopened (for an audit adjustment, say), the card reflects it as Open again, which is a useful control signal in itself. **Same behaviour across Business Central and Finance & Operations?** The concept is the same but the mechanics differ: F\&O has explicit period statuses and module access, BC enforces closure via the posting-date range. The card normalises both into Open / On Hold / Closed. *** ### Tracked live in Vortex IQ Nerve Centre *Ledger Period Close Status* 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.