Record to Report Process: Steps, Owners, Controls

2026-09-24 · Tommaso Maria Ricci

In 2025, US public companies filed 391 financial restatements. That was 18% fewer than the year before and the second lowest count in twenty years, according to the Ideagen Audit Analytics data reported by Accounting Today. Good news, until you read the detail: 70% of those restatements hit income negatively, and the most common cause was debt and equity accounting, which is exactly the kind of judgment call that lives inside the record to report process, not inside any single system.

Record to report, usually shortened to R2R, is the finance process that turns thousands of transactions into numbers people can sign. It starts where operational processes end: order to cash hands over invoices and cash receipts, procure to pay hands over supplier invoices and payments, payroll hands over salary costs. R2R takes all of that, books it, reconciles it, consolidates it and reports it.

Most companies do not have an R2R problem they can name. They have symptoms. The close takes too long. The board pack arrives with numbers that change a week later. The auditors raise the same findings every year. The controller spends the last week of every quarter rebuilding a consolidation in a spreadsheet only one person understands.

This guide treats the record to report process as what it is: a chain of handoffs with named owners. It covers the seven stages and who owns each, the handoffs where accuracy leaks out, the controls that matter, the metrics in causal order, what to automate first, a self-assessment and a 90 day plan. It is written for CFOs, controllers and finance directors at companies between roughly 20 and 500 million dollars in revenue, where the process is big enough to break and small enough to fix.

What is the record to report process

The record to report process is the end to end finance cycle that captures, processes and presents financial information. It begins when a transaction is recorded in a subledger or directly in the general ledger, and it ends when financial statements and management reports are published, reviewed and archived.

In plain terms, R2R answers three questions every period:

Is everything recorded? Every transaction that happened is in the books, in the right period, in the right account.
Is everything right? Balances are reconciled, intercompany matches, estimates are supported, and the numbers tie to external evidence.
Is everything reported? The right people get the right view, on time: management, the board, lenders, tax authorities, regulators and investors.

Record to report vs month end close

People often use the two terms as synonyms. They are not. The month end close is the time boxed sprint inside R2R where the period is locked and the books are finalized. I covered it in detail, with a day by day calendar, in the guide to the month end close process.

R2R is broader. It includes the continuous work that happens every day of the month, such as journal entry processing, reconciliations and master data maintenance, plus what happens after the close: consolidation, statutory and tax reporting, management analysis, audit support and the controls that make all of it reliable. A fast close built on a weak R2R process simply produces wrong numbers sooner.

Record to report vs order to cash and procure to pay

The operational cycles feed R2R. Order to cash produces revenue, receivables and cash. Procure to pay produces expenses, payables and disbursements. When those cycles are clean, R2R is mostly aggregation and review. When they are not, R2R becomes the place where every upstream error is found, investigated and corrected under deadline pressure.

That is why the fastest way to improve R2R is often outside finance. The detailed steps of the revenue side are in the guide to the order to cash process, and the spending side is covered in the article on procure to pay controls.

Why the record to report process matters more in 2026

Three pressures make R2R harder than it was five years ago, and each one lands on the controller's desk.

More entities, more systems

Mid sized companies now routinely operate several legal entities across countries, often on different ERPs after acquisitions. Every additional entity adds intercompany transactions, currency translation, local statutory requirements and another trial balance to consolidate. The process that worked for one entity on one system rarely scales past three.

Fewer people, more expectations

Finance teams are asked to close faster and provide more analysis with the same or smaller headcount. The work that disappears first under pressure is the least visible: reconciliation review, documentation of judgment, cleanup of suspense accounts. That work does not show up in any deadline until an auditor or a lender asks for it.

AI adoption without value

Finance leaders are investing in AI, and the results are uneven. A March 2026 Gartner survey of 204 finance leaders, reported by CPA Practice Advisor, found that 66% of organizations report improved efficiency and productivity from AI, while 63% experienced slower than expected implementation in 2025. Gartner's advice was to measure realized value rather than deployment volume.

In R2R that warning is concrete. An AI tool that drafts reconciliations on top of unclear account ownership and inconsistent master data does not fix the process. It produces confident looking output that someone still has to check.

The benchmark everyone quotes

The most cited close benchmark comes from APQC's General Accounting Open Standards Benchmarking survey. Among roughly 2,300 organizations, top performers completed the monthly close in 4.8 days or less, the median needed 6.4 calendar days, and the bottom quartile needed 10 or more, measured from running the trial balance to completing consolidated statements. The figures were published by CFO.com in 2018, so treat them as an older reference point rather than a current standard. They still describe the shape of the problem well: the gap between the best and the worst is structural, not a matter of working harder.

The seven stages of the record to report process, with owners

Every R2R process I have worked on breaks down into the same seven stages. Names vary by company. What matters is that each stage has one owner who is accountable for its output, even when many people contribute.

|---|---|---|---|

Stage 1: master data and policy

This is the stage nobody puts on the close calendar and everyone pays for later. The chart of accounts, the entity structure, cost centers, the mapping from local to group accounts, and the written accounting policies decide how hard every other stage will be.

The typical failure is slow drift. Someone creates a new account for a one off need. A cost center gets reused for a different purpose. Two entities book the same kind of cost to different accounts. After three years nobody can say with confidence what a given account contains.

Owner: the controller, with a single person authorized to create or change accounts and a documented approval for each change.

Stage 2: transaction capture

Subledgers for receivables, payables, payroll, inventory and fixed assets post to the general ledger. The quality of this stage decides how much of the rest of R2R is review and how much is repair.

The key control is cutoff. A supplier invoice for goods received in March but entered in April, a sales return processed after the period closed, a payroll correction booked late. Each one moves a number between periods, and each one is found, if it is found, in reconciliation or analytical review days later.

Owner: each subledger has its own owner, who confirms completeness and cutoff before the general ledger team starts closing.

Stage 3: journal entries

Accruals, prepayments, allocations, reclassifications and adjustments. Manual journals are where judgment enters the books, and where most errors and most fraud risk sit.

Good practice here is boring and effective. Recurring journals are templated and scheduled. Every manual journal has support attached, a preparer and an approver who is not the same person, and a threshold above which a second review is mandatory. The count of manual journals per period is one of the most useful health indicators of the whole R2R process.

Owner: the general ledger lead, with approval authority matrices defined by the controller.

Stage 4: reconciliation

Every balance sheet account is tied to independent evidence: bank statements, subledger reports, confirmations, schedules. The reconciliation explains any difference, and every open item has an owner and an age.

This is the stage where R2R either protects the company or quietly fails it. A reconciliation that ties to a number with an unexplained plug is worse than no reconciliation, because it creates false comfort. The discipline is simple to write and hard to keep: no unexplained differences, open items aged and escalated, review by someone other than the preparer.

Owner: each account has a named owner. The general ledger lead reviews, and the controller reviews high risk accounts.

Stage 5: intercompany and consolidation

For groups, this is usually the longest and most fragile stage. Intercompany balances must match on both sides, eliminations must be complete, currencies must be translated at the right rates, and minority interests and acquisitions accounted for correctly.

The classic failure is intercompany that does not match at month end because the two entities booked the same transaction at different times, at different rates or in different accounts. Chasing those differences during the close consumes days. The fix is upstream: a single intercompany owner, agreed settlement rules, a monthly matching cycle before the period ends.

Owner: the consolidation lead, often within group reporting.

Stage 6: reporting

Management reports, board packs, lender covenants, statutory accounts in each country, tax filings and, for listed companies, SEC or other regulatory filings. The same underlying numbers are presented in several views, each with its own rules and deadlines.

The risk here is version drift. The management pack is produced from one extract, the lender report from another, the statutory accounts from a third, each with its own manual adjustments. When the numbers disagree, trust disappears. The goal is one set of closed books from which every report is derived, with every adjustment between views documented.

Owner: the financial reporting lead for external reporting, FP&A for management reporting, with a shared data source.

Stage 7: review, controls and audit

Analytical review of results against budget, forecast and prior periods. Sign off by the controller and the CFO. Preparation of the audit file with support for estimates, judgments and significant transactions.

This stage should find surprises, not create them. If the CFO regularly discovers large unexplained variances in the final review, the earlier stages are not doing their job.

Owner: the controller and the CFO, with internal audit or an external auditor testing the controls.

The handoffs where accuracy leaks out

Most R2R problems do not sit inside a stage. They sit between stages, where one team's output becomes another team's input and nobody owns the gap. These are the five handoffs I look at first.

Handoff 1: operations to finance

Budget holders know what was received and not yet invoiced, what contracts changed, what projects were delayed. Finance needs that information to book accruals and estimates. The request usually goes out late, the answers come back later, and the accountant books last month's number plus a guess.

Fix: a fixed request date before period end, a default rule when there is no answer, and a published list of late responders by department.

Handoff 2: subledger to general ledger

The subledger closes, the general ledger team starts, and then a late invoice or a late payroll correction arrives. The subledger reopens, the reconciliation changes, the journal entries are redone.

Fix: a documented subledger lock with a written exception process, and a rule that post lock items go to the next period unless they exceed a materiality threshold.

Handoff 3: entity to entity

Two entities book the same intercompany transaction differently. The difference is discovered during consolidation and resolved by phone calls across time zones.

Fix: intercompany matching as a monthly process with its own deadline before period end, a single owner, and agreed rules on rates and timing.

Handoff 4: preparer to reviewer

Reconciliations and journals pile up in the reviewer's queue in the final days of the close. Review becomes a signature rather than a check.

Fix: spread preparation and review across the month, with risk based review so that high risk accounts get real attention and low risk accounts get a lighter touch.

Handoff 5: accounting to reporting

The books close, and the reporting team discovers that the numbers need adjustments for the management view, the lender definition or the statutory format. Each adjustment is made in a spreadsheet outside the system.

Fix: a documented bridge between the closed books and each report, maintained as part of the process, not rebuilt every period.

Controls that matter in the record to report process

Controls in R2R are often documented for the auditors and ignored in practice. The ones below are the ones that actually prevent errors. For companies subject to SOX, they map directly to key controls over financial reporting under PCAOB Auditing Standard 2201.

Segregation of duties on journals. The person who prepares a manual journal does not approve it, and neither can post it alone above a threshold.
Account ownership. Every balance sheet account has a named owner responsible for its reconciliation.
Reconciliation standards. A written standard for what a complete reconciliation contains, with thresholds for investigation and aging of open items.
Master data change control. Account and entity changes are requested, approved and logged.
Cutoff procedures. Documented cutoff for each subledger, tested periodically.
Intercompany matching. Differences above a threshold are resolved before consolidation, not during it.
Estimate documentation. Every significant estimate has a written method, the data used and the approver.
Management review. Analytical review with defined thresholds and documented explanations for variances above them.
Access controls. Periods are locked after close, and reopening requires approval and leaves a trail.

A useful test: pick three items from last quarter's audit findings and trace which of these controls failed. In most companies the answer points to the same two or three controls every year.

Record to report process metrics, in causal order

Most R2R dashboards start with days to close. That is the last metric in the chain, not the first. Read these from top to bottom: each one drives the ones below it.

|---|---|---|---|

| 1 | Subledger close on time | Whether inputs arrive when planned | Up |

| 2 | Accrual responses on time | Whether operations feeds finance | Up |

| 4 | Reconciliations completed and reviewed on time | Whether balances are verified | Up |

How to use the table

If days to close is too high, do not start by pushing the team to work faster. Look up the table. Late subledgers, late accruals and a high count of manual journals explain most slow closes. If post close adjustments are frequent, look at reconciliations and intercompany, not at the reporting team.

The metric I ask for first in any R2R review is post close adjustments. It is the most honest measure of quality, because it counts how often the books were declared finished and turned out not to be.

Failure modes I see repeatedly

1. The heroic controller. One person knows how the consolidation works, which accounts are sensitive and where the adjustments go. The process runs on their memory. When they are on holiday, the close slips. When they leave, it breaks.

2. The spreadsheet between systems. Consolidation, allocations or the management bridge live in a spreadsheet with hardcoded links and no version control. It works until someone inserts a row.

3. Reconciliations as a signature. Accounts are reconciled to a number with an unexplained plug, reviewed in thirty seconds and signed. The balance looks fine until an auditor asks what the plug is.

4. The suspense account that never empties. Items without a clear home go to suspense, clearing, or a miscellaneous account. The balance grows quietly and gets written off in a year end adjustment nobody can explain.

5. Close speed at the expense of accuracy. The team hits a five day close by pushing estimates and deferring reconciliations. The numbers are on time and then change the next month.

6. Technology before structure. A new close or consolidation tool is implemented on top of an unclear chart of accounts and undefined ownership. The tool automates the confusion.

7. Growth without process redesign. Revenue grows, entities are added, and the R2R process stays the same. In a hotel I worked with, revenue grew from 9M to 10M. Growth of that kind adds transactions, estimates and reporting requests, and finance usually feels it before anyone plans for it.

What to automate in record to report, and what to keep human

Automation pays off in R2R when it removes repetitive work with a measurable error. It fails when it is used to hide unclear ownership. This is the order I recommend.

First: reconciliation matching

Bank reconciliation and high volume account matching are the most mature automation use case. Rules based matching clears the obvious items, leaving people to investigate exceptions. It works best when accounts have owners and standards are written.

Second: recurring journals and allocations

Templated, scheduled journals with automatic support attachment remove a large share of manual entries. Allocations based on defined drivers remove another share. Both reduce the count of manual journals, which is the metric that correlates most with errors.

Third: intercompany matching

Tools that match intercompany transactions continuously during the month, rather than at consolidation, move the work earlier and remove a large part of the close crunch in multi entity groups.

Fourth: close task management

A shared checklist with dependencies, owners and status visible to everyone. It sounds basic. In many companies it is the single change that makes the close predictable.

With care: AI for anomaly detection and commentary

AI is good at flagging unusual entries, unusual balances and unusual variances, and at drafting first versions of variance commentary. The output still needs review by someone who understands the business, and the value should be measured the way Gartner suggests: by fewer post close adjustments and faster reviews, not by the number of models deployed. For a broader view of where AI fits in finance, see the AI for accounting guide.

What stays human

Accounting judgment on estimates and significant transactions. Decisions on policy. Review of high risk accounts. Explanations to the board and auditors. These are the parts of R2R where accountability cannot be delegated to a system, and where the most expensive errors, like the debt and equity issues that lead the restatement data, tend to originate.

If you are trying to decide which parts of your R2R are ready for automation and which need fixing first, an outside view saves time. Send a consultation request through the site with a short description of your entities, systems and current days to close, and we can look at where the process is losing accuracy.

Maturity stages of the record to report process

Stage 1: reactive

The close happens, but differently every month. Reconciliations are done when someone has time. Consolidation lives in a spreadsheet. Reports are rebuilt each period. Audit adjustments are frequent.

Stage 2: documented

A close checklist exists. Accounts have owners. Reconciliation standards are written. Manual journals are approved. The process is slower than it should be but predictable.

Stage 3: managed

Metrics are tracked in causal order. Subledger and accrual inputs arrive on time. Intercompany is matched before period end. Post close adjustments are rare. The close is predictable within a day.

Stage 4: continuous

Reconciliations and intercompany matching run throughout the month. Recurring journals are automated. The close is mostly review. Reporting draws from one source with documented bridges.

Stage 5: integrated

Operational processes feed clean data. Exceptions are flagged automatically. Finance spends most of its time on analysis and decision support rather than on production of numbers.

Most mid sized companies I see sit between stage 1 and stage 2. Getting to stage 3 is where the largest gains in accuracy and time sit, and it rarely requires new software. It requires owners, standards and discipline on handoffs.

Self-assessment: score your record to report process

Answer yes or no. Count the yes answers.

Every balance sheet account has a named owner.
Reconciliations follow a written standard, and no reconciliation contains an unexplained difference.
Open reconciling items are aged, and items older than 60 days are escalated.
Manual journals are approved by someone other than the preparer, with support attached.
You know how many manual journals are posted each period, and the number is falling.
Subledgers close on a documented date and reopen only through a formal exception.
Intercompany balances are matched before period end.
Consolidation is performed in a controlled system, not in a spreadsheet only one person maintains.
Every report is derived from the same closed books, with documented bridges.
Post close adjustments are tracked and are rare.
Chart of accounts changes require approval and are logged.
The close would still run on time if your most experienced accountant were away.

10 to 12 yes. Your R2R is at stage 3 or above. Focus on automation and on moving work earlier in the month.

6 to 9 yes. You have structure but gaps in the handoffs. Start with the items you answered no to, in the order of the list.

0 to 5 yes. The process depends on people rather than design. Start with ownership, reconciliation standards and journal controls before investing in technology.

Record to report in multi entity and international groups

Everything above gets harder when the group spans several countries. Three issues deserve their own attention.

Local statutory and group reporting

Each entity keeps books under local rules for statutory and tax purposes, while the group reports under US GAAP or IFRS. The difference is handled either by keeping two sets of books or, more commonly, by a mapping and a set of adjustments at consolidation. Both work. What does not work is a mapping nobody maintains and adjustments that are rebuilt by hand every quarter.

The practical rule: one owner for the local to group mapping, reviewed whenever an account is added in any entity, and a written list of recurring GAAP adjustments with their method.

Currency

Foreign currency transactions, revaluation of monetary balances and translation of entity results into the group currency are three different steps with three different rate sources. Errors here are rarely large in a single period and often large over a year, because they accumulate in equity and in intercompany differences that never quite clear.

Agree one rate source, one timing rule and one owner. Reconcile the cumulative translation adjustment at least quarterly.

Time zones and calendars

A group with entities in the US, Europe and Asia has a close that never sleeps and never quite aligns. Local holidays, different payroll dates and different bank cutoffs push inputs later in some entities than in others. The group close calendar should be built from the slowest entity backwards, not from the headquarters forwards.

Twenty questions to ask your finance team

Use these in a working session with the controller, the general ledger lead and the consolidation lead. The answers show where the record to report process depends on people rather than design.

Which balance sheet accounts have no named owner today?
Which reconciliation had an unexplained difference last period, and why?
How many manual journals did we post last period, and which ten were largest?
Which subledger closed latest, and what held it up?
Which departments answered the accrual request after the deadline?
What is the balance of our suspense and clearing accounts, and how old is it?
Which intercompany pairs did not match at consolidation?
What adjustments did we make after declaring the books closed?
Which report required manual adjustments outside the system?
Who can change the chart of accounts, and when was it last changed?
Which estimates depend on one person's judgment without a written method?
What did the auditors raise last year that they also raised the year before?
Which step would fail if the controller were away for two weeks?
Which spreadsheet, if lost, would stop the close?
How long does it take to answer a lender's or board member's follow up question?
Which entity consistently delivers its trial balance last?
Where do we re-key data between systems?
Which controls are documented but not actually performed?
What would we automate first if we had the budget tomorrow?
What would we stop doing if we had to close two days faster?

A 30/60/90 day roadmap for the record to report process

Days 1 to 30: measure and assign

Assign a named owner to every balance sheet account and every close task.
Measure the metrics in the table above for the last three periods, even roughly.
Count manual journals and post close adjustments, and list the ten largest.
Map the five handoffs and write down when each input actually arrives.
Write or update the reconciliation standard and the journal approval matrix.

Days 31 to 60: fix the handoffs

Move the accrual request earlier and introduce a default rule for missing answers.
Set a subledger lock date with a written exception process.
Start monthly intercompany matching before period end with a single owner.
Clear or explain every unreconciled item older than 60 days.
Spread reconciliation review across the month with a risk based approach.

Days 61 to 90: automate the routine and stabilize reporting

Template and schedule recurring journals and allocations.
Implement rules based matching on the highest volume accounts.
Build documented bridges from the closed books to each report.
Run a retrospective after each close and publish the metrics.
Decide, with data, which tools to evaluate for consolidation or reconciliation.

If you reach day 60 and find that the hardest decisions are about ownership and policy rather than about tools, that is normal, and it is the point where a second opinion helps most. Send a consultation request through the site describing your entity structure and your current close calendar.

Where record to report connects to the rest of finance

R2R sits at the end of every operational cycle. Improvements in order to cash reduce revenue adjustments and disputed receivables. Improvements in procure to pay reduce late invoices and accrual guesswork. Improvements upstream in sourcing, covered in the guide to the source to pay process, reduce contract driven surprises in the books.

The practical consequence: when you plan R2R improvements, involve the owners of the upstream cycles. A controller can redesign the close alone. A controller cannot fix late accruals, late invoices and inconsistent intercompany without the people who create them.

FAQ

What is the record to report process?

The record to report process, or R2R, is the finance cycle that captures transactions, books them in the general ledger, reconciles balances, consolidates entities and produces financial reports. It starts when subledgers such as receivables, payables and payroll post to the ledger and ends when management, statutory, tax and board reports are published and reviewed. It includes the month end close but also the continuous work during the month and the reporting and audit work after it.

What are the record to report process steps and owners?

There are seven stages. Master data and policy, owned by the controller. Transaction capture, owned by each subledger lead. Journal entries, owned by the general ledger lead. Reconciliation, owned by named account owners and reviewed by the general ledger lead. Intercompany and consolidation, owned by the consolidation lead. Reporting, owned by financial reporting and FP&A. Review, controls and audit, owned by the controller and the CFO.

What is the difference between record to report and month end close?

The month end close is the time boxed period in which the books for a month are finalized and locked. Record to report is the whole cycle around it: master data, daily journal processing and reconciliations during the month, then consolidation, statutory and tax reporting, management analysis and audit support after the close. A fast close built on a weak record to report process produces wrong numbers sooner.

Which record to report metrics should a CFO track?

Track them in causal order. Start with subledger close on time and accrual responses on time, then manual journal entries per period, reconciliations completed and reviewed on time, unreconciled items older than 60 days and intercompany differences. Then post close adjustments, days to close and audit findings. Post close adjustments are the most honest quality measure, because they count how often closed books turned out not to be finished.

What should be automated first in record to report?

Start with reconciliation matching on bank and high volume accounts, then recurring journals and allocations, then intercompany matching during the month and a shared close task list. Use AI for anomaly detection and first drafts of variance commentary, with human review. Keep judgment on estimates, policy decisions and review of high risk accounts human. Automating before accounts have owners and written standards usually automates the confusion.

How long does it take to improve the record to report process?

Most mid sized companies can move from a reactive to a managed process in about 90 days. The first month assigns owners and measures the current state. The second fixes the handoffs: accrual timing, subledger locks, intercompany matching and old reconciling items. The third automates recurring work and stabilizes reporting. Tool selection comes after that, based on measured gaps rather than vendor demos.