Field notes · 27 March 2026
Building a PBC list that survives the first week of fieldwork
Practical steps for preparing a prepared-by-client list that reduces back-and-forth during financial audit fieldwork.
A prepared-by-client list is not a wish list from last year’s Excel file. It is a contract with your own calendar. When we run a closing pack readiness check, we ask controllers to annotate each PBC item with three facts: owner, source system extract date, and the reconciliation it supports.
Items without an owner become hallway questions. Items without an extract date become “we will regenerate it tomorrow.” Items that do not point to a reconciliation become orphans that auditors fill with new requests.
We also map anomaly findings back onto the PBC list. If AI-assisted detection flags unusual credit notes in the final ten days of the year, the related revenue cut-off schedule should already be on the list — with sample-ready detail, not a summary tab. That single habit has shortened first-week churn for several of our Taiwan engagements more than any new binder cover sheet.