2.1 Defining the Organizational Structure

The single most important phase of an FI implementation is the correct definition of the enterprise structure. These decisions are foundational and extremely difficult to change post-go-live, impacting legal consolidation, segment reporting, and internal controls for years to come. This structure establishes the legal and organizational framework upon which all subsequent financial transactions are posted and all reporting is based. It models the company’s legal and business entities, ensuring that financial data is segregated and reported according to both legal requirements and internal management needs.

Company and Company Code

• Company: In SAP, a ‘Company’ is the smallest organizational unit for which financial statements can be created in accordance with commercial legal regulations. It can represent a consolidated group of companies, and all company codes within a single company must use the same Chart of Accounts and fiscal year.
• Company Code: The ‘Company Code’ is the smallest organizational unit for which a complete, self-contained set of accounts can be drawn up for external reporting purposes. This includes generating essential financial statements like the balance sheet and the profit and loss (P&L) statement. From a legal standpoint, the Company Code is the most significant entity in FI.

Business and Functional Areas

• Business Area: A ‘Business Area’ is an organizational unit used to differentiate transactions originating from different lines of business or segments within a company. For example, a corporation might define separate business areas for its manufacturing, marketing, and sales divisions. This allows for the creation of internal financial statements for these specific segments, providing valuable insight for management.
• Functional Area: In contrast, a ‘Functional Area’ is used to classify expenses according to the specific functions they serve, such as Manufacturing, Sales and Distribution, or Administration. This structure is essential for implementing Cost of Sales Accounting, a method of reporting that provides a different view of profitability compared to the standard period cost method.

This organizational framework is complemented by a set of global settings that standardize financial processes and ensure consistency across the entire enterprise.

2.2 Core Financial Configuration

Global settings play a critical role in ensuring consistency, compliance, and control over financial accounting processes. These configurations establish the fundamental rules that govern how documents are posted, how fiscal periods are managed, and how data is entered into the system, creating a standardized environment for all financial transactions. Mistakes in this area can lead to significant rework and reporting issues down the line.

• Chart of Accounts (COA) The Chart of Accounts is a structured list of all G/L accounts used by an organization. SAP supports three types of COA:
  • Operating COA: Contains the G/L accounts used for daily postings in a specific company code. It is mandatory and must be assigned to each company code.
  • Country COA: Contains the G/L accounts required to meet a specific country’s legal reporting requirements.
  • Group COA: Contains the G/L accounts used by the entire corporate group, facilitating consolidated reporting.
  • Consultant’s Note: While SAP allows for flexibility, it is a global best practice for all company codes within a consolidated group to use the same Operating Chart of Accounts (leveraging the Group COA) to ensure streamlined reporting and consistent data governance.
• Fiscal Year Variant This setting defines the posting periods for a company code. It specifies the number of standard posting periods (typically 12 for each calendar month) and the number of special periods (up to four) used for year-end closing adjustments. A fiscal year can be the same as the calendar year or defined differently (e.g., April to March).
• Posting Period Variant The Posting Period Variant is a critical control mechanism that determines which accounting periods are open for transaction posting. This prevents accidental postings to closed periods, ensuring the integrity of financial data for a given month or year. Variants are created and then assigned to company codes to manage their posting periods.
• Field Status Variant & Group These settings provide granular control over the data fields on transaction entry screens. The Posting Period Variant provides high-level control over when postings can occur, while the Field Status Variant and Group provide control over what data is mandatory during that entry.
  • The Field Status Variant is a container assigned to a company code that holds multiple Field Status Groups.
  • The Field Status Group is assigned to a G/L account master record and determines the status of each field for postings to that account. Fields can have one of four statuses:
    • Suppress: The field is hidden.
    • Optional: The field is visible, and entry is optional.
    • Require: The field is visible, and entry is mandatory.
    • Display: The field is visible but cannot be edited.
• Document Type & Number Ranges Document Types are used to classify different business transactions (e.g., customer invoice, vendor payment) and control key aspects of the document posting process. They determine the Number Range from which the document number is assigned and specify which account types (e.g., Customer, Vendor, G/L) are permitted for posting.
• Posting Keys A Posting Key is a two-digit numerical key that controls the entry of document line items. It determines three crucial things: the account type (A=Assets, D=Customers, K=Vendors, M=Materials, S=G/L Account), whether the posting is a Debit or a Credit, and the field status of the transaction screen.

With this foundational structure and configuration in place, the focus can now shift to the central component of financial accounting: the General Ledger.