Year-End Audit Preparation Guide for Clients

Key Takeaways

Send the preparation letter 10 weeks before fieldwork, not 4. This gives the client time to plan their close process around your deadlines and gives bank confirmations enough runway for responses.
Assign every deliverable to a named person at the client, not a department. “M. Hendriks, financial controller” creates accountability. “Finance team” creates ambiguity.
Set the trial balance deadline at five business days before fieldwork. Run preliminary analytics (ISA 520) in that window so you arrive with targeted questions rather than a blank working paper.
The preparation letter references ISA 210.10 engagement terms on management’s responsibilities, connecting the client’s obligations back to the engagement letter they signed.

Last February you started fieldwork at a €30M logistics company. No closed trial balance. Bank confirmations hadn’t been sent. The fixed asset register was “almost done.” You spent the first four days of a ten-day visit waiting for information. That’s not an audit problem. That’s a preparation problem, and it was yours to prevent.

A year-end audit preparation guide sent to the client 8 to 12 weeks before fieldwork, structured around the specific deliverables the audit team needs, reduces information requests during fieldwork by setting clear deadlines, assigns responsibility for each item to a named person at the client, and satisfies the auditor’s communication obligations under ISA 260.14.

Why the preparation letter is audit infrastructure, not admin

Most audit teams send a “prepared by client” (PBC) list a few weeks before fieldwork. The list is usually a spreadsheet of 40 to 80 items, sent as an attachment, with a polite request to have everything ready by day one. The client opens it, scans the first ten rows, and files it for later. On day one of fieldwork, 60% of the items are missing.

The PBC list fails because it treats preparation as a single event rather than a process. ISA 260.14 requires the auditor to communicate with those charged with governance on a timely basis. “Timely” means before fieldwork, not at the planning meeting six months earlier when nobody is thinking about year-end close. It means communicating specific deliverables with specific deadlines to specific people. A PBC spreadsheet addressed to “the finance team” meets none of those criteria.

ISA 210.10 requires agreed terms of engagement that include management’s responsibilities. Those responsibilities extend to preparing the information the auditor needs. When the preparation letter references ISA 210 terms, it connects the client’s obligations back to the engagement letter they signed. This isn’t about threatening the client. It’s about making the obligation concrete and traceable, so when items are late, you have a documented basis for the conversation.

The preparation letter also protects your budget. Every day of fieldwork spent waiting for a bank confirmation or a closed trial balance is a day you can’t bill for productive work (or a day you absorb as overrun). If the letter set a deadline of 15 January for the closed TB, and the TB wasn’t delivered until 24 January, the file shows the delay was the client’s. That matters at the post-engagement debrief and at fee discussion time.

What to include in the preparation letter

The preparation letter isn’t a restatement of the PBC list. It’s a communication tool that does four things: tells the client what you need, when you need it, who should prepare it, and what happens if it’s late.

Structure the letter in two parts. Part one is a short cover letter (four paragraphs maximum) that confirms the fieldwork dates, states the key deadlines, names the client contact you’ll work with, and references the engagement letter terms on management’s responsibilities. Part two is the detailed schedule of deliverables attached as a separate document.

The deliverable schedule

Organise deliverables by category rather than by working paper reference. The client doesn’t know what WP B.3.2 is. They know what a bank confirmation is. Four categories cover most engagements: financial close items, external confirmations, supporting schedules, and access requirements.

Financial close items include the closed trial balance, draft financial statements, and any consolidation adjustments. Set the deadline for these at least five business days before fieldwork starts. If the client can’t close the books five days before you arrive, either move your fieldwork dates or plan for a split visit (interim procedures followed by final fieldwork after close).

External confirmations are the items the client needs to send on your behalf before fieldwork. Bank confirmation letters (sent to all banks the client had a relationship with during the period), legal confirmation letters (sent to external lawyers handling active matters), debtor confirmations if your plan includes circularisation. Under ISA 505.7, the auditor maintains control over the confirmation process, but the client prepares and sends the physical letters. Give the client the templates, pre-populated where possible, with a deadline of six to eight weeks before fieldwork. Bank confirmations in the Netherlands routinely take four to six weeks. If you send them in January for February fieldwork, you’ll have the responses. If you wait until fieldwork starts, you won’t.

Pre-populate the confirmation templates

Fill in the bank name, account numbers, the balance sheet date, and the return address (your firm’s office, not the client’s). The client’s finance team should only need to review the details, get a signature from an authorised signatory, and dispatch. For legal confirmations, include the specific matters you want the lawyer to address. A blank template addressed to “our external legal counsel” will sit in someone’s inbox for weeks. A template that lists the two pending litigation matters by name gets answered.

Supporting schedules include the fixed asset register with additions and disposals, the aged receivables and payables listings as at year-end, the inventory count sheets (if you attended the count, the final valued listing), loan agreements and amendments, lease schedules, and any management calculations (impairment assessments, provision estimates, fair value measurements). Set these deadlines at the same date as the TB deadline or one to two business days later.

Access requirements cover IT system access for data analytics or journal entry testing, physical access to offices or warehouses if needed, and scheduled time with key personnel (the CFO, financial controller, or bookkeeper). Confirm these in the letter so there’s no ambiguity on day one about who’s available when.

Assigning owners

Every deliverable needs a named person on the client side, not a department. “Finance team” isn’t an owner. “J. van Dijk, financial controller” is an owner. When the letter names individuals, those individuals feel accountable. When it names departments, nobody does.

If you don’t know who prepares what at the client, ask. A five-minute call to the financial controller to confirm who handles bank confirmations, who runs the fixed asset register, and who produces the aged listings will save days of misdirected follow-ups during fieldwork.

Setting a preparation timeline that works

The timeline works backwards from your first day of fieldwork. If fieldwork starts on 10 February, the deadlines are:

Milestone	Timing	What happens
Send preparation letter	Week of 2 December (10 weeks before)	First touchpoint. Client has time to plan their close process, assign deliverables internally, and ask questions.
Confirmations dispatched	Week of 6 January (5 weeks before)	Bank and legal confirmations sent by the client. Four to six weeks needed for responses.
Confirmation follow-up	Week of 27 January (2 weeks before)	Check whether bank confirmation responses have been received. Client chases if not.
TB and schedules due	3 February (1 week before)	Closed trial balance, draft financials, and all supporting schedules. Five business days for preliminary analytics.
Final check	7 February (1 business day before)	Call or email the client contact. Confirm everything is ready. Flag any outstanding items and adjust the fieldwork plan.

This timeline assumes a 31 December year-end and February fieldwork, which is the most common pattern for non-Big 4 Dutch engagements. Adjust the intervals for different year-ends or fieldwork windows, but keep the relative spacing. The 10-week lead time for the preparation letter is the critical element. Anything shorter and the client doesn’t have time to incorporate your deadlines into their own close process.

How to handle clients who don’t prepare

Some clients will miss deadlines regardless of how clear the letter is. The question is what you do when it happens, and the answer depends on the severity.

For individual items that are a few days late, adjust the fieldwork schedule. Move the work that depends on the missing item to later in the visit and pull forward other procedures. Document the delay in the engagement file and the adjusted schedule. This is normal engagement management.

For the trial balance not being closed by fieldwork start, you have a decision to make. Starting fieldwork on an open TB means testing numbers that will change, which creates rework. If the TB is expected within two to four days, you can start with areas that don’t depend on the final TB (walkthroughs, controls testing, process documentation). If it’s more than four days out, consider delaying the start. Document the delay in a communication to the client under ISA 260.14, referencing the agreed deadline from the preparation letter.

For systematic non-preparation (the same client is unprepared every year), the conversation moves to the partner level. The engagement partner discusses the pattern with those charged with governance, referencing ISA 260.14 and the engagement letter terms under ISA 210.10. In extreme cases, consider whether the relationship is sustainable. Persistent inability to produce financial records on time may indicate weaknesses in the client’s financial reporting process that have implications beyond fieldwork scheduling.

The follow-up schedule that works

A single preparation letter sent in December isn’t enough. Build a follow-up schedule into the engagement timeline. The first follow-up happens at the confirmation dispatch deadline (five to six weeks before fieldwork). A short email to the client contact: “Confirming bank confirmations were sent to ING and Rabobank on [date]. Please share the dispatch confirmation.” The second follow-up happens two weeks before fieldwork: request a status update on every item. Keep it factual. A one-line status per category is enough.

The third contact is the day-before call described in the timeline section. By that point, any missing items should be isolated exceptions, not entire categories.

Fee implications of client delay

When client delays cause additional audit hours, document the hours separately. Your engagement letter should include a clause on additional fees for delays attributable to the client (most standard Dutch engagement letter templates include this). The preparation letter makes the clause enforceable because it establishes specific agreed deadlines. Without it, the conversation about additional fees becomes a dispute. With it, the conversation references dates both parties agreed to in writing.

Track delays for the debrief

Keep a simple log: item, agreed deadline, actual receipt date, additional hours incurred. Share this log with the engagement partner at the post-fieldwork debrief. If the pattern repeats year over year, the log supports a fee adjustment conversation with the client at engagement renewal.

Worked example: De Groot Transport B.V.

Client: De Groot Transport B.V., a Dutch road haulage company. Revenue €18M, 85 employees. Year-end 31 December 2024. Fieldwork scheduled 10–21 February 2025. Non-Big 4 audit, fourth year of the engagement.

Step 1. Send the preparation letter (week of 2 December 2024)

Address the letter to the financial controller, M. Hendriks, with a copy to the managing director. Confirm fieldwork dates of 10–21 February. Reference the engagement letter signed 15 September 2024, specifically the clause on management’s responsibility to provide timely access to records (ISA 210.10).

Documentation note: “Preparation letter sent to M. Hendriks (FC) on 3 December 2024. Copy to P. de Groot (MD). Fieldwork dates confirmed as 10–21 February 2025. Letter references engagement letter clause 4.2 (management responsibilities under ISA 210.10). Deliverable schedule attached with 23 items, each with a deadline and named owner.”

Step 2. Attach the deliverable schedule with deadlines and owners

The schedule includes 23 items across four categories:

Financial close items (5 items, due 3 February): closed TB, draft financials, intercompany reconciliation, consolidation adjustments, tax computation.
External confirmations (4 items, templates sent with letter, to be dispatched by 6 January): ING Bank, Rabobank, De Brauw Blackstone Westbroek (legal), two selected debtors.
Supporting schedules (12 items, due 3–5 February): fixed asset register, aged receivables, aged payables, inventory valuation, lease schedule, loan agreements, provision calculations, related party transactions list, payroll reconciliation, VAT reconciliation, insurance schedule, grant documentation.
Access requirements (2 items, confirmed in letter): SAP Business One read access for the audit team, scheduled time with M. Hendriks for 10 February at 09:00.

Step 3. Follow up on confirmations (week of 27 January 2025)

Check with M. Hendriks whether bank confirmation responses have been received from ING and Rabobank. ING response received 20 January. Rabobank not yet received. Client to follow up with their Rabobank relationship manager.

Documentation note: “Follow-up call with M. Hendriks on 28 January 2025. ING confirmation received 20/01. Rabobank outstanding; client to contact bank. Legal confirmation from De Brauw received 22/01. Debtor confirmations: 1 of 2 received.”

Step 4. Pre-fieldwork check (7 February 2025)

Call M. Hendriks. TB closed on 31 January. Draft financials completed 4 February. All supporting schedules available except the insurance schedule (expected 10 February). SAP access confirmed. Rabobank confirmation received 5 February.

Documentation note: “Pre-fieldwork check completed 7 February 2025. 22 of 23 deliverables received on time. Insurance schedule delayed; expected day one. Fieldwork plan adjusted: insurance testing moved to day 3. All other areas ready to commence as planned.”

Conclusion

The preparation letter produced a 96% on-time delivery rate (22 of 23 items). The one delayed item was identified before fieldwork and the schedule adjusted without lost time. The file shows the preparation letter, the deliverable schedule with deadlines, the follow-up communications, and the status at fieldwork start. A reviewer can see the entire communication trail from December to February.

Practical checklist

Send the preparation letter 10 weeks before fieldwork. Not 4 weeks. Not 6. Ten weeks gives the client time to plan their close process around your deadlines and gives external confirmations enough runway for responses (ISA 505.7).
Assign every deliverable to a named person at the client, not a department. “M. Hendriks, financial controller” creates accountability. “Finance team” creates ambiguity.
Set the trial balance deadline at five business days before fieldwork starts. Run preliminary analytics (ISA 520) in that window so you arrive on day one with targeted questions rather than a blank working paper.
Send bank and legal confirmation templates pre-populated with the letter. The client should only need to print and send. Every barrier you remove increases the chance they actually do it on time.
Follow up on external confirmations four weeks after the client sent them. If responses haven’t arrived, the client chases. Document every follow-up in the engagement file.
Call the client contact one business day before fieldwork to confirm the status of every item on the list. Adjust the fieldwork plan for any outstanding items before you arrive, not on the morning of day one.

Common mistakes reviewers flag

Sending the PBC list as the preparation letter without deadlines, named owners, or consequences for late delivery. The AFM’s 2023 inspection findings noted insufficient pre-fieldwork communication as a contributing factor in files where audit evidence was obtained late and procedures were rushed at completion.
Setting all deadlines on the same date regardless of lead time. Bank confirmations need six weeks. The closed TB needs five business days. Lumping everything into a single “please have ready by” date means either the confirmation deadline is too late or the TB deadline is too early.

Frequently asked questions

When should the audit preparation letter be sent to the client?

Send the preparation letter 10 weeks before fieldwork starts. For a typical Dutch engagement with February fieldwork and a 31 December year-end, this means sending the letter in early December. Ten weeks gives the client time to incorporate your deadlines into their own close process, dispatch bank and legal confirmations (which need four to six weeks for responses), and assign deliverables to named individuals internally.

What should a year-end audit preparation letter include?

The preparation letter should include a short cover letter confirming fieldwork dates, key deadlines, the client contact, and a reference to the engagement letter terms under ISA 210.10. Attach a detailed deliverable schedule organised by category (financial close items, external confirmations, supporting schedules, and access requirements). Every deliverable needs a specific deadline and a named owner at the client — not a department.

When should the closed trial balance be ready before audit fieldwork?

Set the trial balance deadline at five business days before fieldwork starts. This window allows the audit team to run preliminary analytical procedures under ISA 520 before arriving on site, which means fieldwork starts with targeted questions rather than a blank working paper. If the client cannot close the books five days before fieldwork, either move the fieldwork dates or plan for a split visit.

How should auditors handle clients who consistently miss preparation deadlines?

For individual late items, adjust the fieldwork schedule and document the delay. For the trial balance not being closed by fieldwork start, consider delaying the start and document the communication under ISA 260.14. For systematic non-preparation year after year, the engagement partner discusses the pattern with those charged with governance, referencing the engagement letter terms under ISA 210.10. Track delayed items with agreed deadlines, actual receipt dates, and additional hours incurred to support fee adjustment conversations.

How far in advance should bank confirmation letters be sent?

Bank confirmation letters should be dispatched by the client six to eight weeks before fieldwork. In the Netherlands, bank confirmations routinely take four to six weeks for responses. Under ISA 505.7, the auditor maintains control over the confirmation process, but the client prepares and sends the physical letters. Pre-populate the templates with the bank name, account numbers, balance sheet date, and your firm’s return address to remove the most common excuse for delay.