PBC in an audit: what prepared by client means and who owes what

In audit work, PBC stands for "prepared by client" (some firms say "provided by client"). A PBC item is a schedule, reconciliation or document the client produces for the audit team, as opposed to something the team builds itself. The PBC list is the collection of all those requests for one engagement.

The term sounds like jargon, but the idea underneath it is simple and worth getting right with clients: the client owns its books, so the client prepares the support for them, and the audit team tests that support.

What "prepared by client" means

Management is responsible for its financial statements and the records behind them. The engagement letter for an audit typically says so, and it usually also says management will give the auditor access to the information the audit needs. PBC items are how that access works in practice.

Two kinds of things end up on a PBC list:

• Schedules the client prepares. A fixed asset roll-forward, an accounts receivable aging, a grants receivable schedule, a debt summary. These are analyses of the client's own ledger.
• Documents the client already has. Bank statements, loan agreements, board minutes, grant award letters, insurance policies, payroll tax filings.

The audit team then tests the items: agreeing schedules to the general ledger, tracing amounts to source documents, recalculating. A PBC schedule is not accepted as correct just because the client prepared it; that is the point of testing it.

The exact responsibilities on any engagement come from your engagement letter and professional standards. If you are unsure what a client must provide, that is a question for your firm's quality reviewer, not for a guide.

Why firms ask the client to prepare it

• It is the client's information. The bookkeeper knows why a reconciling item exists; an auditor reconstructing it would be guessing.
• It keeps the team auditing, not bookkeeping. Time spent building a schedule the client could have produced is time not spent testing.
• It is cheaper for the client. Senior audit time billed for clerical work makes the engagement cost more, or makes it unprofitable for the firm at the same fee.

When PBC items are late, the cost lands on both sides. The team waits, reschedules, or starts testing out of order. Staff end up working evenings to recover the schedule, and the client gets more follow-up questions in a busier window.

Typical PBC items by area

The audit program decides the real list, but these are common for a small nonprofit, HOA or private-company audit:

• Planning: trial balance, general ledger detail, prior-year adjustments posted, board minutes, organization chart.
• Cash: bank statements, year-end reconciliations, statements for the month after year end.
• Receivables: aging, grants or pledges receivable, assessments receivable for an HOA.
• Fixed assets: roll-forward, support for additions, disposals.
• Liabilities: payables aging, accruals, loan statements and agreements.
• Revenue: grant agreements, donor restrictions, deferred revenue.
• Payroll: registers, tax filings, benefit contributions.
• Other: leases, insurance, related parties, attorney contacts.

The PBC list guide has a fuller table and the columns that make the list trackable.

Who owes what

A PBC list works when every item has a named owner at the client. On a small engagement that is often three to five people:

Writing the owner on each line, in the client's own terms ("Controller", "Jane - ED"), turns one long list into a few short ones. Each person can see what is theirs, and the in-charge can see who is behind.

How PBC requests go wrong

Most delays come from the request process, not from unwilling clients:

• The list arrives as one attachment to one person. That person forwards parts of it, and nobody knows what was forwarded.
• The wording is the firm's, not the client's. "Lead schedule for 1200 series" means nothing to an HOA treasurer.
• Every item is due the same day, so nothing arrives until that day.
• Follow-up depends on someone remembering. During busy season, nobody does.
• Files come back in email threads, so checking what has arrived means searching inboxes.

Keeping PBC requests on schedule

A few practices fix most of it:

1. Roll last year's list forward and remove what no longer applies before sending.
2. Name an owner on every item and send each owner only their own items.
3. Stagger due dates so the schedules the team needs first come first.
4. Follow up on a fixed rhythm instead of when someone notices. A reminder a week before the due date, one on the date, and a short one every few business days after works for many firms.
5. Keep one live status by owner and days late, so the partner's question "what is still missing?" has a one-minute answer.

The PBC request guide has email wording for each of these messages.

Where PBC Nudge fits

PBC Nudge does the sending and chasing for small audit firms. You upload the PBC list you already use in Excel, and each client contact gets one link listing only their items, with no login. Reminders go to each contact 7 days before their next due date, on it, then every 3 business days, up to six. You see what is outstanding by contact and days late, and you can export the status back to Excel.