1. Enter the Title of the operation / page2. Add the following Labels :
3. Fill in all fields as described above4. Name the title of each section using OPD methodology naming convention - Infinitive verb without the “to”, mainly action verb...something) - " I do something..."5. Once the description of the operation is completed, ensure it is approved and published by launching the SBS-Finance approval workflow |
| Domain: Treasury Reporting |
Responsibility area: Supervise the closing activities D+2 |
WHY - Describe the objective of the operation
The IFG control allows the users to have an overall reconciliation between: Official databases, BFC and the several accounting files. It will be a comprehensive details of all flows reported.
Detail the scope (legal entities, etc.)
This procedure applies to Solvay Energy Services (Company code 3865)
Definitions should be added in the Finance Glossary - Add definition and link it to respective Letter in Finance Glossary
See Finance Glossary:
WHAT and HOW - Main content of the operation
The content should be mainly organized in 2 levels of Headings to ensure a proper link with the Table of Contents.
Select the level of heading in the "Paragraph" option.
You may copy the previous file and save it on the current drive \\NOHVFS01\Treasury-GAR\SES\YYYY\MM
Example from July 2020 closing:
![]()
The file has 9 components/tabs:

Throughout the tabs we will analyse:
All flows posted in SAP through our accounting files (Energy & CO2) and uploaded in BFC
The position end of month of our financial instruments accounts
The monthly variations of our financial instruments accounts
From the official CO2 file received
you need to copy and update the data in the tab. Pay attention to the columns and adapt your official table if necessary (example: we usually add a column "Year" for the maturity dates). You also need to make sure that the formulas from column "BX" (Origin/Transfer) - "CC" (Marché) are applied in all lines.
If for some reason you had discrepancies identified on procedure I control DWISE CO2 related to deal types vs markets, this is where you might have some reconciliation issues. This report should always respect the information coming from official databases and we need to highlight the differences and provide an explanation. This is why it´s so important to have beforehand a check in order to have the necessary justifications and actions. If you look at column "CC" we are identifying what is related to OtC and Exchange.
From the official CO2 file received
you need to copy and update the data in the tab. Pay attention to the columns and adapt your official table if necessary (example: we usually add a column "Year" for the maturity dates). You also need to make sure that the formulas from column "BX" (Origin/Transfer) - "CC" (Marché) are applied in all lines.
If for some reason you had discrepancies identified on procedure I control DWISE CO2 related to deal types vs markets, this is where you might have some reconciliation issues. This report should always respect the information coming from official databases and we need to highlight the differences and provide an explanation. This is why it´s so important to have beforehand a check in order to have the necessary justifications and actions. If you look at column "CC" we are identifying what is related to OtC and Exchange and we might have a deal type associated to the wrong market.
From the Newedge report
copy and update the table in cell A3.
3.4. I update TMS F99 & F15 tabs
To be updated
![]()
On the right side of the table you have the following cells to update:
S12 & T12

Where S12=F99 of reserve policy energy and T12=F00 of reverse policy energy (January task)
S35 & T35

Where S35=F99 of provision risque volume and T35=F00 of provision risque volume (January task)
S57 & T57

Where S57=F99 of reserve policy CO2 and T57=F00 of reserve policy CO2 (January task)
Cells I57 & I63
These formulas you have a criteria based on the current year. In January we need to update the year:

Cells I59 & I65
The F15 is the notional amount coming from the trading of options. Information can be retrieved from "Analysis CO2" tab:

It´s important that this control is zero throughout the lines. It makes the difference between the information from the database with the F99 information:

Basically we make sure that the split is ok.
This section:

For the F99 please take a print screen from FS10N with the following accounts:
Instead of waiting for BFC information to cross check this section our suggestion is you check this summary table with chapter 3.3 of procedure I control the consistency SAP vs MtM Files
Update pivot tables
Update the following pivot tables with M-1 & M information from Official CO2 databases:

Update the MtM amounts for options (amounts booked with CO2 pivot):

Align the formulas (if necessary) on the following table respecting the maturity dates and commodity:

It´s also relevant to say that on the column with "Mtm new deals" we need to update the dates inside the formulas:

The date is from M-1.
The result that we see in the end:
![]()
Should also match with the month variation from SAP (Gl accounts 55100100 and 57000100):

The other part of the control os to reconcile the month variation coming from energy:

Where NRJ = energy and should be equal to SAP:

In this month I have a delta of 15keur not justified from the CO2 activity.
Update the periods accordingly:

Where the first column is the F99 from last year (which is equal to F00 of the current year).
The second column should updated monthly
We should also check cells V15, V34 and V48 to see if the controls are equal to zero.
Update the periods accordingly:

The figures for M-1 need to be updated every month with M-1 data:
![]()
![]()
The figures on M are directly updated by "Synthèse Flux" tab
We also make sure that the controls are zero on cells V15, V34 and V48
This tab allows us to control if we information in BFC matches with reporting.
First update the period
![]()
Afterwards perform a BFC retrieve
![]()
Finally all controls should be equal to OK:
