Connecticut's Office of Policy and Management, in a best practices guide written for municipal finance offices, says planning for an audit should be treated as a year-long process. Read that from the accountant's side of the table. By the week the audit team arrives, most of what will decide how the engagement goes has already been settled: who owns the statements, whether the request list has names and dates on it, whether the minutes exist, and how proposed adjustments will travel.
Year-end audit preparation is a calendar problem before it is a documentation problem. Each step in it is anchored in something the auditor is already required to do, which is why you can ask for it in the autumn.
Settle the Responsibility Split Before Anything Else
Nothing else in the sequence is stable until the client has agreed to three things.
AU-C 210, Terms of Engagement requires at .06 that the auditor obtain the agreement of management that it acknowledges and understands its responsibility for the preparation and fair presentation of the financial statements, for the design, implementation and maintenance of internal control relevant to that preparation, and for providing the auditor with access. Access is spelled out in three parts: all information of which management is aware that is relevant to the preparation and fair presentation of the statements, additional information the auditor may request for the purpose of the audit, and unrestricted access to persons within the entity from whom the auditor determines it necessary to obtain audit evidence.
That agreement is a precondition rather than a courtesy. Where it has not been obtained, .08 says the auditor should not accept the proposed audit engagement, unless the auditor is required by law or regulation to do so (AU-C 210).
For a firm that keeps the client's books, the practical reading is narrow and worth saying out loud early. Your firm can prepare the statements. The client's management still owns them, and it is the client who has to produce records and make people available. Where the same firm both prepares a client's records and performs attest work, independence decides what is allowed, and that is a separate question from readiness.
The written form of all this is the engagement letter. Paragraph .10 requires the agreed terms to be documented in an audit engagement letter or other suitable form of written agreement, and to include, among other items, the objective and scope of the audit, the responsibilities of the auditor, the responsibilities of management, and the applicable financial reporting framework (AU-C 210).
The Planning Conversation Is Where Your Calendar Comes From
Ask for the planning conversation in the autumn, because the auditor's own requirements already put the answers you need on their desk.
AU-C 300, Planning an Audit requires at .06 that the auditor undertake preliminary engagement activities at the beginning of the current audit engagement, including establishing an understanding of the terms of the engagement. At .07 the auditor should establish an overall audit strategy that sets the scope, timing and direction of the audit, and .08 has that strategy ascertain the reporting objectives of the engagement in order to plan the timing of the audit and the nature of the communications required.
Telling somebody about it is also required. AU-C 260 requires at .11 that the auditor communicate to those charged with governance an overview of the planned scope and timing of the audit, including the significant risks identified. Those charged with governance are the people or organizations responsible for overseeing the entity's strategic direction and the obligations related to its accountability, including oversight of the financial reporting process, which in a small business is often the owner sitting across from you.
Take two things out of that communication, whether you sit in on it or your client relays it, and put them at the front of your close calendar: the fieldwork dates, and the risks the auditor has flagged as significant. A significant risk named in November tells you which account will draw the deepest testing, and the schedule behind that account is the one you build first rather than last.
What Is Cheap in the Autumn and Expensive in Week One
What slips in week one usually slipped months earlier without anyone noticing. The Connecticut guide organizes its readiness questions around internal timelines, asking on the closing and trial-balance items whether responsibility has been assigned to a staff person, and although the guide is written for municipalities, the shape of the questions carries over to a book of private clients (Office of Policy and Management, Facilitating a Timely Audit).
- Timelines for closing the books and reconciling balances, with a person's name against each. The recurring mechanics behind that, the sub-ledger close, the accruals and the balance sheet review, are settled elsewhere in the month-end close sequence, and audit preparation only asks whether they ran on cadence.
- A timeline for the year-end trial balance and its supporting documentation. Supporting documentation is the schedule behind each balance, and it is what the auditor will agree the trial balance to.
- Timelines with outside parties, started early. Banking and investment confirmations, management and legal representation letters, actuarial information and insurance information all sit outside your control once requested, so their lead time is the real constraint.
- Entries pulled forward where the calendar allows. The guide's own remark is to consider whether certain year-end entries can be accelerated to quarterly, which turns one large December exercise into work that has already been reviewed.
- Interim reporting kept honest during the year. Interim financial reporting can contribute significantly to the timely completion of the financial statement audit, and the guide singles out the year after a new accounting system went in or after significant auditor adjustments as the one to watch.
The filing calendar that runs the other direction, from the December close toward the return, is a different sequence with different fixed dates, and it is set out in what year-end work actually contains.
The Request List Should Not Arrive as a Surprise
The request list is the first artifact the client meets, and it is the one your firm can build before the auditor sends it.
The Connecticut guide names it in passing: internal timelines to complete auditor-requested information that coincide with the audit schedule, commonly referred to as the Prepared by Client, or PBC, list (Office of Policy and Management, Facilitating a Timely Audit). Start from last year's version, because the auditor almost certainly will.
Give every line five fields: the item, the system it comes out of, the person who produces it, the date it is due to your firm, and the date it is due to the auditor. Then split the list in two. One half is work your firm can produce from the ledger and the workpapers you already hold. The other half only the client can produce, because it needs bank access, signed contracts, board minutes or knowledge of a dispute nobody wrote down.
That second half is where audits stall, and it is the half that has to be in front of the client in the autumn. Which of the first half can move to an outside team is a separate sorting exercise with its own rules.
The Evidence Window Does Not Close at the Balance Sheet Date
The client's year closes on one date. The auditor's evidence window closes on another, later one, and preparation that ignores the gap creates a scramble in February.
AU-C 560, Subsequent Events and Subsequently Discovered Facts defines subsequent events at .07 as events occurring between the date of the financial statements and the date of the auditor's report. The date of the financial statements is the end of the latest period the statements cover.
At .09 the auditor should perform audit procedures designed to obtain sufficient appropriate audit evidence that all subsequent events requiring adjustment of, or disclosure in, the financial statements have been identified, and .10 requires those procedures to cover the period from the date of the financial statements to the date of the auditor's report, or as near as practicable thereto (AU-C 560).
Four procedures are named there, and each one is a preparation instruction if you read it early enough. The auditor obtains an understanding of any procedures management has established to ensure subsequent events are identified, inquires of management and, when appropriate, those charged with governance about whether any have occurred, reads the minutes, if any, of meetings of the entity's owners, management and those charged with governance held after the date of the financial statements, and reads the entity's latest subsequent interim financial statements, if any (AU-C 560).
So the weeks after year end still have to produce evidence. Minutes for meetings held in that window need to exist and be findable, and the auditor will ask about matters discussed at meetings whose minutes are not yet written. Where the client produces interim statements, the new year's should stay on the usual cadence rather than be parked while the audit runs. And a client who has never been asked how it spots a subsequent event will need help building an answer before the question is put.
Adjustments, and the Ones That Never Get Posted
Proposed adjustments are the part of fieldwork that reaches back into your close, so agree the mechanics before any of them exist.
AU-C 450, Evaluation of Misstatements Identified During the Audit requires at .05 that the auditor accumulate misstatements identified during the audit, other than those that are clearly trivial. Clearly trivial is a defined idea and not a softer word for immaterial: the application material says at .A2 that clearly trivial is not another expression for not material, and that misstatements that are clearly trivial will be of a wholly different and smaller order of magnitude, or of a wholly different nature, than those that would be determined to be material.
Both halves of the communication are required. At .07 the auditor should communicate on a timely basis with the appropriate level of management all misstatements accumulated during the audit, and should request management to correct them. If management refuses to correct some or all of them, .09 requires the auditor to obtain an understanding of management's reasons and to take that understanding into account when evaluating whether the financial statements as a whole are free from material misstatement (AU-C 450).
A passed adjustment, what AU-C 450 calls an uncorrected misstatement, is therefore a recorded decision rather than a quiet one. Documentation under .12 includes the amount below which misstatements would be regarded as clearly trivial, all misstatements accumulated during the audit and whether they have been corrected, and the auditor's conclusion about whether the uncorrected ones are material, individually or in the aggregate (AU-C 450).
What that buys you operationally is worth setting up in the planning conversation. Ask how proposed entries will be delivered and by when, then post them as a batch against a stated cutoff, because a single late entry moves the trial balance, the statements and every schedule tied to them.
The Representation Letter Is Signed Last and Assembled First
A written representation is a written statement by management given to the auditor to confirm certain matters or to support other audit evidence, and it arrives at the end of the engagement.
AU-C 580, Written Representations requires at .20 that the date of the written representations be as of the date of the auditor's report on the financial statements, and at .21 that they take the form of a representation letter addressed to the auditor. Being dated last does not mean being built last.
Management is asked at .10 to represent that it has fulfilled its responsibility for the preparation and fair presentation of the financial statements and for internal control, and at .11 that it has provided the auditor with all relevant information and access agreed in the terms of the engagement and that all transactions have been recorded and reflected in the statements (AU-C 580).
Then come the lists that take weeks. Paragraph .14 asks management to represent whether it believes the effects of uncorrected misstatements are immaterial, individually and in the aggregate, with a summary of those items included in or attached to the representation. Paragraph .15 covers all known actual or possible litigation and claims, .17 covers the identity of all related parties and the relationships and transactions management is aware of, and .18 covers subsequent events requiring adjustment or disclosure (AU-C 580).
Not producing the letter carries the heaviest consequence in the sequence. Under .25 the auditor should disclaim an opinion in accordance with section 705 or withdraw from the engagement if management does not provide the representations required by .10 and .11 (AU-C 580).
Which is why the related party list, the litigation list and the minutes file belong to the autumn. A client asked in April to name every related party for the first time will produce a list, and it will be the list they can remember.
What a Year-End Audit Preparation Checklist Should Include
Audit readiness for a CPA firm is not a list of accounts. It is a short list of decisions, each with an owner and a date, in the order they stop being cheap.
- The responsibility split, settled first. Agreed before the engagement is accepted and written down in the engagement letter, so nobody discovers in February that the client thought your firm owned the statements.
- The fieldwork dates and the significant risks. Taken out of the planning conversation and put at the front of the close calendar.
- A dated request schedule with an owner per line. Two dates per line, one for your firm and one for the auditor, and a clean split between what you can produce and what only the client can.
- The outside-party lead times, started first. Anything that has to come from a bank, a lawyer, an actuary or an insurer moves on somebody else's clock, so it gets triggered before the internal work.
- The adjustment protocol. How proposed entries arrive, who posts them, and the cutoff after which they go in as one batch.
- The representation letter's supporting lists. Related parties, litigation and claims, and a minutes file kept current through the report date.
When Preparation Is Not the Problem
Two situations look like a preparation failure and are not, and both are worth naming before you sell the client a readiness project.
If the books were not closed on a monthly cadence during the year, December cannot fix it. What the client needs is a close that runs every month, and audit preparation on top of an unreliable ledger only moves the discovery of the problem into fieldwork.
If the constraint is that the same two people at your firm carry every client's year-end inside the same few weeks, the answer is capacity rather than process, and how to size and close that gap is the prior question. The Connecticut guide reaches the same conclusion from the other direction: where a staffing shortage is what is breaking the timeline, its remark is to consider retaining temporary staff or external assistance as soon as possible until permanent staffing is retained (Office of Policy and Management, Facilitating a Timely Audit).
Start With the Two Dates
Pull the prior year's request list and the prior year's summary of passed adjustments, and put them side by side. The request list tells you which lines arrived late and who owned them. The summary of passed adjustments tells you which accounts produced errors last time. Between them they write most of the autumn plan, and they do it from evidence rather than from a generic checklist.
Then fix the two dates everything else hangs on: the date the books close, and the date the auditor expects to be on site. Every step in the sequence is scheduled backward from one of those.
If your firm is carrying that preparation across a book of clients with the same two people every year, don't trust us, test us. Accountably places trained offshore accountants and tax preparers inside US CPA, EA and accounting firms, working on your software and SOPs, with the signature and the final judgment staying with your firm. The scope is accounting and tax work rather than audit fieldwork. Since 2022 that has meant 20+ US firms and 30+ placements.
The way in is small on purpose. A Free 40-Hour Proof Pilot puts a fixed block of your own representative work through the offshore team and your review chain, so your reviewer grades real output before a client file depends on it. If a placement is not the right fit in the first 30 days, the 30-Day Fit Guarantee replaces them free.