You are on page 1of 17

SAP S4 Hana Finance

SAP FI - Financial Statement Version


SAP FI - Financial Statement Ver sion
Mickael Quesnot ©

General Ledger accounts can be used as per legal regulations to generate the final statements.
Financial statement versions are used to create the financial statements, to run account
balance reports and for General Ledger accounting planning.
You can also define multiple financial statement versions to generate financial statements in
different formats. Follow the steps given below to create financial statement versions −
Financial Statement Version (FSV)

Definition
A financial statement version (FSV) is a hierarchical arrangement of G/L accounts.

The accounts can be arranged in accordance with the legal regulations used to generate your
financial statements. Alternatively, you can arrange the accounts in accordance with your
requirements.

Use
You need an FSV for the following purposes:

▪ To generate financial statements

▪ To create various reports that are structured lists of account balances, such as Trial
Balance

▪ As a basis for planning in General Ledger Accounting, for example, by using Balance
Sheet/Income Statement.

You can define different FSVs for various needs, for example:

▪ For different organizational units, such as corporate group or company code.

▪ For different levels of detail of your financial statements. For your accounting
department, for example, you want to list the individual accounts with their respective
balances. For senior management, you might want to summarize this information to
create one set of financial statements for the whole group.

Attributes
When creating an FSV, you need to set the following attributes at header level:
▪ An FSV ID and description

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

1|P a g e
Mickael Quesnot ©

▪ Chart of Accounts: Only accounts from your specified chart of accounts can be assigned
when you are defining the FSV.

▪ Valid From and Valid To: The FSV can only be applied in reports if the report period is
within your specified timeframe.

Note

Due to time dependency of FSVs, you can create multiple FSV hierarchy versions under
the same FSV ID, as long as their timeframes don't overlap. These hierarchy versions are
represented by timeframes on the app UI. They share the same FSV header attributes,
but can have completely different hierarchy structures.

▪ Allow Contra Nodes: You can assign a hierarchy node (A) as a contra node to another
node (B). Both nodes contain the same group of accounts. Depending on whether the
total balance of the accounts is in credit or in debit, the accounts display under node A
or node B in financial statements. For more information, see Balance-Dependent
Account Display.

Note

Bank account grouping is also made possible with this setting. For more information,
see Bank Account Grouping.

▪ Allow Functional Areas: This makes it possible to assign functional areas (in addition to
G/L accounts) to individual nodes of the FSV. This makes it possible to create P&L
statements in accordance with cost of sales accounting.

▪ Basic FSV structure: When creating an FSV, the following structure is automatically
generated:

▪ Assets

▪ Liabilities and Equity

▪ Net Result: Loss

▪ Net Result: Profit

▪ P&L Result

▪ Financial Statement Notes

▪ Not Assigned
Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

2|P a g e
Mickael Quesnot ©

These nodes are also referred to as "special nodes" or "special FS items". For more information,
see Special Nodes.

Defining FSVs
SAP delivers sample FSVs, which you can copy to create your own versions.

To create or change your FSVs, use the Manage Global Hierarchies app. For more information,
see Define Financial Statement Versions in Global Hierarchies.
Note
The Manage Financial Statement Versions app can also be used for maintaining FSVs, but with
limited features. The FSVs created in this app are independent of those created using Manage
Global Hierarchies. We recommend that you use the latter to create new FSVs. For the FSVs
created with Manage Financial Statement Versions, you can migrate them to global hierarchies
by using the Migrate FSVs to Global Hierarchies app.

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

3|P a g e
Mickael Quesnot ©

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

4|P a g e
Mickael Quesnot ©

Click the button New Entries as shown below −

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

5|P a g e
Mickael Quesnot ©

Provide the following details −


• Enter the Fin. Stmt. Version.
• Enter the Description of the financial statement version.
• Maint. Language − Enter the language key in which you display texts, enter texts,
and print statement.
• Item Keys auto − It tells keys of financial statement items are assigned manually
or automatically when the financial statement versions are defined.
• Charts of Accounts − All accounts from this chart of accounts COA can be
assigned when you define the financial statement. If you do not specify a chart
of accounts, accounts from several charts of accounts can be assigned when you
define the financial statement.
• Group Account Number − Enter this Indicator that specifies that the group
account numbers should be assigned instead of the account numbers when you
define the financial statement version.
• Fun. Area Parameter − This indicator is used to make it possible to assign
functional areas or accounts in the financial statement version. Once the above
fields are defined, you can click on the save configuration and to generate
change request number. To edit this Financial Statement version, click on Fin.
Statement items → you can maintain nodes in version.

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

6|P a g e
Mickael Quesnot ©

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

7|P a g e
Mickael Quesnot ©

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

8|P a g e
Mickael Quesnot ©

Step 7) After the Financial Statement Version is saved you can edit its
structure items by selecting financial statement items button

Step 8) In the next screen, you can maintain nodes in version object A
new version has seven basic nodes by default, listed below

1. Financial Statement Notes


2. Not Assigned
3. P+L result
4. Net result : loss
5. Net result : profit
6. Liabilities+Equity
7. Assets

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

9|P a g e
Mickael Quesnot ©

We can maintain node text by double clicking on the node . We can


create subitems to the node by selecting the node and pressing the
create items button New item will be created as subnode to

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

10 | P a g e
Mickael Quesnot ©

the selected node. We can assign accounts or group of Accounts to a


node by selecting the node and pressing Assign Accounts .

Below is an example of such an assignment.

1. Primary Node “Assets”


2. Subnode “Cash & Cash Equivalents” are assigned to Assets .” Petty
cash” is a subnode assigned to Cash & Cash equivalents.Other
nodes are also assigned to Cash & Cash Equivalents such as :
Checking,Citibank Account, Mellon Bank,Citibank Canada
3. Chart of Account key used for assigning accounts
4. Range of accounts assigned to node Petty Cash
5. Range of Accounts

Step 9) After Maintaining the structure press Save and we have


successfully created a Financial Statement Version.

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

11 | P a g e
Mickael Quesnot ©

DEMO ASSIGN ACCOUNTS

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

12 | P a g e
Mickael Quesnot ©

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

13 | P a g e
Mickael Quesnot ©

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

14 | P a g e
Mickael Quesnot ©

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

15 | P a g e
Mickael Quesnot ©

Mickaël QUESNOT ©

https://www.linkedin.com/in/mickaelquesnot/

16 | P a g e

You might also like