RECORD TO REPORT · CLOSE
How is the financial close coordinated and controlled?
The close is a dependency network across operational cut-off, subledgers, reconciliations, valuations, adjustments, review, reporting, and period control.
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
Close governance makes readiness and exceptions visible
A close calendar must show tasks, dependencies, organizational scope, owners, due dates, evidence, approvals, reruns, failures, unresolved risk, and the authority to restrict or reopen posting.
THREE RHYTHMS
R2R is continuous, monthly, and annual
The same controls operate at different intensities and with different terminal evidence.
Keep accounting current
Record source events, process interfaces, clear open items, reconcile banks, and resolve posting failures.
Measure and report the period
Enforce cut-off, complete subledgers, reconcile, value, adjust, review, report, and restrict late posting.
Complete statutory closure
Confirm balances, complete audit and disclosure work, reclassify, carry balances forward, and close the fiscal year.
OPERATIONAL FLOW
What happens in SAP
Read the sequence as one connected business event, not as isolated transactions.
Release the close calendar
Define scope, sequence, dependencies, owners, deadlines, evidence, reviewers, escalation, and materiality.
Complete source and GL tasks
Run operational cut-off, subledger close, reconciliations, valuations, adjustments, allocations, tax, and reporting tasks.
Control failures and reruns
Job logs, rejected postings, missed dependencies, late journals, reopen requests, and unresolved balances receive explicit decisions.
Approve and protect the period
Review trial balance and statements, retain sign-offs, submit required packages, close posting access, and record residual risk.
DESIGN & CONTROL
What shapes the result
These controls work together; a locally correct setting can still produce the wrong end-to-end outcome.
Dependency control
Task templates, organizational scope, predecessor status, due dates, recurrence, job variants, and responsible roles prevent premature execution.
Evidence and approval
Run logs, reconciliations, attachments, preparer and reviewer decisions, threshold exceptions, and certification establish completion.
Period access
Posting-period variants, account types, authorization groups, special periods, reopen authority, and late-entry monitoring protect closed results.
DIAGNOSTIC EVIDENCE
Distinguish task completion from close readiness
A green task is useful only when the expected population, result, exceptions, and approval can be inspected.
Company, period, owner, due date, predecessor, job or manual action, run ID, status, and completion timestamp.
Expected versus actual output, reconciliation, threshold, exception, rerun, journal entry, and supporting attachment.
Reviewer, unresolved risk, late-posting decision, financial-statement approval, group submission, and period-lock evidence.
CLOSE MOMENT
One failed valuation blocks statement approval
Most tasks are complete, but foreign-currency valuation failed for one company code. The close remains conditionally blocked until the job is corrected, rerun, reconciled, and reviewed; the team does not hide the exception behind a manually completed task.
- Dependency is visible
- Failure has an owner
- Rerun is reconciled
- Period lock follows approval
See how continuous accounting, operational cut-off, parallel subledger workstreams, GL close, reporting, group hand-off, and period control connect.