The difference between a two-week audit and a six-week audit is rarely the size of the company — it's how much of the auditor's "please provide" list was ready on day one. Most of the checklist below can be prepared well before year-end closes.
Timeline: Start 4-6 Weeks Before Fieldwork
| Timing | Activity |
|---|
| At year-end (Day 0) | Finalise bank reconciliations for the year-end date; send confirmation requests to banks, debtors, creditors, lenders, and legal counsel |
| Week 1-2 post year-end | Prepare schedules (fixed assets, receivables/payables ageing, inventory, provisions); complete the financial close |
| Week 2-3 | Internal review of schedules against trial balance; resolve any prior-year audit observations |
| Week 3-4 | Compile related party transaction summary and tax reconciliation; organise documentation in the format requested by the auditor's PBC (prepared-by-client) list |
| Fieldwork begins | All schedules, confirmations (or follow-ups in progress), and supporting documents ready for the audit team |
Core Schedules to Prepare
- Trial balance mapped to financial statements: Each GL account mapped to its line item in the Schedule III format balance sheet and P&L
- Fixed asset schedule: Opening balance, additions, disposals, and depreciation for both books (Schedule II) and tax (block of assets) — see the depreciation comparison guide for why these differ
- Receivables and payables ageing: Aged by bucket (0-30, 31-60, 61-90, 90+ days), with related party balances flagged separately
- Inventory listing: Quantities and values by category, with slow-moving/obsolete items identified for NRV assessment (see inventory valuation methods)
- Loan/borrowing schedule: Opening balance, drawdowns, repayments, interest, and covenant compliance status (see DSCR & ICR covenants)
- Provisions and contingencies: Workings for provisions (gratuity, leave encashment, warranty, etc.) and a list of contingent liabilities (pending litigation, disputed tax demands, guarantees given)
- Related party transaction summary: All transactions and balances by related party, cross-referenced to board/audit committee approvals — see related party disclosure requirements
- Tax reconciliation: Book profit to taxable income reconciliation, including all permanent and timing differences
Third-Party Confirmations: Send Early
⚠ Confirmations are often the critical path. Bank balance confirmations, debtor/creditor confirmations, loan confirmations, and legal confirmations (from advocates regarding pending litigation) typically take 2-4 weeks to come back. Under SA 505, auditors rely on these as external evidence — if requests go out only after fieldwork starts, they become the single biggest cause of audit delays. Send them at or immediately after the year-end date.
| Confirmation Type | From Whom | Why It Matters |
|---|
| Bank balance | All banks where accounts are held | Independent verification of cash and borrowing balances |
| Debtor balances | Significant customers | Confirms receivables are real and not in dispute |
| Creditor balances | Significant suppliers, especially related parties | Confirms payables completeness |
| Loan confirmations | Lenders/NBFCs | Confirms outstanding balances and covenant status |
| Legal confirmations | Company's advocates | Identifies pending litigation for contingent liability disclosure |
Internal Readiness Checks
- Resolve prior-year observations: Auditors will follow up on last year's management letter points — having these closed (or a clear remediation status) avoids re-litigating old issues
- Pre-identify judgmental areas: Revenue recognition cut-offs, provisioning estimates, and impairment assessments should be discussed with the audit team early, not surfaced for the first time during fieldwork
- Organise documentation centrally: A shared folder structure matching the auditor's PBC list, rather than scattered emails, saves significant coordination time
- Brief the team: Ensure the people who'll field auditor questions (AP, AR, payroll leads) know the audit timeline and have their areas ready
How This Connects to IFC
Many of the items above — segregation of duties evidence, reconciliation timeliness, related party identification — are also core to Internal Financial Controls documentation. Companies that maintain IFC documentation throughout the year find statutory audit preparation considerably lighter, because the control evidence the auditor needs has already been gathered as part of routine IFC testing rather than assembled specially for the audit.
Frequently Asked Questions
What schedules should be prepared before the statutory auditors arrive? ▼
Key schedules include a trial balance mapped to financial statements, fixed asset schedules (book and tax depreciation), receivables/payables ageing with related parties flagged, inventory listings with slow-moving items identified, loan schedules with covenant status, provisions and contingent liability workings, related party transaction summaries, and a book-to-tax reconciliation. Preparing these in the auditor's requested format reduces back-and-forth during fieldwork.
Why do auditors need third-party confirmations and how far in advance should they be sent? ▼
Confirmations from banks, debtors, creditors, lenders, and legal counsel provide independent audit evidence under SA 505. They often take 2-4 weeks to come back, so requests should be sent at or shortly after year-end — well before fieldwork begins — so responses are available when needed rather than becoming a bottleneck.
What are the most common reasons statutory audits get delayed? ▼
Common causes include unreconciled schedules handed over at the start of fieldwork, incomplete year-end bank reconciliations, related party transactions not pre-identified, pending third-party confirmations, unresolved prior-year audit observations, and last-minute accounting judgment changes. Starting the checklist 4-6 weeks before fieldwork avoids most of these.