Audit File Checklist
Build an audit file with reconciled balances, support schedules, source documents, and review notes before auditors request the same evidence twice.
- An audit file should include a final trial balance, reconciliations, support schedules, source documents, and explanations for material movements.
- The file should be built before fieldwork starts so audit queries do not interrupt normal month-end work.
- The strongest audit files are organised by balance-sheet and income statement area, not by random document folders.
- Management should review unusual balances and judgement areas before the file is handed to auditors.
An audit file checklist is useful because it turns audit preparation into a controlled finance process instead of a document chase. When the file is organised before fieldwork starts, the business can answer questions from reconciled records rather than from memory.
The file should not be a loose folder of exports. It should show how the financial records connect: trial balance to reconciliation, reconciliation to supporting schedule, schedule to source document, and source document to management explanation where judgement is involved. That structure supports audit readiness because it makes the file reviewable before the auditor asks for evidence.
What a complete audit file should prove
A complete audit file should prove four things.
- The accounting records are complete for the period under review.
- Material balances have been reconciled and reviewed.
- Significant transactions have support and approval.
- Management can explain judgement areas and unusual movements.
This standard applies whether the work is for a statutory audit, independent review, lender request, due diligence exercise, or year-end support pack. The depth of work may differ, but the logic is the same. A reviewer needs enough evidence to understand the numbers without reconstructing the accounting file from scratch.
Core audit file index
Use the index below as the starting structure for the file.
| File area | What to include | Review test |
|---|---|---|
| Trial balance | Final trial balance, general ledger, prior-year comparative reports | Does the ledger agree to the reporting pack? |
| Bank and cash | Bank statements, reconciliations, petty cash, credit card schedules | Are old reconciling items explained or cleared? |
| Debtors | Age analysis, customer reconciliations, doubtful debt notes | Do trade balances agree to the ledger? |
| Creditors | Supplier age analysis, statements, accrual support | Are unpaid balances complete and supportable? |
| Fixed assets | Asset register, invoices, disposal evidence, depreciation schedule | Does the register agree to the trial balance? |
| Loans and funding | Agreements, statements, movement schedules, interest support | Are current and non-current portions explained? |
| Tax and statutory | VAT, PAYE, income tax, SARS correspondence, CIPC records | Do control accounts agree to filings and payments? |
| Revenue and expenses | Cutoff support, major contracts, unusual costs, payroll summaries | Are material movements explainable? |
This index should be adapted to the business. A services company may need stronger revenue cutoff support. A contractor may need work-in-progress schedules. A retail business may need stock support. The file should follow the risk profile of the business, not a generic folder structure.
1. Lock the reporting period and file version
The first control is version discipline.
Before the audit file is circulated, confirm the reporting period, accounting software export date, trial balance version, and person responsible for final changes. If journals continue after the file is shared, the audit team may test one version while finance answers questions from another. That creates avoidable confusion.
The file should include:
- final trial balance for the period
- general ledger detail for material accounts
- prior-year trial balance or signed annual financial statements
- list of year-end journals posted after management review
- summary of unresolved items, if any
This is also where financial statements preparation and audit preparation overlap. If the statements are being drafted from a moving trial balance, the audit file will keep changing and review work will slow down.
2. Reconcile cash before reviewing anything else
Cash control is usually the fastest indicator of file quality.
Every bank account, credit card, petty cash account, and payment platform balance should reconcile to an external statement or support record. Old unreconciled items should not sit silently in the file. They should be cleared, explained, or escalated before the audit starts.
For each cash account, include:
- year-end statement
- reconciliation report
- list of old outstanding items
- explanation for unusual transfers
- confirmation of accounts opened or closed during the year
Where bank reconciliations are weak, use the bank reconciliation checklist before preparing the audit file. A clean audit pack cannot sit on unreconciled cash.
3. Build balance-sheet schedules that agree to the ledger
The balance sheet carries many of the audit file questions.
Debtors, creditors, loans, director balances, fixed assets, VAT, payroll, accruals, prepayments, and provisions all need schedules that agree to the trial balance. The schedule should not be a separate spreadsheet that almost agrees. It should tie exactly, or the reconciling difference should be explained.
| Balance-sheet area | Minimum schedule requirement | Common weakness |
|---|---|---|
| Debtors | Age analysis with notes on stale or disputed balances | Old balances carried without collection assessment |
| Creditors | Supplier listing with statement support for material accounts | Missing accruals or old credits unexplained |
| Fixed assets | Register with additions, disposals, depreciation, and net book value | Ledger and register not agreeing |
| Loans | Opening balance, movements, interest, repayments, closing balance | No agreement or unclear classification |
| VAT and payroll | Control account reconciliation to submissions and payments | Ledger balance not agreeing to statutory records |
This section should connect to the annual financial statements checklist. If a balance will appear in the financial statements, the audit file should already explain how it was built.
4. Prepare income statement support by exception and materiality
The income statement does not need a document for every small transaction, but it does need clear evidence for material and unusual items.
Prepare support for:
- revenue streams and cutoff around year-end
- large once-off supplier costs
- payroll summaries and reconciliations
- rental, finance, insurance, and service contracts
- legal, consulting, or unusual professional fees
- provisions, impairments, and other judgement-based expenses
The goal is to prevent repeated audit queries. If a material expense changed sharply from the prior year, the file should include the reason. If revenue recognition depends on contracts, delivery milestones, or customer acceptance, the support should be available before the review starts.
5. Add management explanations where evidence alone is not enough
Some audit questions cannot be answered by documents alone. The business may need to explain why a customer balance is still recoverable, why a related-party loan changed, why a once-off cost was incurred, or why a provision was estimated in a specific way.
Use short management notes for:
- unusual balance-sheet movements
- director or shareholder transactions
- disputed customer or supplier balances
- estimates, impairments, provisions, and accruals
- post-year-end events that affect interpretation
These notes do not replace evidence. They give context to evidence. They also protect management from trying to reconstruct decisions months later.
6. Include tax, compliance, and statutory support
Audit files often slow down when tax and statutory records sit outside the finance pack.
For South African businesses, the audit file should normally include the relevant SARS records, tax control reconciliations, payroll submission support, VAT return support, CIPC records, and correspondence that affects the reporting period. If a tax clearance issue, payment arrangement, or filing backlog affects the business, the file should make that visible.
This matters where financial reporting and compliance evidence are requested together, especially for lenders, tenders, and governance reviews. If tax clearance depends on the same underlying records, the audit file should not ignore those balances.
7. Use a review framework before handover
Before the audit file is handed over, run a simple internal review.
- Confirm the trial balance is the correct final version.
- Check that every material balance has a schedule.
- Check that every schedule agrees to the ledger.
- Confirm source documents exist for material movements.
- Confirm management explanations exist for judgement areas.
- Identify open items and assign owners.
- Hold the file until unresolved items are either fixed or disclosed as open.
This framework prevents the most common handover problem: sending a large folder before anyone has tested whether it answers the obvious questions.
8. Connect the audit file to the monthly close
The audit file should not be built from nothing once a year.
The best source is a disciplined monthly close. Bank reconciliations, debtor and creditor reviews, VAT control checks, payroll reconciliations, fixed asset updates, and management explanations should already exist during the year. That is why management accounts are part of audit readiness. They keep the business close to the numbers before the formal review begins.
Bookkeeping also matters. If bookkeeping is behind, the audit file becomes a repair project. Missing allocations, unreconciled bank feeds, and incomplete supplier records will show up again during audit preparation.
Common audit file failures
The same failures appear repeatedly.
| Failure | Why it slows the audit | Better control |
|---|---|---|
| Random document folders | Reviewers cannot trace evidence to balances | Index documents by financial statement area |
| Schedules do not agree to the trial balance | Finance must reconcile during fieldwork | Tie schedules before handover |
| Old unreconciled items remain open | Auditors ask repeated follow-up questions | Clear or explain items before review |
| Management review happens late | Commercial explanations arrive under pressure | Review judgement areas before handover |
| Tax balances sit outside the file | Compliance questions interrupt reporting work | Reconcile statutory accounts with the audit file |
These failures are avoidable because they are process issues. They usually do not require new software. They require ownership, timing, and review discipline.
Practical audit file handover standard
A practical handover standard is simple: no material balance should be sent without a route to evidence.
That route should show the ledger balance, the supporting schedule, the source documents, and the management explanation where needed. If that route is missing, the file is not ready. It may be large, but it is not useful.
An audit file built this way reduces rework, protects normal finance operations, and gives management a clearer view of whether the accounting records are ready for external scrutiny. It also leaves the business with a reusable year-end file that can support financial statements, lender requests, procurement questions, and the next close cycle.