Financial statement versions

G/L accounts hold balances. A balance sheet and income statement need those balances arranged into lines: current assets, inventories, trade payables, revenue, cost of sales, operating expenses. The financial statement version (FSV) is the hierarchy that does that arranging. Each G/L account is assigned to a node, nodes roll up into higher nodes, and reports read the hierarchy to present the statements.

Nodes the system creates

When you create an FSV, the system provides special items that every version needs: assets, liabilities and equity, net result (profit and loss), a profit and loss result node, a not assigned item and a notes item. Accounts with balances that are not assigned to any node show up under "not assigned" in financial statement reports. In a well-maintained version that node is always empty.

Debit and credit shift

Some accounts belong on different sides depending on their balance. A bank account with an overdraft is a liability, not a negative asset. An FSV can assign such an account to both a debit node and a credit node, and the report shows it on whichever side its balance falls. Testers should check these accounts with both positive and negative balances.

Maintaining FSVs

In SAP S/4HANA, SAP recommends the Fiori app Manage Global Hierarchies (available since SAP S/4HANA 1809) for creating and maintaining financial statement versions used in Fiori reporting. The classic customizing transaction OB58 still exists for classic versions; to use a classic version in Fiori reports it must be imported or replicated, and classic reports may not read versions maintained only in Manage Global Hierarchies. Know which tool owns each version before you change it.

Testing a financial statement version

FSVs change more often than people expect: new accounts, a reorganized cost of sales line, a new disclosure requirement. Each change deserves a short test, because an error does not stop any posting. It only makes the statements wrong.

• Run the balance sheet and P&L for a closed period before and after the change; totals must match unless the change was meant to move amounts between lines.
• Confirm "not assigned" is empty for all company codes using the version.
• Check accounts with debit and credit shift with both positive and negative balances.
• Confirm the net result in the P&L equals the result shown in the balance sheet.
• If several versions exist (for example a statutory and a management version), test each one the change touches.

Ownership matters too. At Contoso, the FSV used for external reporting is owned by Dan, and only the finance master data team may change it, with his approval. Management views can be maintained more freely, but never by changing the external version.

A practical point: copying an existing account in the master data app does not necessarily copy its FSV assignment. SAP has documented cases where the assignment had to be added separately, so always check the hierarchy after creating accounts by copy or upload.