Back to blog

The PBC List, Explained: What Your Auditor Actually Wants

The LedgerProof Team
audit preparation
PBC list
workpapers
GAAP

If you have ever started an audit, you have met the PBC list. PBC stands for "Prepared By Client," and it is the master checklist of documents, schedules, and reconciliations the audit team expects you to deliver before fieldwork begins. A clean PBC response sets the tone for the entire engagement. A late, disorganized one signals risk and almost guarantees more questions, more sampling, and a longer timeline.

This post breaks the PBC list into the categories auditors actually use, so you can stop guessing what "support for the balance" really means.

Why the PBC list exists

Auditors do not start from your books. They start from your assertions — that the cash balance exists, that receivables are collectible, that liabilities are complete. The PBC list is how they gather the evidence to test those assertions efficiently. Every item on it maps to a financial-statement line and a specific risk the auditor is required to address.

When you understand that mapping, the list stops looking like busywork and starts looking like a structured argument for why your numbers are right.

The core categories

1. Trial balance and lead schedules

The starting point is always a final, locked trial balance that agrees to the financial statements. From there, auditors want lead schedules that group accounts into financial-statement captions (for example, all cash accounts rolling up to one "Cash" line). Each lead schedule should tie to the trial balance to the penny.

2. Reconciliations

For every significant balance-sheet account, expect a request for a reconciliation that explains the difference between the general ledger and an independent source:

  • Bank reconciliations for each cash account
  • Accounts receivable aging that ties to the GL control account
  • Accounts payable aging that ties to the GL control account
  • Fixed-asset and accumulated-depreciation roll-forwards
  • Debt schedules with principal, interest, and covenant detail

3. Support for activity

Beyond balances, auditors test the transactions that produced them. Common requests include revenue detail by customer or contract, payroll registers, and major expense support around the period end (the "cutoff" testing window).

4. Estimates and judgments

Reserves, allowances, accruals, and impairment analyses are where audits slow down, because they require documented judgment. Auditors want your methodology, your inputs, and your math — not just the final number.

5. Governance and legal

Board minutes, signed agreements, debt covenants, and attorney letters round out the package. These rarely change your numbers, but missing them stalls sign-off.

How to assemble it without the fire drill

The most painful part of the PBC list is not any single item — it is the cumulative effort of pulling, formatting, indexing, and cross-referencing dozens of schedules while still closing the books. A few habits make it dramatically easier:

  1. Lock the trial balance first. Nothing else can be relied on until the TB is final. Build every schedule off the same locked version.
  2. Index everything. Give each workpaper a reference (A-1, B-2, and so on) and cross-reference it to the lead schedule and the trial balance line.
  3. Reconcile before you submit. If a schedule does not tie to the GL, the auditor will find it — and now you own a finding instead of a clean file.
  4. Document the judgment, not just the answer. For every estimate, write a short memo: method, inputs, conclusion.

Where LedgerProof fits

LedgerProof connects to QuickBooks Online (read-only by default) and generates much of the PBC package directly from your data: a locked trial balance, lead schedules that roll up by caption, account reconciliations, fixed-asset and debt roll-forwards, and an indexed workpaper set you can hand to the audit team. It also runs a library of GAAP-oriented review procedures to flag likely adjustments before the auditor does, so you walk in with a cleaner file.

A note on scope: LedgerProof is a preparation aid, not an audit, an assurance engagement, or a GAAP-conformity opinion, and it is not a substitute for a CPA or auditor. Its findings are heuristic, may include false positives, and require your professional judgment. Think of it as the tool that gets your PBC package organized and defensible — the audit itself still belongs to your independent auditor.

The bottom line

The PBC list is not a hurdle; it is a preview of how the audit will go. Treat it as a structured set of assertions to support, build every schedule off a locked trial balance, index and reconcile as you go, and document your judgments. Do that, and fieldwork becomes a confirmation exercise instead of an investigation.