> ## 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. # Period Close On-Time Rate (12mo) > Percentage of the last 12 monthly closes completed by the target close date. A trailing measure of close discipline and finance capacity. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Percentage of the last 12 monthly closes completed by the target close date. A trailing measure of close discipline and finance capacity. ## At a glance > Of the last twelve monthly period closes, the share that finished on or before their target close date. This is the single best trailing indicator of whether your finance function is in control of its calendar or perpetually firefighting. A close that slips is rarely just late; it usually means reconciliations were rushed, accruals were plugged, and the numbers the board saw were less reliable than they looked. Sage Intacct tracks the soft-close and hard-close timestamps per period; the card compares each against the configured target close date and rolls the last twelve into a single rate so the Controller can see the trend, not just this month. | | | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | For each of the trailing 12 periods, whether the hard close (period locked in Intacct) landed on or before the target close date. Sage Intacct's period management records the close action and timestamp per book and per entity; the card reads the close event against the configured target and computes the on-time share. | | **Threshold** | Default alert at `<90%` (more than one slipped close in twelve). Configurable per workspace. High-discipline groups target 100%; fast-growth businesses mid-restructure may temporarily set 75-80%. | | **Target close date** | Configured per workspace, typically expressed as "business day N after period end" (e.g. BD5, BD10). The card uses the workspace target; if none is set it defaults to BD10 for mid-market and flags that the target is unconfigured. | | **Soft vs hard close** | Default measures the hard close (period locked). The field map can switch to soft close (sub-ledgers closed, GL open for adjustments) for businesses that report off the soft close. | | **Currency** | Not applicable. This is a count-based rate, currency-independent. | | **Entity scope** | Card respects the dashboard entity filter. In Multi-Entity Console the consolidated close date is the gating event; per-entity close rates are available as a drill. | | **Dimensional cut** | Drillable by entity and by book (primary book vs reporting books such as tax or budget books that close on their own cadence). | | **Time window** | `12mo` trailing, rolling forward each close. | | **Alert trigger** | `<90%` on the trailing 12, sentiment `close_discipline`. Configurable per workspace. | | **Roles** | owner, finance | ## Calculation Calculated automatically from your Sage data by comparing each of the last twelve close events against its target close date. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A US direct-to-consumer brand on Sage Intacct, single primary entity plus a small UK subsidiary, consolidated monthly. Annual revenue \~\$25M across Shopify and Amazon. Target close is business day 8 (BD8). Snapshot taken 6 Jun 26 covering the trailing twelve closes from Jun 25 to May 26. Default alert threshold of 90%. | Period | Target (BD8) | Actual close | On time? | | ---------------------------- | ------------ | ----------------- | ------------------------ | | Jun 25 - Sep 25 | BD8 | BD7 to BD8 | Yes (4 of 4) | | Oct 25 | BD8 | BD12 | No (Q3 audit prep) | | Nov 25 - Dec 25 | BD8 | BD8 | Yes (2 of 2) | | Jan 26 | BD8 | BD15 | No (year-end) | | Feb 26 - Apr 26 | BD8 | BD8 to BD9 | Yes (3 of 3) | | May 26 | BD8 | BD11 | No (new ERP integration) | | **On-Time Rate (this card)** | | **9 of 12 = 75%** | | Five things to notice: 1. **75% is below the 90% threshold, but two of the three misses are explainable and one is not, and the card's job is to make that distinction visible.** The October miss (Q3 audit prep) and the January miss (year-end close) are predictable, seasonal, and arguably acceptable; a year-end close that runs to BD15 is normal for a business this size. The May miss is the one to chase, because it was caused by a new ERP integration that disrupted the close, and if that disruption is structural rather than one-off, the next close will slip too. A Controller reading only the headline 75% might over-react; a Controller reading the breakdown knows that the underlying monthly discipline is actually strong and only one miss is a live risk. 2. **A slipped close is a leading indicator of unreliable numbers, not just a late number.** When the close runs long, the usual cause is that reconciliations (bank, AR, AP, inventory) were not done in time, so the period was either held open while they caught up or closed on estimates that later needed correction. That is why this card pairs so tightly with [Accrual Reversals (last close)](/nerve-centre/kpi-cards/sage/accrual-reversals-last-close): a late close and a spike in reversals in the same period usually means the books were closed on plugs. On this account the May close that ran to BD11 also showed elevated reversals, confirming the close was rushed rather than clean. 3. **The trailing-12 framing smooths out single-month noise and reveals the real trajectory.** Any one close can slip for a one-off reason. The value of the 12-month rolling rate is that it answers the question a board actually cares about: is finance reliably in control of its calendar over a year, or is it slipping more often than it used to? A rate trending from 92% to 75% over a few quarters is a capacity or process warning even if no single month looks alarming. The fix is usually one of three things: more finance headcount, more automation of the reconciliations that gate the close, or a more realistic target date. 4. **The target date itself is a policy choice and the card flags when it is unset or unrealistic.** A business that sets BD5 but consistently closes at BD9 does not have a close problem; it has a target problem. The honest move is either to invest in the automation that makes BD5 achievable or to move the target to BD9 and hit it reliably. A target nobody ever meets erodes the credibility of the whole close calendar. The card surfaces the gap between target and actual so the conversation about which lever to pull is grounded in twelve months of evidence, not one bad month. 5. **Pair with [Period Close Status](/nerve-centre/kpi-cards/sage/period-close-status) for the live view alongside the trailing trend.** This card is the rear-view mirror (how reliably have we closed on time over a year); Period Close Status is the windscreen (is the current period on track right now). Read together they tell the full story: a strong trailing rate with the current period drifting overdue is an early warning that this month is about to break the streak, while a weak trailing rate with the current period on track suggests a fix is taking hold. On this account the two cards together showed the May disruption had not recurred in June, which was the reassurance the CFO needed before the board meeting. ## Sibling cards merchants should reference together | Card | Why pair it with Period Close On-Time Rate | | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | | [Period Close Status](/nerve-centre/kpi-cards/sage/period-close-status) | The live current-period view alongside this trailing trend. | | [Accrual Reversals (last close)](/nerve-centre/kpi-cards/sage/accrual-reversals-last-close) | A late close plus a reversal spike means the books were closed on plugs. | | [Transaction Imbalances](/nerve-centre/kpi-cards/sage/transaction-imbalances) | Imbalances must clear before a clean close; they gate the date. | | [Days Since Last Bank Reconciliation](/nerve-centre/kpi-cards/sage/days-since-last-bank-reconciliation) | Unreconciled cash is the most common cause of a late close. | | [Manual JEs as % of Total](/nerve-centre/kpi-cards/sage/manual-jes-as-of-total) | High manual-JE load slows the close and stretches the calendar. | | [Smart Coding Queue Depth (24h)](/nerve-centre/kpi-cards/sage/smart-coding-queue-depth-24h) | An uncoded transaction backlog delays the close. | | [Current VAT Return Status (MTD)](/nerve-centre/kpi-cards/sage/current-vat-return-status-mtd) | VAT filing deadlines interact with the close calendar in the UK. | | [Sage Health Score](/nerve-centre/kpi-cards/sage/sage-health-score) | Close discipline is a major input into the overall GL health composite. | ## 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** to see each period's open/closed state and the close timestamp per book > **Company → Setup → Books** to confirm which books (primary, tax, budget) are in scope and their close cadence > **Audit Trail** on the period-close action to see who closed each period and exactly when, which is the source of truth for the actual close date > **Reports → General Ledger → Trial Balance** run as-of each close date to confirm the period was balanced when locked > **Interactive Custom Report (ICR)** on period state changes, comparing the close timestamp to the configured target close date across the last twelve periods In Intacct the close event is a discrete, timestamped action recorded against each reporting period, which is what makes this card precise: there is no ambiguity about when a period was hard-closed. For Multi-Entity Console accounts the consolidated close is the gating event; run Manage Reporting Periods at the consolidation level as well as per entity, because a subsidiary can close on time while the consolidation slips on inter-entity eliminations. Common reconciliation pitfalls: * **Soft close vs hard close**: Intacct supports closing sub-ledgers while leaving the GL open for adjustments. The card measures the hard close by default; if your team reports off the soft close, switch the field map, otherwise the card will read later than your internal "we closed" date. * **Reopened periods**: a period closed on time, then reopened to post a correction, then re-closed. The card uses the first hard-close date for on-time purposes by default (you did close on time; the reopen is a separate event). Some teams prefer the final close date; the field map can switch. * **Multiple books**: tax and budget books close on different cadences. The card measures the primary book by default; a tax book that closes weeks later is not a primary-close miss. **Why our number may legitimately differ from a Sage Intacct period listing:** | Reason | Direction | Why | | ------------------------------ | ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | **Soft vs hard close** | Either | Card measures hard close by default; teams reporting off soft close will see an earlier internal date. | | **Reopened periods** | Either | Card uses first close date by default; final-close date is a field-map option. | | **Target date definition** | Either | "BD8" can mean business day 8 excluding or including weekends and holidays; the card uses the workspace calendar. | | **Book in scope** | Either | Tax and budget books close on their own cadence; card measures the primary book unless configured otherwise. | | **Entity scope** | Either | Card respects the dashboard entity filter; consolidated close can differ from any single entity's close. | | **Holiday calendar** | Small | Business-day counting depends on the configured holiday calendar; a mismatch shifts the target by a day or two. | | **Mid-period workspace setup** | Card may understate | Periods that closed before Vortex IQ was connected may lack a recorded target, reducing the denominator until twelve full periods accrue. | **Cross-connector reconciliation:** | Card | Expected relationship | What the comparison reveals | | ------------------------------------------------------------------------------------------------------- | --------------------- | --------------------------------------------------------------------------------------------------------- | | [Days Since Last Bank Reconciliation](/nerve-centre/kpi-cards/sage/days-since-last-bank-reconciliation) | Causal | Unreconciled cash is the single most common reason a close slips; a high day count predicts a late close. | | [Accrual Reversals (last close)](/nerve-centre/kpi-cards/sage/accrual-reversals-last-close) | Correlated | A late close paired with a reversal spike means the period was closed on estimates that later unwound. | | [Transaction Imbalances](/nerve-centre/kpi-cards/sage/transaction-imbalances) | Gating | Imbalances must clear before a clean close, so they directly affect the close date. | | [Smart Coding Queue Depth (24h)](/nerve-centre/kpi-cards/sage/smart-coding-queue-depth-24h) | Diagnostic | A backlog of uncoded transactions stalls the close because nothing can be reconciled until it clears. | | [Sage Health Score](/nerve-centre/kpi-cards/sage/sage-health-score) | Input | On-time close rate is a heavily weighted input into the composite GL health score. | The cross-connector value is that a late close almost never has a single cause inside the GL alone. It is the downstream symptom of upstream friction: unreconciled bank lines, an uncoded transaction backlog, a flood of manual journals, or a revenue gap between commerce and the GL that nobody could explain in time. Reading this card next to its causal siblings turns "the close was late again" into "the close was late because the Shopify payout reconciliation took six days," which is a fixable problem with an owner, not a vague capacity complaint. ## Known limitations / merchant FAQs **What is a good on-time rate?** For a stable, well-resourced finance function, 100% is achievable and worth targeting. Below 90% (more than one miss a year) is the default alert. But context matters: a business mid-ERP-migration or mid-acquisition will legitimately slip more often, and the right response is a temporary target adjustment, not a panic. The trend matters more than the absolute level. **Should I count the year-end close the same as a monthly close?** Most teams give year-end a longer target because it carries audit prep, statutory adjustments, and tax provisioning. The card uses your configured target per period, so you can set a longer year-end target. If you use a single target for all periods, expect year-end to be your most common miss, which is normal. **Soft close or hard close, which does the card measure?** Hard close (period locked in Intacct) by default, because that is the unambiguous, timestamped event. If your team reports off the soft close (sub-ledgers done, GL still open for tweaks), switch the field map so the card matches your internal definition of "closed." **What if we reopen a period after closing?** By default the card credits the first on-time close and treats the reopen as a separate event, because you did close on time. If your governance requires the final close date to count, the field map supports that. Either way, a high reopen rate is itself a signal worth watching. **How does the business-day target work across weekends and holidays?** "BD8" is computed against the configured workspace calendar, so it skips weekends and the holidays you define. A mismatch between the card's calendar and your internal one can shift the target by a day or two, which is the most common source of a small disagreement. Align the holiday calendar in the field map. **Why does my trailing rate look low when we only just connected?** The card needs twelve closed periods to fill the trailing window. Periods that closed before Vortex IQ was connected may not have a recorded target, so the denominator builds up over the first year. Once twelve full periods have accrued under the connector, the rate stabilises. **Sage Intacct vs Sage 50 / 200 on close tracking?** Intacct records a discrete, timestamped period-close action per book and entity, which makes this card precise. Sage 50 and Sage 200 handle period close differently and expose the close event less cleanly, so the equivalent metric on those products relies on different signals. This connector targets Intacct; reach out about availability on other Sage products. **Does multi-entity change the close date that counts?** Yes. In Multi-Entity Console the consolidated close is the gating event for group reporting, and it can slip even when every subsidiary closed on time, usually on inter-entity eliminations or intercompany balancing. The card measures the consolidated close at group scope and offers per-entity close rates as a drill. **Is a fast close always better?** Not unconditionally. A close that is fast because it is automated and reconciled is excellent. A close that is fast because reconciliations were skipped and accruals were plugged is worse than a slightly slower clean close. That is why this card should always be read with [Accrual Reversals (last close)](/nerve-centre/kpi-cards/sage/accrual-reversals-last-close) and [Transaction Imbalances](/nerve-centre/kpi-cards/sage/transaction-imbalances): on-time and clean is the goal, not on-time alone. **What action should I take when the rate drops below threshold?** Look at which closes slipped and why. If the misses cluster around audit and year-end, the target may just need a seasonal adjustment. If they are spread across ordinary months, the cause is usually capacity or an upstream bottleneck (bank rec, coding backlog), and the fix is automation or headcount. The card points you at the pattern; the causal siblings tell you the lever. **Implementation Partner role on this metric?** The Partner typically owns the close calendar, the target close-date policy, and the reconciliation checklist that gates the close. If this card disagrees with the Partner's close pack, the cause is almost always a soft-vs-hard-close definition or a business-day calendar mismatch. Align both in the Vortex IQ field map and bring the Partner into the conversation early. *** ### Tracked live in Vortex IQ Nerve Centre *Period Close On-Time Rate (12mo)* is one of hundreds of KPI pulses Vortex IQ tracks across Sage 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.