R2R 303 · PRACTITIONER PROCESS MAP
How does R2R close and report?
A practitioner close view across operational cut-off, parallel source workstreams, local accounting, entity reporting, group hand-off, and period control.
PREREQUISITE AND OUTCOME
Translate 101/202 concepts into close execution
Enter with: the R2R cycle plus the Finance structure, journal, integration, reconciliation, valuation, bank, close, and reporting capabilities from 101/202. Leave able to: trace close dependencies, evidence, exceptions, and ownership across workstreams. This map builds practitioner judgment; it does not grant posting authority or replace company-specific procedures.
READ THE CLOSE
What the diagram is really saying
R2R is a dependency network. Source workstreams progress in parallel, the general ledger coordinates their evidence, and reporting advances only when required populations and exceptions are controlled.
Create a stable reporting population
Logistics and operational periods are controlled so late material, billing, invoice, asset, payroll, and manual activity cannot silently change the close population.
Finish source and subledger workstreams
AP, AR, assets, manufacturing, inventory, bank, tax, and intercompany teams complete postings, clearing, reconciliation, and owned exceptions on coordinated schedules.
Execute the general-ledger close
Finance reconciles balances and runs accruals, provisions, depreciation, allocation, foreign-currency valuation, reclassification, and tax activities under the applicable accounting principles.
Approve statements, submit, and lock
Entity statements are reviewed before group hand-off. Reconciliation, mapping, translation, adjustment, and elimination remain distinct from local period access and close certification.
THREE ACCOUNTING RHYTHMS
The diagram shows month-end, but R2R starts earlier
Reliable close performance depends on continuous accounting and adds further obligations at year-end.
Record, clear, and resolve
Process source events and interfaces, clear open items, reconcile bank activity, and own posting failures.
Explore bank and cash → MONTH-ENDCut off, measure, and certify
Complete subledgers, reconcile, value, adjust, review, report, submit, and restrict late posting.
Explore close governance → YEAR-ENDConfirm, disclose, and carry forward
Add balance confirmations, audit, statutory work, reclassification, carry-forward, and fiscal-year closure.
Explore reporting →PARALLEL WORKSTREAMS
One close, different evidence
R2R is not a single serial transaction. Multiple source workstreams close in parallel, while the general ledger coordinates dependencies and only advances when required evidence and exceptions are controlled.
CLOSE OUTPUTS
Each gate produces different evidence
Cut-off, GL close, entity reporting, and group reporting are related but not interchangeable completion claims.
Late operational activity is prevented or explicitly governed so the close has a stable population.
Reconciliations and close entries place balances in the correct period and valuation basis.
Approved balances become statutory, management, and consolidation outputs with traceable support.
PRACTITIONER VIEW
What the close owner watches
The practitioner follows populations, dependencies, evidence, exceptions, approvals, and period access rather than a checklist alone.
Cut-off discipline
Material, billing, supplier invoice, asset, payroll, and manual-posting cut-offs; late-entry approval; and close-calendar status.
Subledger completeness
AP, AR, assets, inventory, manufacturing, bank, tax, and intercompany populations agree to their reconciliation accounts.
Reconciliation evidence
Prepared balance, source detail, unexplained difference, owner, ageing, reviewer, sign-off, and retained support.
Adjustment quality
Business rationale, calculation, accounting policy, dimensions, reversal logic, supporting evidence, preparer, and approver.
Valuation and tax
Exchange rates, valuation method, scope, posting logic, deferred or current tax inputs, and local compliance deadlines.
Reporting and lock
Trial-balance approval, statement review, group submission status, unresolved exceptions, posting-period authorization, and close sign-off.
WHEN THE CLOSE BREAKS
Start with the incomplete population or failed dependency
A late task is often a symptom. Identify which business evidence is missing before forcing completion or posting a compensating journal.
Is the comparison population complete?
Align company, ledger, currency, key date, account scope, posting status, reversal timing, source extraction, and reconciliation-account assignment.
Can the run be reproduced safely?
Inspect selection, run ID, method, rate or driver, prior update, log, posting period, account determination, reset or reversal behavior, and rerun ownership.
Are report views aligned?
Align company, ledger, currency, period, hierarchy validity, account assignment, unassigned accounts, adjustments, eliminations, and approval status.
Connect the practitioner flow to the configuration decisions, dependencies, transport boundaries, and end-to-end proof required to make it work.