TL;DR
A PBC list, short for Prepared by Client, is the itemized list of documents, schedules, and records an auditor requests from a company to support the audit. It is the audit’s intake document, and without it there is no evidence to test. Its handling matters more than most finance teams expect, because auditors cannot test what has not arrived, and audit fees are rarely fixed.
Key Takeaways: The PBC list is prepared by the audit team and answered by the client, typically issued 30 to 60 days before fieldwork. It requests reconciliations, supporting schedules, contracts, board minutes, system reports, and sample populations, each with a description, period, format, and due date. Outstanding items extend fieldwork directly. Almost all of the client-side work is retrieval and tie-out rather than judgment.
What is a PBC list?
A PBC list is the formal, itemized list of documents, schedules, and data an external auditor requests from a company in order to perform the audit. PBC stands for Prepared by Client, though some firms say Provided by Client, and the same artifact is also called the audit request list or the information request list.
It functions as the audit’s intake document. The evidence on that list becomes the evidentiary foundation for the auditor’s opinion, and without it the engagement cannot meaningfully proceed, since auditors are required to obtain sufficient appropriate evidence before expressing an opinion.
The division of labor is fixed. The audit team prepares the list, typically drafted by the senior auditor or engagement manager based on scope, industry, applicable standards, and issues from the prior year, then reviewed by the engagement partner. The client’s finance team gathers and submits everything on it.
It is not a standard checklist. It varies by company, by industry, by audit type, and from year to year, and it grows during fieldwork as auditors raise follow-up requests, particularly around related party transactions and accounting estimates.
What a PBC list contains
The composition varies, but most lists draw from the same categories.
Financial statements and the trial balance for the period under audit.
Account reconciliations, particularly bank, intercompany, and balance sheet accounts.
Supporting schedules substantiating material balances, such as the fixed asset register, accounts receivable aging, inventory listings, and accruals and prepayments.
Contracts and agreements, including leases, debt facilities, significant customer and supplier contracts, and related party agreements.
Governance records, typically board and committee minutes.
System-generated reports and populations, including transaction listings from which the auditor selects samples, and, for IT controls, user access listings and evidence of report parameters.
Third party confirmations, such as bank, legal, and customer confirmations, which depend on external parties responding and therefore need starting first.
Each request typically carries an identifier, a description, the period covered, a format requirement, a due date, and sometimes a specific sample selection. Those identifiers matter more than they appear to, because every conversation for the following two months will reference them.
When it arrives, and why the timing matters
Practice varies by firm and jurisdiction, but the common pattern is a planning list issued four to six weeks before fieldwork and a fieldwork list two to four weeks before, with many firms sending a consolidated list 30 to 60 days ahead of the engagement start.
That lead time exists for a specific reason. Items depending on third parties, such as bank confirmations, legal letters, and customer confirmations, cannot be accelerated by internal effort, so they have to be initiated first regardless of where they sit on the list.
Every week the list is held before it reaches the client is a week of collection the client does not control. Where an auditor cannot produce even a preliminary list until fieldwork begins, that is worth pushing back on.
Why the PBC response determines audit cost
Here is the part that reframes the exercise, and it is rarely stated plainly by either side.
Audit fees are rarely fixed, and stalled PBC responses are the most common reason audit timelines slip.
The mechanism is simple. Auditors cannot test what has not arrived. When items are outstanding, fieldwork extends, staff remain assigned, open item lists compound, and follow-up cycles multiply. Each of those consumes audit hours, and audit hours are what you are billed for. Scope creep is among the biggest drivers of fees running above projection.
So the variable that determines audit cost is not primarily the complexity of your accounts. It is response latency: how quickly, and how completely, the requested evidence can be produced.
That reframes what the finance team is actually being measured on during an audit. The useful metrics are not accounting quality metrics at all. They are logistics metrics: request completion rate, on-time submission rate, average response time, number of auditor follow-ups, open request aging, and rework volume. They measure the operation of a control you intend to rely on rather than the quality of the underlying accounting.
Rework deserves particular attention. A submitted schedule that does not tie out, where the total on the client’s schedule does not exactly match the general ledger and trial balance, is rejected and comes back. That round trip costs more time than getting it right initially, and tie-out failures are among the most common causes.
What the work actually consists of
Look at what a finance team does when a PBC list arrives, and the character of the work is unmistakable.
Each row has to be read and mapped to an evidence source. The document has to be located, which frequently means it lives in a different system from the one the requester assumed, owned by someone in a different function. The schedule has to be extracted in the requested format and period. It has to be tied out to the general ledger. It has to be named and filed according to the auditor’s structure. And its status has to be tracked against a due date while the auditor asks about something else.
Almost none of this is accounting judgment. It is retrieval, formatting, reconciliation to a control total, and coordination, performed under time pressure by the same people who have just finished the close and are being asked for a forecast update.
This is why audit readiness is described as a year-round discipline rather than a seasonal sprint. When the underlying evidence is continuously organized and tied out, the request list is answered from stock. When it is not, every audit is a collection project run from a standing start.
Where automation fits
Because the constraint is retrieval and tie-out rather than judgment, that is where automation changes the economics.
Automation that can read documents and reason about their contents can take on the assembly step: interpreting what each request is actually asking for, locating the supporting documentation across the systems it lives in, extracting schedules in the requested period and format, and reconciling submitted totals against the general ledger before the schedule goes out rather than after it comes back.
The effect is on response latency specifically, which is the variable that drives fee outcomes. It also reduces rework, since tie-out failures are detectable before submission.
Because this material forms the evidentiary basis of an audit opinion, anything automated here has to be traceable. A schedule assembled by a process nobody can explain invites exactly the question you least want during fieldwork.
To be clear about scope, Kognitos is not audit software. It does not replace the PBC tracking platforms that manage request status and file exchange between firm and client, and it is not an audit management system. What it addresses is the client-side assembly work underneath that tracking: finding the evidence, producing it in the requested form, and confirming it ties, with a record of how each item was produced.
For related material, see our guides on internal controls, AI audit trail requirements, record to report automation, account reconciliation automation, and quality management systems. To see how deterministic AI assembles supporting evidence with a full audit trail, book a demo or try the platform.
Getting started
Three practices consistently separate a smooth audit from a painful one.
Assign an owner to every individual item, not to a department. Departmental ownership produces the same result as no ownership, and the auditor should have one coordinator as their single point of contact rather than contacting people directly.
Map every row to its evidence source before collecting anything. Knowing where each item lives, and which system and person it depends on, turns an undifferentiated list into a sequenced plan and surfaces the third party dependencies that must start immediately.
Tie out before submitting. Run a mock review of each schedule against the original request and against the general ledger. Most rework originates in submissions that were complete but did not reconcile.
