R2R Internal Audit Checklist: Record-to-Report RCM for Month-End Close
Record-to-report internal audit tests whether the books close completely, accurately and on time. The R2R cycle covers journal entries, account reconciliations, provisions, estimates, intercompany balances, financial-statement mapping and management reporting. It is the bridge between transaction processing and the financial statements.
The core R2R audit question is simple: can management prove that every material balance in the trial balance is supported, reviewed and correctly reported? The checklist below is an illustrative RCM starting point. The actual close calendar, account-ownership model and review cadence should be set by the entity's internal-audit scope and risk assessment.
R2R RCM: core risks and controls
| Sub-process | Risk | Control | Internal audit test |
|---|---|---|---|
| Chart of accounts | Wrong account mapping or duplicate ledgers | COA creation and mapping should be approved by finance controller | Test new ledgers and Schedule III mapping |
| Journal entries | Unauthorised or unsupported manual JE | JE workflow should require preparer, reviewer, support and reason code | Test high-risk JEs: weekend, post-close, round amount, unusual users |
| Accruals and provisions | Expenses understated or estimates unsupported | Provision checklist and review sign-off should run at close | Compare accruals to subsequent invoices and prior-period trend |
| Account reconciliation | Control accounts not reconciled | Balance-sheet reconciliation tracker should carry owner and due date | Test bank, GST, TDS, AP, AR, loans, payroll, intercompany |
| Intercompany | Group balances do not eliminate | Intercompany confirmation and matching should run before group reporting | Compare reciprocal ledgers across entities |
| Close calendar | Delayed or backdated close | Close checklist should define task owners and lock date | Check late entries and reopen events after close |
| Financial reporting | Wrong classification in financial statements | Trial balance should be mapped to Schedule III / Ind AS captions | Test high-value and judgemental mappings |
| MIS reporting | Board pack differs from books | MIS should be generated from controlled source data or reconciled back to books | Reconcile MIS to TB and approved adjustments |
Journal entry testing
R2R audit lives or dies on journal-entry testing. A random sample is weak because risky entries are not random. Use risk filters first.
High-risk JE filters:
- Posted on weekends or holidays
- Posted after the month-end close date
- Posted by users outside finance
- Posted by preparer and approver from same user ID
- Round numbers above materiality or internal threshold
- Debits to revenue or credits to expense
- Manual entries to cash, bank, GST, TDS, payroll, inventory or fixed assets
- Narrations containing adjustment, provision, reclass, rectification, reversal or suspense
- Entries posted and reversed shortly after period-end
Reportable observation example: 43 manual journal entries worth ₹2.8 crore were posted after the monthly close lock date. 12 had no supporting file attached in the ERP. The close-control design exists, but operating effectiveness is weak.
Balance-sheet reconciliation checklist
Every material balance should have an owner, a support file and a reviewer sign-off.
| Area | Minimum support |
|---|---|
| Bank | Bank reconciliation, outstanding cheques, stale items, bank confirmation |
| Accounts receivable | Ageing, confirmations, credit notes, ECL/provision working |
| Accounts payable | Vendor ageing, debit balances, MSME classification, supplier statements |
| GST | GSTR-1/3B/2B reconciliation, ITC reversals, RCM working |
| TDS/TCS | Books vs returns vs Form 26AS/AIS reconciliation |
| Payroll liabilities | PF/ESI/PT/TDS payable vs challans |
| Loans | Sanction terms, interest recomputation, confirmation, covenant status |
| Fixed assets | FAR, additions/disposals support, depreciation recomputation |
| Intercompany | Counterparty confirmation and elimination difference |
| Provisions | Basis, assumptions, ageing and subsequent settlement |
Month-end close testing
The close process should be tested as a process, not as a pile of account schedules.
- Is there a formal close calendar?
- Are close tasks assigned to named owners?
- Are reconciliations reviewed before reporting?
- Are late entries logged and approved?
- Is the accounting period locked after close?
- Are reopen events tracked with reason and approver?
- Does the MIS reconcile to the final trial balance?
- Are prior-period adjustments separately identified?
R2R observations that matter
Strong R2R reporting focuses on root cause. Examples:
- Close calendar exists but is not enforced because ERP periods remain open.
- Reconciliation tracker is maintained, but reviewer sign-off is not evidenced.
- Provisions are booked based on management estimate without subsequent validation.
- Intercompany balances are reconciled only at year-end, causing recurring elimination differences.
- MIS numbers are adjusted outside the ERP, with no controlled bridge back to books.
R2R audit data fields to request
R2R fieldwork should start with the close evidence, not only the signed financial statements.
| Data table | Minimum fields |
|---|---|
| Trial balance | Ledger code, ledger name, opening balance, period debit/credit, closing balance, Schedule III caption |
| Journal entries | JE number, date, posting date, user, approver, narration, debit/credit ledgers, amount, attachment flag |
| Close calendar | Task, owner, due date, completion date, reviewer, reopen events |
| Reconciliation tracker | Account, owner, preparer date, reviewer date, unreconciled items, ageing |
| Provisions | Basis, computation, approval, prior-period comparison, subsequent settlement |
| MIS bridge | MIS line item, TB source, manual adjustment, approver, board-pack reference |
R2R internal audit FAQ
What is R2R in internal audit?
R2R, or record-to-report, is the internal audit cycle covering month-end close, journal entries, reconciliations, provisions, estimates, financial-statement mapping and management reporting.
What are the most important R2R controls?
The key controls are controlled chart-of-account creation, maker-checker approval for journal entries, balance-sheet reconciliation with reviewer sign-off, a formal close calendar, period lock and a documented bridge from books to MIS or financial statements.
Why is journal-entry testing central to R2R audit?
Manual journal entries can override normal transaction controls. Internal audit should therefore test risky populations such as post-close entries, weekend postings, round numbers, unusual users, revenue debits, expense credits and entries reversed shortly after period-end.
Related CORAA resources
- Internal Audit Software for India
- Journal Entry Risk Scorer
- Schedule III Mapping Validator
- Enterprise Intelligence and Business DNA
Sources
- ICAI Internal Audit Standards Board, Compendium of Standards on Internal Audit - as on February 2026 and listed by ICAI as applicable from 1 April 2026
- Companies Act, 2013, Section 138 and Section 143(3)(i)
- ICAI Guidance Note on Audit of Internal Financial Controls over Financial Reporting
- MCA, Schedule III to the Companies Act, 2013