General Ledger
FI / FICOintermediate

FICO General Ledger Part 2: Posting Flow, Integration and the Universal Journal

Key takeaway

Follow a posting from entry to report: document header and line items, posting keys, document types and number ranges, automatic postings from MM, SD and payroll, derivations (profit center, segment, functional area), and how everything lands in the universal journal (ACDOCA) in S/4HANA.

Explanation

📌 KEY POINTS
✅ An FI document = header (company code, dates, document type, currency) + at least two balanced line items.

✅ Document types control number ranges and allowed account types; posting keys control debit/credit and account type per line.

✅ Most GL postings come automatically from sub-ledgers and logistics (AP, AR, assets, MM, SD, payroll).

✅ In S/4HANA every posting writes one line per item to ACDOCA with FI, CO and derived dimensions together.

⚠️ Wrong postings are reversed (with reason and date), never deleted — the audit trail must stay intact.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 1 built the foundation. Now the posting flow.

━━━━━━━━━━━━━━━━━━━━
▶ 1. DOCUMENT STRUCTURE

  • Header: company code, document date, posting date, document type, reference.
  • Items: account, amount, posting key, tax code, cost object.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DOCUMENT TYPES AND NUMBER RANGES

  • SA GL posting, KR vendor invoice, DR customer invoice, AA asset, WE goods receipt...
  • Number range per company code and fiscal year.

━━━━━━━━━━━━━━━━━━━━
▶ 3. INTEGRATION POSTINGS

  • AP/AR via reconciliation accounts; MM via automatic account determination; SD via revenue account determination.

━━━━━━━━━━━━━━━━━━━━
▶ 4. DERIVATIONS AND SPLITTING

  • Profit center and segment derived from cost objects; functional area for cost-of-sales reporting; document splitting balances by segment if active.

━━━━━━━━━━━━━━━━━━━━
▶ 5. REVERSAL AND REPORTING

  • Reversal with reason (normal or negative posting); line items and balances in real time.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Post an accrual with FB50 (or the Fiori app) using a cost center.
  2. Display the document and its line items.
  3. Reverse it with FB08 and a reversal reason.

✅ CHECKPOINT: you can trace the posting to ACDOCA line items with profit center and segment filled.

Code example

ABAP Code
===== CONFIG MAP =====Document types ........... OBA7 | Number ranges FBN1Posting keys ............. OB41 (e.g. 40 debit GL, 50 credit GL, 31 credit vendor, 01 debit customer)Reversal reasons ......... SPRO > FI > GL Accounting > Business Transactions > Adjustment Posting/Reversal > Define Reasons for ReversalAutomatic-only accounts .. FS00 flag "Post automatically only" ===== POSTING =====FB50 / Fiori "Post General Journal Entries" (simulate → post)Example: Dr 610000 Rent expense (cost center 1000) 5,000 | Cr 211000 Accrued liabilities 5,000 ===== DISPLAY & CORRECT =====FB03 display document | FAGLL03H line items | FB08 reversal | Fiori: Manage Journal Entries

Real project scenario

During an S/4HANA private cloud migration, month-end journals posted to a balance sheet account without profit centers, so segment reports did not balance. Enabling document splitting with profit center as a mandatory split characteristic and a default profit center for exceptions gave balanced segment balance sheets.

Common mistakes

  • Deleting instead of reversing.
  • Posting manually to reconciliation accounts.
  • Ignoring document type controls.
  • Missing cost objects on P&L lines.
  • Not simulating complex entries.

Best practices

  • Standardize document types.
  • Protect automatic-only accounts.
  • Always add cost objects to P&L lines.
  • Simulate before posting.
  • Use reversal reasons consistently.

Interview angle

Questions: "What is a posting key?", "How do MM/SD postings reach GL?", "How do you reverse a document?", "What is ACDOCA?"
Strong answer: document structure, types and number ranges, posting keys, integration via reconciliation and account determination, derivations, reversal, universal journal.

Practice this lesson

Quick check

1. Why should reconciliation accounts for AP/AR not be posted to manually?

2. 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 architecture, reconciliation and reporting versus classic EC. A production team now has to make a design decision in General Ledger Posting Flow, Integration and S/4HANA Universal Journal Differences. Which option best preserves reliability and supportability?

3. A wrong journal entry was posted last week. What is the correct correction?

Interview questions

1. During year-end close, you find long-outstanding open items sitting on a customer reconciliation account, distorting the AR aging report and preventing clean GL-to-subledger reconciliation. How would you investigate and resolve this, and what document control settings are relevant?

Answer it in your own words first, then compare.

2. During year-end closing, an AP clerk attempts to post a manual FB60 vendor invoice directly to a GL account normally updated only through automatic MM postings (e.g., GR/IR clearing), and the system blocks the posting. As a junior consultant, explain the likely cause and the account master governance control involved.

Answer it in your own words first, then compare.

Practice more with Interview AI →

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.

More lessons in this topic

Interview questions on this topic

Related SAP topics