Key points
Record to report (R2R) turns recorded transactions into closed books, financial statements and management reports.
It has five working stages: record, adjust, reconcile, close and consolidate, then report and analyze.
Each stage should leave evidence an auditor can follow, such as signed reconciliations and supported entries.
Usage-based pricing makes R2R harder because revenue and cost of revenue depend on event data outside the ledger.
Unbilled usage and unbilled cloud costs are the two accruals most often missed at month-end.
What record to report means
Record to report (R2R) is the accounting process that turns recorded transactions into closed books and financial statements. It covers capturing activity, posting journal entries, reconciling balances, closing the period, and reporting results. Other processes feed it; R2R is where their output becomes numbers someone signs off on.
Microsoft's process catalog draws R2R as a circle around every other end-to-end process. That is a useful mental model. Order to cash and procure to pay produce the transactions; R2R decides whether they are complete, correct and in the right period.
The five stages and what each one proves
Vendors list anywhere from two to seven steps. The count matters less than knowing what evidence each stage should leave behind.
Stage | What happens | Evidence it should leave |
|---|---|---|
1. Record | Billing, payroll, cards, bank feeds and cloud bills post to the general ledger | Each source has a documented posting rule and completeness check |
2. Adjust | Accruals, deferrals, reclasses and revaluations bring the ledger to accrual basis | Each entry has support, a preparer and a reviewer |
3. Reconcile | Balance sheet accounts are tied to subledgers, bank statements and schedules | Signed reconciliations with reconciling items explained and aged |
4. Close and consolidate | The period is locked; entities are combined and intercompany is eliminated | A close checklist with completion dates and a locked period |
5. Report and analyze | Statements, flux analysis and management reports go to leadership | Variance explanations tied to transactions, not guesses |
How R2R connects to the other finance cycles
R2R does not create most transactions. It receives them from other processes and is only as good as each handoff.
Upstream process | What it hands to R2R | What R2R checks |
|---|---|---|
Quote to cash and order to cash | Invoices, payments, credits, usage records | Revenue timing, deferred and unbilled balances, cash application |
Procure to pay | Vendor bills, purchase orders, payments | Accruals for received but unbilled goods and services |
Hire to retire (payroll) | Payroll journals, benefits, equity grants | Payroll accruals, stock-based compensation, clearing accounts |
Treasury and banking | Bank feeds, transfers, card statements | Bank and card reconciliations, intercompany transfers |
Worked example: one month of R2R at Fieldnote AI
Illustrative only. Fieldnote AI, a fictional Series B company with usage-based pricing, closes October. It bills usage in arrears on the 5th of the following month and pays a cloud provider whose invoice arrives mid-November.
On October 31, the usage database shows 1,000,000 billable credits consumed at $0.04 each. No invoice has gone out, but the service was delivered. The ledger should reflect $40,000 of October revenue.
Account | Debit | Credit |
|---|---|---|
Unbilled accounts receivable | $40,000 | |
Usage revenue | $40,000 |
The cloud console shows $25,000 of October production compute that has not been invoiced. Production hosting belongs in cost of revenue, so it hits gross margin in the month it was consumed.
Account | Debit | Credit |
|---|---|---|
Cost of revenue: production hosting | $25,000 | |
Accrued expenses | $25,000 |
Without these two entries, October revenue is understated by $40,000 and cost of revenue by $25,000. Gross margin would look wrong in both directions, and November would absorb the catch-up. The reconcile stage should then tie unbilled receivables to the usage export and accrued hosting to the console report.
Why R2R is harder with usage-based pricing
With seat-based subscriptions, revenue follows a schedule set at contract signing. With usage, credits or hybrid plans, revenue depends on event data that lives outside the ledger. The R2R process has to pull that data in, test it for completeness, and match it to what billing actually invoiced.
Costs move the same way. Inference and hosting scale with customer activity, so cost of revenue needs the same period discipline as revenue. If either side lags by a month, flux analysis will chase timing noise instead of real changes in margin.
Common mistakes at close and audit
Booking revenue from invoices, not usage. Arrears billing pushes revenue into the wrong month unless unbilled usage is accrued.
Reconciling only cash. Bank recs pass while deferred revenue, unbilled receivables and accruals drift. See account reconciliation.
Cloud bills coded to one expense line. Production, staging and R&D compute end up together, so gross margin is unreliable.
Manual entries with no support. Auditors sample top-side entries first. An entry without a calculation or source file becomes a finding.
Reopening closed periods. Late adjustments after lock change reported numbers and erode trust in the close.
What auditors and boards look for
Auditors test R2R from both ends. They pick reported balances and trace them back to source, and they pick source transactions and trace them forward to the statements. A gap in either direction is a finding.
Completeness of revenue. Can you show every billable usage event became revenue in the right period?
Manual journal entries. Who prepared, who approved, and what supports the amount?
Reconciliation quality. Are reconciling items explained, or carried forward month after month?
Period lock. How many entries were posted after the close, and why?
Boards care about a different symptom. If reported gross margin or revenue changes after the board deck goes out, the R2R process lost a step somewhere.
An R2R checklist for a startup finance team
List every source system that touches the ledger and who owns its posting rule.
Set a completeness test for each: record counts, totals, or a tie-out to the source report.
Define standard accruals for usage revenue, hosting, payroll and contractors.
Assign an owner and reviewer to every balance sheet account.
Write a dated month-end close calendar and lock the period on the last day.
Explain every material movement in revenue, cost of revenue and gross margin before reporting.
How Quanta handles R2R
R2R is Quanta's core process. Quanta's in-house accounting team keeps the ledger, and integrations pull from the customer's usage database, Stripe, Ramp, Rippling and cloud bills. Revenue follows how the company charges, and COGS lines are tagged, so gross margin is visible each close. Finance leads can query the books in Claude through the Quanta MCP, and numbers trace back to journal entries.
Quanta perspective
Most close problems at usage-based companies are timing problems, not math problems. If revenue comes from invoices and cost of revenue comes from bills, gross margin is off every month. Accrue both from the underlying usage, then reconcile to billing.
Frequently asked questions
What is the difference between R2R and the month-end close?
The month-end close is one part of R2R. R2R also covers how transactions are recorded during the month and how results are reported and analyzed afterward.
Who owns the record to report process?
Usually the controller. Accountants run daily recording and reconciliations, and the controller reviews, signs off and owns the close calendar.
How is R2R different from order to cash and procure to pay?
Order to cash and procure to pay generate sales and purchasing transactions. R2R takes those transactions, checks them, and turns them into closed books.
How long should R2R take each month?
It depends on complexity, entity count and automation. The more useful target is a consistent close date with no late reopenings.
What is continuous accounting in R2R?
It means doing reconciliations and accruals throughout the month rather than all at month-end, so the close itself is mostly review.