Welcome to the Ultimate Hands‑On GL Configuration Lab
Day 1 – General Ledger (GL) Configuration: Chart of Accounts, Posting Keys & Document Types
Functional Consultant Track – Part 16
Picture this: you’re the lead FI consultant for GlobalTech, a mid‑sized manufacturing giant that just decided to move from a legacy system to SAP S/4HANA 2023. GlobalTech operates in the US, Germany, and India. The CFO demands a single source of truth while local statutory reporting must still work flawlessly. Your mission today is to build the general ledger foundation – the chart of accounts, posting keys, document types, tolerance groups, and the full parallel ledger setup with document splitting.
By the end of this tutorial, you’ll have configured a complete, audit‑ready GL structure in your sandbox client. You won’t just read theory; you’ll execute every SPRO step, understand why each setting matters, see real account numbers and sample postings, and learn the best practices that experienced consultants swear by. Let’s dive in.
1. The Consultant’s Scenario & Business Requirements
GlobalTech has three company codes:
GT01 – US operations (leading valuation under US GAAP, group reporting under IFRS)
GT02 – German operations (local GAAP = HGB, group reporting IFRS)
GT03 – Indian operations (local GAAP = Ind AS, group reporting IFRS)
Management requires:
A group chart of accounts (GCORP) for consolidated IFRS reporting.
Operational charts of accounts (CAUS for US, CADE for Germany, CAIN for India) that map to the group COA.
Flexibility to post in any company code and automatically derive the correct group account.
Strict control over which accounts can be used for direct postings (field status).
Automated clearing of foreign currency balances and tolerance limits for over/under payments.
Real‑time parallel accounting with document splitting to produce full balance sheets by profit centre, segment, or any custom dimension.
We will build all of this right now.
2. SPRO Path Basics – Your Compass in the IMG
Before we configure, remember the most important SAP menu path you’ll ever type: SPRO – SAP Reference IMG. We will work with the following structure:
SAP Customizing Implementation Guide
└── Financial Accounting (New)
└── General Ledger Accounting (New)
└── Master Data
└── G/L Accounts
└── Preparations
└── G/L Account Creation and Processing
└── Business Transactions
└── Document Splitting
└── Parallel AccountingEvery step will reference the exact SPRO path. Bookmark this, because you’ll live here.
3. Chart of Accounts – Operational, Country‑Specific & Group
A chart of accounts (COA) is the backbone of your GL. In S/4HANA you can link up to three COAs to a company code: an operational COA, a country‑specific COA, and a group COA. This is a huge improvement from classic ECC where you often had to use special purpose ledgers.
Step 3.1: Define Chart of Accounts (Operational COA – CAUS)
SPRO path: Financial Accounting (New) → General Ledger Accounting (New) → Master Data → G/L Accounts → Preparations → Edit Chart of Accounts List (transaction OB13)
Click “New Entries” and create:
| Chart of Accts | Description | Maintenance language | Length of G/L account no. | Controlling Integration |
|---|---|---|---|---|
| CAUS | Operational US COA | EN | 8 | Manual cost element creation allowed |
| CADE | German operational COA | DE | 8 | Manual |
| CAIN | Indian operational COA | EN | 8 | Manual |
Set the group chart of accounts to GCORP. (We’ll define it in a moment.)
Best practice: keep the G/L account number length 8–10 digits, all numeric, to allow room for hierarchical grouping. Avoid alphanumeric keys unless required by local legislation.
Step 3.2: Define Group Chart of Accounts (GCORP)
Same transaction OB13, but tick the “Group chart of accts” checkbox. Create:
Chart of Accts: GCORP
Description: Group COA – IFRS
Step 3.3: Assign Company Codes to Chart of Accounts
SPRO: Financial Accounting (New) → General Ledger Accounting (New) → Master Data → G/L Accounts → Preparations → Assign Company Code to Chart of Accounts (transaction OB62)
| Company Code | City | Oper. COA | Country COA | Group COA |
|---|---|---|---|---|
| GT01 | New York | CAUS | – | GCORP |
| GT02 | Munich | CADE | CADE (same) | GCORP |
| GT03 | Mumbai | CAIN | CAIN | GCORP |
For GT01, the country COA is blank because US GAAP reporting is already covered by the operational CAUS. For GT02 and GT03 we use the same COA for both operational and country because local requirements mirror the operational one, but we still map to GCORP for consolidation.
Why group COA? It allows you to enter an operational account in a local company code and automatically determine the corresponding group account in real time, eliminating batch mapping. You’ll define the group account in the G/L master record.
Step 3.4: Define Account Groups for G/L Accounts
Account groups control the number range interval and field status of a G/L account. Path: Financial Accounting (New) → General Ledger Accounting (New) → Master Data → G/L Accounts → Preparations → Define Account Groups (transaction OBD4)
Create the following for CAUS (and similar for other COAs):
| Acct Group | Name | From Acct | To Acct | Field status group |
|---|---|---|---|---|
| SAKO | Cash & bank | 10000000 | 19999999 | G001 |
| MAT | Materials/inventory | 20000000 | 29999999 | G001 |
| RECN | Reconciliation – AP/AR | 30000000 | 39999999 | G001 (but with open item mgmt mandatory) |
| KOST | Cost elements | 40000000 | 49999999 | G001 (cost element category later) |
| ERNA | Revenue | 50000000 | 59999999 | G001 |
| AST | Asset accounts | 60000000 | 69999999 | G001 |
By using account groups, you enforce correct number ranges. For instance, any G/L account in the range 30000000–39999999 automatically becomes a reconciliation account if you set the account control in the chart of accounts settings. We’ll configure that next.
Step 3.5: Field Status Groups and Field Status Variants
Field status groups control which fields are suppressed, required, or optional when posting to a G/L account. The standard delivered field status group G001 suppresses cost centre for balance sheet accounts, etc. You can create custom ones.
Path: Financial Accounting (New) → General Ledger Accounting (New) → Master Data → G/L Accounts → Preparations → Define Field Status Variants and Define Field Status Groups (transaction OBC4 / OBC5)
A field status variant is assigned to the company code. For GT01 we use standard variant “0001”. The field status group “G001” (General basic accounts) usually has the following field settings:
Cost centre: optional
Profit centre: optional
Business area: optional
Tax code: optional
Assignment: optional
For reconciliation accounts, you might create a variant group “G003” where the “Reconciliation Account” checkbox is mandatory and open item management is forced.
Step 3.6: Define G/L Account Master Records (Hands‑On Example)
We will now create three real accounts for company code GT01 using transaction FS00 (centrally). The accounts belong to chart of accounts CAUS.
Example 1: Cash Clearing Account
G/L Account: 10000010
Company code: GT01
With template: leave blank, create manually.
Type/Description: in chart of accounts section enter Account Group “SAKO”, select P&L statement acct? “Balance Sheet”.
Short text: “Cash clearing US”
G/L account long text: “Bank cash clearing for daily settlements”
Control Data tab: Account currency = USD, Tax category = “-” (no tax), Posting without tax allowed = Yes, Recon account = No.
Create/bank interest tab: field status group = G001.
Group chart of accounts section: enter Group account 10000000 in GCORP. This links the operational account to the group account for consolidation.
Example 2: Domestic Accounts Payable Reconciliation
G/L Account: 30000010
Account Group: RECN (Reconciliation)
Select “Balance Sheet”.
Short text: “Domestic AP Recon”
Control Data: Account currency = USD, Recon. account for acct type = “Vendors”, Open item mgmt = mandatory, Line item display = required.
Field status group: G003 (custom, ensures reconciliation field is active).
Group account: 30000000 in GCORP.
Example 3: Revenue – Product Sales
G/L Account: 50000010
Account Group: ERNA (Revenue), P&L account.
Short text: “Sales – Product US”
Control Data: Tax category = “+” (output tax allowed), Posting without tax allowed = No.
Field status group: G001 (cost centre required because P&L). In group COA, assign 50000000.
Pro tip: Always use the Create with reference button in FS00 to copy from an existing similar account – it saves time and reduces errors.
4. Posting Keys – The Gatekeepers of Debit/Credit & Field Control
Posting keys are two‑digit codes that determine:
Debit or credit entry
Account type allowed (G/L, customer, vendor, asset, material)
Which fields are visible/suppressed on the entry screen
Whether the line item is a payment or invoice (relevant for cash discount, etc.)
SAP delivers standard posting keys 01 to 50 for G/L accounts, and 21‑39 for customers/vendors, but you can create additional ones.
Standard posting keys you’ll use daily:
| Posting Key | Description | Debit/Credit | Account Type |
|---|---|---|---|
| 40 | G/L debit | Debit | G/L (S) |
| 50 | G/L credit | Credit | G/L (H) |
| 01 | Customer invoice | Debit | Customer (D) |
| 11 | Customer credit memo | Credit | Customer (D) |
| 21 | Vendor credit memo | Debit | Vendor (K) |
| 31 | Vendor invoice | Credit | Vendor (K) |
| 81 | Asset debit | Debit | Asset (A) |
| 91 | Asset credit | Credit | Asset (A) |
How posting keys control fields – an example:
When you post a vendor invoice (PK 31), the system automatically proposes the vendor line as a credit, forces “Vendor” account type, and hides fields like “Cost centre” on that line. The offset line (PK 40) posts a debit to an expense G/L account, where the cost centre is required. This two‑key logic makes document entry bullet‑proof.
Configuration of posting keys
SPRO path: Financial Accounting (New) → General Ledger Accounting (New) → Business Transactions → Document Posting → Define Posting Keys (transaction OB41)
You can double‑click on any existing key, e.g., 40, to see its settings:
Debit/Credit indicator: Debit
Account type: S (G/L account)
Transaction type: G/L account posting
Field status: You can define field status definitions for each posting key to control additional details like “Payment block”, “Assignment”, “Text”.
A real‑world tweak: Sometimes you want to allow the text field to be mandatory on certain posting keys to enforce descriptions. Create a new posting key, say “4Z”, copy from 40, and modify the field status to make “Text” required. Use this for all manual journal entries.
Exercise: Create a custom posting key for “Accrual Reversal”
Go to OB41, choose “New Entries”.
Posting key: 4Y, Debit, Account type S, Field status: make “Reverse posting date” optional, “Reference document number” required.
Usage: Every accrual reversal entry will demand a reference to the original accrual document, ensuring audit trail.
5. Document Types and Number Ranges – Fiscal Year Dependency
Document types classify business transactions and control:
Number range assignment (internal/external)
Account types allowed (e.g., only G/L accounts for SA)
Reverse document type
Net document type for invoices
Authorisation group
Standard key document types:
| Document Type | Description | Number range | Allowed Acct Types |
|---|---|---|---|
| SA | G/L account document | Internal 01 | S (G/L) |
| AB | General reversal | Internal 01 | S, D, K |
| KG | Vendor credit memo | External 16 | K, S |
| DR | Customer invoice | Internal 14 | D, S |
| KR | Vendor invoice | External 17 | K, S |
| AA | Asset posting | Internal 06 | A, S |
Step 5.1: Define Number Ranges
Path: Financial Accounting (New) → General Ledger Accounting (New) → Business Transactions → Document Posting → Define Number Ranges for Documents (transaction FBN1)
For company code GT01:
Number range 01: 0100000000 – 0199999999, internal, current number 0100000001. Assigned to document type SA, AB.
Number range 17 (vendor invoice): 1700000000 – 1799999999, external (because vendor invoices often use the vendor’s invoice number). Assigned to KR, KG.
Fiscal year dependency is crucial. In FBN1 you can set a number range as “to fiscal year” dependent. For example, document type SA uses a single number range that is fiscal year independent, but you could configure it to start fresh each year by checking “Fiscal year dependent”. Many companies prefer fiscal‑year‑independent numbering to avoid gaps.
Step 5.2: Define Document Types
Path: Financial Accounting (New) → General Ledger Accounting (New) → Business Transactions → Document Posting → Define Document Types (transaction OBA7)
Key settings when defining a new document type, e.g., “ZJ” for month‑end accrual journals:
Number range: internal 01
Reverse document type: “ZR” (custom reversal type)
Allowed account types: S only
Net document type: leave blank
Document type for recurring entries: optional
Hands‑On Scenario: GlobalTech wants a separate document type for all “Management Adjustment” postings that must not be reversed automatically by the month‑end closing program. So you create document type “ZM” with no reverse document type. In OBA7, you set “Reverse document type” blank. This ensures no accidental reversal.
6. Tolerance Groups for Over/Under Payment
When a customer pays slightly less (say $2.50) due to bank charges, you don’t want the invoice to remain open forever. Tolerance groups define how much difference the system can automatically write off.
Step 6.1: Define Employee Tolerance Groups
Path: Financial Accounting (New) → General Ledger Accounting (New) → Business Transactions → Open Item Clearing → Define Tolerance Groups for Employees (transaction OB57)
Create:
Group: GTOL
Company code: GT01
Amount per document: 50 USD (single line item difference)
Amount per open item: 5% or 20 USD, whichever is smaller
Cash discount adjustment tolerance: 2%
Assign this tolerance group to the user IDs of the accounts payable clerks. Now, when they process a payment of 10,000, the system will automatically post the $2 difference to a predefined gain/loss account and clear the invoice.
Step 6.2: Vendor/Customer Tolerance Groups
You can also define tolerance limits for auto‑clearing on the master data (transaction OBA3). Typically, you set a small “permitted payment difference” for each vendor. GlobalTech sets 5 USD for all domestic vendors.
7. New GL – Parallel Ledgers & Document Splitting (S/4HANA Only)
In S/4HANA, the New General Ledger is the only GL – classic GL doesn’t exist. All features are active by default, but you must configure the parallel ledgers and document splitting to meet multi‑GAAP reporting and segment/profit centre reporting.
Step 7.1: Define Ledgers
SPRO: Financial Accounting (New) → General Ledger Accounting (New) → Ledgers → Define Ledgers
Standard delivered:
0L – Leading ledger (US GAAP for GT01)
L1 – Non‑leading ledger for IFRS (you can rename)
For GlobalTech, we define:
Leading ledger 0L = US GAAP
Non‑leading ledger L1 = IFRS
Non‑leading ledger L2 = German HGB (only assigned to company code GT02)
Assign the fiscal year variant K4 (calendar year) and posting period variant to each ledger.
Step 7.2: Activate Document Splitting
Document splitting is mandatory if you want to produce full balance sheets by segment or profit centre. Path: General Ledger Accounting (New) → Business Transactions → Document Splitting → Activate Document Splitting
Turn on document splitting globally. Then define splitting characteristics: we’ll use Profit Centre as the mandatory splitting characteristic. You can also add Segment, Business Area, etc.
Step 7.3: Define Splitting Method
Path: General Ledger Accounting (New) → Business Transactions → Document Splitting → Define Splitting Method
Create method Z001 with:
Item categories to be split: 01000 (balance sheet accounts), 02000 (P&L accounts), etc.
Splitting rule: “Profit Centre” is a mandatory field for balance sheet lines. If a posting does not have profit centre, the system will split the line based on the other line items’ profit centres.
For example, a vendor invoice (credit vendor 31, debit expense 40) posted with profit centre PC‑ADMIN for expense. The system will automatically create a balancing line on the vendor reconciliation account with profit centre PC‑ADMIN, ensuring the balance sheet by profit centre balances.
Step 7.4: Define Zero‑Balance Clearing Account
Path: General Ledger Accounting (New) → Business Transactions → Document Splitting → Define Zero‑Balance Clearing Account
Enter a G/L account (e.g., 19999999) per company code. This account will be used temporarily during splitting if there is an imbalance; it should clear automatically.
Hands‑on test: Post a vendor invoice (F‑43) with expense G/L 50000010 and profit centre PC100, no profit centre on the vendor line. Activate simulation. The system will generate a secondary entry: debit reconciliation account 30000010 with profit centre PC100, and a credit to 19999999 clearing account. After splitting, the clearing account must net to zero.
8. Real‑Life Scenario – End‑to‑End Configuration Test
Let’s simulate a day in GlobalTech’s finance department.
Setup complete: CAUS operational COA, GCORP group COA, account groups, posting keys, document type ZM, tolerance group GTOL, leading ledger 0L, non‑leading L1, document splitting active on profit centre.
Transaction 1: Record a utility expense invoice from vendor “UTILCORP”.
Use transaction F‑43.
Header: Document type KR (vendor invoice), company code GT01, posting date today.
Line 1: Posting key 31, account 30000010 (vendor AP Recon), amount 1,200 USD, vendor UTILCORP.
Line 2: Posting key 40, G/L account 40000020 (electricity expense), amount 1,200 USD, profit centre PC‑ADMIN, cost centre CC‑ADMIN.
Simulate. The system splits the vendor line automatically to carry profit centre PC‑ADMIN on the AP reconciliation line, generating a clearing entry.
Post. Document number 1700000001 generated (external range).
Transaction 2: Customer payment received with minor shortfall.
Customer invoice 1400000001 for 5,000 USD. Payment received 4,998 USD.
Use transaction F‑28 (Incoming payment).
Select invoice, enter partial amount 4,998. The system checks tolerance group GTOL for the user. Difference 2 USD ≤ 5 USD per document, so it auto‑posts the difference to account “Small Difference Gain” (55000010) and clears the invoice.
Everything integrates perfectly. The group ledger L1 receives the same documents, but the group account mapping (e.g., 40000020 maps to 40000000 in GCORP) ensures consolidation‑ready data.
9. Best Practices, Common Pitfalls & Pro Tips
Best Practices:
Always define a group chart of accounts and link it to every operational account. It pays off tenfold during consolidation.
Use fiscal‑year‑independent number ranges for most internal document types to keep a continuous audit trail; use external ranges only for external documents (vendor invoices).
Keep posting keys standard (40, 50, 31, etc.). Only create custom keys when a unique field control is absolutely necessary.
For document splitting, activate it early in the project and test with all real transaction types (MM invoice, SD billing) before go‑live. Retrofitting splitting is a nightmare.
Leverage field status groups to prevent accountants from posting to a material inventory account without a plant, or posting expense without a cost centre.
Common Pitfalls:
Forgetting to extend the G/L account to the company code with FS00. A chart of accounts segment alone won’t let you post.
Number range exhaustion. Always set a high current number and add a warning threshold in FBN1.
In document splitting, if the zero‑balance clearing account is not defined, the system will error out. Don’t skip it.
Mixed usage of external and internal number ranges causing gaps in audit trails if not properly documented.
Alternatives and When to Use Them:
If you don’t need multi‑GAAP parallel ledgers, you can work with a single leading ledger and use special purpose ledgers for minor adjustments – but in S/4HANA, parallel ledgers are the standard.
If your document splitting requirements are very complex (e.g., 5 dimensions), consider enhancing with BAdIs rather than custom splitting rules, to keep the configuration manageable.
10. Wrap‑Up & What’s Next
You’ve just built the entire GL backbone of a multi‑national company. You can now:
Create operational, country‑specific, and group charts of accounts.
Set up account groups and field status controls that enforce data quality.
Configure posting keys that govern every debit and credit line.
Design document types with airtight number ranges and fiscal‑year logic.
Enable tolerance groups that smooth the payment clearing process.
Activate parallel ledgers and document splitting that deliver real‑time segment reporting.
Tomorrow, in Part 17, we will dive into Accounts Payable & Accounts Receivable End‑to‑End Configuration: vendor/customer account groups, reconciliation accounts, payment terms, automatic payment program (F110), dunning, down payments, and foreign currency valuation in S/4HANA. You’ll configure the entire Procure‑to‑Pay and Order‑to‑Cash engine.
*Bookmark this page, take a screenshot of your SPRO settings, and stay tuned. Your journey to becoming an S/4HANA functional master has just begun.*
FreeLearning365
Tech Partner: @techbook24
(End of Part 16)
0 Comments
thanks for your comments!