This procedure describes purpose of Tax Reporting and how it is managed in BFC, as well as other related customizing in other BFC modules.
Core principles
The tax package aims at reporting the income tax charge at entity level
The objective of the tax package is
Scope: WW consolidated companies (IG / IP / not required for MEQ)
Actors involved and responsibilities
Reporting periods for Taxes organized around :
In order to comply with the above, the tax package has been divided in two phases
INTERIM PERIODS - overview


HARD CLOSE and YEAR END - overview

For more detail, refer to the Tax Package guidebook published in GAR AODOC Library.
BFC Admin team is in charge of:
GAR Team - SYENSQO Group Accounting & Reporting Team (including position of Tax Reporting manager)
BFC-Admin Team - Team administrating BFC (SYENSQO Group Consolidation tool)
FSL CAM - Company Account Manager
FSL TCM - Tax Compliance Managers
IG - Full Consolidated method
IP - Proportional Consolidation method
In the Reporting Organizer module it is created the Reporting ID and it is defined the common data for the packages, as the Deadline, Folder, Set of Controls, Opening Balances, etc.
An option to create the Reporting for a new period is through the option Saving As based in the last version available.
In this procedure it will be created the ACTUAL1-TAX category for the period 2023.09, so the Reporting ID to be entered as reference is ACTUAL1-TAX - 2023.06.

The General tab defines the general properties of the reporting ID.
Enter the following information:

The Definition tab indicates the reporting status. It can also be specified the associated category scenario and the start and end dates for the reporting.
Enter the following information:

The Package tab defines the settings of the data entry environment for the packages.
Enter the following information:
Opening Balance data:

The Restrictions tab defines the data entry restrictions which are applied when the data is entered.
The flow F00 (Opening Balances) must be informed in Read-only Flows, this way it will not be available for edition in the package.
Data entry restrictions SSCONSO.

The Operation tab defines the settings to publish the packages.
In the Deadline it has to be informed the date that the packages will have to be published.
It has to be changed each quarter, according to date defined in the SYENSQO Finance Accounting Closing Calendar available in the SYENSQO GAR AODOCs Library.

The Translation tab defines the object descriptions for the selected language.
Both French and English should be informed.

In the RU Organizer we define the companies to be reported in the category.
Select the IG and IP packages in the RU Organizer module from category ACTUAL2 / previous period and copy (through the icon
or Ctrl+C).

Change the period to the one that is being created and paste packages (through the icon
or Ctrl+V).

Then the reporting packages are created in RU Organizer module.
Note that the packages will have the status
, meaning that they are still not available in the Package Manager module.

Before Generate the packages to the Package Manager module, ensure that all the companies are with the correct Consolidation Method (column Entity Portfolio), and if any company needs either to be added or deleted |
Companies entering or leaving the SYENSQO Group are registered in the following file Syensqo Structure file available in SYENSQO GAR AODOC Library
To make the reporting available in the Package Manager module, select all packages and with the right click choose "Generate Package at Current Site".

The package status changes to
, meaning that the package are now available in the Package Manager module.

In order to facilitate the work from FSL CAM and TCM's, there are formulas in ACTUAL1-TAX category scenario to pre load Tax rates in schedule T1-1, flow F99, but keeping them editable ,as follow:
Pre-loading based on formula from ACTUAL1-TAX category Scenario

Content of T1-1 Schedule

To avoid double work in ACTUAL2 , there are formulas in ACTUAL2 category scenario to pre load from ACTUAL1-TAX Tax rates in schedule T1-1-ACTUA2, flow F99, without any possible modification, as follow:
Formula from ACTUAL2 category Scenario (example below for TXRDS heading, same applies for the other tax rates headings)

Content of T1-1-ACTUA2 Schedule (same layout as T1-1 schedule from ACTUAL1-TAX)
![]()
This control can not be performed through Excel retrieves as there is no way to generate a massive saving of ACTUAL1-TAX packages right after their generation in WD-9, and the same for ACTUAL2 packages generated in WD-2. Without the "Save" action, pre-loaded Tax rates can not be retrieved in Excel.
Thus, control will be performed through a direct check in packages on a representative company - 02002 Syensqo SA - considering that if the formula works for one company it works for all (no restriction or filter of companies in the settings of the Pre-loading formula):


Few days later (WD-2) after ACTUAL1-TAX package generation (done in WD-9), pre-loading of Tax Rates from ACTUAL1-TAX to ACTUAL2 packages (generated in WD-2) has to be checked as well.
![]()

Hard Close and Year End are managed under a single category ACTUAL2 and a single December period (yyyy.12).

Hard Close Tax packages need to be pre-filled with:



From the exported file a new file must be created by save as and named as 12.YYYY ACT2 HC import.csv.
In this new file we need to clean/change some data as follow:
The import file should also be saved in this folder selecting the folder of the year

Choose set of folders and controls applicable for HC Tax - refer to this document "BFC Admin Reporting set up per category and period"
Adapt the deadline for submission according to date defined in the Syensqo Finance Accounting Closing Calendar available in the SYENSQO GAR AODOCs Library

Select the reporting units from ACTUAL2 September (yyyy.09) excluding:
Copy through the icon
or Ctrl+C:

Paste through the icon
or Ctrl+V:

Note: Do not flag "delete first" in order to not delete the Tax rates preloaded by formulas.
Note: do not flag Run controls or Publication.


In order to ensure that the data imported is correct BFC Admin must run and refresh the following Excel/BFC retrieval file which is comparing P&L and Tax rates in both ACTUAL2 packages: 09 and 12 periods => expected results : data are equal between both periods
If there are companies entering the scope since the last time Excel file was updated, the following adjustments must be done in the Excel / BFC file:
If there are companies that entered the scope after September and thus contributing to the HC reporting (while having no data on September), the following adjustments must be done in the Excel / BFC file:
If there are companies that left the scope after September and thus not contributing to the HC reporting, the following adjustments must be done in the Excel / BFC file:
Companies entering or leaving the Solvay Group are registered in the following file Syensqo Structure file available in Syensqo GAR AODOC Library.
Link to the Excel/BFC retrieval file named "HC Opening check YYYY".xls stored in BFC Admin google folders selecting the folder of the year
Tax rates check (tabs YYYY.12 TXxx HC F99 / YYYY.12 TXxx HC F00 / YYYY.12 ETxx HC F99)

P&L check (tab P&L HC):

P&L investigations if P&L checks do not match (tab P&L Control per given heading):

Controls to be made consulting directly packages of the most significant companies:
Open the related packages and consult P&L L2018 and each tax schedule to check that:



There is a task created to manage planned runs of HC consolidation - ACT2-HC-SYEN - that needs to be updated.

Definition - needs to be changed for current year 12.YYYY HC

Task period of validity: period of runs to be validated with GAR Tax reporting manager


After last run of Hard Close (ACTUAL2 YYYY.12 variant 2) done by GAR Tax Reporting manager (expected to be between Dec 10th and 15th), BFC Admin team save the last run under a variant 1 and lock it.
Control in Excel/BFC retrieves that P&L Conso Group Net Result variant 1 = variant 2 - link to the file named "HC Tax back up variant 1 check.xls" located in BFC Admin google folders selecting the folder of the year


BFC Admin exports massively (without any restriction on accounts, flows, etc) all the reported packs under a flat file (csv or txt)
File exported should be named as Backup ACT2-YYYY.12-HC-export.txt and saved in the folder of the year

BFC Admin exports massively all the reported packs (filtered by R* Headings) under a flat file:
Notes
Open the file in csv format to confirm all is OK (no empty or broken lines).
File exported should be named as ACT2-YYYY.12-HC P&L export.csv and saved in the folder of the year


BFC Admin to save the 2nd massive Export under a new document “Import file” named ACT2-YYYY.12-HC P&L import.csv.
When opening the file into Excel (step after) and formatting text to columns do not forget to adjust the format of columns related to RU and ORU to TEXT to avoid to lose "0" in company codes (example 00001 becoming 1 without the "text" formatting)
Cleaning to be done:
Remove all lines with flow (D_FL column) F00 and C01 | Why ? -F00 is the opening generated by BFC - can not be imported |
Keep flow F99AJ even if it is expected to be rejected during import as calculated data | Why to keep ? to avoid too many deletion of lines |
Keep lines with partner (T1) S9999 , even if expected to be rejected during import as calculated data | Why to keep ? to avoid too many deletion of lines |
Keep lines with flow F99EX (even if some of them will be rejected during import as calculated by BFC) | Why to keep ? not easy to guess which ones to be kept or removed - safer to keep all |
Check that detailed analysis dimension such as SITES / PAYS / MARK / CGU/ T2 / YEAR…) are empty | |
Replace for all remaining lines amounts (P_AMOUNTS column) by 0 | This is the way to set the P&L to 0 and to erase the HC P&L |
Replace for all remaining lines comments (P_COMMENTS column) by empty cells | This is the way to erase the HC P&L comments |
Save and close the file. Warning: check that coding of companies kept with 5 digits (example: company SSA is coded “00001” and not transformed to “1” |


Packages need to be unlocked to allow the massive import.

Key points on Import options to be selected:
Download the Rejected data file and check that root cause if justified (calculated amounts, data not opened to import)
Expected rejected data are calculated data:

Objective of the check in Excel done on the full scope of companies but using PACK amounts:
Link to the file named "Tax reporting - Move Hard close to Year End YYYY.xls" located in this folder selecting the folder of the year
If there are companies entering the scope since the last time Excel file was updated, the following adjustment must be done in the Excel / BFC file:
Companies entering or leaving the Syensqo Group are registered in the following file Syensqo Structure file available in SYENSQO GAR AODOC Library.
1) Check on P&L (tab P&L F99 F99EX F99AJ):

2) P&L investigations if P&L checks do not match (tab P&L search on specific heading):

3) Check on Tax rates (tabs Tax rates F99 & Tax rates F00):

Controls to be made by opening the most significant companies:
Open the related package and consult each tax schedule to check that Hard close data and comments are still there / consult P&L schedule L2018 to check that no data and no comment
Example, T3-3 Current income tax:

P&L (schedule L2018):

In the following table (refer to this document "BFC Admin Reporting set up per category and period") are defined the Folders and Set of Controls to be used for each type of company in each Category and reporting period (monthly, Quarterly, Hard Close, Year-End):
Warning: Apply to central manual journal entries option MUST NOT be flagged

Adapt the deadline according to date defined for package publication in the Package Generation Planning file.
Regenerate all packages to get the application of the new folders / controls / deadline

In order to clean the data at conso level the packages that have just been cleaned with the mass import must be published.
Publication has to be done by special permission, in most cases, since packages are not valid (having blocking controls).
Note it could happen that some packages, if not having tax data and thus no blocking controls, are published with standard mode and thus become locked.


Once packages have been published, 12.YYYY conso SYENSQO / V2 needs to be run to clean data at conso level.

In order not to confuse end users, the package status must be changed from Published to Modified.
Packages have been published almost empty (only tax schedules have data) in order to clean up the data at conso level.
The status should now be set back to modified by reimporting the file imported in section 2.3.6.
Note : Before launching the reimport, check that all packages are unlocked and proceed packages unlockings if needed (case to happen on packages published by Standard mode in step 2.3.9)

Key points on Import options to be selected:
Check that all packages appear with modified status .
If some packages still appear as Integrated" then workaround to be applied


Adapt set of Folders and controls (refer to this document "BFC Admin Reporting set up per category and period") of Equity Methods (different from IG and IP companies) to Year End profile . Exception for company 66263 Hindustan Gum.

Check also the list of IG / IP / MEQ versus November ACTUAL2 reporting one (in case companies have entered in the scope in November, after the launch of HC Tax).
Companies entering or leaving the Syensqo Group are registered in the following file SYENSQO Structure.
If a company leave the YYYY.12 scope:
Check that package status is:
Open the following packages (without any action or saving inside !) to check that F00 there in L7010 / Year end schedules there / P&L schedule L2018 with 0 data / Tax schedules still with data (IG and IP used during Hard close):

L7010/F00:
Year end schedules:



END OF THIS PROCEDURE