SAP Finance Blog #2

Summary

This blog explains the foundational principles of organizational structure and process integration within SAP S/4 HANA’s financial accounting framework. The central theme revolves around the transformative impact of the Universal Journal. It unifies Financial Accounting (FI) and Management Accounting (CO) into a single, cohesive data model. This architectural shift establishes a “single source of truth.” It eliminates the need for traditional reconciliation between internal and external accounting. This change makes data available in real-time at the document level.

The core business processes Order-to-Cash, Purchase-to-Pay, Acquire-to-Retire, and Record-to-Report, are deeply integrated with accounting. This means transactions from upstream operational steps directly impact financial records. The quality of this data is crucial. Its completeness is paramount. Accounting often functions as a “repair shop for badly set up processes.”

The system’s organizational structure is defined by elements like the Client, Company, and Company Code. These elements form a critical foundation. This foundation is largely immutable. The Company Code stands as the central organizational unit for financial accounting, to which every posting must be assigned. Management-oriented structures such as the Controlling Area and Profit Center enable analysis across legal entity boundaries. New capabilities provide significant advantages. They include Extension Ledgers for delta-based reporting and real-time intercompany management postings. These capabilities significantly streamline closing activities. They enhance reporting flexibility. A successful implementation requires close coordination across all business functions. It is essential to ensure the system setup correctly maps processes to the general ledger.

1. Core Business Processes in Financial Accounting

Financial accounting is intrinsically linked to a company’s entire value chain, which consists of design, build, sell, and support phases. Accounting is a support process. It also yields a critical result. Reports provide information on business performance. Most accounting bookings now come from upstream process steps. This makes accounting highly dependent on the quality of incoming information.

SAP differentiates several core processes that have significant touchpoints with financial accounting.

Process Name	Description	Primary Accounting Area
Order-to-Cash	Encompasses all steps from initial customer contact and presales activities to the final collection of cash. Described as the “lifeline of a company.”	Accounts Receivable
Purchase-to-Pay	Covers the procurement cycle from supplier selection and requisitions to outgoing payments. Crucial for profitability and internal controls.	Accounts Payable
Acquire-to-Retire	Manages the entire lifecycle of a company’s fixed assets, from initial capital expenditure requests to eventual disposal.	Asset Management
Record-to-Report	The central accounting process, responsible for documenting all business transactions and providing reliable financial reports.	General Ledger

Other key processes with accounting connections include:

• Build-to-Stock: The production process, connected to the material ledger.
• Hire-to-Retire: Human resources processes with touch points in payroll accounting.
• Idea-to-Market: The innovation process, linked to project accounting and intangible assets.
• Plan-to-Perform: The financial planning process, where accounting data serves as a starting point and a basis for comparison.

2. Foundational Organizational Structure

The organizational elements in SAP S/4 HANA are fundamental specifications. They must be carefully considered during implementation. These elements have enormous consequences for operational processes. Additionally, they are difficult to change later.

2.1 Hierarchy of Organizational Elements

These structures map the legal, business, and management dimensions of the enterprise within the system.

Element	Level / Purpose	Key Details
Client	Highest	The technical framework of the system. Ideally, a single client should map an entire corporate group. This approach offers advantages in master data management. It also benefits process design and consolidation.
Company	Legal Entity	Intended for a legal entity for which a balance sheet must be created. It serves as the consolidation element and is also referred to as the “trading partner” in reports.
Company Code	Central FI Unit	The central organizational element of financial accounting. It represents a closed accounting system for which a balance sheet and income statement can be generated. Every financial posting must be assigned to a company code. All company codes within a single Company must use the same chart of accounts and fiscal year.
Controlling Area	Management Accounting	An organizational unit for management accounting purposes that can include one or more company codes. It structures the business from a management standpoint, independent of legal boundaries, and allows for cross-company management accounting.
Profit Center	Management-Oriented Control Unit	Structures the enterprise in a management-oriented way, independent of legal forms. It is used to generate P&L results. It can also report balance sheet figures. This supports control concepts like Return on Capital Employed (ROCE).
Segment	External Reporting	Used for segment reporting according to IFRS and US GAAP, structuring the company into business segments (e.g., by region or activity). The segment is derived from the profit center during posting.
Functional Area	Cost Classification	Classifies expenses according to functions (e.g., Administration, Cost of Sales) to enable cost-of-sales accounting.
Credit Control Area	Credit Management	An organizational unit that specifies and checks customer credit limits. A single credit control area can be assigned to multiple company codes for centralized credit management.

2.2 Cross-Application Assignments

Financial accounting is connected to structural elements in other modules through specific assignments, ensuring data integrity across the system.

• Plant to Company Code: A plant is a logistics unit for manufacturing or service provision. It is assigned to a single company code. Inventory valuation is typically defined at the plant level.
• Purchasing Organization to Company Code: A purchasing organization can be centralized. It is then assigned to multiple company codes. Alternatively, it can be decentralized. It would then be assigned to a single company code.
• Sales Organization to Company Code: A sales organization is assigned to exactly one company code.
• Personnel Area to Company Code: A personnel area (an HR unit) is assigned to one company code.

3. Central Financial Accounting Settings

These system settings are foundational decisions that define how financial data is managed and reported. They are made during implementation and cannot be easily altered.

• Ledgers: SAP S/4 HANA supports multiple parallel general ledgers to accommodate different accounting principles (e.g., local GAAP, IFRS). You must designate one ledger as the leading ledger (0L in the standard system). It serves as the primary source for group reporting.
• Extension Ledgers: This new ledger type sits on top of a standard (underlying) ledger and stores only delta entries. This avoids data redundancy. It is used for specific purposes. Examples include posting IFRS valuation adjustments on top of a local GAAP ledger, tax-specific valuations, or management accounting delta values.
• Accounting Principles: These control valuation rules for various applications like foreign currency valuation and asset depreciation. They are defined in the system and assigned to ledger groups.
• Currencies: In addition to the transaction currency, every journal entry persists amounts in the local currency. This is also known as the company code currency. It also persists amounts in the group currency by default. The system allows for up to eight freely defined additional parallel currencies.
• Fiscal Year Variants: This setting defines the number of posting periods and special periods in a fiscal year. It can be configured to match the calendar year or to be shifted (e.g., starting in July).

4. The Unification of Financial and Management Accounting

The integration of FI and CO via the Universal Journal is a cornerstone of the SAP S/4 HANA architecture. This eliminates the previous “two-circuit system,” creating a single database for all financial postings and rendering reconciliation efforts obsolete.

4.1 The Universal Journal: A Single Source of Truth

The Universal Journal is a single table that contains all relevant financial data from both FI and CO. This architecture ensures that internal and external reporting are continuously reconciled at the document level. As stated in the source, “The single point of truth thus becomes the single source of truth.”

4.2 Management Accounting Postings in the General Ledger

Business transactions that were previously confined to the CO module now post directly as documents in the general ledger. These include:

• Activity allocations (e.g., time sheet entries)
• Cost center allocations
• Overhead surcharges
• Cost object settlements

These postings typically use the same P&L general ledger account for both the debit and credit lines. This usage results in a zero balance on the account itself. However, they transfer value between different cost objects (e.g., from a cost center to a project) and enrich the journal entry with characteristics like Profit Center, Segment, and Functional Area, which directly impacts financial reporting.

4.3 Market Segment Reporting in the Universal Journal

When account-based Profitability Analysis (CO-PA) is activated, the Universal Journal is enhanced with market segment attributes. This means that fields like Customer, Product, Sales Organization, and Industry are stored directly in the general ledger line items. This allows for detailed margin analysis directly from financial data without needing a separate module. This represents a significant change for organizations migrating from SAP ERP, which predominantly used costing-based CO-PA.

4.4 Intercompany Management Accounting Postings

SAP S/4 HANA introduces a new posting logic for cross-company code management accounting transactions, enabling real-time clearing and reconciliation. When a transaction occurs between two company codes (e.g., an employee in Company A records time on a project in Company B), the system automatically generates two balanced journal entries—one in each company code. These documents include offsetting line items posted to intercompany clearing accounts. They are populated with the respective trading partner ID. This simplifies group consolidation and makes the old reconciliation ledger obsolete.

• Amazon
• LinkedIn

• LinkedIn
• Facebook
• Mail
• Reddit
• WhatsApp
• Telegram
• Print
• ShareCopied to clipboard