Audit PBC request list: a workflow, not a static file

The audit PBC request list for a March 31 fiscal-year-end client went out on April 10. By April 25, three reconciliations sit in a shared drive under someone’s initials, the confirmation letters are unsigned, and the manager is asking the senior why fieldwork is still two exhibits short of ready. Nobody sent the list to the wrong person. The list itself was never wrong. What broke was tracking: forty-six line items, one status column, and no way to tell which four are actually blocking sign-off.

An audit PBC request list (PBC stands for prepared by client) is the itemized set of financial statements, reconciliations, contracts, confirmations, and supporting schedules the audit team needs before and during fieldwork. Every firm already builds one. What fails is the layer underneath it: a spreadsheet or PDF that shows what was asked for but not who owns each item, when it is due, or whether a file that arrived is actually the right one.

Why a PBC list template turns into a bottleneck

Whether you call it a PBC list, a prepared by client list, or an audit document request list, the failure mode is the same. Most firms already have a solid PBC list template: a document organized by section, cash, receivables, payables, equity, subsequent events, that lists every schedule the engagement needs. The template is not the problem. What breaks is what happens after the client opens it.

A list with forty or fifty items and a single status column collapses past about a dozen entries. Nobody assigned individual items to a specific person at the client, so everything routes through the controller, who is also closing the books during the same window. Items get marked “sent” the moment the client uploads anything, not when the auditor confirms it is the right document at the right version. A trial balance that ties to last year instead of this year can sit in a shared folder for a week before anyone opens it.

That deadline does not move because a nonprofit’s development director is slow to send grant agreements, or because a controller cannot find last quarter’s debt covenant calculation. For a firm running a dozen single audits in the same quarter, a list that cannot show which of those twelve engagements has three items outstanding and which has thirty is a planning problem long before it is a fieldwork problem. The hidden cost of chasing clients for documents compounds the same way outside audit season, and the fix is structurally identical: replace the single status column with per-item ownership and a due date.

What belongs on the audit PBC request list

What goes on the list depends on the engagement, but most audits repeat the same core categories.

Entity-level documents that apply to nearly every audit:

• Current trial balance and general ledger detail
• Bank reconciliations for every account, with the statement attached
• Fixed asset roll-forward and depreciation schedule
• Debt schedules with amortization tables and covenant compliance calculations
• Signed leases and material contracts entered or amended during the period
• Board and committee minutes for the fiscal year
• Legal letters: the attorney representation letter, plus a list of counsel handling active or threatened litigation
• Management representation letter, signed at the close of fieldwork, not before

Added for single audits and other federal-award engagements:

• Schedule of expenditures of federal awards
• Grant agreements and award letters for each program tested
• Subrecipient monitoring documentation, if the entity passes funds through

Added when related parties are involved:

• Related-party transaction schedules and the terms behind them
• Loan agreements between the entity and any officer, owner, or affiliated entity

Running the PBC list as a tracked workflow

1. 1

   Build the list once per engagement type

   Write a separate template for each recurring engagement type: single audit, employee benefit plan, commercial financial statement audit. A generic list forces every client to scroll past items that do not apply to them, and that is where items stop getting read carefully.

2. 2

   Assign every item to a named person, not a title

   Route the grant agreements to the grants manager and the debt schedule to the CFO directly, instead of sending all forty-six items to the controller and letting them forward pieces by email. The controller becomes a bottleneck the moment they are the single point of contact for documents they do not personally hold.

3. 3

   Send one link with a slot per item and a due date on each

   A single portal link with labeled upload slots and individual due dates replaces an email with a PDF attachment. The client sees exactly what is outstanding and what is done, without opening a spreadsheet someone else is also editing.

4. 4

   Chase only what is outstanding, by name

   A reminder that says "we still need the December bank reconciliation and the signed representation letter" gets a faster response than one that says "please send any remaining items." Naming the exact items left tells the client the list is being watched, not sent once and forgotten.

5. 5

   Validate uploads the day they arrive

   A trial balance in the wrong format or a bank statement missing its final page should surface as a flag on day one, not when the senior opens the file during fieldwork in week three. Catching it early turns a re-request into a same-day fix.

6. 6

   Close the file with a full submission record

   When the last item lands, the complete set exports with a timestamped log of who submitted what and when. That record matters for peer review and for any engagement where a regulator or grantor asks how the file was assembled.

How zendoc runs the audit PBC request list

zendoc for accounting firms is built around exactly this structure: a reusable workflow template per engagement type, one link per client with a labeled slot for every item, AI review that flags an unreadable or wrong-type upload before staff opens it, and reminders that name the specific items still missing. It is not audit engagement software. It does not connect to CaseWare, Suralink, or ProSystem fx Engagement, and it does not perform any audit procedure. It runs the client-facing half of the list: requesting, tracking, validating, and getting signatures on the letters that need one.

Every signed item, the attorney letter and the management representation letter included, keeps a tamper-evident record: timestamp, IP address, browser and device, and per-field signing events, alongside the signed PDF. When the list closes, the engagement team downloads the full set into the workpaper system that actually documents the audit.

Before and after

Firms running the list this way close single audits against a fixed nine-month submission deadline without a last-week scramble, because the outstanding items are visible on day three, not week six. The same structure applies to financial-statement audits, employee benefit plan audits, and reviews: anywhere a firm sends a client a list and needs every item back with a clear record of who provided what.

For the tax-season version of the same problem, tax document collection software for CPAs covers W-2, 1099, and K-1 collection with the same reminder-and-validation pattern. If you are comparing collection tools more broadly, the best document collection software guide covers the category, including where a flat $149-a-month plan beats per-seat pricing and where it does not.

Sources:

• 2 CFR § 200.512, eCFR: single audit report submission deadline under the Uniform Guidance
• Journal of Accountancy, auditing topic hub: AICPA reporting on audit documentation and engagement planning practice