RECORD TO REPORT · REPORT
How do ledger balances become financial statements?
Financial statement hierarchies organize G/L balances for balance sheet and income-statement reporting. Entity results can then be mapped, translated, reconciled, submitted, and eliminated for group reporting.
GL ACCOUNTANT OUTCOME
Use this capability inside the complete close
Learn the business purpose, SAP record, controls, diagnostic evidence, and hand-offs for this capability. Complete all R2R 202 guides to form the role-level knowledge foundation; company policy, local procedures, system authorization, and supervised execution remain workplace requirements.
PROCESS ROLE
Reporting presents governed balances without breaking drill-down
The reporting structure must preserve ledger, accounting principle, currency, company, profit center, segment, account, and source-journal context while controlling mappings, eliminations, adjustments, approval, and publication.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Approve the entity trial balance
Complete reconciliations, valuations, adjustments, tax inputs, review, and period controls for the reporting entity.
Apply reporting hierarchies
Financial statement versions or global hierarchies organize accounts into balance-sheet and income-statement nodes.
Prepare group data
Map company and accounts to consolidation units and financial-statement items, translate currency, validate, and submit the package.
Reconcile and eliminate
Match intercompany activity, post approved adjustments, eliminate internal balances and results, and review consolidated statements.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Statement structure
Hierarchy version, validity, account assignment, retained earnings, functional area, profit center, segment, and unassigned-account checks protect presentation.
Submission integrity
Consolidation unit, FS-item mapping, version, posting level, currency translation, validation, data release, and package approval govern group hand-off.
Intercompany and disclosure control
Partner dimensions, matching methods, reconciliation cases, tolerances, elimination rules, adjustment workflow, ownership, and disclosures protect group results.
DIAGNOSTIC EVIDENCE
Trace a reported number to the journal and the group adjustment
A report is trusted when its hierarchy, filters, mapping, currency, eliminations, and source line items can be reproduced.
Company, ledger, accounting principle, currency, fiscal period, FSV node, account balances, unassigned accounts, and trial-balance approval.
Consolidation unit, FS item, mapping, group currency, posting level, validation, submission status, and package approval.
Partner unit, matching assignment, difference category, adjustment, elimination method, resulting posting, and reviewer.
REPORTING STORY
A margin variance from statement to source
A reviewer starts with a profit-and-loss node, drills to revenue and cost accounts, filters by company and profit center, reaches the originating journal entries, and separately identifies the intercompany elimination applied at group level.
- Hierarchy is current
- Unassigned accounts are zero or explained
- Entity and group views are distinguished
- Drill-down reaches source evidence
See how continuous accounting, operational cut-off, parallel subledger workstreams, GL close, reporting, group hand-off, and period control connect.