SAP General ledger

The G/L holds all accounts (from the chart of accounts) and records every financial posting against them, both directly and via sub-ledgers (AP, AR, assets). It is the single source for statutory financial statements. In S/4HANA the G/L is powered by the universal journal (table ACDOCA), unifying FI and CO line items.

• G/L accounts: from the chart of accounts, balance-sheet or P&L.
• Document postings: every entry is a balanced document (debits = credits).
• Ledgers: leading and non-leading ledgers for parallel accounting (e.g. IFRS + local GAAP).
• Reconciliation: sub-ledgers reconcile automatically to the G/L.

FS00 maintains a general ledger account, and the screen splits in two for a reason: the chart of accounts view holds what the account is, shared by every company code, and the company code view holds how it behaves here, including the currency, whether it takes open item management and which field status group applies.

FB50 posts a journal directly. FB03 displays any document. FAGLL03 lists general ledger line items and is where most investigations start. FAGLB03 shows balances. F.01 produces the financial statement.

OB52 opens and closes posting periods, and it is the transaction that decides whether a closed month can quietly change. OBYC holds automatic account determination for logistics postings, which is where a goods receipt learns which account to hit.

Fifteen minutes, and it teaches the document structure everything else in finance rests on.

1. Post a simple journal with FB50: one debit, one credit, same amount. It will refuse to save if they do not balance, per company code and per currency.
2. Open it in FB03. Read the header for the document type and posting date, then the line items for the posting keys.
3. Run FAGLL03 for one of the accounts and find your line. This is the view an accountant investigates from.
4. Try posting into a period that OB52 has closed. The refusal is the control working, and knowing where it comes from saves an afternoon.
5. Post a document with a cost element account and no cost object. It fails, because that account requires a controlling assignment. See asset accounting for a sub-ledger with its own version of the same idea.

The universal journal (ACDOCA) is the biggest S/4HANA finance change: one line-item table holds G/L, CO, and more, giving real-time, reconciled financial and management reporting from a single source and removing many old aggregate tables.

The practical consequences are worth spelling out. Reconciliation between finance and controlling no longer exists as a period end task. Cost elements are general ledger accounts rather than separate master records. Reporting reads one table, so a report can slice by cost centre, profit centre and segment without joining anything. And custom reports written against the older line item tables need rewriting, which is one of the most common findings in a conversion assessment.

• Chart of accounts design. One operating chart across the group makes consolidation work and forces every country onto a shared structure. It is close to irreversible, so it is made early and carefully.
• Document splitting. Splitting produces a balanced balance sheet by segment or profit centre. It has to be switched on from the start.
• How many ledgers. Parallel ledgers let one set of postings report under IFRS and a local standard, which is cheaper than two sets of books.
• Field status. Which fields are required, optional or suppressed when posting to an account. Dull, and it is what stops a posting arriving with no cost centre on it.

Everything in the general ledger points at the close, and knowing its shape explains why so many FI settings exist.

The sequence runs roughly the same way everywhere. All sub-ledgers post everything they have: payables, receivables, assets and inventory. Then the periodic postings run: depreciation, accruals, foreign currency valuation, and any allocations in controlling. Then the sub-ledgers are reconciled to their reconciliation accounts. Then the period is closed with OB52, and the financial statement is produced.

Order matters because each step depends on the one before. Running depreciation before all asset acquisitions have posted produces a number that has to be redone. Closing the period before finance has finished means reopening it, and a reopened period is how reported figures change after they were reported.

Two mechanisms make it survivable. Posting period variants let you close for most users while leaving a period open for a small group who still have work, which is the practical compromise every month end needs. And document splitting, where it is switched on, means the balance sheet balances by segment without a manual allocation at the end.

Year end adds the carry-forward: balance sheet accounts roll their balance into the new year, profit and loss accounts roll into retained earnings and start at zero. That runs as a program, and running it is not optional, but it can be repeated safely if postings arrive afterwards.

The habit worth building is reading a trial balance before and after each step. If a number moved that you did not expect to move, the reason is easier to find now than in three weeks. See SAP FI troubleshooting for what to do when it does.

Not every document is posted the moment it is entered, and the three alternatives exist for different reasons.

A held document is a personal draft. It is incomplete, nobody else sees it, and it has no document number. It exists so you can stop mid-entry without losing work.

A parked document is different and more useful. It is complete enough to have a number, it is visible to others, and it has updated nothing. Parking is how an approval step is built into data entry: one person parks, another reviews and posts. It is also how an entry can be saved when a field is still being chased.

Recurring entries handle the postings that repeat unchanged, such as a monthly rent accrual. A template is created once with a schedule, and a periodic program creates the real documents from it.

The practical point for anyone investigating: a parked document explains a number that finance expects to see and the ledger does not have. It is not missing, it is waiting for somebody, and the parked document list is the first place to look.

• Unbalanced postings, documents must balance.
• Ignoring parallel ledgers for multi-GAAP reporting.
• Not understanding ACDOCA in S/4HANA.

• Creating an account without the company code view. It exists and cannot be posted to, and the error does not say which half is missing.
• Leaving prior periods open. Reported numbers change afterwards and nobody notices until an auditor does.
• Assuming a wrong account is an FI error. If the posting came from logistics, the answer is in OBYC and the material's valuation class. See SAP FI taxes for the other common source of surprise lines.

Posting a journal is the easy half, and designing the chart of accounts, ledgers and field status so a real business posts correctly is the part you do in the course.

And one working practice. When a number in a report does not match expectation, go to the line items rather than the balance, then to the document, then to whatever created the document. The answer is nearly always one step further back than where the question was asked.