How to Build a PBC List Without the Fieldwork Scramble

The PBC list — Prepared by Client — is the set of documents, schedules, workpapers and supporting evidence that you provide to your auditors. It is, in practical terms, the foundation on which the entire audit is built.

A well-organised, complete PBC pack shortens fieldwork. It reduces query volumes. It signals a well-controlled finance function. And it protects your team from the disruption and stress of being caught unprepared when auditors arrive.

A poorly organised or incomplete PBC pack does the opposite: it extends fieldwork, generates queries, creates the impression of a fragile control environment and leaves the finance team scrambling to produce evidence while simultaneously trying to do their day jobs.

The difference between these outcomes is almost entirely within management's control.

What the PBC List Actually Contains

The PBC list is not a single document. It is a structured collection covering several categories of request:

Financial workpapers: Reconciliations, lead schedules, account analyses and calculation workpapers that support material balances and transactions in the financial statements.

Control evidence: Documentation that key controls operated during the period — approved journals, reconciliation sign-offs, access review records, board minutes confirming approvals.

Supporting schedules: Aged debtor reports, fixed asset registers, accruals schedules, prepayments, inter-company balances, bank reconciliations.

Legal and compliance documents: Board minutes, shareholder resolutions, material contracts, debt agreements, regulatory correspondence.

Accounting judgement papers: For each area of significant estimate or judgement — standalone papers documenting the treatment, the basis and the approval.

HR and payroll: Headcount records, starters and leavers listing, payroll reconciliations, benefit schedules.

Systems documentation: For ITGC testing — user access listings, change logs, segregation of duty matrices.

The exact content varies by engagement. The auditors' PBC list, issued in advance of fieldwork, is the definitive scope. The point is that "the PBC" is a significant body of work — not a collection of a few spreadsheets.

Why the Scramble Happens

The fieldwork scramble is almost always a planning failure, not a competence failure. The items on the PBC list are not secret. Most of them are predictable from prior years. And yet, in many finance teams, the response to the PBC list is a reactive surge of activity in the days immediately before auditors arrive.

Several dynamics contribute to this:

The list arrives later than expected. Auditors sometimes issue the PBC list later than planned, compressing preparation time. This is partly within your control: ask for it early, and push back if it is delayed.

Items require work that was not built into the schedule. A request for a fully reconciled, signed-off accruals schedule at year end sounds simple. But if the accruals calculation was not completed and signed off as part of the close process, producing it post-close requires rework.

The team is still mid-close when auditors arrive. Where the year-end close runs long — delayed management accounts, late adjustments, unresolved reconciling items — the finance team is simultaneously trying to close the books and prepare the PBC. These two activities compete.

Ownership of the PBC is unclear. Without a named owner for each item and a clear delivery deadline, items drift. The scramble is the natural outcome of undistributed responsibility.

Building a PBC Pack That Works

Start with last year's list.

The best predictor of this year's PBC is last year's. Pull the prior year list and categorise every item: items that were provided on time, items that required chasing, and items that caused extended queries or rework. The last two categories are your highest-risk items for this year.

Request the current year list early.

Engage your audit partner in the pre-fieldwork period and ask for the PBC list at least six to eight weeks before fieldwork begins. Some items — particularly complex schedules and judgement papers — cannot be produced in days.

Assign every item an owner and a deadline.

Create a PBC tracker. For each item on the list: the request description, the name of the person responsible for producing it, the target completion date (at least two weeks before fieldwork starts), the review owner, and the current status.

This is a project management exercise as much as an accounting one.

Build PBC items into the close process.

Many PBC items are not separate pieces of work — they are outputs of the close process. A bank reconciliation prepared and signed off as part of month-end close is also a PBC item. An accruals schedule approved by the FD during close is audit-ready from the moment it is completed.

Design the year-end close process with the PBC list in view. Every deliverable that appears on both lists should be produced once, correctly, as part of close — not twice.

Create a naming and filing convention.

Disorganised files are almost as problematic as incomplete ones. Auditors working through a shared folder that contains unlabelled spreadsheets, multiple versions of the same document and inconsistent naming cannot work efficiently. Before fieldwork begins, agree a folder structure, a naming convention and a version control approach. Enforce it.

Review before you submit.

Before handing the PBC pack to auditors, review it. For each item: is it present? Is it complete? Does it agree to the financial statements? Is it signed off by an appropriate reviewer?

An item in the PBC pack that does not reconcile to the accounts is worse than an item that was not provided — because it raises questions about the reliability of the whole pack.

What a Good PBC Pack Signals

Beyond its functional purpose, the PBC pack is one of the clearest signals of the maturity of the finance function.

Auditors form an impression of the control environment within the first day of fieldwork. A complete, well-organised, clearly labelled PBC pack — delivered before fieldwork begins, with every item signed off — tells them that the finance team is in control, that evidence is being retained as a matter of course, and that the audit is likely to proceed smoothly.

That impression affects how auditors approach their work: the level of scepticism they apply, the depth of testing they perform on items that appear orderly, and the overall tone of the engagement.

It is not possible to eliminate audit risk through a good PBC pack. But a poor one increases it.

The Practical Timeline

• 8 weeks before fieldwork: Request PBC list. Begin preparing complex items — judgement papers, consolidation workings, significant estimates.
• 6 weeks: Assign all items in PBC tracker. Confirm owners and deadlines.
• 4 weeks: First status review. Identify items at risk of late delivery.
• 2 weeks: All items should be substantially complete. Begin review process.
• 1 week: PBC pack reviewed, reconciled and filed. Outstanding items escalated to FD.
• Fieldwork start: Complete pack handed to auditors, with a covering index.