Skip to main content
Metrics type: Key Metrics • Category: Nerve Centre
An early-warning alert that fires the moment any Company Code drifts past its FI period-close deadline.

​
At a glance

The single governance pulse that tells the CFO whether the books will close on time. It watches every Company Code in scope, compares each one’s actual period-close status against its scheduled close deadline, and raises a P1 alert the moment any Company Code runs more than five days late. A late close on even one Company Code holds up the whole Group Reporting consolidation run, which means the consolidated P&L and balance sheet cannot be finalised, the audit trail has a gap, and the statutory filing clock is at risk.

​
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 UK enterprise group running SAP S/4HANA Cloud Public Edition with four Company Codes and a 12-month fiscal year. The Group close calendar sets the soft close at working day 4 (WD4) and the hard close at WD6 for fiscal period 005 (May 26). The Group Reporting consolidation run is scheduled for WD8. The card is read on 09 Jun 26, which is WD7. Four things to notice:
  1. One Company Code trips the whole card. Three of four Company Codes are either closed or comfortably inside the five-day tolerance. Company Code 4000 alone, at six days past its earlier local WD4 deadline, takes the card from 0 to 1. The card is deliberately blunt: a single late close is a P1 because it blocks the consolidation that depends on all four.
  2. Deadlines are per Company Code, not group-wide. APAC Trading runs a tighter local statutory deadline (WD4) because its local tax authority demands an earlier filing. The card compares each Company Code against its own configured deadline, not a single group number, so a Company Code can breach even while the group hard close (WD6) has not yet arrived.
  3. In-close is not the same as breaching. Company Code 3000 is mid-close with foreign-currency valuation still running. It is four days past deadline, so it is on the watchlist but not yet breaching the five-day trigger. If FX valuation stalls one more day, 3000 joins 4000 and the card reads 2. This is the value of the card: it shows the slow drift before it becomes a crisis.
  4. The downstream blocker is consolidation. With 4000 still open, the Group Reporting data-collection task for the APAC consolidation unit cannot complete, so the WD8 consolidation run cannot produce a clean consolidated set. The CFO’s WD8 board pack slips. The card surfaces this two days before the consolidation deadline, which is enough lead time to escalate.

​
Sibling cards merchants should reference together

Period Close Past Deadline is the headline governance alert, but the period-close health story is told across several cards. Pair it with these to see why a close is slipping and whether the pattern is chronic.

​
Reconciling against SAP

Where to look in S/4HANA Cloud: The closest native equivalents inside the SAP Fiori launchpad are:
Manage Closing Tasks / Close Financial Period apps for the period-control and close-task status Group Reporting: Data Monitor and Consolidation Monitor for the per-consolidation-unit close status that gates the group run Open and Close Posting Periods configuration (conceptually transaction OB52) for the per-Company-Code period-control variant Embedded Analytics: the close-task status query inside the Advanced Financial Closing (AFC) content, where AFC is licensed
Direct link template: https://my{tenant}.s4hana.cloud.sap/sap/bc/ui2/flp#ClosingTasks-manage The period-control state you see in Open and Close Posting Periods should agree with this card to the Company Code: a Company Code whose closing periods are still open beyond its deadline is the same Company Code the card flags. For the consolidation view, the Group Reporting Data Monitor shows each consolidation unit’s data-collection status; any unit not at “completed” is what holds the consolidation run, which is the downstream risk this card warns about. Common mistakes when comparing against SAP’s own reports:
  • Confusing posting-period open status with close-task completion. A Company Code can have its posting periods technically open for legitimate late postings yet still be reported as on-time by the close team. The card uses the scheduled close deadline, not raw period-open status, so it can read healthy even when periods are still open inside tolerance.
  • Reading the group hard close instead of the local deadline. Local statutory deadlines for some Company Codes fall earlier than the group hard close. A Company Code can breach its own deadline while the group calendar still shows time remaining.
  • Treating a manual sign-off as a system close. Some teams sign off a close in a spreadsheet before the system close tasks complete. The card reads the system state, not the spreadsheet, so it can flag a Company Code the team believes is done.
Why our number may differ from SAP’s reports:

​
Known limitations / merchant FAQs

Why is a single late Company Code a P1 alert? Because Group Reporting consolidation is all-or-nothing. The consolidated P&L and balance sheet cannot be finalised until every consolidation unit has completed its data collection. One late Company Code blocks the entire group close, delays the board pack, and risks the statutory filing deadline. A late close also means the audit trail for that period is incomplete, which auditors flag. The blast radius of one late entity is the whole group, so the card treats it as a top-tier alert. What exactly counts as the deadline? The scheduled close deadline configured for each Company Code in the close calendar, expressed in working days from period-end (for example WD4 soft close, WD6 hard close). Some Company Codes carry tighter local statutory deadlines than the group calendar. The card compares actual close status against each Company Code’s own deadline, not a single group number. Why five days and not zero? A small tolerance avoids alert fatigue. Almost every close has one or two Company Codes that finish a day or two late for legitimate reasons (a late bank statement, a pending FX valuation). The five-day trigger separates normal close friction from a genuine blocker. If you want a tighter governance posture, the underlying status is also visible on the per-Company-Code breakdown card with no tolerance applied. Does the card know the difference between open posting periods and an unfinished close? Yes. A Company Code can keep posting periods open for legitimate late entries without being late on its close. The card reads the close-task / consolidation-unit completion state, not raw period-open status, so routine open periods inside tolerance do not trip it. What clears the alert? The Company Code completing its close: all close tasks done and the consolidation-unit data collection reported complete. The card is real-time, so it clears on the next connector poll after the close finishes. There is no manual acknowledgement step; the alert reflects live system state. Does it cover Group Reporting eliminations and intercompany close steps? The card focuses on per-Company-Code close timeliness. Intercompany matching and elimination blockers are a distinct failure mode covered by the Intercompany Imbalances (consolidation blocker) card. A close can be on time per Company Code yet the consolidation still stalls on unmatched intercompany pairs, so read both together near period-end. We use Advanced Financial Closing (AFC). Does the card use it? Where AFC is licensed and configured, the card reads task-level completion, which is the most precise signal. Where AFC is not in use, the card falls back to FI period-control status, which is coarser but still flags a Company Code stuck open past its deadline. The behaviour degrades gracefully rather than going dark.

​
Tracked live in Vortex IQ Nerve Centre

Period Close Past Deadline (any CompanyCode) is one of hundreds of KPI pulses Vortex IQ tracks across SAP 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 or book a demo to see this metric running on your own data.