FS10N — G/L Account Balance Display

FS10N shows period balances for a single G/L account or account range within a company code and fiscal year: opening balance, debit and credit movement per period, and closing balance. The one structural fact that explains most confusion is that FS10N reads from the totals table, not from the line item table. On classic General Ledger that totals table is GLT0; on New GL it is FAGLFLEXT (and on S/4HANA it draws from the universal journal aggregation on ACDOCA). Because the report is aggregated, the figures shown will only ever be as reliable as the consistency between the totals table and the actual posted line items. Any gap between what FS10N reports and what FBL3N sums to is a reconciliation problem between those two layers, not a bug in the balance report itself.

FS10N is reached for during period-end and month-end close, when someone needs to see how an account moved period over period before deciding whether to open the individual documents. It is the natural first step ahead of FBL1N, FBL3N or FBL5N drill-down, because it shows trend and magnitude across periods rather than a flat document list. It also gets used for balance confirmation work, for spot-checking a P&L or balance sheet line at account level, and for validating that a correction posting landed in the expected period. Where the requirement is genuinely transactional detail from the start (searching for one specific document, one vendor invoice, one clearing), FBL3N or a vendor/customer line item report is the better entry point instead.

In SE16 on FAGLFLEXT (or GLT0 on classic GL), filter on company code, G/L account, and fiscal year, and sum the relevant period balance fields to reproduce the figure FS10N displays. Then run the same filter on BSEG joined to BKPF for posting date within that fiscal year and period, summing the local currency amount field. If the two totals disagree, the totals table is out of sync with the line items and a reconciliation or totals rebuild is needed rather than a report fix.

On S/4HANA the underlying source is the universal journal table ACDOCA rather than separate classic and New GL totals tables, but FS10N itself still presents the same period-balance layout and drill-down behavior. The Fiori app for G/L account balances covers the same use case with a more analytical, drillable interface and is the direction SAP is pushing new users toward, but FS10N remains available and is still the faster tool for a quick account-by-account period check.

This is a functional FI general ledger accounting problem, owned by the accounting or FI configuration team, not Basis or ABAP unless the totals table itself is corrupted or a custom program bypassed standard posting. A good handover includes the company code, account, fiscal year and period in question, the exact figures from FS10N versus FBL3N, and whether a mass reversal, migration, or direct table update happened recently.

FBL1N and FBL3N are the natural next stop for anyone drilling from a period balance into actual documents. FAGLB03 is the New GL equivalent balance display with more ledger-aware options and is worth comparing against FS10N when parallel ledgers are in play. FD10N and FK10N follow the identical balance-display pattern for customer and vendor accounts, so understanding FS10N's totals-versus-line-item behavior transfers directly to those two.