The external audit is one of the most resource-intensive annual exercises a finance team undertakes. Done well, it produces a clean opinion on time, within budget, with a short management letter. Done poorly, it drags on for months, generates surprise scope expansions, and leaves the CFO fielding uncomfortable conversations with the audit committee about internal control findings that should have been caught internally.
The difference almost always comes down to preparation. Auditors work faster and at lower cost when they receive well-organized, complete deliverables on the first request. They expand scope and increase billing when they encounter unexplained variances, missing documents, or slow responses from the client team. The 90-day window before audit fieldwork begins is the most valuable investment a finance team can make in controlling audit outcomes.
This checklist is organized into three phases aligned to the 90-, 60-, and 30-day marks before fieldwork. Use it as a working document: assign owners, track completion, and review it in your weekly finance team meetings as the audit approaches.
Why Audit Preparation Matters
Audit preparedness affects four things simultaneously: auditor fees, engagement timeline, the quality of the audit opinion, and the number and severity of findings in the management letter. A finance team that delivers complete, well-organized PBC (Prepared by Client) requests on the first due date signals to auditors that the financial reporting process is well-controlled — which reduces the extent of substantive testing required. A team that trickles in documents over weeks, produces incomplete schedules, or cannot explain significant variances signals the opposite.
The cost of surprises is asymmetric. Auditors bill for out-of-scope work at standard rates, and scope expansions triggered by client issues are rarely negotiable. A single unexplained variance that expands the revenue testing scope can add $15,000 to $50,000 in fees for a mid-market company. A control deficiency that auditors identify before management does signals an inadequate internal control self-assessment, which may trigger broader ICFR testing. Preparation eliminates the vast majority of these exposure points before fieldwork begins.
Phase 1: Foundation and Scope Alignment
Confirm Audit Scope and Timeline
- Confirm audit period end date and fieldwork start date with your audit firm in writing.
- Agree on a preliminary milestone schedule: fieldwork start, draft financial statements, draft audit opinion, final signed opinion.
- Clarify audit scope: consolidated financials, standalone subsidiaries, or both. Confirm which entities require separate audit opinions.
- Identify year-over-year scope changes: acquisitions, divestitures, new locations, new business lines, or changes in material accounting estimates.
- Confirm the materiality threshold with the engagement partner. Typical ranges: 1–2% of revenue, 0.5–1% of total assets, or 5% of pre-tax income.
- Confirm which significant accounting policies are under active review or require audit focus (revenue recognition, lease accounting, goodwill impairment, stock compensation).
- Request the prior-year audit team's internal notes (the predecessor package) if there has been any auditor transition.
Internal Team Preparation
- Designate a single audit coordinator — typically the Controller or Senior Accounting Manager — as the primary point of contact for all auditor requests.
- Identify subject matter experts for each major audit area: revenue, AR, fixed assets, debt, equity, taxes, payroll, IT systems.
- Brief the CFO and audit committee on the audit timeline, key risk areas, and any anticipated accounting issues.
- Set internal PBC response deadlines at least two weeks before external due dates. This buffer absorbs the inevitable last-minute complications.
- Block the audit team's calendars for the entire fieldwork period. Make clear to department heads that audit requests take priority over routine work during this window.
- Assign backup contacts for each subject matter expert in case of vacation or illness during fieldwork.
Financial Close and Year-End Adjustments
- Accelerate the year-end close timeline if possible. An earlier close gives the audit team more lead time and reduces pressure during fieldwork.
- Complete all account reconciliations: bank accounts, all sub-ledgers, intercompany balances.
- Process all year-end accruals and cutoff adjustments before the books are closed. Avoid post-close adjusting entries that were foreseeable pre-close.
- Finalize revenue recognition calculations under ASC 606, including any variable consideration estimates, standalone selling price allocations, and contract modifications.
- Complete lease accounting schedules under ASC 842, including right-of-use asset rollforwards and lease liability amortization tables.
- Process all year-end equity entries: stock option vesting, option expense calculations (Black-Scholes), cap table updates.
- Complete the goodwill and intangible asset impairment analysis if applicable.
Phase 2: Document Organization and PBC Preparation
Document Organization
- Organize all general ledger accounts with supporting schedules that tie to the trial balance. Every account balance should have a corresponding schedule that explains what it contains.
- Compile the prior-year audit binder as a reference for the current year. Prior-year workpapers help prepare explanations for year-over-year variances.
- Gather all signed agreements executed or modified during the audit period: leases, debt facilities, equity agreements, material vendor contracts, customer MSAs.
- Collect board of directors minutes and audit committee minutes for all meetings held during the audit period. These are always requested and frequently incomplete when assembled late.
- Compile equity and capitalization table documentation: current cap table, option grants, vesting schedules, any repurchases or conversions.
- Gather bank and investment account statements for all accounts for the full audit period, plus any post-period-end statements needed for subsequent events.
- Organize insurance policy documentation: coverage types, carrier, policy period, premium amounts.
Common PBC (Prepared by Client) Request List
The PBC list is the master document request list that auditors issue at or before fieldwork. Being ready with these items before the list arrives eliminates the most common source of audit delays. The table below reflects the standard items requested in virtually every mid-market audit.
| Category | Documents Required |
|---|---|
| Financial Statements | Draft P&L, balance sheet, statement of cash flows, and statement of equity for the audit period and prior comparable period; management-prepared footnote drafts |
| General Ledger | Full trial balance, adjusted trial balance, complete journal entry log for the period (including adjusting and closing entries), chart of accounts |
| Revenue | Revenue recognition schedules by performance obligation, contract detail for significant contracts, deferred revenue rollforward, backlog analysis, sales commission calculations |
| Accounts Receivable | AR aging report as of period end, allowance for doubtful accounts calculation and methodology, post-period-end collections data for cutoff testing |
| Inventory | Physical inventory count sheets, count procedures documentation, inventory valuation schedules, obsolescence reserve analysis and supporting data |
| Fixed Assets | Fixed asset rollforward (beginning balance, additions, disposals, depreciation, ending balance), useful life policy, supporting invoices for material additions, gain/loss on disposals |
| Accounts Payable | AP aging report as of period end, accrued liabilities schedule with supporting calculations, cutoff test support (receiving log vs. AP recording around period end) |
| Debt | All loan agreements, debt rollforward with beginning balance / draws / repayments / ending balance, amortization schedules, covenant compliance calculations, confirmation of outstanding balances |
| Equity | Cap table as of period end, option grant schedules, Black-Scholes inputs and calculations, stock-based compensation expense schedule by grant, any warrants outstanding |
| Leases | All lease agreements (property, equipment), ASC 842 lease schedules including right-of-use asset rollforward, lease liability amortization, discount rate documentation |
| Income Taxes | Prior-year federal and state tax returns, current-year tax provision (ASC 740) workbook, deferred tax rollforward, uncertain tax positions analysis, estimated tax payments |
| Payroll | W-2 reconciliation (payroll expense per GL vs. W-2 aggregate wages), commission expense schedules, bonus accrual calculations, key employee compensation detail |
| Related Parties | List of all related parties (officers, directors, significant shareholders, affiliates), description of all related-party transactions during the period, balances outstanding |
| Significant Contracts | Material vendor contracts, significant customer agreements, partnership or joint venture agreements, any contracts with unusual terms or contingent obligations |
Tip: Set up your PBC file structure in your secure sharing platform (SharePoint, Box, Suralink, or similar) at 90 days, not 30 days. Populate folders as items become available. When the formal PBC request arrives, most items should already be uploaded.
Internal Control Documentation
- Update process documentation for key financial reporting processes: order-to-cash, procure-to-pay, record-to-report, payroll, and treasury.
- Review and update the segregation of duties documentation. Identify any personnel changes that have altered existing SOD arrangements.
- Compile IT general controls documentation: access provisioning and de-provisioning logs, change management records, backup and recovery procedures.
- Prepare the management assessment of internal controls if required under your governance framework or investor agreements.
- Document any material changes to internal controls during the year, including the reason for the change and the effective date.
- Confirm that all identified deficiencies from the prior year's audit have been formally remediated and that the remediation has been re-tested.
Phase 3: Final Technical Review and Readiness
Technical Accounting Issues
- Identify and document all non-routine transactions from the year: acquisitions, disposals, debt restructurings, equity transactions, litigation settlements, significant contract modifications.
- Prepare accounting position memos for any significant judgments: fair value measurements, impairment analyses, revenue recognition positions, lease modifications, contingent liabilities.
- Confirm your accounting positions on any grey-area transactions directly with your audit engagement partner before fieldwork begins. Surprises during fieldwork are significantly more disruptive than pre-fieldwork discussions.
- Review the FASB and SEC accounting pronouncement calendar for your fiscal year. Confirm which new standards are effective for your current period and that your accounting reflects them.
- Prepare significant estimate documentation: contingent liability assessments, inventory obsolescence methodology, useful life assumptions, accounts receivable collectability, valuation allowances on deferred tax assets.
- Review goodwill and indefinite-lived intangible impairment analyses for completeness and supportability of key assumptions.
Systems Access and Logistics
- Provision read-only auditor access to the ERP system and all relevant sub-ledgers. Test that credentials work before fieldwork day one.
- Set up the secure file sharing environment and confirm auditor access. Test the document upload and retrieval process.
- Identify data extract capabilities for large-population testing (journal entry population, AP transaction population, revenue transaction detail). Prepare standard extracts in advance.
- Reserve a conference room or dedicated workspace for the audit team if they will be working on-site.
- Brief IT staff on auditor access requirements, particularly for ITGC testing, and confirm they are available during the fieldwork window.
Final Review and Analytical Procedures
- Self-review all draft financial statements for mathematical accuracy: confirm that the balance sheet balances, that net income flows to the equity statement, that the cash flow statement reconciles to the change in cash.
- Perform a financial statement analytical review: calculate year-over-year changes in every P&L line item and balance sheet account, and prepare written explanations for any change exceeding 10% or $100,000.
- Prepare variance explanations for significant fluctuations between actual results and budget. Auditors will ask; having pre-prepared explanations with supporting data eliminates delays.
- Calculate and document key financial ratios: gross margin, operating margin, current ratio, debt-to-equity, days sales outstanding, inventory turns. Review for anomalies that auditors will flag.
- Brief your internal team on what to expect during fieldwork: types of questions they will be asked, how to interact with auditors professionally, and who to escalate to if they are unsure how to respond.
- Prepare a schedule of all known subsequent events (events occurring after the period end but before the audit opinion date) that require disclosure or consideration.
During Fieldwork: Best Practices
Preparation determines the trajectory of audit fieldwork, but execution during the fieldwork period determines whether that preparation converts into a smooth audit. The following practices are consistently cited by audit partners as the behaviors that distinguish well-run client engagements from difficult ones.
Maintain a single point of contact. All auditor requests should flow through the designated audit coordinator. Direct outreach to individual staff bypasses tracking, creates conflicting information, and generates confusion about what has and has not been delivered. Route all requests through one person and all deliverables back through one platform.
Respond within 24 to 48 hours. Slow response to open items is the primary reason audits extend beyond their planned timeline. Auditors cannot test items they have not received. A standard of same-day or next-day response to routine requests keeps fieldwork on schedule and prevents accumulation of open items that compound at the end of the engagement.
Track open items daily. Maintain a shared tracker of all outstanding requests, their due dates, the responsible team member, and current status. Review it every morning during fieldwork. A running open items list prevents items from falling through the cracks and gives both teams visibility into where the bottlenecks are.
Hold weekly status meetings. A 30-minute weekly call with the audit manager to review progress, discuss open issues, and confirm timelines catches problems early. Auditors appreciate the proactive communication and are more likely to surface concerns in a scheduled setting than through ad hoc messages.
Do not give auditors unsupervised system access. Read-only access is appropriate; unsupervised queries of production systems without accounting team involvement can produce data extracts that lack proper context and generate unnecessary follow-up questions. Have your IT or accounting team available when auditors are conducting systems testing.
Common Audit Surprises and How to Prevent Them
| Audit Surprise | Prevention Strategy |
|---|---|
| Unexplained variance triggers expanded scope | Prepare written year-over-year variance analyses for every P&L line and material balance sheet account at 30 days out. Deliver proactively with financial statements. |
| Revenue recognition disagreement | Pre-discuss ASC 606 positions and significant contract interpretations with the audit partner before fieldwork. Surface disagreements early when there is time to work through them. |
| Internal control deficiency identified by auditors before management | Conduct a self-assessment of key controls at 90 days. Finding and remediating gaps internally is always preferable to auditors identifying them first. |
| Missing agreements or executed contracts | Create a signed agreement inventory at 90 days and track down missing items before they become auditor requests during fieldwork. |
| Slow PBC responses extend timeline and add fees | Set internal deadlines two weeks before external deadlines. Track daily. Treat PBC delivery as a team performance metric. |
| Key person unavailable during fieldwork | Block calendars 90 days in advance. Assign backups for each subject matter expert. No vacations during fieldwork without a qualified backup in place. |
| New accounting standard applied incorrectly | Review the effective date calendar at 90 days. Engage your audit firm for pre-implementation guidance on complex new standards well before year-end close. |
| IT general control deficiencies block reliance on automated controls | Review access logs, change management records, and terminated user access at 90 days. ITGC findings discovered during fieldwork are among the most disruptive to audit scope. |
Building your internal controls framework?
Read our COSO framework guide for a full breakdown of the five components, 17 principles, and implementation approach for mid-market companies.
Post-Audit: Management Letter Response
The management letter (also called the "communication to those charged with governance") is a formal document the external auditors issue at the conclusion of the audit summarizing any significant deficiencies and other observations about the company's internal controls, accounting practices, and financial reporting processes. It is not an audit opinion — it does not affect the auditor's conclusions on the financial statements — but it is reviewed closely by audit committees, investors, and lenders.
The management response process should begin as soon as the draft management letter is received, typically within two to four weeks of the draft audit opinion.
- Draft responses within two weeks. Each finding in the management letter should receive a written management response acknowledging the issue, describing the planned remediation, identifying the owner of the remediation, and stating a target completion date.
- Assign remediation owners with accountability. Vague responses (“we will review our controls”) satisfy no one. Specific responses with named owners and completion dates signal genuine commitment to remediation.
- Track open items into the next audit cycle. The findings from this year's management letter become the first items reviewed in next year's audit. Remediating all open items before fieldwork begins next year demonstrates operational effectiveness.
- Use findings as a roadmap. Auditors observe your processes with an independent eye. The best finance teams treat management letter findings as free consulting — a diagnostic of control gaps that the internal team was too close to see.
Audit Fee Management
Audit fees are one of the most significant and controllable costs in the finance function budget. The primary driver of fees you can control is client preparedness. Everything else — auditor billing rates, team composition, scope of the engagement — is largely negotiated at the engagement letter stage. But preparedness converts into lower effective costs in every audit, every year.
Early, complete, and well-organized PBC delivery is the single most impactful fee lever available to clients. Every hour an auditor spends waiting for a document, following up on a request, or reformatting a schedule you provided in the wrong format is billed at your expense. A controller who delivers a complete, auditor-ready PBC package on day one of fieldwork typically saves 20 to 40 hours of audit time compared to a controller who delivers piecemeal over three weeks.
Understand what triggers overage billing. Most fixed-fee audit engagements have scope assumptions built in: a certain number of PBC items, a certain number of follow-up requests, a certain number of significant accounting issues. Scope expansions — triggered by surprises, control deficiencies, slow responses, or new accounting issues that were not disclosed at engagement signing — are billed as out-of-scope at standard hourly rates. Know what your engagement letter's out-of-scope provisions say.
For companies without strong controllers, consider outsourced audit preparation services. Several fractional CFO and outsourced accounting firms offer audit readiness as a standalone service: organizing documentation, preparing schedules, managing the PBC process, and acting as an intermediary between the audit team and internal management. For companies that lack the internal capacity to run a well-organized audit process, the cost of outsourced audit prep is typically recovered in reduced auditor fees and shortened timelines within the first engagement.
Key Takeaways
- Start audit preparation 90 days before fieldwork, not 30. The compounding effect of early preparation — confirmed scope, organized documents, blocked calendars, pre-identified technical issues — is the difference between an efficient audit and a chaotic one.
- Complete, first-time PBC delivery is the highest-ROI investment in audit fee management. Treat it as a team performance standard.
- Pre-fieldwork alignment with the audit partner on accounting positions, scope changes, and significant judgments eliminates the most expensive audit surprises.
- Conduct an internal control self-assessment at 90 days. Finding your own gaps is always better than having auditors find them.
- The management letter is a free diagnostic. Build a structured response and tracking process that converts findings into control improvements before the next audit cycle begins.
- For companies without strong audit coordination capability, outsourced audit prep services deliver measurable ROI in reduced fees and timeline.