The financial close is the process of finalizing the accounting records for a period and producing reliable financial statements. In a group, this happens at two levels: each legal entity closes its own books (the entity or local close), and the group consolidates those results into group financial statements. SAP S/4HANA Cloud Public Edition supports both levels, and because they run on the same unified data foundation, the path from an operational posting to a consolidated statement stays connected.
This article describes the entity close, the orchestration of the close across many entities with SAP Advanced Financial Closing, and group consolidation with SAP S/4HANA Cloud for group reporting. It applies to SAP S/4HANA Cloud Public Edition only and does not describe SAP ERP (ECC), Private Edition, or on-premise deployments.
The entity close finalizes the books of a single company code for a period. In SAP S/4HANA Cloud Public Edition, it is carried out through a set of standard closing activities delivered as SAP Fiori applications. Typical tasks include recording accruals and deferrals, posting depreciation for fixed assets, valuing foreign-currency open items, running allocations in management accounting, and reconciling sub-ledger activity, followed by opening and closing the relevant posting periods.
Posting periods are opened and closed to control when entries may be recorded, so that a period can be locked once its close is complete. At year-end, the closing sequence finalizes the individual periods, posts final adjusting entries, and carries the balances forward into the new fiscal year so that opening balances are established. Because the general ledger, sub-ledgers, asset accounting, and management accounting all post to the Universal Journal, many reconciliations that were historically separate steps are inherent to the data model rather than tasks to be performed at close.
The standard closing activities are executed through individual applications for each task. Coordinating those tasks across periods and entities, with dependencies, responsibilities, and status tracking, is the role of the close orchestration described next.
For organizations that run the close across many company codes and, in some cases, several systems, coordinating the individual closing tasks becomes a significant undertaking in its own right. SAP Advanced Financial Closing addresses this by orchestrating the entity close across the landscape.
SAP Advanced Financial Closing is a separately licensed solution that runs as an application on SAP Business Technology Platform and connects to SAP S/4HANA Cloud as a communication system. It provides a central place to define the closing tasks and task lists, schedule them, automate the routines that can run without manual intervention, and monitor the progress and status of the entire close in real time. Standard operating procedures for recurring closes can be captured once and reused, and manual steps can be assigned to responsible users with clear timing and dependencies.
The result is that the close moves from a set of individually run tasks to a managed, repeatable process with visibility into where each entity stands. Because it is a separate solution, SAP Advanced Financial Closing is adopted where the scale or complexity of the close justifies dedicated orchestration; smaller organizations may run the standard closing activities directly through the delivered applications. The table below distinguishes the two levels.
| Level | What it does | How it is delivered |
|---|---|---|
| Standard closing activities | Perform the individual close tasks for a company code (accruals, depreciation, period control, carryforward). | SAP Fiori applications in SAP S/4HANA Cloud Public Edition. |
| SAP Advanced Financial Closing | Orchestrate, schedule, automate, and monitor the close across entities and systems. | Separately licensed application on SAP Business Technology Platform, integrated with SAP S/4HANA Cloud. |
Group consolidation combines the financial results of the individual entities into financial statements for the group as a whole, eliminating the effects of transactions between group entities. SAP S/4HANA Cloud Public Edition provides this through SAP S/4HANA Cloud for group reporting, a consolidation capability embedded in the solution.
Group reporting builds on the same data foundation as the rest of finance. Accounting data in the Universal Journal feeds the consolidation, and consolidation-specific entries are held in a dedicated consolidation journal. Because the source accounting data and the consolidation run on the same platform, group reporting can draw directly on entity results rather than importing them through a separate interface, which supports a shorter path from local close to group statements.
The main consolidation functions include:
Group reporting supports both statutory consolidation, for external group financial statements, and management consolidation, for internal group reporting. Where data must be collected from entities that are not on the same SAP S/4HANA Cloud system, SAP Group Reporting Data Collection supports gathering that data, and SAP Analytics Cloud provides analytical and management reporting on the consolidated results.
A defining characteristic of running consolidation on the same platform as the operational accounting is that consolidation activities can be performed throughout the period rather than only at period-end. SAP positions this as continuous accounting: because entity results are continuously available in the Universal Journal, preparatory consolidation steps and reconciliations can be carried out earlier and more frequently, so that the period-end run is less of a single, concentrated effort. This is an approach enabled by the unified data model rather than a switch to be turned on, and organizations realize it by designing their close process to take advantage of the real-time availability of data.
Financial statement versions define the structure of the balance sheet and income statement and are the basis for statutory reporting as well as internal reporting. An organization can define as many financial statement versions as it needs, for example to meet the requirements of different tax authorities or to present internal management views, and global hierarchies are used to create and maintain these structures.
At entity level, multidimensional financial statement reporting presents the balance sheet and income statement across operational, local, and group chart-of-accounts perspectives, supporting both management and statutory views from the same data. At group level, the consolidated statutory and management statements are produced from group reporting, with analytics delivered through SAP Analytics Cloud. Because all of these outputs draw on the Universal Journal and the consolidation journal, the entity and group views remain consistent with one another.
SAP S/4HANA Cloud Public Edition includes automation and AI capabilities that assist the close, and these are extended over successive releases. Examples include agent-assisted support for the financial close accountant across tasks such as clearing, reconciliation, and journal entries; assistance that generates journal-entry proposals for review; and AI support for generating accrual entries from historical data and accounting policies. The Joule copilot is embedded in the solution and can support close-related tasks. These capabilities are designed to reduce manual effort while keeping review and posting under human control. Because the specific features and their availability change by release, organizations should confirm the current close-related AI capabilities against official SAP documentation for the release they are running.
When designing the close in SAP S/4HANA Cloud Public Edition, two questions shape the approach. The first is how much orchestration the close needs: organizations with many entities or systems benefit from SAP Advanced Financial Closing, while a simpler landscape may run the standard closing activities directly. The second is the consolidation scope: which entities are in the group, what group currencies and consolidation versions are required, and how data is collected from any entities outside the SAP S/4HANA Cloud system.
Both decisions depend on the accounting foundation being in place, particularly the ledger and parallel accounting design, which is covered in the companion article on financial accounting and the Universal Journal. For the overall structure of finance and how close and consolidation relate to the other finance areas, see the companion overview article on finance in SAP S/4HANA Cloud Public Edition.