SAP S/4HANA Cloud offers two methods for generating a Cash Flow Statement using the Indirect Method. The first — the Semantic Tags approach — has been available since early S/4HANA Cloud releases and relies on assigning predefined tags to Financial Statement Version (FSV) nodes. The second — the Reporting Rules approach — is the strategic replacement, introduced to address the limitations of the tag-based model and to align with the requirements of IFRS 18.
Both approaches ultimately display a cash flow statement, but they differ fundamentally in how they select, structure, and maintain the underlying data. This document details those differences dimension by dimension.
Process Architecture: Side by Side
|
Legacy: Semantic Tags |
New: Reporting Rules |
|
1. Define Financial Statement Version (FSV) 2. Assign Semantic Tags to FSV nodes / G/L accounts 3. Cash Flow Statement — Indirect Method 4. Custom Analytical Queries (optional, for customization) |
1. Manage Reporting Rules (F9259) — define reporting logic 2. Manage Global Hierarchies (F2918) — build hierarchy 3. Financial Statements Review Booklet (F8587) — display & analyze |
The table below compares both approaches across 12 key dimensions. Green cells indicate an advantage held by the Reporting Rules approach.
|
Dimension |
Semantic Tags (Legacy) |
Reporting Rules (New) |
|
Configuration Approach |
Tag-based: assign semantic tags to FSV hierarchy nodes or individual G/L accounts. Tags are predefined by SAP. |
Rule-based: define granular selection criteria (account range, debit/credit, transaction type, dimensions) per cash flow line item. |
|
Granularity of Data Selection |
FSV-node level. All accounts under a tagged node are included — no sub-filtering possible. |
Account range + business transaction type + financial transaction type + profit center / segment / business area / cost center. Full control over what is included. |
|
IFRS 18 Readiness |
Not supported. SAP explicitly recommends migrating away from Semantic Tags to support IFRS 18. |
Built-in IFRS 18-aligned hierarchy template. Ready for the 2027 effective date with no rework. |
|
Business User Ownership |
Requires Key User or developer to restructure FSV and re-assign tags when accounts change. |
Finance team can create, edit, and maintain reporting rules independently via Fiori — no IT ticket needed. |
|
Custom Dimension Filtering |
Not available in standard. Requires Custom Analytical Queries for any custom logic or dimensions. |
Extension Fields natively supported in reporting rules — expose custom journal entry fields as filter criteria. |
|
Reporting Hierarchy Structure |
Re-uses the Financial Statement Version (FSV) — same structure as balance sheet/P&L. Cash flow layout is constrained. |
Dedicated cash flow hierarchy, independent of the FSV. Structure is freely defined/owned by customers by matching IFRS 18 categories exactly. |
|
Drill-Down Capability |
Cash Flow Statement – Indirect Method app provides tag-level data. Limited drill-through to journals. |
Financial Statements Review Booklet (F8587) delivers full drill-down from any item to multiple objects such as Trading Partner, G/L account, Journal Entry etc. |
|
Display App |
Cash Flow Statement – Indirect Method (standalone app). |
Financial Statements Review Booklet (F8587) — unified with Balance Sheet, P&L, Trial Balance, and Statement of Changes. |
|
Customization Path |
Custom Analytical Queries required for non-standard layouts or custom semantic tags. |
Extension Fields in Manage Reporting Rules (F9259) handle most customization without custom queries. |
|
Setup Complexity |
Moderate: configure FSV, then assign tags to nodes/accounts — but locked to predefined tag types. |
Lower initial setup (rules + hierarchy), and far more flexible and future-proof. |
|
SAP Roadmap Alignment |
No further development planned. SAP recommends migration. |
Strategic solution — actively developed and aligned with IFRS 18, cloud-first roadmap. |
The following sections explain the most significant advantages in practical terms.
|
1 |
IFRS 18 Compliance — Built In, Not Bolted On Why it matters: IFRS 18 takes effect for annual periods beginning on or after 1 January 2027. • Reporting Rules ships with an IFRS 18-aligned hierarchy template covering the mandatory categories: Operating, Investing, Financing, Integral Associates & JVs, and the reconciliation to opening/closing cash. • The Semantic Tags approach was designed before IFRS 18 and has no built-in template for the new structure. Migration is required regardless of whether the customer changes the reporting surface. • With Reporting Rules, organizations can adapt their cash flow classification for IFRS 18 by updating rules in Fiori — no developer involvement, no transport needed. |
|
2 |
Granular, Multiple-Level Selection Criteria Why it matters: Not every G/L account under an FSV node belongs in the same cash flow category. • With Semantic Tags, all accounts under a tagged FSV node are included — there is no way to include only a subset of accounts or filter by debit/credit within that node without restructuring the FSV. • Reporting Rules let you define account ranges (From / To), account hierarchy node, Financial transaction type, and additional dimensions — all within a single rule, without touching the account master data. • This is critical for scenarios like separating cash payments to suppliers from non-cash provisions that share the same G/L account structure. |
|
3 |
Finance Team Owns the Configuration Why it matters: Every IT-dependent change slows down period-end close and increases cost. • Semantic Tags are predefined by SAP. Adding new tags or creating custom calculation logic requires Custom Analytical Queries — a developer-level task. • Reporting Rules are created and maintained entirely within Fiori app F9259 by a finance user with Key User or GL Accountant role. Adding a new cash flow line item, adjusting an account range, or modifying a sign takes minutes. • Extension Fields in Manage Reporting Rules additionally allow custom journal entry fields (e.g., project, fund, grant) to become filter criteria — again without ABAP development. |
|
4 |
Dedicated Cash Flow Hierarchy — Decoupled from FSV Why it matters: FSV restructuring for balance sheet or P&L purposes should not break the cash flow statement. • The Semantic Tags approach attaches to the FSV. If the FSV is restructured — for example, to comply with a new country-specific balance sheet format — the tag assignments may need to be reviewed and corrected for the cash flow statement. • The Reporting Rules hierarchy is completely independent of the FSV. It lives in Manage Global Hierarchies (F2918) as a separate object of type Reporting Rules Hierarchy. • This structural independence eliminates an entire class of configuration errors during FSV maintenance cycles. |
|
5 |
Unified Reporting Experience in the Financial Statements Review Booklet Why it matters: Finance teams should not need to switch between multiple apps for different statements. • The Semantic Tags approach renders the cash flow in a dedicated standalone app: Cash Flow Statement — Indirect Method. • The Reporting Rules approach renders the cash flow inside the Financial Statements Review Booklet (F8587) — the same app used for Balance Sheet, P&L, Trial Balance, and Statement of Changes. • Users get a single navigation experience across all financial statements, consistent filter behavior, shared comparison period controls, and unified PDF/Excel export. |
If you are currently running the Semantic Tags approach, the question is not whether to migrate — SAP has already stated the recommendation clearly. The question is when and how to sequence the transition.
Migrate immediately if any of the following apply:
- Your organization is preparing for IFRS 18 adoption (mandatory by 2027 for most groups).
- You are adding new company codes or restructuring your chart of accounts.
- Your finance team currently raises IT tickets for cash flow line item changes.
- You need multiple level filtering that the FSV node structure cannot provide.
|
Migration Path: From Semantic Tags to Reporting Rules Migrating does not require deleting or restructuring your existing FSV. The two approaches can coexist temporarily during transition. A recommended migration sequence: 1. Step 1 — Analyze your existing FSV and semantic tag assignments to identify which G/L accounts map to each cash flow category. 2. Step 2 — Create equivalent reporting rules in Manage Reporting Rules (F9259), replicating each line item with explicit G/L account ranges. 3. Step 3 — Build the new reporting hierarchy in Manage Global Hierarchies (F2918) using the IFRS 18 template. 4. Step 4 — Run both statements in parallel for one period to validate figures. 5. Step 5 — Switch to the Financial Statements Review Booklet (F8587) as the primary reporting surface. |
The Cash Flow Statement Based on Reporting Rules is not merely an incremental improvement over the Semantic Tags approach. It is a fundamentally different configuration model that gives finance teams direct ownership of cash flow data, removes the dependency on FSV structure, enables parallel ledger reporting, and provides a migration path to IFRS 18 — all without writing a line of code.
For any organization planning to stay on SAP S/4HANA Cloud beyond 2026, migrating from Semantic Tags to Reporting Rules is the recommended and strategically correct path.
