Statutory Audit Preparedness: How to Avoid Year-End Chaos
A 90-60-30 day audit plan linking governance, books, systems, confirmations and statutory reporting.
Audit delay usually begins long before the auditor asks the first question. It starts with unreconciled ledgers, missing contracts, poor cut-off, unresolved tax notices and no owner for confirmations. A strong audit plan converts those items into a controlled pre-close programme.
Auditor appointment, eligibility, independence and rotation should be confirmed before fieldwork.
Accounting-software audit trail and edit-log controls are a distinct reporting area.
Schedule III, CARO, IFC, consolidation and branch reporting must be assessed.
Reconciliations and external confirmations should exist before the audit request list arrives.
1. The operating framework
| Timing | Finance focus | Governance/audit focus |
|---|---|---|
| 90 days before close | Clean vendor/customer masters, old balances, fixed assets and intercompany accounts. | Confirm auditor appointment, independence, rotation, reporting framework and component auditors. |
| 60 days before close | Inventory plan, confirmation list, provisions, tax reconciliations and going-concern forecast. | CARO/IFC/applicability memo, Board calendar and legal-letter process. |
| 30 days before close | Cut-off instructions, close checklist, journal approval and document freeze. | Audit-trail system evidence, management representation topics and unresolved-matter escalation. |
| After close | Trial-balance lock, lead schedules, cash-flow and note support. | Board/Audit Committee review, audit differences and signing timetable. |
2. CFO playbook
- Confirm the auditor’s valid appointment, consent, eligibility and ADT-1 position; test rotation thresholds.
- Prepare an accounting-framework memo: AS/Ind AS, Schedule III division, consolidation and component reporting.
- Document CARO 2020 and Section 143(3)(i) IFC applicability instead of assuming based on company type.
- Map every accounting system and interface for audit-trail/edit-log reporting; test that logs were enabled throughout the year.
- Issue bank, customer, vendor, lender and legal confirmations centrally and track exceptions.
- Complete revenue/expense cut-off, inventory, PPE, leases, related parties, provisions, taxes and subsequent-event schedules.
- Maintain an audit-differences log with management decision, materiality and Board/Audit Committee escalation.
3. Practical example
A private company with ₹25 crore paid-up capital assumes auditor rotation is “only for listed companies.” That is incorrect. The prescribed class includes private companies meeting the paid-up-capital threshold, with separate borrowing-based coverage for other companies. Applicability should be documented before reappointment.
4. Common failure points
- Starting confirmation requests after the year-end audit begins.
- Assuming the ERP audit trail covers spreadsheets and satellite systems.
- Leaving related-party completeness to ledger narration searches.
- Not assessing CARO or IFC exemptions in writing.
- Changing signed schedules without version control.
5. Evidence folder
- Auditor appointment/eligibility file
- Accounting-framework and applicability memo
- System and audit-trail map
- Year-end close checklist
- External confirmation tracker
- Lead schedules and reconciliations
- Audit-differences and representation log
6. Finin2min takeaway
Design the evidence before the transaction.
Reliable compliance is the result of clear ownership, timely action, reconciled records and a documented escalation route—not a last-minute filing exercise.