Multi-entity SAP installs close per CompanyCode; one late entity blocks consolidation. The card that tells the group controller which entity is holding up the close.
At a glance
The financial-period close state of each Company Code in S/4HANA Cloud, shown side by side. Multi-entity SAP installs do not close as one; each Company Code closes its own posting period on its own timetable, and group consolidation cannot complete until every entity is closed. This card surfaces the per-entity status so the group controller can see at a glance which Company Code is on time, which is in progress, and which is overdue, because a single late entity holds up the entire group close.
| What it counts | The posting-period open or closed state per Company Code, plus the close progress relative to each entity’s close deadline. Driven by the posting-period control in S/4HANA Cloud (managed via the Manage Posting Periods Fiori app and the posting-period variant) and the close-task status where a financial close cockpit is in use. |
| Reading the value | For each Company Code the card shows whether the current period is still open for posting, in the process of closing, closed on time, or overdue past its deadline. The group is only fully closed when every entity shows closed. One overdue entity is the blocker. |
| What “overdue” means | A Company Code whose close has run past its configured deadline by more than the alert tolerance. The card flags the days late so the controller can prioritise the slowest entity. |
| Currency | Status and count metric, currency-agnostic. The card reports close states and days-late counts, not values. For the financial impact of an unposted period, pair with the journal and unposted-entry cards. |
| Company Code scope | The whole point of the card is the per-Company-Code breakdown. It lists each Company Code visible to the connected SAP business user / API role with its individual close status. Respects the dashboard Company Code filter if one is applied. |
| Time window | RT (real-time close status) |
| Alert trigger | overdue >5d on any CompanyCode |
| 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 UK enterprise group on SAP S/4HANA Cloud Public Edition, four Company Codes, closing the April period. Group close deadline was 06 May 26. Snapshot taken 12 May 26.| Company Code | Period | Close deadline | Status | Days late |
|---|---|---|---|---|
| 1000 UK Distribution Ltd | Apr 26 | 06 May 26 | Closed on time | 0 |
| 2000 US Distribution Inc | Apr 26 | 06 May 26 | Closed on time | 0 |
| 3000 EU Distribution BV | Apr 26 | 06 May 26 | Closed (1 day late) | 1 |
| 4000 APAC Trading Pte | Apr 26 | 06 May 26 | Open, overdue | 6 |
| Period Close Status (this card) | 1 entity overdue |
- CC 4000 is six days overdue, above the 5-day alert tolerance. The gauge fires. The group close cannot complete and consolidation cannot run until APAC Trading closes its April period. The card names the single blocker out of four entities.
- Three of four entities are effectively done. CC 1000 and 2000 closed on the deadline; CC 3000 slipped one day, within tolerance, so it does not alert. The group is held hostage by one entity, which is the exact pattern this card exists to expose.
- The blocker usually has a concrete cause. An overdue entity is typically waiting on unposted journals, an IDoc-failure backlog, or an intercompany reconciliation that has not balanced. Drill into Open (Unposted) Journal Entries and the intercompany cards filtered to CC 4000 to find what is stuck.
- One late entity has a group cost. Consolidation, group reporting, and the board pack all wait on the slowest Company Code. The card turns “the close is late” into “CC 4000 is late by six days”, which is the actionable form the controller can escalate on.
- Manage Posting Periods Fiori app: open and close posting periods per Company Code.
- OB52 (heritage posting-period variant): posting-period control table.
- Financial close cockpit / Manage Closing Tasks: per-entity close-task status where used.
- Manage Journal Entries: find unposted documents blocking an entity’s close.
Sibling cards merchants should reference together
Period Close Status names the blocking entity. Pair it with the cards that explain why an entity is stuck and the cards that measure close performance over time.| Card | Why pair it with Period Close Status |
|---|---|
| Period Close Past Deadline (any CompanyCode) | The group-level alert that any entity is late; this card names which one. |
| Period Close On-Time Rate (12mo) | The longer-run track record behind today’s snapshot. |
| Open (Unposted) Journal Entries | The most common reason an entity cannot close; unposted documents block the period. |
| Journal Imbalances (Debit/Credit) | An unbalanced entry blocks posting and therefore close. |
| Intercompany Imbalances (consolidation blocker) | Unreconciled intercompany lines stop consolidation even after entities close. |
| Accrual Reversals (last close) | Accrual and reversal hygiene is part of a clean close. |
| SAP S/4HANA Health Score | Close-on-time is a component of the composite health score. |
| Top Findings Across Company Codes | The broader per-entity findings roll-up. |
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 showing the open/closed period per Company Code
Posting Period control (heritage transaction OB52) for the posting-period variant table
Manage Closing Tasks / financial close cockpit for per-entity close-task progress where in use
Embedded Analytics: the posting-period status and closing-task CDS views in your release
Direct link template: https://my{tenant}.s4hana.cloud.sap/sap/bc/ui2/flp#PostingPeriod-manage
To reproduce the card, open the Manage Posting Periods app and read the open/closed state per Company Code for the period being closed. Where you run the financial close cockpit, the per-entity close-task completion gives the in-progress and overdue states. The per-Company-Code status should match the card.
Common mistakes when comparing against SAP’s own reports:
- Posting-period variant sharing. Several Company Codes can share one posting-period variant. Closing the variant closes all of them at once, so per-entity status can look identical when entities actually share a control. Confirm whether each entity has its own variant.
- Account-type ranges. The posting-period control opens and closes by account-type range. A period can be closed for customers and vendors but still open for GL adjustments. A naive “is the period open” check can mislead; the card reads the close state relevant to the financial close.
- Special periods. SAP supports special posting periods (13 to 16) for year-end adjustments. A period can be closed for normal postings but open for special-period adjustments. Confirm which the report is showing.
| Reason | Direction | Why |
|---|---|---|
| Posting-period variant sharing | Either | If entities share a variant, their statuses move together. The card reports per Company Code; a variant-level check may look different. |
| Account-type range | Either | A period closed for some account types but open for others can read as open or closed depending on which range the comparison checks. |
| Deadline definition | Either | The card measures overdue against the configured close deadline. A manual check against a different internal target date will land on a different days-late count. |
| Snapshot timing | Either | Close status changes the moment an entity closes. A report run after the card snapshot can show the blocker resolved. Match the timestamp. |
| Special periods | Small | A period open only for special-period adjustments may read as open in one report and closed in another. |