Record-to-Report(R2R)
From a single journal entry to the financial report: how the record-to-report process runs, how it is measured and where month-end and year-end closes lose time.
Also known as: R2R · Record to Report · Account-to-Report · Financial close
What is Record-to-Report?
Record-to-report (R2R) is the end-to-end process from recording a business transaction in the general ledger to the finished financial report. It covers master data and the chart of accounts, ongoing posting, reconciliations between general ledger and subledgers, the period-end and year-end close, and consolidation and reporting. Because almost every other process – order-to-cash, purchase-to-pay, hire-to-retire – ends up in the general ledger, R2R decides how quickly and reliably a company knows its numbers.
Starts with
A business transaction is recorded in the general ledger or a subledger.
Ends with
The audited close is reported and the period is locked.
Typical phases
- 1
Master data & posting logic
Chart of accounts, cost centres, legal entities and posting rules define how transactions from the operational processes arrive in the general ledger.
- Chart of accounts maintained
- Cost centre created
- Posting rule defined
- 2
Ongoing posting
Subledgers for receivables, payables and assets hand over their postings, complemented by manual journals, accruals and reclassifications.
- Subledger posting transferred
- Manual journal created
- Journal approved
- Accrual posted
- 3
Reconciliation
Accounts, bank balances, subledgers and intercompany balances are reconciled; differences are clarified and corrected.
- Account reconciliation started
- Difference identified
- Correcting entry
- Reconciliation signed off
- 4
Period-end close
Close tasks run in a fixed order according to a close calendar: valuation, depreciation, allocations, intercompany matching and locking the period.
- Close task started
- Valuation & depreciation
- Allocation posted
- Intercompany matched
- Period locked
- 5
Consolidation & reporting
The individual financial statements are consolidated, reviewed and reported to management, supervisors and the capital market.
- Consolidation
- Review & approval
- Report published
Business objects and systems
These are the objects the process leaves in the source systems – with timestamps, owners and relationships to each other.
- Journal entry
- Every transaction in the general ledger, with author, time, account and origin in the upstream process.
- Manual journal
- Postings without an operational upstream process – a frequent place for corrections and controls.
- Reconciliation
- Matching an account against a subledger, bank or counterparty entity, including differences.
- Close task
- A task in the close calendar with an owner, a due date and dependencies.
- Intercompany balance
- Receivables and payables between entities that have to match.
- Period
- Posting period with the status open, in close or locked.
Typical source systems
- ERP general ledger (e.g. SAP S/4HANA FI/CO, Microsoft Dynamics 365 Finance)
- Close management tools
- Consolidation software
- Bank and payment data
KPIs that can be measured
- Days to close
- Working days from period end to the finished close.
- Share of manual journals
- How many postings arise without an operational upstream process.
- Post-close adjustments
- Postings that change a period after it has been closed.
- On-time close tasks
- Share of tasks completed by their due date in the close calendar.
- Open intercompany differences
- Number and age of unresolved differences between entities.
Typical problems
The close waits for upstream processes
Late invoices from purchase-to-pay or open deliveries from order-to-cash delay accruals and reconciliations – the problem arises outside accounting.
Manual journals as a permanent fix
Recurring manual corrections hide faulty posting rules or interfaces and tie up capacity every month.
Dependencies in the close calendar
One late task blocks all that follow. The checklist alone does not show which task determines the critical path.
Controls without evidence
Four-eyes principle and approval limits for journals are defined but not traceably met in every case.
How Noreja analyses Record-to-Report
The general ledger shows the result, not the way there. A correcting entry often has its cause in a purchase order, a delivery or a master data change weeks earlier. Noreja connects journal entries with the objects of the upstream processes in the event knowledge graph instead of treating the close as an isolated event log.
The close calendar is modelled as the expected order. This shows which task was skipped, started late or repeated – and which delay carries through to the report.
Questions Noreja answers
- Which close tasks are regularly on the critical path?
- Which upstream processes cause most correcting entries?
- Which manual journals recur every month?
- Where are journals posted without the required approval?
- Which entities cause most intercompany differences?
- How much do late incoming invoices delay the close?
Matching agents from the Minerva Agent Library
Frequently asked questions about Record-to-Report
What is the record-to-report process?
Record-to-report (R2R) is the end-to-end process from recording a business transaction in the general ledger to the finished financial report. It covers posting, reconciliation, the period-end and year-end close, and consolidation and reporting.
What is the difference between record-to-report and order-to-cash?
Order-to-cash describes the operational path from customer order to incoming payment. Record-to-report starts where this and other processes post to the general ledger and ends with the financial report.
Which KPIs matter in record-to-report?
Typical KPIs are days to close, the share of manual journals, post-close adjustments, on-time completion of close tasks and open intercompany differences.
Can process mining be used in the financial close?
Yes. Journal entries, manual journals, reconciliations and close tasks leave timestamps and owners in the ERP and in close management tools. Process mining shows the actual flow of the close, waiting times between tasks and control deviations.
Demo cases with a worked-through analysis
End-to-end processes we have played through with findings, causes and measures – some of them touching Record-to-Report.
- Touchless order processingOrder-to-CashHow causal process mining shows which customer orders can run touchless – and where a targeted review protects quality.
- Procurement in special machine buildingPurchase-to-PayFrom internal requirement to payment: how causal process mining makes approval bypasses, rework, capacity dependencies and supplier performance in purchase-to-pay visible and explainable.
- Insurance premium tax (IPT)Premium-to-TaxFrom the insurance premium to the paid tax return: how process intelligence exposes skipped controls, wrong sequences, rework and open tax obligations in insurance premium tax.
Understand your process causally — talk to us
Join companies that are redefining growth and efficiency with intelligent process analysis.