Year-end close and audit readiness depend on many of the same records. While auditors need supporting schedules, sub-ledgers, and source documents to verify the numbers in your financial statements, your accounting team needs those materials to close the books accurately.
When prior-year records are incomplete or inconsistent, the work can extend well beyond the current year. That’s why it’s smart to organize everything before year-end. Doing so helps the process run more smoothly by reducing delays, limiting disruption to daily operations, and helping prevent additional audit work caused by missing records.
Key Takeaways
- Auditors test year-end balances using three categories of records: supporting schedules, sub-ledgers and account detail, and source documents. Your year-end close produces all three.
- Four schedules carry the most weight before fieldwork begins: fixed assets, prepaid expenses, the inventory roll-forward, and the cap table.
- Begin preparation 90 to 120 days before year-end, and allow about 30 days to build the audit data room so the folder structure is in place before the close starts.
- A first-year audit reaches back further than the current year. The auditor needs evidence that prior year-end opening balances are reliable, and the source document window typically begins one month before the fiscal year and runs through audit completion.
- Revenue recognition is the area auditors test hardest. Pair each material transaction with its contract, delivery confirmation, and recognition method, and keep written records of any accounting process change, including when it took effect and who approved it.
- Know which engagement you are preparing for. An audit, a review, a compilation, and an IRS audit call for different procedures, different documentation, and different levels of time and cost.
- NOW CFO helps you build the schedules, organize the data room, and close the gaps before the auditor arrives, on an as-needed basis. You only pay for the hours you need.
What Will an Auditor Ask for at Year-End?
There are three different categories of documents that your year-end close will produce. These documents establish the balances an auditor will test, and they are:
- Supporting schedules: Worksheets that explain the amounts reported on the balance sheet and income statement.
- Sub-ledgers and account detail: Transaction-level records that connect supporting schedules to the general ledger.
- Source documents: Invoices, receipts, bank statements, contracts, and other records that support individual transactions.
Each category serves a different purpose. A supporting schedule explains how a balance was calculated. A sub-ledger provides the underlying transaction detail. Source documents provide evidence of the transactions.
When these records are organized and easy to access, your team can respond to auditor requests fast. But when they’re scattered across spreadsheets, email threads, and filing cabinets, a straightforward request can become an hours-long search.
Year-End Audit Versus Review, Compilation, and IRS Audit
Before prepping for an audit, make sure you understand which type of engagement your company needs. A financial statement audit, review, compilation, and IRS audit serve different purposes and require different procedures.
A financial statement audit is an independent examination that results in an opinion on whether the financial statements are fairly presented. The auditor tests transactions, evaluates controls, and performs substantive procedures to gather evidence.
A review provides limited assurance through inquiry and analytical procedures. A compilation involves preparing financial statements from financial information without providing assurance.
An IRS audit is a tax agency examination of filed returns, including income, deductions, and tax calculations.
| Engagement Type | Definition | Procedures | Documentation Needs | Time + Cost |
|---|---|---|---|---|
| Financial Statement Audit | Independent examination with an opinion on fair presentation | Tests transactions, evaluates controls, performs substantive procedures | Sub-ledgers, supporting schedules, source documents, reconciliations | Longest and highest cost |
| Review | Limited assurance through inquiry and analytics | Inquiries and analytical procedures | Limited inquiry support materials | Moderate |
| Compilation | Formats financial statements | Compiles and organizes financial data | Basic financial information | Shortest and lowest cost |
| IRS Audit | Tax agency examination of filed returns | Verifies income, deductions, and tax computations | Tax records and deduction documentation | Varies by IRS review scope |
Understanding the engagement helps you plan for the work ahead. A financial statement audit differs from a review or compilation, while an IRS audit focuses on tax reporting rather than the fair presentation of financial statements.
The Three Things Auditors Always Ask for at Year-End
Auditors need evidence to support the balances you report in your financial statements. Supporting schedules, sub-ledgers, and source documents show how your accounting team arrived at those numbers and let auditors verify them.
Why Supporting Schedules Matter
A supporting schedule is a worksheet that shows a prior-year balance, the current-year balance, the breakdown of the amount, and how management calculated it. The schedule connects to the general ledger and explains the balance without requiring the reader to review every transaction individually.
It’s smart to build these schedules during the year-end close, so they’re ready to go when an auditor requests them.
Three common examples of this are:
- Fixed asset schedule: Details each asset’s acquisition cost, accumulated depreciation, disposals, and net book value.
- Prepaid expense schedule: Lists prepaid costs, the expense recognized during the current period, and the remaining deferred balance.
- Inventory roll-forward: Shows the beginning balance, purchases, sales, and reconciliation to the physical inventory count.
These schedules help explain how account balances changed during the year. They also make it easier to identify missing information or discrepancies before the audit begins.
Year-End Supporting Schedules That Go Missing
Supporting schedules can fall behind when records are spread across systems, accounting processes change, or nobody is responsible for maintaining the details. Several account categories deserve particular attention before year-end:
- Fixed assets: Ledgers may be missing acquisition costs, depreciation, or disposal details.
- Prepaid expenses: Insurance, rent, licenses, and subscriptions may lack schedules showing how much expense belongs in each period.
- Inventory: Roll-forwards may not reconcile to physical counts.
- Accounts receivable: Customer invoices, payments, and aging reports may be spread across multiple systems.
- Accounts payable: Vendor bills, payment schedules, and aging reports may be incomplete or unorganized.
- Equity: Shareholder ownership, share classes, and changes in equity may not be documented in one place.
- Revenue contracts: Delivery dates, contract terms, and revenue recognition methods may be difficult to locate.
Reviewing these areas before fieldwork begins gives your team time to resolve gaps while the people and records needed to address them are still accessible.
What Is an Audit Data Room, and Why Does It Matter for Your Year-End Timeline?
An audit data room is a central, organized location, physical or digital, where auditors can find the records they need to review your financial statements. It brings together supporting schedules, general ledger detail, contracts, reconciliations, and source documents.
For example, an invoice should be easy to connect to the transaction it supports. A bank reconciliation should include its date and preparer information. The goal is to let the auditor follow the evidence behind a number without searching through unrelated files or repeatedly asking your team for missing documents.
A well-organized data room can reduce the time auditors spend locating and requesting materials. When you prepare the folder structure and documentation during the year-end close, you can make maintaining them part of your regular accounting process.
How to Organize a Data Room Before Year-End
Moving from ad hoc file storage to a structured data room takes planning. The original preparation estimate is about 30 days, so begin early enough to have the structure in place before the close starts.
Use these steps to organize your records:
- Create main folders for general ledger accounts, bank reconciliations, contracts, and fixed assets.
- Establish subfolders by month or quarter for cash activity and reconciling items.
- Attach original invoices to transactions above the materiality threshold.
- Date and sign monthly reconciliations, identifying the person who prepared them.
- Consolidate revenue contracts with their delivery dates and revenue recognition methods.
- Organize payroll records and benefits data, including supporting accrual calculations.
Keep the structure consistent, so your team can file new documents in the right place throughout the year. That way, year-end preparation involves reviewing and completing existing records rather than starting from scratch.
How Far Back Does an Auditor Go at Year-End?
A first-year audit often requires information from before the current fiscal year. The auditor needs to verify opening balances from the prior year-end balance sheet before relying on the current year’s financial information.
The source document window described in this article begins one month before the fiscal year under audit and continues through the audit completion date; for a company with a December 31 year-end, that may extend into late February or March.
The exact documentation period and scope depend on the engagement. Confirm the requirements with your auditor early, so your team knows which records to gather and how far back to look.
Beginning Balances and Why Prior Year-End Quality Matters
Your opening balance sheet reflects the balances carried forward from the prior year-end. Those amounts affect the current year’s financial statements, so the auditor needs evidence that they are reliable.
First audits can uncover unrecorded prior-year adjustments, unsupported accruals, and inconsistent accounting policies. If prior-year records are incomplete, the auditor may need to expand testing to establish a reliable starting point.
Organize prior-year schedules and supporting documents with the same care as current-year materials. If an account balance changed significantly, make sure your team can explain the change and provide the supporting records.
The Role of Sub-Ledgers in Making Audits More Efficient
A sub-ledger is a detailed record of transactions within a general ledger account. Auditors use sub-ledgers to verify account balances and trace amounts back to individual transactions.
Maintaining them throughout the year helps your team start the year-end close with reconciled balances. It also makes it easier to answer questions when an auditor selects transactions for testing.
Use these practices to keep sub-ledgers organized:
- Export sub-ledgers from your accounting system each month.
- Reconcile sub-ledger totals to general ledger balances monthly.
- Investigate and document reconciling items as they arise.
- Assign accounting staff responsibility for preparation and sign-off.
- Archive sub-ledgers with their supporting documentation by month.
- Maintain a monthly audit trail showing transaction activity.
- Review aging reports and unusual items before year-end.
These steps give your team a consistent record of what happened, how balances were calculated, and how differences were resolved.
What Auditors Test Hardest at Year-End
Auditors examine whether reported balances are supported, accurate, and recorded consistently. Revenue, equity, and liabilities can require particular attention, depending on the company’s circumstances and the risks identified during the engagement.
Revenue recognition is one area where the details matter. Revenue accounting may involve interpreting contract terms, determining when goods or services are delivered, and applying the appropriate recognition method over time.
If your accounting team can’t explain why revenue was recorded in a particular period, the auditor may need additional documentation and testing to determine whether the financial statements are accurate.
Revenue Testing and the Year-End Audit Hotspot
Revenue testing often focuses on whether transactions were recorded in the correct period and whether the accounting treatment follows the company’s stated policies.
Auditors may look for:
- Transactions recorded in the wrong period.
- Revenue without a supporting contract.
- Differences between contract terms, delivery records, and the recognition method used.
A revenue schedule can bring the necessary evidence together. For each material transaction, include the related contract, delivery confirmation, and revenue recognition method. Prepare the schedule during the close, so your team has time to resolve missing documentation before fieldwork begins.
How Process Changes Can Extend a Year-End Audit
Undocumented or inconsistently applied accounting process changes can create additional work. For example, if a new bookkeeper changes how revenue is recorded midway through the year, the auditor may need to determine which method was used for different transactions and whether the treatment was appropriate.
Keep written records of process and policy changes, including when they took effect and who approved them. Pay particular attention to changes involving:
- Revenue recognized by invoice date instead of delivery date.
- Accounting policies changed without written documentation or staff notification.
- Payment approval limits changed without a formal update to authorization procedures.
- Inventory counting procedures changed without a revised manual.
- Accrual methods changed between monthly and year-end close.
- Manual journal entry approvals changed without updated control documentation.
- Bank reconciliation procedures changed without corresponding internal control updates.
When the auditor can understand what changed and why, they have a clearer basis for testing the affected transactions. Your team also has a record to follow when applying the process in future periods.
The Cost of Not Being Ready for a Year-End Audit
Missing schedules and disorganized records can increase the amount of work required during an audit. When an auditor can’t obtain enough evidence from the available documentation, they may need to perform additional substantive testing.
That work takes time. It can also pull your accounting team away from its regular responsibilities while people locate documents, answer questions, and resolve discrepancies.
Common consequences of poor audit readiness include:
- More auditor testing hours when supporting documentation is missing.
- Delays that disrupt operations and staff productivity.
- Additional audit fees from unplanned testing.
- Accounting staff pulled away from other work to respond to audit requests.
- Management spending time resolving operational issues instead of focusing on business priorities.
- The same documentation gaps recurring in future audits.
- Strained lender and investor relationships when audit timelines slip.
Preparing earlier gives your team more time to address missing records and investigate discrepancies before the auditor arrives. It also helps prevent avoidable requests from competing with the work required to close the books.
What You Should Do Right Now to Get Year-End Audit Ready
Start with four supporting schedules that often require additional attention:
- Fixed assets: Confirm acquisition cost, accumulated depreciation, disposals, and net book value.
- Prepaids: Itemize costs, current-period expenses, and remaining deferred balances.
- Inventory roll-forward: Reconcile beginning balances, purchases, sales, and physical
- inventory counts.
- Cap table: Document the complete ownership structure, share classes, and equity balances.
Begin preparation 90 to 120 days before year-end. That gives your team time to identify missing documentation, resolve prior-period issues, and prepare schedules before the auditor arrives.
The First 100 Days of Year-End Audit Readiness
A structured 100-day plan breaks audit preparation into phases, with clear milestones and assigned owners. Use the timeline below as a starting point, adjusting it to fit your fiscal year and audit requirements.
Weeks 1–2: Gather key dates and agreements
Consolidate agreements, deadlines, and important dates on one calendar. Assign an owner to each item so everyone knows who owns the next step.
Weeks 3–4: Build the four critical schedules
Prepare the fixed asset schedule, prepaid expense schedule, inventory roll-forward, and cap table. Aim for 80% completion on each so you can identify missing information early.
Weeks 5–8: Organize the data room
Create the folder structure and transfer bank reconciliations, revenue contracts, and supporting documents into their appropriate locations. Verify that key records trace back to the balances they support.
Weeks 9–12: Document accounting processes
Document your three most important accounting processes. Walk one transaction through each process and verify that the steps documented match what your team actually does.
By the end of this period, your team should have a clearer view of what’s ready, what’s missing, and what still needs to be resolved before fieldwork begins.
Frequently Asked Questions
What Is an Auditor Looking for in a Year-End Data Room?
Auditors look for organized, cross-referenced materials that support year-end balances. A data room should include general ledgers, sub-ledgers, supporting schedules, source documents, and summaries of relevant accounting policies.
How Far Back Does an Auditor Need Documentation at Year-End?
A first-year audit may require prior-year records to verify opening balances, plus source documents from one month before the fiscal year begins through the end of the engagement. Confirm the specific period and documentation requirements with your auditor.
What Is a Sub-Ledger, and Why Do Auditors Ask for It?
A sub-ledger records transactions for an individual general ledger account. Auditors use it to check that account balances are accurate and supported by transaction-level documentation.
What Supporting Schedules Should Every Company Have Before a Year-End Audit?
Common schedules include fixed assets, prepaid expenses, inventory roll-forwards, and cap tables. Auditors may also request accounts receivable and accounts payable aging schedules, depending on the company and the engagement.
How Does Inconsistent Accounting Affect a Year-End Audit?
Inconsistent accounting practices can make it harder for auditors to determine whether transactions were recorded correctly. When policies or processes change during the year without documentation, auditors may need additional testing to understand how the changes affected reported balances. That can extend the audit timeline.
Conclusion
A clean year-end close and a well-prepared audit rely on the same foundation: supporting schedules, sub-ledgers, source documents, and consistent accounting processes. Organizing those materials during the close gives your team a clearer view of the numbers and helps the auditor verify them.
Start preparing 90 to 120 days before year-end so you have time to complete schedules, organize your data room, and resolve documentation gaps. NOW CFO can help you assess your year-end accounting needs and prepare your team for the audit process.
Schedule a complimentary consultation with NOW CFO.