Accounting
ERP
Financial Management
Record-to-Report Process: How Finance Teams Close and Report
Last updated: October 8, 2026 · Independent guide · We do not sell rankings or coverage.
The record to report process is the end-to-end finance workflow that turns individual transactions into reviewed, published financial statements. It runs from subledger capture and journal entries, through account reconciliations and consolidation, to the reports that go to management, lenders, boards and, for public companies, the SEC. The month-end close is the most visible part of record to report (R2R), but R2R also covers the ownership, controls and systems around it.
This guide is written for controllers and finance managers at US mid-sized companies. It describes each stage, who should own it, the controls that matter, and where the process usually breaks. For a deeper look at the close itself, see our guides to ERP for financial close and accounting close automation.
The six stages of record to report
- Capture and subledger close. Transactions post from billing, payables, payroll, inventory, banking and fixed assets, and each subledger is cut off and locked for the period.
- Journal entries and adjustments. The accounting team books accruals, deferrals, allocations, reclassifications and other entries the subledgers do not create.
- Account reconciliations. Every balance sheet account is tied to independent support, and differences are explained or corrected.
- Intercompany and consolidation. Intercompany balances are matched and eliminated, foreign currency balances are revalued and translated, and entities are rolled into consolidated results.
- Review, flux analysis and period lock. The controller reviews the trial balance, investigates variances, approves late entries and locks the period.
- Financial reporting. The team produces statements, management packs, lender covenant reports and, where required, SEC filings.
Some vendors add a separate “data collection” or “audit” stage. The work is the same. What matters is that every stage has a named owner, a defined output and a control that proves it was done.
Who owns each stage
The table below is a RACI-style summary for a typical US mid-sized company with a controller, an assistant controller or accounting manager, and staff or senior accountants. Treat the roles as functions rather than job titles, and keep preparer and reviewer separate on every stage.
| Stage | Responsible (prepares) | Accountable (reviews and signs off) | Main output |
|---|---|---|---|
| 1. Capture and subledger close | AP, AR, payroll and inventory staff | Accounting manager | Locked subledgers tied to the general ledger |
| 2. Journal entries | Staff and senior accountants | Accounting manager (controller above a set threshold) | Approved entries with support attached |
| 3. Reconciliations | Account owners | Accounting manager or assistant controller | Signed reconciliations with aged reconciling items |
| 4. Intercompany and consolidation | Senior or consolidation accountant | Controller | Consolidated trial balance with eliminations |
| 5. Review and lock | Accounting manager | Controller | Explained variances and a locked period |
| 6. Reporting | Controller or reporting lead, with FP&A | CFO | Financial statements, management pack, covenant and SEC reports |
Operations, HR and FP&A are consulted on accruals, cutoff and variances. Auditors, lenders and the board are informed through the published reports.
Stage 1: Capture and subledger close
Inputs: invoices, bills, payroll registers, bank feeds, inventory movements, fixed asset additions and disposals. Output: subledgers that are cut off at period end and agree to their general ledger control accounts.
The key control is a period lock by subledger. Oracle NetSuite’s Period Close Checklist, for example, starts with tasks to lock accounts receivable, accounts payable and payroll so no more transactions post to the period, and in its OneWorld edition you can lock by subsidiary (Oracle NetSuite documentation, no date shown).
What goes wrong: late vendor invoices, shipments recorded in the wrong period, and inventory transactions with dates that do not match their posting period. A cutoff policy shared with operations before period end prevents most of these.
Stage 2: Journal entries and adjustments
Inputs: locked subledgers, accrual support, contracts, allocation drivers. Output: approved journal entries that bring the ledger to an accrual basis.
Typical entries include expense accruals for goods and services received but not billed, prepaid amortization, depreciation, payroll and bonus accruals, revenue recognition and deferral, and cost allocations. Recurring entries that follow a fixed schedule should be templated or generated by the system.
Controls: segregation of duties between preparer and approver, a dollar threshold above which the controller approves, mandatory supporting documents, and a regular review of manual entries posted by unusual users or at unusual times. What goes wrong: entries posted without support, entries that the preparer also approves, and top-side adjustments made in a spreadsheet consolidation that never reach the ledger.
Stage 3: Account reconciliations
Inputs: trial balance, bank statements, subledger reports, schedules for prepaids, accruals, fixed assets and debt. Output: a reconciliation for every balance sheet account, signed by a preparer and a reviewer, with each reconciling item explained and aged.
A common approach is to rank accounts by risk and balance size. High-risk accounts such as cash, revenue-related balances and intercompany are reconciled monthly with full review. Low-risk, low-balance accounts may be reconciled quarterly. Write the policy down.
What goes wrong: reconciliations that show a balance but do not prove it, unexplained items that roll forward for months, and “plug” entries to force a tie-out. Escalate reconciling items older than 60 or 90 days.
Stage 4: Intercompany and consolidation
Inputs: entity trial balances, intercompany schedules, exchange rates, ownership percentages. Output: a consolidated trial balance with eliminations, translation adjustments and, where relevant, noncontrolling interest.
The accounting rule behind this stage is ASC 810-10-45-1, which states that “intra-entity balances and transactions shall be eliminated” when you prepare consolidated statements, including open account balances, security holdings, sales and purchases, interest and dividends (quoted in PwC Viewpoint, no date shown). Subsidiaries reporting in another currency also need translation under ASC 830, which creates a cumulative translation adjustment in equity.
Systems handle this stage very differently. In Microsoft Dynamics 365 Business Central, the consolidated company is a separate company that combines business unit ledgers, and eliminations are entered as general journal lines and previewed with the G/L Consolidation Eliminations report before posting (Microsoft Learn, April 7, 2026). NetSuite OneWorld runs currency revaluation, consolidated exchange rates and intercompany elimination as checklist tasks, and warns that consolidated rates cannot be changed once that task is marked complete (Oracle NetSuite documentation, no date shown). Sage Intacct markets automated eliminations, ownership structures that change by period, and automated cumulative translation adjustments for ASC 830 (Sage, no date shown). See our guide to ERP for multi-entity and global accounting for entity design.
What goes wrong: one side of an intercompany transaction is booked and the other is not, the two entities use different exchange rates or dates, or a transaction is coded to the wrong partner entity. Agree balances between entities before the consolidation deadline.
Stage 5: Review, flux analysis and period lock
Inputs: consolidated and entity trial balances, prior period and budget figures, reconciliation status. Output: explained variances, approved late adjustments and a closed period.
Flux analysis compares each account against the prior month, the prior year and the budget, and requires a written explanation above a set threshold, for example a percentage change combined with a minimum dollar amount. The controller then signs off and the period is locked. In NetSuite, the final Close task excludes all posting transactions, and changes require the period to be reopened (Oracle NetSuite documentation, no date shown).
What goes wrong: periods left open for weeks, so balances shift after reports are issued; review that happens only at the consolidated level and misses offsetting errors in individual entities; and post-close entries with no reopen approval.
Stage 6: Financial reporting
Inputs: locked consolidated ledger, account mappings, disclosure support. Output: balance sheet, income statement, cash flow statement, management reporting pack, and lender or board reports.
Private mid-sized companies usually report to management, owners and lenders, often with covenant certificates due a set number of days after period end. Public companies face fixed SEC deadlines. Form 10-Q is due 40 days after quarter end for large accelerated and accelerated filers and 45 days for all other registrants (SEC Form 10-Q General Instructions, revision 02-25). Form 10-K is due 60, 75 or 90 days after fiscal year end depending on filer status (SEC Form 10-K General Instructions, revision 02-25).
Public companies also carry Sarbanes-Oxley obligations across the whole R2R process. Every issuer, including non-accelerated filers, must include management’s report on internal control over financial reporting under Section 404(a), while non-accelerated filers are exempt from the auditor attestation under Section 404(b) (SEC Release 33-9142, September 15, 2010). Many companies document those controls against the COSO Internal Control Integrated Framework, updated in 2013 (COSO, no date shown). For reporting tools and dashboards, see our guide to ERP reporting and analytics.
What goes wrong: statements rebuilt by hand in spreadsheets, numbers re-keyed into board decks, and unreviewed mapping changes that put an account on the wrong line.
Metrics to track
Close cycle time is the headline metric, but it should not be the only one. APQC’s Open Standards Benchmarking measure “Cycle time in days to complete monthly financial close” shows a cross-industry median of 8.0 days on a sample of 3,389 (APQC, no date shown). Pair speed with quality measures.
| Metric | How to measure it | What it tells you |
|---|---|---|
| Days to close | Business days from period end to period lock | Overall speed of the close |
| Days to report | Business days from period end to issued management pack | How quickly leadership receives numbers |
| Manual journal entries | Count and value of non-system entries per period | Candidates for automation and higher-risk entries |
| Post-close adjustments | Entries posted after lock, and auditor adjustments | Quality of the first close |
| Reconciliation status | Percentage completed and reviewed on time; value of items older than 60 days | Hidden balance sheet risk |
| Intercompany differences | Unmatched intercompany value at consolidation cutoff | Entity discipline and consolidation risk |
How software supports each stage
Stages 1 and 2: the ERP or accounting system. Subledgers, recurring entries, approval workflows and period locks belong in the core system.
Stage 3: close and reconciliation tools. BlackLine and FloQast sit on top of the ERP to manage checklists, reconciliations and sign-offs. BlackLine describes automated matching and exception handling for high-frequency reconciliations (BlackLine, no date shown). FloQast lists close management, reconciliations and a separate risk and compliance package covering controls and audit readiness, and lists ERP-specific solutions for NetSuite, SAP, Workday, Microsoft, Sage Intacct and Xero (FloQast, no date shown). Neither vendor publishes prices, and their customer results are vendor claims rather than independent measurements.
Stage 4: native ERP consolidation or a dedicated tool. If your entities share one ERP instance, native consolidation is usually enough. Business Central’s manual eliminations suit a few entities. Many entities, partial ownership or frequent restructuring point toward the automated eliminations in NetSuite OneWorld or Sage Intacct, or a separate consolidation product.
Stages 5 and 6: reporting and disclosure. Financial statements and management packs usually come from the ERP’s report writer or a reporting layer on top of it. SEC filers often add disclosure management software. Workiva, for example, supports 10-K and 10-Q preparation, XBRL tagging and linking data from source systems to create a single source of truth, and does not publish pricing (Workiva, no date shown).
How we researched this
We read the top-ranking pages for “record to report process” in October 2026. Most come from close software vendors or outsourcing providers, and none gave a stage-by-stage ownership model, the rules behind each stage, or a neutral view of how ERPs differ at consolidation. We then checked vendor documentation, SEC forms and releases, PwC’s summary of ASC 810 and APQC benchmark data. No vendor paid for inclusion.
Related guides
- Month-End Close Checklist Template (2026)
- Trial Balance Template: Prepare, Check and Fix It
- Flux Analysis: Month-End Thresholds and Explanations
Frequently asked questions
What is the difference between record to report and the month-end close?
The month-end close is the set of tasks that finalize the books for one period. Record to report is the wider process that includes the close, plus the transaction capture before it, the consolidation and reporting after it, and the controls and ownership that run all year.
Who owns the record to report process?
The controller usually owns R2R and is accountable for the closed books and the financial statements. The CFO is accountable for the reports that go to the board, lenders or the SEC. Individual stages are delegated to accounting managers and account owners, with a separate reviewer for each.
How long should the record to report cycle take?
APQC’s open benchmark for monthly close cycle time shows a cross-industry median of 8.0 days. Public companies must also fit quarterly and annual SEC filing deadlines of 40 to 90 days, depending on filer status.
Do private companies need SOX controls in their R2R process?
Sarbanes-Oxley Section 404 applies to SEC registrants, not to private companies. Private companies still benefit from documented controls, because external auditors, lenders and potential acquirers often ask to see them.
Do we need a separate close tool if we have an ERP?
Not always. A single-entity company with a modern ERP can often run the close from the ERP checklist and a reconciliation workbook. A separate tool tends to pay off with many accounts, several entities, or audit findings about reconciliation evidence.
Sources
- Oracle NetSuite, Using the Period Close Checklist, no date shown, checked October 8, 2026. docs.oracle.com
- Microsoft, Consolidate financial data from multiple companies (Business Central), April 7, 2026. learn.microsoft.com
- Sage, Sage Intacct consolidation accounting (vendor page), no date shown, checked October 8, 2026. sage.com
- PwC Viewpoint, Consolidation guide, section 8.2 intercompany transactions (quotes ASC 810-10-45-1), no date shown. viewpoint.pwc.com
- SEC, Form 10-Q General Instructions, revision February 2025. sec.gov
- SEC, Form 10-K General Instructions, revision February 2025. sec.gov
- SEC, Release 33-9142, Internal control over financial reporting in exchange act periodic reports of non-accelerated filers, September 15, 2010. sec.gov
- COSO, Guidance on internal control, no date shown, checked October 8, 2026. coso.org
- APQC, Cycle time in days to complete monthly financial close (Open Standards Benchmarking), no date shown, checked October 8, 2026. apqc.org
- BlackLine, Account reconciliations (vendor page; BlackLine sells close software), no date shown, checked October 8, 2026. blackline.com
- FloQast, Pricing (vendor page; FloQast sells close software), no date shown, checked October 8, 2026. floqast.com
- Workiva, SEC reporting (vendor page; Workiva sells reporting software), no date shown, checked October 8, 2026. workiva.com
Sherman Hsieh
Independent analysis of enterprise software — ERP, CRM and more
