FICO General Ledger Part 1: Foundations — Company Code, Chart of Accounts and GL Master Data
The general ledger is the backbone of SAP Finance: every financial posting ends here. Learn the organizational elements (company code, chart of accounts, fiscal year variant, ledger), how GL accounts are built in three layers, and the global settings that control every posting — with the exact configuration path for each.
What this complete series covers
Standalone reference lessons on General Ledger in the FI / FICO track.
- Who it is for
- Best for SAP consultants, developers, and learners who want a practical understanding of General Ledger.
- Prerequisites
- Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
- Final outcome
- By the end, you should be able to use these lessons as a quick working reference for General Ledger and know where to look when a related issue appears.
- Part 1: FICO General Ledger Part 1: Foundations — Company Code, Chart of Accounts and GL Master Data
An orientation lesson explaining why the General Ledger exists, how organizational elements (company code, chart of accounts, ledgers) and G/L account master data fit together, and
- Part 2: FICO General Ledger Part 2: Posting Flow, Integration and the Universal Journal
Explains how postings flow into the General Ledger from sub-ledgers and other modules, the configuration elements that drive that flow, and how S/4HANA's Universal Journal changes
System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.
Explanation
📌 KEY POINTS
✅ The company code is the legal entity for which a complete set of books (balance sheet and P&L) is produced.
✅ A chart of accounts lists GL accounts; one chart can serve many company codes for consistent reporting.
✅ GL accounts have a chart-of-accounts part (name, type, group) and a company-code part (currency, open item, field status).
✅ Fiscal year variant and posting period variant decide when you can post.
⚠️ In S/4HANA cost elements are GL accounts — the account type (balance sheet, nonoperating, primary or secondary cost) is chosen at creation and matters for CO.
━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Foundations — organization, chart of accounts, master data
Part 2: Posting flow, integration and the universal journal
━━━━━━━━━━━━━━━━━━━━
▶ 1. COMPANY CODE AND LEDGER
- Company code = legal entity with its own currency and financial statements.
- Leading ledger 0L holds the main accounting principle; other ledgers for parallel valuation.
━━━━━━━━━━━━━━━━━━━━
▶ 2. CHART OF ACCOUNTS
- Operational chart used for daily postings; optional group and country charts.
- Assignment company code → chart of accounts.
━━━━━━━━━━━━━━━━━━━━
▶ 3. GL ACCOUNT MASTER DATA
- Chart level: account number, type, account group, texts.
- Company code level: currency, tax category, open item / line item display, sort key, field status group.
- Account groups control number ranges and screen fields.
━━━━━━━━━━━━━━━━━━━━
▶ 4. FISCAL YEAR AND POSTING PERIODS
- Fiscal year variant: 12 periods + special periods for year-end.
- Posting period variant: which periods are open per account type.
━━━━━━━━━━━━━━━━━━━━
▶ 5. CONTROLS
- Field status groups decide which fields are required/optional/suppressed.
- Retained earnings account carries P&L balances into the new year.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Review company code and its assigned chart of accounts.
- Create a GL account (balance sheet) and a primary cost account in FS00.
- Open the current period in the posting period variant.
- Post a test entry and display the account balance.
✅ CHECKPOINT: you can explain every field you maintained and why the posting succeeded.
Code example
===== CONFIG MAP (SPRO > Enterprise Structure / Financial Accounting) =====Company code ............. OX02 (copy with EC01)Chart of accounts ........ OB13 → assign to company code OB62Fiscal year variant ...... OB29 → assign OB37Posting period variant ... OBBO → assign OBBP → open/close periods OB52Field status variant ..... OBC4 → assign OBC5Account groups ........... OBD4 | Retained earnings: OB53 ===== MASTER DATA =====FS00 central maintenance | FSP0 chart level | FSS0 company code levelAccount types (S/4HANA): Balance sheet | Nonoperating expense/income | Primary costs/revenue | Secondary costs ===== CHECK =====FAGLB03 account balance | Fiori: Display GL Account Balances / Trial BalanceReal project scenario
A newly onboarded FI consultant on a global rollout created revenue accounts as nonoperating income, so CO never received revenue and margin reports were empty. Changing the design to "primary costs or revenue" before go-live (after reversing test postings) fixed it; the team added an account-type review step to the master data checklist.
Common mistakes
- Treating the company code as a plant or site.
- Creating accounts without an account group strategy.
- Wrong S/4HANA account type (CO impact).
- Forgetting open item management on clearing accounts.
- Opening all periods permanently.
Best practices
- One operational chart of accounts for the group.
- Define account groups with number ranges.
- Decide account type with controlling.
- Use open item management for clearing accounts.
- Open and close periods deliberately each month.
Interview angle
Questions: "What is a company code?", "What are the two levels of a GL account?", "What changes for cost elements in S/4HANA?", "How do you control posting periods?"
Strong answer: company code as legal entity, chart of accounts assignment, chart/company-code master data, account types, fiscal year and period variants, field status.
Practice this lesson
Quick check
1. Interviewers frequently ask candidates to explain, in their own words, what the Universal Journal changed and why it matters operationally (real-time FI-CO alignment, single source of truth, elimination of reconciliation runs) - strong answ. In the General Ledger context, which answer shows the strongest practical judgment?
2. A GL account has settings at two levels. Which setting belongs to the company code level?
3. A team wants to create revenue accounts as "nonoperating income" to save time. What is the consequence in S/4HANA?
Interview questions
1. A vendor invoice for a purchase order is received in USD, while the PO was created in EUR, and the company code's local currency is GBP. Walk through how SAP calculates and posts the currency amounts and any exchange rate differences to the GL.
Answer it in your own words first, then compare.
2. During year-end close configuration, what chart of accounts and GL account master settings ensure tax-relevant accounts are correctly identified for statutory tax reporting?
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.