How to prepare for an audit of your financial statements: 7 steps

A receivables schedule for the wrong date sends the reviewer back with another question. So does a debt balance submitted without its supporting agreements. Audit preparation is about making balances traceable, not simply collecting files. The same discipline applies when a business is preparing for a sale, a divestiture or a merger, because buyers, lenders and auditors all ask for the same thing: evidence they can follow. Start with the auditor’s requests, reconcile the underlying records and assign responsibility for each response.

Photo by Towfiqu barbhuiya from Pexels: https://www.pexels.com/photo/pen-calculator-and-magnifying-glass-on-documents-13156204/
Photo by Towfiqu barbhuiya from Pexels: https://www.pexels.com/photo/pen-calculator-and-magnifying-glass-on-documents-13156204/

1. Confirm the scope and work backward from key dates

Agree which entities and reporting periods the audit covers, the applicable financial reporting framework and the expected reporting deadline. Establish milestones for closing the accounts, delivering schedules and answering follow-up questions.

Discuss matters that need advance coordination before fixing the timetable. Inventory observation and evidence supporting opening balances in a first audit deserve early attention.

If a divestiture is planned, raise it early. The sale of a division, subsidiary or business unit may require separate carve-out financial statements, with their own audit scope and timetable. Agree which financial information is needed, who will prepare it and how the audit schedule aligns with the proposed transaction. This helps avoid delays when buyers and their advisors request supporting financial records.

Some sellers also commission a vendor due diligence (VDD) report. This is an independent review of the business, covering financials, tax, legal and commercial matters, that the seller pays for and shares with prospective buyers. It can speed up a sale and reduce repeated questions, but it works only if the numbers in it agree with the audited accounts. Check whether one is planned, because it affects which schedules need to be ready, and when.

Management remains responsible for the financial statements and relevant internal controls; the independent auditor provides an opinion.

2. Assign requests and agree how to submit evidence

Use the auditor’s prepared-by-client list, usually called a PBC list, to assign a preparer, reviewer and deadline to each request. Agree on submission arrangements early: the auditor may require its own portal. Teams considering VDR providers should first confirm that the auditor accepts a virtual data room and agree on file formats and access permissions.

If you do use a data room, choose it deliberately. The features worth looking for include:

  • granular permissions by folder, file or user group;
  • an audit log showing who opened what and when;
  • dynamic watermarking and download controls;
  • NDA gating for outside parties;
  • document versioning, so replaced files are traceable;
  • a structured question-and-answer tool;
  • bulk upload and indexing; and
  • pricing that suits the length of the process.

Costs vary widely, from flat monthly fees to per-page or per-GB models, so it helps to compare data room prices against the number of users, rooms and storage you actually need.

Keep a tracker linking each request to its reporting period, owner, reviewer, deadline, evidence location and status.

For example, AR-01 could cover the December 31 receivables aging, assigned to the accounting manager for controller review by February 10. Its entry would identify the receivables folder and show “awaiting review,” keeping preparation, submission and resolution distinct.

3. Reconcile account schedules to the ledger

Check supporting schedules against the relevant trial balance accounts before sending them. Use the same entity, reporting date and account scope, retaining explanations for reconciling items.

Suppose the ledger shows $125,000 in receivables while the aging report totals $122,000. Investigate the $3,000 difference. A report filter excluding open invoices calls for a corrected report. If a manual ledger posting explains the difference, examine its support and decide whether the schedule needs updating.

Record the cause and retain evidence supporting the correction. An unexplained adjustment made solely to force agreement leaves the underlying problem unresolved.

4. Assemble support for requested balances and transactions

Build each response around the specific request. Typical supporting records include bank statements and reconciliations for cash, plus loan agreements, repayment schedules and interest calculations for debt. For revenue, gather the requested contracts, invoices and evidence of delivery.

Label files with the entity, period and request reference so reviewers can locate the right evidence quickly.

Where the auditor requests evidence of controls, provide dated approvals or reviewed reconciliations alongside process descriptions. The policy explains how a control should work; the records show how it was performed.

For a business that has acquired another, add the purchase agreement, the opening balance sheet of the acquired entity and the allocation of the purchase price. Include workforce records too, such as headcount, retention arrangements and liabilities taken on, because these feed accruals and disclosures. 

5. Explain significant estimates and unusual transactions

Prepare short explanations for balances involving management judgment, such as allowances for doubtful accounts, inventory reserves or accrued expenses. Include the method, source data, assumptions and reasons for changes from the prior year.

Flag significant transactions outside normal operations, including new financing arrangements, acquisitions and major contract changes. Supply the underlying agreements and management’s accounting assessment.

Where a company has completed an acquisition or merger during the reporting period, the audit team may need additional evidence supporting how the transaction was accounted for. This can include the valuation of acquired assets and liabilities, goodwill calculations, contingent consideration and any associated restructuring costs.

Document the accounting treatment of significant transactions, explain the judgments involved and reconcile the figures to the underlying agreements and financial records. Where integration has resulted in changes to accounting policies, internal controls or financial reporting systems, identify any resulting risks or adjustments that could affect the audited statements.

For unresolved accounting questions, set out the issue, available support and decision required. Identify the responsible manager and raise the matter early enough for discussion before the reporting deadline.

6. Review the statements and evidence before submission

Have the designated reviewer check the financial statements against the current trial balance and supporting schedules. Review disclosures for consistency with contracts, estimates and other information gathered during preparation.

Each response needs four checks: the correct entity and period, an identifiable source, reconciliation where relevant and documented management review.

Open the attachments, too. Check that spreadsheets include the necessary tabs and calculations, scans are legible and permissions allow auditor access. Record missing support in the tracker and tell the auditor what remains outstanding.

7. Track follow-up questions and changed files

Keep follow-up questions alongside the original requests, with an owner and next action. Separate administrative problems, such as broken links, from accounting issues requiring management review.

When replacing a submitted schedule, identify the new version, explain the change and preserve the earlier submission. Update any other schedules or financial statements affected by the correction.

The same rule holds in a data room: replace files through version control rather than uploading duplicates, so everyone works from one current document. 

Use agreed status definitions to keep unanswered questions visible after files have been uploaded. Before fieldwork and at subsequent check-ins, review the blockers: missing evidence, unresolved judgments and corrections affecting other submissions.






Leave a Reply

Your email address will not be published. Required fields are marked as *

This site uses Akismet to reduce spam. Learn how your comment data is processed.