1. Objective and Scope
RSB category is managed by and is under the responsibility of Corporate and Business Controlling teams. Purpose of this category is to restate historical data (Y-1 / source ACTUAL2 category) with current (Y) structure and exchange rates and store the results in BFC.
Restated Y-1 data is used for internal Business performance analysis as well as for external publication.
Scope of restated data:
- quarterly cumulative data (no monthly restatement)
P&L: Sales up to Underlying EBIT (including Equity results)
Capital Employed ( WC + Assets + Investments)
Planning:
- Category initialized in July Y
- Business structure changes expected for Y+1 defined before Christmas - BFC set up in 2 waves Q4 Y and end Jan Y+1
- Q1 Y+1 (February at latest to be ready before Q1 Y+1 results): technical checks, input of structure effects (through top entries or using dedicated consolidation rules. no usage of packs)
- updated all during Y+1 year each time a structure effect requires a restatement
Changes in the structure are reported by each enterprise/zone using specific flows:
- RS00 Historical data (Y-1 Actual2 figures): technically ACTUAL2 Y-1 is preloaded in RS00 by Activity 1 (P&L + A/R) and Activity 2 (Capital Employed excluding A/R)
- RS01 Acquisition (perimeter inflow: companies entering in conso scope as IG, MEQ or IP / Business acquired)
- RS98 Disposal (perimeter outflow: companies divested / Business divested)
- RS50 Reclassifications (account reclassifications i.e. change of depreciation in inventories to fixed costs - subject to approval from Corp. Controlling teams as it may impact extternal communication made in Y-1)
- RS6x Business transfers intra Solvay
- RS61 - Inter Markets (Intra BU) Transfers
- RS62 - Inter BU (Intra GBU) Transfers
- RS63 - Inter GBU's Transfers
- RS7x Organizational Solvay Changes (change in accounting rules i.e. IFRS16 implementation - subject to approval from Corp. Controlling teams as it may impact external communication made in Y-1)
- RS80 Conversion effect (automatically calculated in BFC through dedicated Consolidation rules using Y-1 and Y Exc rates tables)
- RS99 Restated = (Sum of the flows this above)
- NB are excluded from structure effects : correction of mistakes in Y-1 Actuals, shutdown of a product line, change of contract terms, discontinued operations (already recorded in Y-1 Actuals)
RSB category has its own category scenario "RSB", scope "RSBSOL" and exch. rates version "PREV".
- RSB scope includes the « ACTUAL2 » entities + fictive Business entities (GEST-xxx – used to record the structure changes).
- RSB is a multi-period category with one single data entry period YYYY.01
2. RSB Reporting Setup
2.1 Reporting setup - Reporting Organizer
The opening of RSB phase should occur in July.
To create a new Reporting ID for the period, select the one of the previous year in the field Select Reporting IDs.
Then in Reporting Organizer module Open it and Save As.
In the General tab defines the general properties of the reporting ID.
Enter the following information:
- Category - RSB
- Data entry period - YYYY.01
- Short & Long description - RSB YY/YY+1 "Official" left-to-go converted at Budget rate
The Definition tab will define the associated category scenario and the start and end dates for the reporting.
Enter the following information:
- Version of category scenario: latest version to be selected
- Start & End Date: Adjust start and end date
The Package tab defines the data entry settings applicable to packages:
- Windows and Internet folder: LRSB
- Set-of controls: LRSB
- Control level to be reached: RSB
- Blocking - Flag the option Blocking
- Opening balance data : not applicable (this is through the dedicated RS00 flow that Y-1 ACTUAL2 historical data will be preloaded)
The Restrictions tab defines the data entry restrictions which are applied when the data is entered.
- Read-only flows: RS00 is the opening balance flow automatically generated (Y-1 Actual2 / F99AJ)
- Data entry restrictions: SOCIALRSB
In the Operation tab defines the settings associated with packages publication.
In the Deadline it has to be informed the deadline for package's publication. It has not such an importance as, in principle, there no packages and if any it will be completed centrally by Corporate Controlling.
3. RSB initialization (July)
3.1 RSB consolidation scope
There is only one scope per year - RSBSOL YYYY.12 - and it should be aligned with December ACTUAL2 scope of corresponding year of restatement (example: RSB 2022/2023 => aligned with 12.2022 ACTUAL2 scope).
BFC Admin starts working in the RSB YY/YY+1 phase in July YY and the RSBSOL YYYY scope should be created by a save as of ACTUAL2 YYYY.06 (most recent scope available in FCPROD). The following principles have to be applied:
1) include companies conso at both opening and closing in ACTUAL2 scope;
2) include companies consolidated at opening even if sold or merged during the year in ACT2 scope;
3) include companies consolidated at closing even if non conso at opening (ex newco stardust US) ;
4) exclude companies non conso at opening and non conso at closing in ACT2 scope.
Further updates from July to Dec YYYY will be limited to the replication (manually) of ACTUAL2 scope changes.
3.2 RSB set of rules
A new set of rules should be created every year - RSBSOLYY - to be associated to RSB Y/Y+1 conso.
The following subset of rules should be included and not changed as they are permanent rules applying to RSB phase every year:
- 10-AN-RSBS16 - Generation of opening flow RS00
- 15-STAT-RSB - Calculation of sales (company level)
- 18-ELI-RSB - Sales elimination
- 40-TOT-RSB - Calculation and storage of Totals - RSB
- 046-TX-RSB14 - Special rules for conversion
Only subset 13-REC-RSBYY should be created every year as it includes dedicated consolidation rules customized to manage automatically (when possible) some structure effects.
Examples:
- Business 100% internally transferred from A to B using flows RS61, RS62 or RS63.
- External divestments: full company(ies) divested (share deals) or Business 100% sold
When creating the set of rules in July YY, this subset should be left empty and should be completed once Corporate Controlling has requested BFC Admin to customize the conso rules for the scope changes effects.
See chapter 4.RSB consolidation rules update
3.3 RSB consolidation
RSB YY/YY+1 consolidation should be created and run already in July YY to allow early technical consistency (pre loading of ACT2 balances into RSB through RS00).
To create RSB conso BFC Admin should do a save as of previous year conso RSB Variant 2.
In the General tab replace the data entry period to 01.YYYY and correct the long description.
In the Properties tab replace
- the scope by the new one RSBSOL 12.YYYY
- the set of rules by the new one RSBSOLYY
- the conversion rates by PREV March YYYY+1
In the Periods tab replace
- the conversion rates by PREV March YYYY+1
- the scope by RSBSOL 12.YYYY
3.4 RSB opening checks
Once RSB consolidation has been run, BFC Admin should check the alignment of flow RS00 with ACTUAL2 F99AJ (P&L) and F99 (BS).
Report GRSB-040 should be used to check P&L and GRSB-002 to check BS.
In report GRSB-040 - Flow Audit : Doc: Account - Row: Market/Entity - Col: RS00 vs Actual selection criteria should be completed as follows:
Data Source
Data Source: Consolidation data - Consolidated amount
Dimension Members
Account (aggregated): Filter CRR000-37
Consolidation Currency: EUR
Contribution Level: TS
Partner 1: All or no members
Site: All or no members
Variant: 2
Reference period: YYYY.03 (or 06 or 09 or 12) to check RSB00 is aligned with F99AJ / YYYY.03 / ACTUAL2
Activity 1 (Itemized, total after): All members
Reporting Unit (Itemized, total after): All members
Category: ACTUAL2
Data entry period: YYYY.03 (or 06 or 09 or 12) to check RSB00 is aligned with F99AJ / YYYY.03 / ACTUAL2
Scope: RSBSOL
