FAGLB03 — New GL Account Balance Display

FAGLB03 shows period-by-period debit, credit and balance figures for a G/L account, company code and fiscal year, sourced from the New General Ledger totals table FAGLFLEXT rather than the classic GLT0 table that FS10N reads. The structural fact behind most confusion: New GL carries multiple ledgers (a leading ledger such as 0L and any parallel non-leading ledgers for local GAAP or tax reporting), and FAGLB03 defaults to whichever ledger is set in the selection screen. If the analyst does not deliberately pick the ledger relevant to the question being asked, the balance shown can be technically correct but answer the wrong question, looking like a discrepancy when it is not.

Used during period-end and year-end close to reconcile account balances before running financial statement reports, and whenever a balance sheet or P&L account needs to be checked at the summary level rather than line item by line item. Reached for instead of FS10N specifically on clients running parallel ledgers, where the same account can carry different balances under local GAAP versus group accounting, or where document splitting has redistributed a balance across segments or profit centers. Also used to sanity-check a suspected posting error before drilling into line items, and to confirm whether a balance discrepancy reported by a business user is a ledger-selection issue rather than a true posting gap.

Open SE16N on FAGLFLEXT and filter on RLDNR (ledger), RBUKRS (company code), RACCT (G/L account) and GJAHR (fiscal year). Compare the relevant balance field for the currency type in question against what FAGLB03 displayed, period by period. If FAGLB03 and FS10N disagree, pull the same filters against GLT0 and compare row counts and totals side by side; a mismatch in ledger selection shows up immediately as different balances at identical filter values, while a genuine posting gap shows up as a document present in BKPF/BSEG but missing from one of the totals tables.

On S/4HANA the Universal Journal (table ACDOCA) is the single source of truth for FI and CO, and FAGLFLEXT is retained as a compatibility view over ACDOCA rather than a separately updated table. FAGLB03 continues to run and shows the same period balance logic; the underlying storage is different but the selection screen and drill-down behavior are unchanged. The Fiori equivalent for the same balance question is the G/L Account Balances app, which most clients migrate to for routine close work while keeping FAGLB03 for ad hoc checks.

Functional FI problem in essentially all cases; this is a display transaction with no configuration of its own to break. A good handover to the FI consultant includes the exact ledger, company code, fiscal year, account and currency type used, plus the specific period where the figure looked wrong, so the comparison can be reproduced without guessing at selection parameters.

FS10N is the natural comparison point since it answers the same question from the classic totals table and is the fastest way to isolate a ledger-selection issue. FS00 explains the account's master data settings, including whether it participates in open item management or is line-item display relevant, which affects how far a drill-down can go. OB52 is worth checking when a period appears closed unexpectedly during a balance investigation. FB50 is useful context for understanding how a New GL posting actually populates the segment and profit center fields that later show up split in the balance display.