Share of period closes completed on or before the deadline over the trailing 12 months. The one number that tells the CFO whether the finance function actually closes on time, or just says it does.
At a glance
The percentage of period closes that finished on or before their target deadline across the selected Company Codes over the trailing 12 months. Each accounting period (month, typically) has a close calendar with a hard deadline. This card measures, across all the closes in the year and across all Company Codes, how many landed on time. It is the single best proxy for finance-function maturity and the metric a CFO or auditor reaches for first, because a slipping close rate predicts late statutory filings, late group consolidation, and stale management reporting.
| What it measures | On-time closes divided by total closes over the trailing 12 months, expressed as a percentage. A close is “on time” if the period was set to closed (posting period locked) on or before the deadline defined in the financial close calendar for that Company Code and period. |
| What “close” means here | In S/4HANA Cloud, closing a period means locking the posting period in the Manage Posting Periods configuration so no further normal postings land, and completing the close checklist (accruals, FX valuation, reconciliations, GR/IR clearing, intercompany matching). The card keys on the period-lock event timestamp versus the calendar deadline. |
| Hard close vs soft close | A soft close locks the period for most users but leaves it open for finance to make adjustments; a hard close locks it fully. The card measures against the configured deadline regardless of close type, but a tenant that relies on long soft-close windows will see a different shape than one that hard-closes fast. |
| Per-Company-Code resolution | Each Company Code has its own close calendar and deadline. The rate is computed across every close event for every in-scope Company Code in the window, so a 12-Company-Code group has roughly 144 close events in a year feeding the rate. |
| Why a gauge | This is a bounded 0 to 100% health metric, so it renders as a gauge. The further below 100% the rate sits, the more close slippage is happening somewhere in the group. |
| Company Code scope | Respects the selected Company Code filter. By default rolls up every Company Code visible to the connected SAP API role. Drilling into a single Company Code shows that entity’s own on-time history. |
| Time window | 12mo (the trailing 12 months of close events) |
| Alert trigger | <90% on-time rate flags for review |
| Roles | owner, finance |
Calculation
Calculated automatically from your SAP 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 retail group running SAP S/4HANA Cloud Public Edition with three Company Codes: 1000 UK Retail Ltd (GBP), 2000 US Retail Inc (USD), and 3000 EU Retail BV (EUR). Each closes monthly, so across 12 months there are 36 close events. The window ends 22 Jun 26 and looks back to Jul 25.| Company Code | Closes in window | On time | Late |
|---|---|---|---|
| 1000 UK Retail Ltd | 12 | 12 | 0 |
| 2000 US Retail Inc | 12 | 11 | 1 |
| 3000 EU Retail BV | 12 | 9 | 3 |
| Totals | 36 | 32 | 4 |
| Period Close On-Time Rate (this card) | 88.9% |
- The blended rate is 88.9%, just under the
<90%alert threshold. The Nerve Centre flags it. Looking at the group total alone, you might shrug. The value is in the breakdown. - CC 3000 EU Retail BV is the problem. It closed late 3 times out of 12, a 75% on-time rate on its own, while the UK entity was perfect. The blended number hides a single struggling entity. Always drill into the per-Company-Code view when the gauge dips.
- One late close drags the whole group. Because group consolidation in SAP Group Reporting cannot complete until every contributing Company Code has closed, the EU entity’s three late closes delayed group reporting three times that year, even though two of three entities were flawless.
- The trend matters more than the snapshot. A flat 89% is a stable-but-stretched finance team. A rate falling month on month is a team losing the close, often because of a new ERP go-live, a staffing gap, or a data-quality problem upstream (failed IDocs, unposted journals) that has to be cleared before the period can lock.
- On time is measured against the configured deadline, not against “the end of the month”. If the close calendar gives EU Retail BV until working day 6 and it locked on working day 5, that is on time even though it is later in the calendar than the UK entity’s working-day-3 close. The card respects each Company Code’s own deadline.
Sibling cards merchants should reference together
The on-time rate is the lagging summary of close performance. Pair it with the real-time and detail cards to see why it moves.| Card | Why pair it with Period Close On-Time Rate (12mo) |
|---|---|
| Period Close Status by CompanyCode | The live snapshot of which Company Codes are open vs closed right now. The on-time rate is the history; this is the present state. |
| Period Close Past Deadline (any CompanyCode) | The real-time alarm. When a Company Code blows its deadline today, that is the event that will pull this 12-month rate down. |
| Accrual Reversals (last close) | Close hygiene. A close that skipped its accrual reversals may have closed on time but closed badly. |
| Open / Unposted Journal Entries | A backlog of unposted journals is one of the most common reasons a close slips. Clear these and the close speeds up. |
| Journal Entries Failing to Post (IDoc Error Queue) | Inbound integration errors block the data a close depends on. A full error queue is a leading indicator of a late close. |
| Intercompany Imbalances (consolidation blocker) | Even when every Company Code closes on time, an intercompany imbalance can block group consolidation. Pair to see the full close-to-consolidate picture. |
Reconciling against SAP
Where to look in S/4HANA Cloud: The closest native equivalents inside the SAP Fiori launchpad are:Manage Posting Periods Fiori app to see which periods are open vs closed per Company Code Financial Closing Cockpit (or the Advanced Financial Closing / SAP Financial Closing cockpit, where licensed) for the close calendar, task list, and completion timestamps Display Posting Period Variant configuration for the deadlines that define “on time” Embedded Analytics: close-task completion CDS views where the Financial Closing cockpit is in useTo match this card, take the close-task or period-lock completion timestamps from the Financial Closing cockpit for each Company Code and period over the last 12 months, compare each against its calendar deadline, and compute the on-time share. Group by Company Code to see the entity-level breakdown the card exposes on drill-in. Common mistakes when comparing against SAP’s own reports:
- Using “end of month” instead of the configured deadline. On time means on or before the close calendar deadline, which is usually a working day a few days into the next month, not the last calendar day of the period. Comparing against the wrong benchmark inflates or deflates the rate.
- Counting calendar months instead of close events. A multi-Company-Code group has one close event per Company Code per period. The rate is over close events, not months, so a 3-Company-Code group has 36 events a year, not 12.
- Ignoring soft vs hard close. A period that was soft-closed on time but hard-closed late can be read either way depending on which event you key on. The card keys on the period-lock event that matches the configured deadline; align your manual check to the same event.
| Reason | Direction | Why |
|---|---|---|
| Deadline definition | Either | The card uses the configured close-calendar deadline. A manual check against calendar month-end will not match. |
| Close-event basis | Either | The rate is over close events per Company Code, not over calendar months. A single-entity comparison will not match a group rate. |
| Soft vs hard close keying | Either | Whether you key on the soft-close or hard-close event changes which closes count as on time. The card keys on the period-lock that maps to the deadline. |
| Company Code scope | Either | The card respects the dashboard’s Company Code filter. A report run across a different set of entities will compute a different blended rate. |
| Tenants without the Closing cockpit | Either | Where no Financial Closing cockpit is licensed, the card infers close timing from posting-period lock events, which can differ slightly from a formal task-completion timestamp. |
Known limitations / merchant FAQs
Why is on time measured against a deadline rather than month-end? Because the close legitimately runs into the next month. SAP close calendars give finance several working days after the period ends to post accruals, run FX valuation, clear GR/IR, and reconcile. On time means hitting that configured deadline, not the last day of the period. Measuring against month-end would label every normal close late. A single late Company Code dropped my whole group’s rate. Is that fair? It is deliberate. Group consolidation cannot complete until every contributing Company Code closes, so one late entity really does hold up group reporting. The blended rate reflects that reality. Drill into the per-Company-Code view to find the entity responsible. Does the card distinguish soft close from hard close? It keys on the period-lock event that corresponds to the configured deadline. If your process relies on long soft-close windows with late hard closes, the shape of the rate will reflect whichever event maps to your deadline. Align any manual reconciliation to the same event. My tenant does not license the Financial Closing cockpit. Does the card still work? Yes, with a small caveat. Without a formal close-task list, the card infers close timing from posting-period lock events in the Manage Posting Periods configuration. That is a very good proxy but can differ slightly from a hand-tracked close-checklist completion time. Why a gauge and not a trend? The headline is a bounded 0 to 100% health figure, which reads best as a gauge. The trend over the trailing months is still available on the card so you can see whether the rate is improving or slipping, which is usually more informative than the point value. What is a good target? Most mature finance functions aim for 100% and treat any miss as an exception to be investigated. The<90% alert is a floor, not a goal: dropping below it means more than one in ten closes is late somewhere in the group, which is enough to put statutory filings and group consolidation at risk.
How fresh is the rate?
The rate recomputes as new close events land. S/4HANA Cloud exposes posting-period and close-task data via real-time APIs, and Vortex IQ’s connector refreshes on a regular cadence, so the trailing-12-month figure updates within minutes of each close completing.