Building a PBC list the auditor will actually use
How to turn a scattered request email into an indexed prepared-by-client list with owners and due dates.
A prepared-by-client (PBC) list fails when it is treated as a dumping ground for every spreadsheet the finance team can export. Auditors need retrieveable items tied to assertions they will test.
Start from the engagement letter
Pull the areas the auditor has flagged for substantive focus — revenue cut-off, inventory existence, related-party disclosures — and build folders around those themes before adding routine lead schedules.
Assign owners, not departments
“Finance” is not an owner. Name the person who can approve release of bank confirmations, the person who holds lease files, and the warehouse supervisor for count sheets.
Date every request
Hong Kong year-ends often collide with Chinese New Year leave and warehouse shutdowns. Put realistic due dates on confirmation letters and count plans, then share the calendar with the auditor’s manager early.
Keep a change log
When the auditor adds a request mid-fieldwork, append it with a date rather than rewriting the whole index. That history prevents arguments about what was “always” on the list.
If you want a second pair of eyes on a draft index before planning week, request a briefing for an audit readiness review.