Audit file preparation: what the work involves

What preparing an audit file means under AU-C 230, 330 and 200: schedules, evidence references, tick marks, indexing, and what the signer still decides.

US rule · Updated November 5, 2026

What this is

US rule. Audit file preparation is the hands-on work that turns an audit plan into a documented file: schedules built from the trial balance, procedures performed, evidence referenced, results recorded, open items listed. It is done by the people on the engagement team, which can include a freelancer working for the firm, under the direction and review of the engagement partner. The auditor's report and the conclusion behind it belong to the firm.

This page explains what the standards say about the file you are building. It is general information about AICPA auditing standards for audits of non-issuers, not a substitute for the standard or for the firm's own methodology. It covers the AICPA's AU-C sections, which the AICPA lists as the standards for audits of nonissuers.

What the file has to show

AU-C 230 sets the objective: documentation that is a sufficient and appropriate record of the basis for the auditor's report, and evidence that the audit was planned and performed in accordance with GAAS and applicable legal and regulatory requirements (AU-C 230.05).

The test for each workpaper is whether an experienced auditor with no previous connection to the audit could understand three things (AU-C 230.08):

  1. The nature, timing and extent of the procedures performed.
  2. The results of those procedures and the evidence obtained.
  3. Significant findings or issues, the conclusions reached, and the significant judgments made.

"Experienced auditor" has a defined meaning: someone with practical audit experience and a reasonable understanding of audit processes, GAAS and legal requirements, the entity's business environment, and the auditing and financial reporting issues of its industry (AU-C 230.06). Write for that reader. They do not know the client, they were not on the call, and they cannot ask you what you meant.

What goes on each workpaper

In recording the nature, timing and extent of procedures, AU-C 230.09 requires three things beyond the description of the work:

  • The identifying characteristics of the specific items or matters tested.
  • Who performed the work and the date it was completed.
  • Who reviewed the work and the date and extent of the review.

The standard's explanatory material gives examples of identifying characteristics: purchase order numbers and dates for a test of purchase orders; the population and the threshold for an all-items-over-an-amount test; source, starting point and sampling interval for a systematic sample; names, dates and the matter discussed for an inquiry (AU-C 230.A14). The practical rule is that another auditor must be able to find the same items.

Sign-offs and dates are not decoration. The standard says the review requirement means documenting what work was reviewed, who reviewed it and when, without needing evidence of review on every individual working paper (AU-C 230.A15). Follow the firm's sign-off convention exactly.

Contracts and agreements need more. For procedures involving the inspection of significant contracts, the file must include abstracts or copies (AU-C 230.10).

What building the file looks like

A typical sequence for one area, for example accounts receivable:

  1. Lead schedule. Agree the schedule's total to the trial balance. A schedule that does not agree to the ledger cannot support the financial statements.
  2. Procedure. State what you did: for example, "selected all balances over the stated threshold and sent positive confirmation requests".
  3. Evidence. Reference each item to the source: confirmation reply, subsequent receipt, invoice, contract.
  4. Result. Record what you found, including exceptions.
  5. Open items. List anything you could not clear and who owns it.
  6. Conclusion. Where the firm's methodology asks for a preparer's conclusion, write what the evidence supports. The reviewer decides whether the conclusion stands.

For accounts receivable, the standard requires the use of external confirmation procedures unless the overall balance is immaterial, confirmation would be ineffective, or the assessed risk of material misstatement at the assertion level is low and other planned substantive procedures address it (AU-C 330.20). Whether one of those exceptions applies is a judgment for the engagement team, and your note should say which approach the plan uses.

Timing and the final file

Prepare documentation on a timely basis (AU-C 230.07). The explanatory material says documentation prepared when the work is performed or shortly after is likely to be more accurate than documentation written much later (AU-C 230.A3).

Several dates matter for the file as a whole:

  • Report release date: the date the auditor grants the entity permission to use the report. It must be documented (AU-C 230.15).
  • Documentation completion date: no later than 60 days after the report release date, when the auditor has assembled a complete and final set of documentation (AU-C 230.06 and .16).
  • Retention: after the completion date, nothing may be deleted or discarded before the end of the retention period, which must not be shorter than five years from the report release date (AU-C 230.17).
  • Changes after the completion date: any modification or addition must be documented with the specific reasons and when and by whom it was made and reviewed (AU-C 230.18).

For you this means two things. Do not edit a file that the firm has marked complete. If you find an error in finished work, report it to the firm so they can follow the standard's process.

Inconsistencies and departures

If you find information that is inconsistent with the conclusion on a significant matter, the standard asks the auditor to document how it was addressed (AU-C 230.12). It does not require keeping documents that are incorrect or superseded (AU-C 230.A17). In practice: record what you found, what you did about it, and what resolved it, and tell the reviewer. Do not delete the line that shows the difference.

A departure from a presumptively mandatory requirement is for the auditor to judge and document (AU-C 230.13). Do not decide to skip a required procedure yourself. Ask.

Ethics, skepticism and confidentiality

The auditor must comply with relevant ethical requirements (AU-C 200.16) and plan and perform the audit with professional skepticism (AU-C 200.17). For a freelance contributor, the ethical requirement shows up as an independence check before each file, and skepticism shows up as noting the item that looks wrong even when the client's explanation sounds reasonable. The auditor must also adopt reasonable procedures to maintain the confidentiality of client information (AU-C 230.19). Keep the client's data in the firm's approved place.

How review works on your work

Under AU-C 220, the engagement partner takes responsibility for direction, supervision and review, and reviews documentation relating to significant matters and judgments (AU-C 220.29 and .31). Expect review notes. Treat them as part of the file: answer each in writing, with a reference to evidence, as the review notes and clear-a-finding pages in this section describe.

Standards are amended

AICPA has issued amendments to some AU-C sections with later effective dates. The edition in the AICPA's current download states that amendments to AU-C 230 take effect for audits of financial statements for periods ending on or after December 15, 2026 (SAS No. 149, group audits), and that SAS No. 150 on external confirmations amends AU-C 230 for periods ending on or after December 15, 2028. Work to the edition the firm tells you applies to the engagement period.

FAQ

Is a workpaper complete if the numbers agree?

No. It also needs the procedure, the evidence, who did it and when, and the reviewer's sign-off. A schedule with correct numbers and no source reference does not let another auditor re-trace the work.

Do I need a separate checklist for every requirement?

Not necessarily. The standard says it is unnecessary to document separately compliance with matters shown by documents already in the file (AU-C 230.A9). Follow the firm's templates.

Can I keep a copy of the file?

Only where the agreement and the firm's confidentiality terms allow it. The default should be that nothing leaves the firm's workspace.

Who is responsible for the final file assembly?

The auditor, meaning the firm (AU-C 230.16). A contributor supplies complete, indexed work in time for the assembly.

Sources

Last verified November 20, 2026. Sources checked by the editorial team; not yet reviewed by a named professional. General information, not legal, tax or accounting advice.

Related pages

Terms used on this page

Engagement team

Join the CORAA CPA network waitlist

CORAA prepares audit files for US CPA firms. Network members are independent contractors who clear what the software flags, with evidence and a note, paid per file under a contractor agreement.

  • Files are offered to you; you accept or decline
  • No exclusivity: you can work for others
  • The firm reviews and signs; CORAA never does

* required