Audit Evidence: What Auditors Request and How to Prepare Your PBC List

Audit Evidence: What Auditors Request and How to Prepare Your PBC List

var(--variable-LoqRZ1RA_)
var(--variable-LoqRZ1RA_)

Audit evidence is the information an auditor uses to reach conclusions about financial statements and, when applicable, internal controls. For companies preparing for a financial statement audit, understanding what evidence is needed—and organizing it in a clear prepared-by-client (PBC) list—can reduce delays, improve coordination, and help finance teams respond accurately to audit requests.

Auditors do not simply collect documents. They assess whether information is relevant, reliable, complete, and sufficient to address specific risks. This guide explains the major types and sources of audit evidence, how PCAOB AS 1105 and ISA 500 approach evidence, and how to build a practical PBC tracker for a private company audit, SEC audit, or IPO readiness engagement.

What Is Audit Evidence in Auditing?

Audit evidence includes information obtained from audit procedures and other sources that supports or contradicts management’s financial statement assertions. Examples include bank confirmations, approved contracts, invoices, accounting records, external valuation information, inventory observations, and evidence of control performance. An auditor evaluates evidence rather than accepting every client-provided document at face value.

For a fuller overview of audit planning, see MBP Global’s Financial Statement Audit Services guide and what to expect from a financial statement audit.

What Makes Evidence Sufficient and Appropriate?

Sufficiency refers to the quantity of evidence needed. Appropriateness refers to its quality—specifically its relevance and reliability. Higher assessed risks generally require more persuasive evidence. Importantly, a large volume of weak evidence cannot necessarily compensate for poor quality. These principles are central to PCAOB AS 1105 and ISA 500.

The Assertion Determines the Evidence

Evidence has to address the relevant audit assertion. A bank statement may support the existence of cash, but not by itself resolve all rights, restrictions, or disclosure questions. Likewise, invoices may support recorded sales but may not demonstrate that all revenue earned during the period was recorded. Auditors tailor tests to assertions such as existence, completeness, accuracy, valuation, rights and obligations, and presentation.

Types of Audit Evidence: Seven Common Audit Procedures

Audit procedures can yield several kinds of evidence. There is no universally reliable ranking that applies to every circumstance; source, controls over information, how directly evidence was obtained, and the assertion being tested all matter.

Procedure

Practical example

Key limitation

Inspection

Inspect an executed customer agreement or physically examine inventory

Authenticity and completeness may require further work

Observation

Watch an inventory count or control being performed

Evidence generally relates to the time observed

External confirmation

Obtain a bank or receivable confirmation sent directly to the auditor

Response and exception handling must be controlled

Recalculation

Recompute depreciation or interest

Tests mathematics, not all underlying assumptions

Reperformance

Independently reperform a reconciliation or review control

Scope limited to selected activity and timing

Analytical procedures

Compare gross margins, headcount, and payroll patterns

Unexpected variations usually require investigation

Inquiry

Interview finance staff about a significant transaction

Inquiry alone is normally insufficient for key assertions

 

Additional Sources of Audit Evidence

Documents and data may come from the general ledger, subledgers, customer or supplier contracts, banks, third-party custodians, payroll processors, tax authorities, ERP systems, board minutes, lawyers, and specialists. External sources may provide stronger evidence in some settings, but the auditor still considers the trustworthiness of the source and whether the information has been modified. Company-produced reports may require accuracy and completeness testing.

Characteristics of Audit Evidence: Relevance, Reliability and Sufficiency

A useful way to prepare for an audit is to evaluate each requested file against four questions: Does it cover the correct reporting period? Can the figures be tied to the ledger? Is it complete and supported by source information? Can someone identify who prepared or approved it?

  • Relevance: evidence relates directly to the particular assertion or control objective.

  • Reliability: evidence quality depends on its source, nature, controls over production, and how it was obtained.

  • Sufficiency: evidence quantity responds to assessed risk and quality.

  • Consistency: contradictory evidence must be investigated, not set aside.

  • Traceability: clear file naming, report parameters, and reconciliations let auditors follow transactions from sources to the financial statements.

PCAOB AS 1105 vs. ISA 500: Audit Evidence Requirements

PCAOB AS 1105 governs evidence for audits under PCAOB standards, including applicable U.S. issuer engagements. International Standard on Auditing (ISA) 500 addresses audit evidence within the International Standards on Auditing framework. Both emphasize sufficient appropriate evidence, with detailed differences in their language, related standards, and application. Companies should confirm which auditing framework applies to their engagement.

Topic

PCAOB AS 1105

ISA 500

Primary context

PCAOB-standard audits, often SEC issuer audits

Engagements under International Standards on Auditing

Core principle

Sufficient appropriate evidence supports opinion

Sufficient appropriate evidence supports reasonable conclusions

Quality emphasis

Relevance and reliability

Relevance and reliability

Client-generated information

Evaluate accuracy, completeness, and necessary detail

Evaluate reliability of information produced by the entity

Practical takeaway

Prepare traceable support and reliable electronic data

Prepare traceable support and reliable electronic data

 

For publicly reporting companies, MBP Global’s PCAOB audit guide and public company versus private company audit comparison provide relevant context.

What Is a PBC List in a Financial Statement Audit?

A prepared-by-client (PBC) list is a coordinated request tracker identifying records, schedules, confirmations, explanations, and supporting files that the client is responsible for assembling for the audit team. The specific list is tailored by the auditor to the engagement and should not be mistaken for an exhaustive standardized requirement.

A good PBC list gives every request an owner, due date, period, purpose, status, and file location. The list should also distinguish original requests from follow-up items and track whether auditors have accepted the submission or asked for revisions.

Recommended PBC Tracker Fields

Field

Example

Request ID

REV-03

Category

Revenue

Request

Signed agreements for selected material customers

Reporting period

Year ended December 31, 2026

Owner

Revenue controller

Due date

Agreed with auditor

Status

Not started / In progress / Submitted / Follow-up / Closed

Evidence link

Controlled folder path

Reviewer notes

Reconciles to ledger account 4000

 

Financial Statement Audit PBC List: Copyable Checklist

Use this illustrative checklist to organize information. The independent auditor will define actual sample selections and request scope. Do not send sensitive records through unsecured channels.

Corporate, Governance and Accounting

  • Trial balance and general ledger export for the audit period.

  • Chart of accounts and year-end close schedule.

  • Organization chart, legal entity listing, and board minutes.

  • Accounting policies and prior-year audited financial statements.

  • Significant transaction and related-party summaries.

Cash, Receivables and Revenue

  • Bank reconciliations and statements for all significant accounts.

  • Cash restrictions and debt covenant information.

  • Accounts receivable aging and allowance calculations.

  • Revenue roll-forward, contracts, refunds, and significant credit memos.

  • Selected invoice, shipping, and performance-obligation support.

Expenses, Payroll, Assets and Liabilities

  • Accounts payable aging and accrual supporting schedules.

  • Payroll registers and reconciliation to financial statements.

  • Fixed asset register, additions, disposals, and depreciation.

  • Inventory counts, roll-forward, and valuation analyses if applicable.

  • Debt agreements, lease schedules, and interest calculations.

Estimates, Taxes, Equity and Disclosures

  • Impairment, expected credit loss, or other material estimates and assumptions.

  • Tax provision support and significant tax correspondence.

  • Equity capitalization table, option grants, and stock compensation valuations.

  • Related-party and litigation representations or documentation.

  • Draft financial statements, footnotes, and subsequent-events log.

Public Company and ICFR Items, if Applicable

  • Relevant control narratives and risk-control matrices.

  • Selected control evidence and system access reports.

  • Management’s evaluation of identified control deficiencies.

  • Audit committee communications and relevant governance documentation.

  • SEC reporting schedules and support for significant disclosures.

For ICFR documentation, refer to Internal Control Over Financial Reporting: Guide for Public Companies, the SOX compliance checklist, and guidance on material weakness remediation.

How to Prepare an Audit-Ready PBC List: A Six-Step Workflow

A disciplined preparation process helps avoid duplicate requests and repeated follow-up questions.

1. Agree on Scope and Deadlines

Confirm entities, reporting periods, audit standards, milestones, and the secure document-sharing method with the engagement team.

2. Assign Owners and Reviewers

Allocate each request to a person who can obtain the material. Require a second review for high-risk or significant schedules.

3. Reconcile Every Major Schedule

Tie schedules to the signed-off trial balance and document reconciling differences before submission.

4. Preserve Source and Parameters

Retain original exports, report dates, filters, formulas, and key assumptions so auditors can assess accuracy and completeness.

5. Submit in Batches With Status Tracking

Use controlled naming, version numbers, and clear submitted/accepted/follow-up status. Do not overwrite prior evidence silently.

6. Resolve Exceptions Promptly

Log clarifications, mismatches, missing documentation, and owners; record the final resolution and supporting file.

Practical Audit Evidence Example: Testing Revenue Cutoff

Suppose a company records a material sale on December 31. The auditor may request the customer contract, invoice, delivery or acceptance documentation, revenue recognition analysis, and accounting entry. The objective is not simply to see an invoice: the auditor seeks support for when the performance obligation was satisfied and whether the transaction belongs in the reporting period.

If the company supplies only an invoice without delivery or acceptance evidence, the auditor may request additional evidence. This illustrates the difference between providing paperwork and providing evidence that addresses the relevant assertion.

Common PBC and Audit Evidence Mistakes

Typical avoidable problems include sending unreconciled schedules, providing screenshots without report parameters, ignoring contradictory documents, sending incomplete populations, failing to document management reviews, and supplying explanations without corroboration. Sensitive records also require access controls and a secure transfer method.

One particularly important issue for public companies is information produced by the company (IPE): reports drawn from ERP systems may need testing of completeness, accuracy, and sufficient detail. See PCAOB AS 1105 for the specific requirements.

How Long Does Audit Evidence Collection Take?

There is no standard duration. Preparation depends on the number of entities, records quality, audit scope, significant accounting estimates, available personnel, and responsiveness to auditor follow-ups. Companies should agree on staged delivery dates and prioritize high-risk accounts before the audit fieldwork peak.

Cost and timing often increase when reconciliations are incomplete or document ownership is unclear. For a fuller breakdown, read Financial Statement Audit Services: Process, Timeline and Cost.

When to Engage an Independent Financial Statement Auditor

A company may need an independent audit for lender or investor requirements, corporate transactions, an IPO, or ongoing SEC financial reporting. For a U.S. issuer audit, the firm generally must be PCAOB-registered and meet applicable independence requirements. The appropriate standards and scope depend on the intended use of the financial statements.

MBP Global LLP offers audit and assurance services to organizations with public and private company reporting needs. Businesses preparing for an audit can review MBP Global’s Audit & Assurance services and contact the firm to discuss engagement scope, documentation needs, and timing.

Frequently Asked Questions About Audit Evidence

What is audit evidence in auditing?

It is information auditors use to support conclusions about financial statements or controls, including information that corroborates or contradicts management assertions.

What are the main types of audit evidence?

Common procedures include inspection, observation, inquiry, external confirmation, recalculation, reperformance, and analytical procedures.

What are the sources of audit evidence?

Evidence may originate from internal accounting records, bank or customer confirmations, legal agreements, specialists, third-party platforms, and auditor-performed procedures.

What is the difference between sufficiency and appropriateness?

Sufficiency concerns quantity; appropriateness concerns relevance and reliability. Both are required.

What are audit evidence notes?

In study contexts, the term often refers to concise summaries of standards, methods, and evidence evaluation. In practice, documentation should identify the procedure, source, period, conclusion, and exceptions.

Does ISA 500 apply to PCAOB audits?

ISA 500 and PCAOB AS 1105 belong to different auditing frameworks. Confirm the applicable standards with the engagement auditor.

Can inquiry alone serve as sufficient audit evidence?

Ordinarily, inquiry alone is not enough to address key assertions or establish control effectiveness in a PCAOB audit; corroborating procedures are typically needed.

What is a PBC list?

A prepared-by-client list tracks documents and schedules the client will provide, with owners, due dates, status, and follow-up notes.

Can a company download a standard audit evidence PDF?

Standards can be reviewed through official regulator or standard-setting sources; there is no single universal PBC PDF suitable for every engagement.

How do we reduce repeat audit requests?

Reconcile schedules first, retain source reports and parameters, name evidence consistently, and maintain a centralized exception and request tracker.

Conclusion:

A complete PBC list does not replace professional judgment or independent audit procedures. It does help companies deliver organized, relevant, and traceable information so auditors can assess evidence efficiently. Finance teams should start with reconciled financial records, prioritize higher-risk balances, preserve reliable source data, and maintain a clear request tracker.

For companies planning a financial statement audit, IPO, or SEC reporting engagement, MBP Global LLP’s Audit & Assurance practice provides a starting point for discussing the appropriate audit scope and readiness steps.