Audit documentation is the written record that demonstrates what an independent auditor did, which audit evidence was obtained, and how the auditor reached important conclusions. For public company audits, PCAOB AS 1215 sets foundational requirements for the content, organization, assembly, retention, and subsequent modification of audit workpapers.

For finance teams preparing for a PCAOB audit, understanding these requirements can make audit requests easier to manage. For auditors, an organized and sufficiently detailed file is essential to demonstrate compliance with professional standards. This guide explains the audit documentation process, includes a realistic audit documentation example, compares AS 1215 with ISA 230 and AICPA AU-C 230, and provides a practical audit documentation checklist. It is educational guidance, not a substitute for engagement-specific professional judgment.

What Is Audit Documentation?

Under PCAOB AS 1215, audit documentation is the written record supporting the auditor’s conclusions and representations. Often called audit working papers or workpapers, it includes records of procedures performed, evidence obtained, significant matters considered, and conclusions reached. Documentation may be maintained in paper or electronic form.

An audit file is the organized collection of engagement documentation. The concepts are connected but not identical: documentation refers to the records; the audit file is the assembled, indexed collection of those records for an engagement.

Why audit documentation matters

• Supports the independent auditor’s opinion and the conclusions regarding relevant financial statement assertions.

• Allows supervision and review of work performed by engagement team members.

• Provides an audit trail for internal quality reviews and PCAOB inspections.

• Connects risks, audit responses, evidence, and final conclusions.

• Helps future engagement teams understand prior-year judgments and recurring matters.

PCAOB AS 1215: Core Audit Documentation Requirements

AS 1215 requires documentation sufficiently detailed to let an experienced auditor with no previous connection to the engagement understand the nature, timing, extent, results, evidence, and conclusions of audit procedures. It also must identify who performed the work, when it was completed, who reviewed it, and the review date.

Document purpose, source and conclusion

Each important workpaper should make clear what was tested, why it was tested, the population or source used, the procedure performed, the result, and the auditor’s conclusion. A saved spreadsheet with numbers but no explanation of the tests and findings may not be sufficient.

Link documentation to financial statement assertions and assessed risks

The file should demonstrate compliance with PCAOB standards, support conclusions regarding relevant assertions, and show how underlying accounting records reconcile with financial statements. Risk assessments and responses should be documented with clear linkage, including significant risks and responses.

Retain contradictory and significant findings

AS 1215 requires retention of information concerning significant findings that contradict or are inconsistent with final conclusions, along with the responses and resolutions. Workpapers cannot simply discard unfavorable evidence because an issue was ultimately resolved.

Record identification and reviewer details

When documents, confirmations or samples are inspected, the items inspected should be identifiable. Workpapers also need preparer and reviewer information and completion/review dates. Significant issues must be captured in an engagement completion document or cross-referenced to detailed workpapers.

Audit Documentation Process: From Planning to Archive

The 14-Day Assembly Deadline and Seven-Year Retention Rule

For audits within the relevant effective-date provisions, amended AS 1215 requires the final audit documentation to be assembled for retention no more than 14 days after the report release date. The older 45-day assembly rule is not the current default for covered audits. The 14-day change applies to firms with more than 100 issuer audit reports in calendar 2024 for financial statement audits of fiscal years beginning on or after December 15, 2024; for other registered firms it applies to audits of fiscal years beginning on or after December 15, 2025.

Importantly, all necessary audit procedures, sufficient supporting evidence, and supervisory reviews must be completed before the report release date. The post-release assembly window is not permission to perform the underlying audit later.

AS 1215 generally requires retaining audit documentation for seven years from the report release date, unless a longer retention period is required by law. Special starting points apply where no report is issued or the engagement is not completed. After the documentation completion date, the auditor must not delete or discard audit documentation; any additions must show who added the material, when, and why.

As of October 2026, additional amendments to AS 1215 paragraphs .09 and .11 have been approved and become effective on December 15, 2026. Auditors should consult the text applicable to the specific engagement period and effective date.

Audit Documentation Example: Accounts Receivable Confirmation Workpaper

The following is an illustrative workpaper outline, not a completed audit opinion or proof of sufficient audit evidence.

Weak documentation: “Checked AR. No issues.” Strong documentation identifies the specific records, selection criteria, evidence inspected, exceptions, resolution, and basis for the conclusion. This example should be adapted to the audit risks and applicable PCAOB requirements.

Audit Documentation Checklist for PCAOB Engagements

• Confirm applicable PCAOB standards and effective dates for the engagement.

• Prepare an index of workpapers and a clear naming/cross-reference convention.

• Document engagement acceptance, independence and planning considerations or approved repository references.

• Identify significant accounts, assertions, risks and corresponding audit responses.

• Record nature, timing, extent, results and conclusions for every relevant procedure.

• Preserve sufficient evidence of items selected and inspected.

• Document estimates, unusual transactions, contradictory evidence and professional consultations.

• Record detected misstatements and evaluation of uncorrected misstatements.

• Identify significant deficiencies and material weaknesses when applicable.

• Capture who performed work, completion date, reviewer and review date.

• Prepare the engagement completion document listing significant findings and issues.

• Complete all procedures and supervisory reviews before report release.

• Assemble and archive the final file within the applicable 14-day completion period.

• Preserve the file for at least seven years or longer if legally required.

• Maintain controlled access and records of additions after finalization.

Audit Documentation PDF, Notes, PPT and Audit File Templates

Professionals searching for an audit documentation PDF often want either the authoritative PCAOB standard or a reusable checklist. The official AS 1215 page and PCAOB auditing standards publications are the appropriate primary references. A downloadable checklist can summarize workflow, but it should not be represented as a substitute for full documentation requirements.

Audit documentation notes or PPT training materials can explain objectives, sample workpapers, and completion rules. For the actual audit file, however, the team needs evidential records, cross-references, conclusions and review trails—not only slides or narrative summaries.

Audit Documentation ISA 230 vs PCAOB AS 1215 vs AICPA AU-C 230

A company’s audit framework matters. An issuer audit should not adopt ISA or AICPA timelines where PCAOB standards govern the engagement. Jurisdiction-specific laws, firm policies and additional requirements can impose longer retention periods.

Common Audit Documentation Deficiencies

Missing evidence or incomplete conclusions

A procedure named in an audit program does not demonstrate it occurred. Auditors should retain sufficiently clear workpaper evidence and explain conclusions that are not evident from the records.

Unclear selection criteria

Samples should be traceable to identified populations and selection methods. Reviewers must be able to determine which records were tested.

Late review and undocumented changes

Review activity and resolution of notes must be documented before report release. After final assembly, additions require clear attribution, date and reason; deletion or discarding is prohibited.

Failing to connect workpapers to identified risks

An organized audit file should demonstrate which audit response addressed each identified material risk, not merely contain large volumes of unrelated documents.

How Finance Teams Can Prepare Better Supporting Documents

Management does not prepare the independent auditor’s workpapers, but it can help by maintaining accurate accounting schedules, reconciliations, contracts, approval evidence and a well-organized prepared-by-client (PBC) request tracker. The external auditor remains responsible for determining sufficient appropriate audit evidence and documenting the audit.

• Assign an owner to each PBC request and agree on document formats.

• Reconcile submitted schedules to the trial balance and financial statements.

• Use consistent version controls and secure upload methods.

• Provide full contracts and supporting approvals when requested.

• Respond to unresolved exceptions promptly and retain management explanations.

For a more detailed client-side process, see MBP Global’s audit evidence and PBC guidance and its financial statement audit preparation resources.

Choosing an Independent Auditor for PCAOB-Documented Engagements

For companies preparing for a U.S. public company audit, the relevant question is not which workpaper software the firm uses alone. Management and the audit committee should evaluate PCAOB registration, applicable independence, issuer audit experience, technical accounting resources, engagement staffing, communication, and the firm’s quality management procedures.

A qualified independent auditor applies professional judgment in planning procedures, evaluating audit evidence, documenting conclusions, and issuing the required report. MBP Global LLP offers audit and assurance services for organizations navigating financial reporting and public company audit requirements. Any services provided must comply with applicable auditor independence requirements.

Explore MBP Global Audit & Assurance Services

Frequently Asked Questions

What is audit documentation?

The records of procedures, evidence, findings and conclusions supporting the auditor’s representations, including the independent audit report.

What is the difference between audit documentation and an audit file?

Documentation is the individual workpaper and other records; the audit file is the organized collection for an engagement.

What is a good audit documentation example?

A confirmation workpaper that identifies its objective, population, selections, responses, exceptions, conclusion, preparer and reviewer.

How long must PCAOB audit documentation be kept?

Generally seven years from the report release date, unless a longer legal period applies.

Is the PCAOB documentation assembly deadline 45 or 14 days?

For audits covered by the amended effective dates, 14 days. Older resources may still describe the superseded 45-day rule.

Can audit documentation be changed after final assembly?

Additions may be documented with date, author and reason. Existing documentation must not be deleted or discarded after completion.

Are audit documentation templates sufficient for compliance?

No. Templates help organize work, but sufficiency depends on risks, procedures, evidence and professional judgment.

Is ISA 230 the same as AS 1215?

No. The principles overlap, but they apply under different standard-setting frameworks with different assembly and retention guidance.

Conclusion: 

Audit documentation under PCAOB AS 1215 is not simply administrative recordkeeping. It supports the audit opinion, documents professional judgments, allows informed review, and preserves evidence of the work performed. Proper risk linkage, complete findings, timely supervisory review, a final engagement completion document, and compliant retention are critical parts of the process.

For businesses preparing for issuer audits or assessing independent auditor qualifications, MBP Global LLP’s audit and assurance practice can help clarify the scope of the appropriate engagement.