Current open accounting period and whether the close is on track, in progress, or overdue against the close calendar.
At a glance
The live status of the current accounting close: which period is open, how far through the close checklist it is, and whether it is on track, in progress, or overdue against the target close date. This is the executive at-a-glance answer to “are we closed yet, and if not, are we on schedule.” Sage Intacct tracks each reporting period’s open/closed state and the close action timestamp; the card reads the open period against the workspace close calendar and the gating tasks (reconciliations, sub-ledger close, eliminations) to render a single status the owner and CFO can read in two seconds.
Calculation
Calculated automatically from your Sage data by reading the current open period against the close calendar and the live state of the gating close tasks. 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 omnichannel retailer on Sage Intacct, two entities (UK Retail Ltd in GBP, IE Retail Ltd in EUR), consolidated monthly. Annual revenue ~£18M across Shopify, a BigCommerce B2B portal, and physical stores. Target close is business day 6 (BD6). Snapshot taken 9 Jun 26, which is BD7 of the May 26 close. Default overdue alert at 5 days past target.
Five things to notice:
- The status is Overdue and the card immediately tells you why, which is the whole point of a hero close card. The May 26 close is at BD7 against a BD6 target, so it has slipped by one business day. A plain “overdue” flag would prompt a round of “what’s holding it up” emails. This card already shows the two blocking gates: the EUR bank reconciliation and the intercompany eliminations. The CFO does not need to chase; the card has named the bottleneck and the owner. The fix is to get Treasury onto the EUR bank rec and group finance onto the eliminations, in that order, because VAT provisioning is itself waiting on the eliminations.
- The blocking chain matters more than the count of open tasks. Three tasks are outstanding, but only two are actually blocking, and one of those (eliminations) is blocking a third (VAT provisioning). So the critical path is eliminations, not the longer list. Reading the dependency is what turns a status card from a scoreboard into an action tool. On this account the Controller reordered the day’s work around clearing eliminations first, which unblocked VAT and let the close finish at BD8 rather than drifting to BD10.
- A one-day slip is not yet an alarm, and the card’s threshold reflects that. The default overdue alert fires at 5 days past target, not at the first day. This is deliberate: a close that runs a day or two long for an explainable reason (a late carrier invoice, a bank feed delay) is normal operational variance, not a crisis. The card shows the status honestly (Overdue at BD7) but does not escalate to an alert until the slip is material. A business that wants a tighter signal can lower the threshold; a business with a lumpy close can raise it.
- This card is the live companion to the trailing close-rate metric. Where Period Close On-Time Rate (12mo) tells you how reliably you have closed on time over a year, this card tells you whether this close is about to add another miss to that record. Read together they let the CFO answer the board’s two questions at once: “are we usually on time” and “are we on time right now.” On this account the trailing rate was strong, so the one-day slip read as ordinary variance rather than a deteriorating trend, which is the reassuring interpretation and the correct one.
- The gating-task view connects the close to its upstream causes across other cards. The outstanding EUR bank reconciliation links straight to Days Since Last Bank Reconciliation; the outstanding eliminations link to Sage Intercompany Balance; the pending VAT provisioning links to Current VAT Return Status (MTD). The status card is the hub; the gating cards are the spokes. A finance team that wires these together can move from “the close is late” to “the close is late because the EUR bank feed lagged two days and eliminations are queued behind it” without a single status meeting.
Sibling cards merchants should reference together
Reconciling against Sage
Where to look in Sage Intacct: The native Sage Intacct views to run side by side with this card:General Ledger → Setup → Manage Reporting Periods for the open/closed state of the current period per book and entity General Ledger → All → Close Checklist (where configured) for the gating tasks and their completion state Cash Management → Reconciliation for the live bank reconciliation status that gates the close Consolidation → Eliminations for the intercompany elimination state that gates the consolidated close Reports → General Ledger → Trial Balance as-of the open period to confirm it balances before the close action Interactive Custom Report (ICR) on period state and elapsed-days-since-period-end against the configured target close dateIn Intacct the period’s open/closed state is authoritative and timestamped, and the close checklist (where the team uses it) records each gating task. The card overlays the close calendar to derive on-track / overdue. For Multi-Entity Console accounts the consolidated close is the headline event; check Manage Reporting Periods at the consolidation level as well as per entity, because a subsidiary can be fully closed while the group close waits on eliminations. Common reconciliation pitfalls:
- Soft close shows “closed” internally but the GL is open: a team that has soft-closed the sub-ledgers may consider the period done while Intacct still shows the GL open for adjustments. The card distinguishes the two; align the field map to whichever your team treats as “closed.”
- Reopened periods read as open again: a period reopened to post a late correction flips back to open and the card reflects that. If your governance treats the original close as final, expect a brief disagreement until the reopen is re-closed.
- Per-book divergence: the tax book may still be open while the primary book is closed. The card reports the primary book by default; a tax-book reader sees a different status.
Cross-connector reconciliation:
The cross-connector value is that a close is gated by signals living all over the stack: cash that has not been reconciled to the bank feed, an intercompany position that does not net to zero, a revenue gap between what Shopify and Amazon reported and what posted to the GL. This card is the single place a CFO can see the close status and click straight to the gate that is holding it up, which is the difference between a status meeting and a status card.