SAP ConsultingFinance
SAP Group Reporting - Consolidation
SAP Group Reporting collects subsidiary data, translates it into the group currency, matches intercompany balances and posts the eliminations behind your consolidated statements. It runs inside S/4HANA, so ledger lines from companies on the same system are read without being copied.
Part of these processes
Process
Consolidation steps in SAP Group Reporting
The Data and Consolidation Monitors run tasks in order; adjustments and eliminations land in ACDOCU with their own posting level.
- 01Group structureF4685 · F3733
Units, groups, FS items
- 02Data collectionData Monitor · CXCD
0F or flexible upload
- 03Currency translationFINCS_CTR_EXEC
Into group currency
- 04Intercompany matchingF3868 · F4774
Differences get reason codes
- 05EliminationsCX20 · F7271
Posting levels 20 and 30
- 06Group reportsW0135 · F6133
Balance sheet, P&L, equity
Layers
Where does group data come from?
The system a company keeps its books in decides how its numbers reach consolidation.
- 01
Source company
- Books kept in S/4HANA
- Still on ECC
- On a non-SAP ERP
- 02
Data path
- 0F: read, not copied
- Flexible upload
- Data Collection (BTP)
- 03
Group Reporting
- Actuals version Y10
- Group currency extension
- Postings in ACDOCU
- 04
Output
- Consolidated statements
- SAC report books
- Changes in equity
Scope
What we cover in consolidation projects
Units, groups and FS items
Consolidation units, period-based group structures, financial statement items and the G/L to FS item mapping.
Data collection paths
0F for S/4HANA companies; flexible upload or Data Collection forms for entities on ECC or non-SAP systems.
Intercompany reconciliation
Matching methods, reason codes, responsible teams and the period reconciliation close; eliminations can use ICMR rules.
Translation and versions
Translation methods; actual, budget and forecast versions, and extension versions for a second group currency.
Eliminations and equity
Sales, dividend and balance sheet eliminations; investment consolidation and the equity method through Equity Pickup.
Report books
Group Data Analysis, the review booklet (F6133) and live SAP Analytics Cloud reports on consolidated data.
Current state
Moving from EC-CS and BCS to SAP Group Reporting
- Group Reporting licenses include EC-CS use until 31 Dec 2027 (Note 2999249). On RISE and SAP S/4HANA Cloud Private Edition (new name: SAP Cloud ERP Private), the limit is 31 Dec 2033.
- SEM-BCS and Real-Time Consolidation have been in deprecation state since S/4HANA 2022 and get no new features; SAP names Group Reporting as their alternative.
- EC-CS works on its own totals table (ECMCT). Group Reporting keeps consolidated postings in ACDOCU and reads ledger lines of S/4HANA companies straight from ACDOCA.
- In release 1809, EC-CS and Group Reporting cannot run side by side in one system. From 1909 a hybrid state is possible, though SAP Support carries out some of the steps (Note 2833748).
Localization
IAS 29, BOBİ FRS and Turkish groups
No ready-made IAS 29 solution
SAP's Türkiye documentation says there is no standard or localized inflation solution for Türkiye (Note 3378302). The adjustment layer is chosen at project start.
BOBİ FRS 22.11
A parent that is not a large entity must still consolidate if one of its subsidiaries qualifies as a public interest entity.
TFRS and BOBİ FRS side by side
When the parent reports under TFRS and a subsidiary under BOBİ FRS, policy gaps such as operating leases go in as standardizing entries at posting level 10.
An IFRS ledger in the subsidiary
A subsidiary reporting to its parent under IFRS can also keep the adjustments in its own SAP system. Negzel's IFRS Package calculates them in a parallel IFRS ledger.
IFRS Package
From the field
What we keep seeing in SAP Group Reporting projects
- From Year cannot be changed later. Once entered, the start year for preparation ledger integration is fixed, and SAP Support changes it only for reasons it accepts. We tie the year to the migration and comparative period plan before anyone types it in.
- Unmapped accounts leave gaps. The release task does not carry G/L accounts without an FS item mapping into consolidation. Every new account should pass a mapping check, and that check belongs on the closing checklist.
- The trading partner field stays empty. Intercompany documents posted without a trading partner never match, so eliminations are done by hand. Deriving the partner from the business partner and validating it at posting fixes this for good.
- IAS 29 moves around from year to year. If the adjustment sits in the company ledger one year and in a spreadsheet the next, consolidated figures stop being comparable. Pick the layer in a written decision and keep to it every period.
FAQ
SAP Group Reporting: common questions
What is SAP Group Reporting?
SAP Group Reporting is the consolidation solution that runs inside S/4HANA. Data collection, currency translation, intercompany reconciliation, eliminations and group reports all happen in the same system. Consolidated postings are stored in ACDOCU; the official name is SAP S/4HANA Finance for group reporting.
Do we need a separate system for consolidation?
No. Group Reporting is part of S/4HANA and reads the ledger lines of companies on the same system without copying them. Companies that keep their books on another ERP or a non-SAP system send data through flexible upload, the import apps or SAP Group Reporting Data Collection.
Can Group Reporting apply IAS 29 automatically?
No. SAP's own documentation states that there is no standard or localized inflation solution for Türkiye (Note 3378302). Whether the IAS 29 adjustment is made in the company ledger or in the data brought into consolidation is decided at project start, based on audit trail and comparative period needs.
Which Turkish companies must prepare consolidated statements?
Under BOBİ FRS 22.10, a parent that is not a large entity does not have to consolidate; if it chooses to, it must continue for at least two reporting periods. Under 22.11 the obligation arises when one of its subsidiaries is a public interest entity. Companies under TFRS or CMB rules are assessed separately.
How does intercompany reconciliation work in Group Reporting?
ICMR (Intercompany Matching and Reconciliation) matches counterpart documents with defined matching rules; differences get a reason code and workflows route them to the responsible team. The period close is handled in Manage Reconciliation Close, and eliminations can also run as tasks based on ICMR posting rules.
When should we plan the move off EC-CS?
The right to use EC-CS under a Group Reporting license ends on 31 December 2027. Per SAP Note 2269324, RISE and SAP S/4HANA Cloud Private Edition (SAP Cloud ERP Private) subscriptions keep it to the end of 2033. On release 1909 or later both can run in a hybrid state, but SAP Support carries out some of the steps. An early start leaves room for a parallel run.
Sources12 sourcesSAP Help Portal, KGK, SAP Support
SAP Help Portal
- Group Reporting (SAP S/4HANA 2025, Group Reporting FIN-CS) help.sap.com (opens in a new tab)
- Data Monitor (SAP S/4HANA 2025, Group Reporting) help.sap.com (opens in a new tab)
- Consolidation Monitor (SAP S/4HANA 2025, Group Reporting) help.sap.com (opens in a new tab)
- Consolidation Versions (SAP S/4HANA 2025, Group Reporting) help.sap.com (opens in a new tab)
- Configuration for Group Reporting Preparation Ledgers (SAP S/4HANA 2025) help.sap.com (opens in a new tab)
- Release Universal Journal (Classic Integration) (SAP S/4HANA 2025, Group Reporting) help.sap.com (opens in a new tab)
- Document Types and Posting Levels (SAP S/4HANA 2025, Group Reporting) help.sap.com (opens in a new tab)
- Simplification List for SAP S/4HANA 2025 - Feature Pack Stack 1 help.sap.com (opens in a new tab)
- Note on Inflation Management (SAP S/4HANA 2025, Turkey) help.sap.com (opens in a new tab)
KGK
SAP Support
Sources checked as of October 2026. SAP Notes require an SAP for Me account.
SAP Consulting
Map your group structure with an expert
We can work out how each company's data flows in and where the IAS 29 layer should sit.