Reporting Data Category

Reporting Data are determined based on a combination of BFC dimension Category, Scope, Variant and Flow as shown below:

1. IFRS Data derived based on:
1. Category - ACTUAL2
2. Scope - SYENSQO
3. Variant - IFRS
4. Flow - F99 (Closing)
2. Underlying Data derived based on
1. Category - ACTUAL2
2. Scope - SYENSQO
3. Variant - IFRS
4. Flow - F99X (Closing)
3. RSB – FX Scenarios

Syensqo consolidates in group currency EUR. Currently BFC does not have consolidation in additional Group Currency.

BFC Reporting Categories to be defined as Versions in Group Reporting.

In SAP S/4HANA for Group Reporting, a version represents a specific data area within the consolidation database, used to differentiate between various sets of financial data, such as actual data, plan data, or different scenarios like restatements and simulations. It allows for the parallel processing of these different data sets within the same system

The Version stacking feature will be used to optimize data and process. In Version stacking multiple extension versions can be linked to a single standard version, forming a "version stack," allowing for the analysis of different scenarios built on the same foundational data.

Group Reporting Versions identified that cover existing business requirements are as follows:

• Standard Version (e.g. IFRS)
• Extension Version (e.g. Underlying, APM/MPM)
• Reference Version (e.g. for restating using different exchange rate)

Additional consideration.

• Group Currency Extension Version (e.g. USD)-  this can be automated to consolidate in USD in the background.

The version can share master data, configuration and rules and at the same time  it is possible to use different methods or rules for achieving the specific Consolidation effect, including elimination rules, validation rules or reporting rules in the specific version.

Single Consolidation Group

Syensqo consolidates all legal entities from the perspective of top group SYENSQO. The intercompany transactions are eliminated completely irrespective of whether the partner is part of the GBU or region. 

There is no sub-consolidation performed in BFC. 

Group Reporting can manage the existing consolidation approach\level performed in BFC.

Following the current approach, SYENSQO as a Consolidation Group will be created in Group Reporting consisting of all the company codes. The intercompany transactions will be eliminated from group perspective at Company Code level.

This is also the simplest approach to consolidation.  

At present, there is no requirement for Synesqo to perform sub-consolidation, however this will be reviewed and confirmed in Detailed Design. 

If required, Group Reporting can support sub-level consolidation, by utilizing Profit Centre to determine sub-levels.

Additional View: Global Business Unit (GBU) Reporting

GBU is derived  based on the BFC dimension called Activity. The dimension “Activity" is derived from the Business Area field in ECC based on naming convention and updated in the data package load for BFC.

The “Data Package” is prepared in a csv file for upload in BFC.

Example:

In BFC, the Activity is a manual input field which is derived from the naming convention of Business Area in ECC.

• A Global Business Unit is a semi-autonomous division or subsidiary of Syensqo group that focuses on a specific vertical market, product line, or set of products, services, and functions within a global operation.

• Each GBU is a roll-up of Profit Centres. Each Profit Centre belongs to single GBU
• Group Reporting can utilize the Profit Centre Hierarchy to report financials by GBU.

Single Level Consolidation

• Eliminations and financial consolidation are performed at the entity level.
• Intercompany eliminations are not performed at GBU level. 
• Report to be utilized to view inter-GBU sales \ transactions.
• Depending on the design, the report can be standard within Group Reporting or via SAC.

Sub Level Consolidation

• Eliminations and financial consolidation are performed at Profit Centre level
• GBU is represented by Profit Centre. 
• Intercompany eliminations between GBUs are visible within the sub-level Consolidation.
• The intercompany elimination represents the inter GBU sales\transactions.

Additional View: Operating Segment

Syensqo reports financials by Operating Segment which are derived by roll-up of GBU’s in BFC. 

GBUs are roll-ups of  BFC Activity that are captured in manual data packages

An operating segment is a component of an entity that engages in business activities from which it may earn revenues and incur expenses (including revenues and expenses relating to transactions with other components of the same entity) (IFRS). Syensqo has the following target operating segments:

• Performance & Care
• Materials
• Corporate Business Services (Residual, not reported as Operating Segment)

Single Level Consolidation

• Eliminations and financial consolidation are performed at the entity level.
• Intercompany eliminations are not performed at Segment level. 
• Report to be utilized to view inter-Segment sales \ transactions.
• Depending on the design, the report can be standard within Group Reporting or via SAC.

Sub Level Consolidation

• Eliminations and financial consolidation are performed at Profit Centre level
• Segment is represented by Profit Centre. 
• Intercompany eliminations between Segments are visible within the sub-level Consolidation.
• The intercompany elimination represents the inter Segment sales\transactions.

Additional View: Regional Reporting

At Syensqo, the region is a grouping of company codes based on Country of incorporation.

The financials by country or region  are reported using dimension “Scope”  by selecting relevant values.

• The Consolidation units (mapped to Company Code) will be grouped into regions based on country of incorporation in a hierarchy called Region Hierarchy for reporting Syensqo Consolidated data by region.

Sales Reporting for external result publication

Syensqo requires additional sales information for result publication.

• Net sales by country and region based on the customer’s location
• External net sales by segment 
• External net sales GBU
• Information per segment:
• Net sales (including inter-segment sales)
• Inter-segment sales
• Net sales (external)

• The design for the region based on “ship to" will be based on S/4HANA finance fields for example Customer Source Country (Sold to Country).
• Sales Reporting requirement and solution will be assessed in the Detailed Design, where that outcome from Group Reporting or SAC needs to be determined.

Flow Type

Syensqo uses BFC Flow Type to classify and categorize financial transactions within its consolidation process. 

Flow types are further designated to be used for different set of accounts for example

1. Mutual Flows / Open for all B/S accounts
2. Fixed Assets - Gross Values
3. Fixed Assets - Depreciation & Impairment
4. Goodwill
5. Investment and Shares
6. LT loans & Other LT Receivables
7. Deferred Tax - Assets & Liabilities
8. Financial Instruments - Assets & Liabilities
9. Inventories
10. Short Term Receivables-Cash & Cash Equiv.
11. Equity
12. Provisions - Current and non-current
13. LT Financial Debts & Other LT Liabilities
14. Other Current Payables

Example of BFC Flows:

Flow for all accounts/Mutual flows:

F00 OPENING

F99 CLOSING

F15 VARIATION

F50 RECLASS

F60 OTHER VARIATION

F70 SPECIAL OPERATIONS

F80 FOR.EX. DIFF.

F01 PERIMETER INFLOW

F90 CHG METH. (NEW)

F91 VAR INTEG RATE

F98 PERIMETER OUTFLOW

Flow for Fixed Assets- Gross Values:

F20 INCREASE

F30 DECREASE

F33 ASSETS OUT OF SERVICE

F34 ASSETS BROUGHT INTO SERVICE

Flow for Fixed Assets- Depreciation and Impairment:

F25 ALLOWANCE

F36 WRITE BACK (NOT USED PROV.)

F30 DECREASE

F33 ASSETS OUT OF SERVICE

F34 ASSETS BROUGHT INTO SERVICE

Rest of flows:

F05 NET INC N-1

F06 DIVID PAID

F10 NET INCOME

F24 ALLOWANCE

F26 RESEARCH ALLOW

F27 REV PREV MEASURES

F28 NEW MEASURES

F31 SHORT TERME TRANSFERT

F32 ACTUALIZATION / CURRENCY

F35 W.B. (USED PROV.)

F37 WRITE BACK (NOT USED PROV.)

F40 CHG CAP

F51 EQ. COMP. FIN. INST

F52 SHARE-BASED PAIEMENTS

F53 ASSETS CREATED WITHIN GROUP

F55 FAIR VALUE DIFF.

F56 ACCRETION OF DISCOUNT

F57 EFFECT OF HIGH INFLATION

F61 RECYCLING CFH

F89 CHG METH (FORMER)

F92 PROFIT SHARE INCREASE

In Group Reporting Subitems are used to classify and categorize financial transactions by providing further breakdown of values recorded on financial statement items / accounts. The breakdown is categorized by transaction types or functional areas commonly known as sub-assignments.

• Transaction Type (TTY) subitems for Balance Sheet accounts
• Functional Area subitems for P&L accounts

Group Reporting offers Breakdown Category to classify transaction type/functional areas needed for financial statement (FS) items/account. It determines which sub-assignments must be recorded for each FS item.

Example of Breakdown category that can be configured in the system are

• BS00 - B/S Accounts (e.g.  allowing Mutual TTYs)
• BS10 - Fixed Assets - GBV (e.g. allowing mutual TTYs+ Assets TTY)
• BS20 - Fixed Assets - Depreciation (e.g. mutual TTYs + Acc Depn TTY)

Below is a list of pre-delivered Transaction Types in Group Reporting that as an example can be adapted or additional transaction types created to meet consolidation and reporting requirements. 

900 Opening balance

901 Incoming units

902 Cons Mthd Chg(Old)

903 Cons Mthd Chg(New)

904 EquityMth Rate Chg

906 Dividends

909 Change in accounting policies

915 Net variation

920 Increase/Purchase

925 Increase in depreciation

930 Decrease /Disposal

935 Decrease in depreciation

940 Capital increase/decrease 

950 Reclassification

955 Fair Value

970 Internal Merger

980 Currency translation adjustment

992 Change in ownership interest

998 Outgoing unit

9R0 Opening Restatement

Further, transaction types and functional areas are supported for hierarchy set-up to enable movements report for example Fixed Assets Movements Report.

Finance Integration – Company Codes

BFC Reporting Units are not automatically integrated with the ECC system. The integration is done manually while preparing the csv file called data package.

The data package has some mandatory and optional dimensions. Example:

Mandatory BFC dimensions:

• Category = Always set to “ACTUAL2”
• Period
• Reporting Unit - reporting company
• Currency
• Audit ID - Always set to “0LIA01”
• Account
• Flow
• Currency - Company Reporting Currency
• Amount in Local Currency

Optional  BFC dimension:

• Partner 1 & 2
• Activity /Activity 2
• Activity Partner
• Sales Movement
• Administrative Zone - 4 possible values: EUR, AMNC, ASIA or AMSU
• Comment

The Company Codes in Finance will be integrated as Consolidation Units in Group Reporting for seamless data integration.

The integration takes place in source with Core Consolidation Fields populated for every transactional line item in Universal Ledger/table ACDOCA. 

The core consolidation fields are:

• Consolidation Unit - mapped to Company
• Partner Consolidation Unit - mapped to Trading Partner
• Financials Statement (FS) Item - mapped to GL account
• Subitem - Transaction Type - as per Group Reporting design
• Subitem - Functional Area - as per Group Reporting design

The core consolidation fields in the finance ledger creates a tight and seamless integration layer which is used for pulling data via release mechanism into the consolidation database /table ACDOCU.

Example of Consolidation Data base:

• Version  = as per Group Reporting design
• Period: posting period /year of the data extracted
• Consolidation Unit -xxxx where x is company code
• Partner Consolidation Unit  - where available
• Profit Center
• FS Item - same as GL account
• Subitems - transaction types or functional areas or blank per design
• Transaction Currency - from accounting 
• Amount in Transaction Currency - from accounting
• Local Currency - from accounting
• Amount in Local Currency - from accounting
• Group Currency - as per design of Version
• Amount in Group Currency - as per design of currency translation rule
• Posting Level - # (default by system)
• Document Type- e.g. 0F  as per design
• Custom Field as per design
• Username - User who executed data release task
• Timestamp - When data was extracted from accounting

Finance Integration – Chart of Accounts

Syensqo has a disparate chart of accounts between accounting and consolidation. Operating GL chart of account is mapped to BFC Reporting items and uploaded in BFC via data package. 

Group Reporting will use the same Chart of Account as General Ledger Operating Chart of Account.

The Operational Chart of Accounts will be mapped as a Financial Statement (FS)  item on one to one basis in Group Reporting.

Finance Integration – Additional Master Data 

Additional Master Data for reporting are created as custom fields in BFC for data loading and reporting.

Group Reporting can integrate and read additional fields from S/4HANA accounting for reporting. For example:

• Functional Area as a subitem
• Material Group (Product Sold)
• Customer Source Country (Sold to Country)
• Segment
• Market etc.

Note: Additional Custom fields can be set up to meet consolidation and reporting requirements to be determined in detail design phase.

Finance Integration – Drilldown to GL Document

Drill down from BFC to ECC is not possible.

Group Reporting provides functionality for analysis and processing with full drilldown to source data at its origin.

Note: Drill-down to source will not be available in other S/4 instances for example China and CUI systems, however common charts of account and system design will still enable easy access to detailed information in China and CUI systems.

Finance Integration – Intercompany Matching and Reconciliation (ICMR)

No integration to BFC available

S/4HANA Intercompany Matching and Reconciliation (ICMR) a built-in and integrated solution will be used to automate and streamline the intercompany matching and reconciliation process. It supports real-time matching and reconciliation of financial data, eliminating the need for separate load processes.

ICMR can also connect to separate S/4HANA China and CUI systems.

Integration with separate ERP System – China / CUI

China is not in a separate system.  Although BFC could manage this via the existing manual data package loads.

SAP Group Reporting Data Collection (GRDC) App will be used to integrate with China/CUI instances of S/4 system for collection of data. GRDC is specifically designed to integrate with SAP S/4HANA for Group Reporting , allowing for seamless data transfer and consolidation. 

Cash Flow

BFC used cash flow codes (CFxxxx) and rules based on account and flow to produce automated cash flow reports with some manual adjustments.

BFC produce below two cash flow reports :

1. Management Cash Flow /Simplified Cash Flow by GBU
2. IFRS Cash Flow Report (Group) - comprising of
1. Operating Cash Flow
2. Investing Cash Flow
3. Financing Cash Flow

Group Reporting offers functionalities that can help develop Cash Flow Reporting through “Reporting Rules”. These include a range of mathematical operators to instruct the system on how to compile data for each line in the cash flow statement. 

Group Reporting's reporting rules provided extensive customization capabilities, including account movements (transaction types/functional areas), journal entries (document types), consolidation units and reverse sign indicators among others.

This  solution can be used to prepare multiple versions of fully automated cash flow reports in Group Reporting.

1. Management Cash Flow -Simplified Cash Flow by GBU

1. IFRS Cash Flow Report (Group) - comprising of
1. Operating Cash Flow
2. Investing Cash Flow
3. Financing Cash Flow

The system flexibility can be built to adjust cash flow line items by manual journal entries. The report can drill-down to underlying FS items and transaction types aiding in understanding the composition of balance and reconciliation.

The cash flow reports can be executed for Syensqo, Operating Segments, GBU’s and to the lowest unit for example Consolidation Unit/Company codes or Profit Centre.

In addition, validation rules/controls can be built to ensure accuracy and consistency of cash flow reporting using Group Reporting Validation Rules.

Currency Translation

Syensqo used BFC currency translation features to translate reported local currency into EUR and re-state for RSB versions.

Group Reporting has standard currency translation features using S/4HANA exchange rate table to translate trial balance of entities as per configurable translation rules and methods.

Translation Rules can be set-up for FS items for example

• Non-Historic Balance Sheet items - Closing Rate
• Historic Balance Sheet items - Opening balance unchanged, movements at average rate
• Income Statement - Average rate

Translation Method can be configured to:

• Record any resulting translation difference in the appropriate accounts
• Assign appropriate Exchange Rate Type. 
• Assign Translation Method to Versions. Apply different exchange rates for versions. Example version specific rules can be maintained to produce RSB for example Last year data at Current Rate using specific exchange rate settings for version.

Audit ID and Ledger Dimension

BFC uses Audit ID to identify the source of data stored in the consolidation database for example:

• Packaged data
• Journal entry (uses “Ledger” dimension along with Audit ID) 
• Auto Journal entry (elimination /reclassification)

Audit ID also enable to build control such as

• Whether or not a manual journal entry is authorized for an Audit ID
• Whether Audit ID is available in the package
• Currency of the Journals
• Scope and variant restriction

There are approx. 175 Audit IDs set-up in BFC. Example:

• 0LIA01 - Packaged Data
• 1LIA10 - Local adjustments
• 1RET95 - Reclassification
• 2AJU10 - Inter-company accounts adj.
• 2CONV10 - Other adjustments
• 2ELI10 - Elimination of inter-co accounts
• 2NRI10 - Elimination of inter-company dividends
• 2NRI40 - Elimination of margin on inter-company stocks

Group Reporting uses Posting Level and Document Type to identify source of data and their purpose within the consolidation process. 

Posting level enables to distinguish posting entry types and select data accordingly. They are not user-defined, but rather built-in to the solution.

• Local close: Consolidation unit-dependent, group independent
• # Blank: Reported data / Trial Balance  from S/4
• 00: Flat File load for non-integrated companies
• 0C: Reported data correction
• 01: Manual journal before consolidation
• 10: Standardizing entries
• Pairwise eliminations : Dependent on the pair of consolidation unit and partner unit, group-independent
• 20: Two-sided elimination
• Group-dependent eliminations/entries
• 30: Consolidation entries that represent postings that are explicitly made on consolidation groups. For example, consolidation of investment - elimination of investment and equity, goodwill and NCI postings.
• 02,12 and 22: Entries to accommodate the consolidation group change

Document types identify the type and source of data. For example, reported data is stored on different document types than elimination data. Document types have various attributes assigned, including data source for example manual or automatic posting, file upload or API, deferred income tax handling, automatic reversal and currencies to be used in posting.

Document types are always assigned to a posting level thus document type in conjunction with posting level help identify source and type of data. Document type is user defined, however SAP also delivers some pre-defined document type for our use. Example:

• 0F – Read from Universal Journal (Posting level #)
• 00 – Flexible Upload (Posting level 00)
• 0B – Consolidation of investment (Posting level 00) 
• 07 – External reported data using API (Posting level 00)
• 08 – External plan data (Posting level 0C)
• 01 – Manual correction of universal journal (Posting level 0C)
• 02 – Manual correction of reported data (Posting level 01)
• 10 - Manual correction for goodwill (Posting level 10)
• 12 - Manual standardizing, deferred tax, auto reversal (Posting level 10)
• 2E - Interunit elimination of sales (Posting level 20)
• 2F - Interunit elimination of balance sheet (Posting level 20)
• 3A - Consolidation of investment (Posting level 30)

Manual Journals

BFC uses dimension “Ledger” to control and classify manual journal entries.

Manual Journal entries (for example top entries) are copied, adjusted and posted using the BFC ledger feature.

Currently there is no workflow/approval process for manual journals in BFC. The manager needs to be intimated offline for review when a journal is posted in BFC.

Group Reporting allows manual journal positing by document type (equivalent of ledger in BFC) which can be configured to track and manage financial data for consolidation purposes.

Document Type, a familiar concept in accounting, can be designed for easy identification as manual journals, classification of postings and checks and control can be built on it.

Manual Group Journal can be submitted via 

• Post Group Journal Entries App - Journals are entered on the screen for relevant version, fiscal year, posting period and document type.
• Import Group Journal Entries App - Journals are prepared in an excel template and imported into the system.

Reporting on Manual Journal via Display Group Journal Entries App - This is a report to display a list of documents based on parameters such as consolidation units/groups and the fiscal year/period.

Group Reporting also provides Standard Workflow which can be configured for group manual journal entries to automate review and approval (or rejection) of manual journals.

Data Package

There is no automatic system integration between BFC and ECC systems.

The data for ECC or non ECC entities are mapped and prepared outside the system in a csv file data package and loaded into the BFC system.

Similarly if there is new acquisition made, the trial balance is prepared in csv file and loaded via Data Package in BFC for consolidation.

Group Reporting is fully integrated within the S/4HANA platform. This integration allows for real-time extraction of accounting journals from S/4HANA finance system. 

Group Reporting is closely connected with the Group Reporting Data Collection (GRDC) tool that facilitates the collection of data from various sources, including both SAP and non-SAP systems for use in group reporting and consolidation processes.

1. S/4 entities on Rest of World (ROW) S/4 instance – Accounting Journal data is released into Group Reporting based on tight integration between financial accounting and group Reporting
2. S/4 entities on China/CUI S/4 instance- GRDC tool can integrate with Group Reporting
3. Other entities /recently acquired companies - Flexible upload of data into Group Reporting or integrate with GRDC tool.

Inter Co Eliminations

BFC uses Audit Ids for intercompany elimination postings. Example:

• 2ELI10 - Elimination of inter-company accounts
• 2IMP25 -Elimination of internal provisions
• 2IMP30 -Elimination of internal gains/losses
• 2NPI10 - Elimination of I/C prov. on securities
• 2NPI20 - Elimination of  I/C RC provisions
• 2NRI10 - Elimination of inter-company dividends
• 2NRI40 - Elimination of margin on inter-company stocks (covered separately under PISE Elimination)
• 2NRI50 - Elimination of gain/loss on I/C assets
• 2NRI60 - Depn gain/loss on disposals of I/C fixed assets
• 2TIT10 - Elimination of securities

Group Reporting provides a reclassification function for interunit elimination. Using the reclassification function, automatic elimination tasks will be created for intercompany business transactions. 

Following is an example of elimination tasks each with specific method/rule and unique document type will be created for inter company elimination

• Elimination of intercompany sales
• Elimination of intercompany other income/expenses
• Elimination of intercompany profit in inventory (see section “PISE”)
• Elimination of intercompany dividends
• Elimination of intercompany balance sheet

The above broader category can be further split by group of business transactions. For example elimination of intercompany balance sheets can be split into the following sub-group with each group having its own elimination tasks.

• Short Term Loans
• Trade Receivable & Payable
• Non-trade Current Receivable & Payable
• Non-trade Non-current Receivable & Payable
• Interest Receivable/Payable
• Inter-co Dividend Receivable/Payable
• Long term loans
• Provisions

Inter Co Matching and Reconciliation 

Intercompany matching and reconciliation is performed in the source ECC system. Consolidated elimination mismatch report is available in BFC.

Group Reporting offers pre-delivered “Reporting Item” solutions which can be configured for Intercompany reconciliation reports.

In addition, a fully integrated ICMR (Inter Company Matching & Reconciliation) tool can be used not only for matching and reconciliation but also for elimination posting in Group Reporting.

Consolidation of Investment – Subsidiary, associate

BFC uses Audit ID to perform elimination of investment in subsidiaries and related equity.

Group Reporting offers two design options for consolidation of investment. 

Option 1: Rule based: The system performs C/I calculation and postings by processing a sequence of reclassification steps defined in reclassification methods.

Option 2: Activity based: The system performs C/I calculation and postings by processing one automatic posting task of category Consolidation of Investments. The behavior of the task is influenced by configuration settings which are predefined and delivered by SAP.

Activity Based Consolidation of Investment provides automated posting for:

• First Consolidation – Investment, Equity Elimination and NCI posting
• Subsequent Consolidation – Periodic NCI Calculation
• Step Acquisition
• Increase in Capitalization 
• Decrease in Capitalization
• Partial Divestment
• Total Divestment
• Partial Transfer
• Total Transfer
• Horizontal Merger
• Vertical Merger

Each Consolidation Units are assigned a Consolidation Method based on IFRS consolidation requirement. Available methods are:

• Parent
• Purchase Method
• Equity Method
• Proportionate Method

Balance Carry forward

The balance carry forward is performed in BFC using which creates opening balance for balance sheet account on opening flow F00.

Group Reporting offers standard Balance Carryforward Task to pull the balances of relevant financial statement (FS) items from the previous financial year to the current financial year. The system records these balances as opening balances on specified transaction type in period 00.

The balances are carried forward based on the FS item type of account:

• AST: Asset item: carried forward to the same account as in the previous year
• LEQ: Liability/equity item: carried forward to the same account  as in the previous year
• INC: Profit and Loss statement item: not carried forward
• STAT: Statistical item:  not carried forward unless specified explicitly. Example cash flow account are not carried forward

In addition, it is also possible to define a source document type and a destination document for a specific time frame as a result closing balances at year-end are carried forward from the source document type to the destination document type.

Profit in Stock Elimination (PISE)

Stock Margin custom program executed by shared service team is used in BFC to remove profit from intercompany stock.

Group Reporting has following options:

Option 1: Directly source group valuation ledger as a basis for financial group statements

1. Assign group valuation ledger as group preparation ledger to GR version.
2. Directly retrieve margin free amounts from the Group Preparation ledger.
3. User Delivered Reclassification Rule to eliminate the Gross Margin which was posted in Valuation Clearing account.

Option 2: Keep legal valuation as consolidation ledger and use group valuation to calculate elimination postings.

1. Assign legal valuation ledger as group preparation ledger to GR version.
2. Legal Valuation of Inventory values sourced from legal ledger.
3. Group Valuation of inventory sourced from group valuation ledger into statistical FS items (inventory and markup) using SAP GRDC*
4. Group Reporting reclassification calculate elimination postings on PL20 on top of legal valuations (inventory/COGS)

Option 3: As this area is still evolving under future innovation further solution may be possible in future releases such as extension version/reference version/stack.

The options require further study and analysis during the detailed design phase.

*SAP GRDC stands for SAP Group Reporting Data Collection which is part of SAPs product strategy for consolidation and may require additional licenses.

Excel Retrieve

Integrated Excel retrieve is available in BFC

Integrated Excel retrieve will be available with Group Reporting.

Blocking Controls

and Validation Rules

BFC has blocking controls on specific accounts for example provision accounts where only specific flows are allowed and one cannot post with non-allowed flow.

Line Item Validation :Group Reporting has Breakdown Category Check on account which defines whether transaction type (flows), functional area and trading partner are mandatory and within the list of permissible transaction types. This is checked during postings in group reporting and error is issued if not complied.

In addition, validation will be built in S/4HANA on a specific set of GL accounts with a permissible list to control postings of transaction types/functional areas.  

In addition to Line Item Validation, Group Reporting also offers validation rules at different postings levels.

Example of validation rule that can be set up:

• Total assets must equal total liabilities
• The depreciation expense charged to P&L equals depreciation credited in the Balance Sheet.
• The gross value of Land and Buildings must be > or = depreciation at closing.

Tax Reporting

Tax Reporting is currently completed utilizing BFC to bring data together.

Source information comes from the ECC systems.

Some calculations are performed in Excel.

Country Finance reps submit data.

Options have been identified for Tax Reporting.  

Options will be reviewed and assessed as part of the tax sub stream.

Tax Reporting design is separate to the Group Reporting tool decision. 

Year End Disclosure

Group Reporting & S\4HANA can provide supporting data for year end disclosure.

Existing data can be replicated, with the aim to streamline and simplify.

Shareholdings

Managed by an external application called Khephren

The view at this stage is to continue to utilize Khephren.

Reporting

Reporting requirements will be covered in the detailed design phase.  Group reporting has standard reporting features, however for additional \ custom reports, the project wide approach is to utilize SAP Analytics Cloud (SAC).