For CPA Firms
Requesting and tracking evidence (Provided-By-Client list)
How the Provided-By-Client (PBC) list works — single requests, bulk Provided-By-Client uploads, deadlines, reminders, and the cross-link to sampling rows.
8 min readUpdated 16 April 2026
Three ways to request evidence#
- From a sampling row — auto-fills entity, period, transaction reference. Best for §3/§4/§5/§6/§7 sampling.
- From the AUP module — when a procedure needs an extra document (e.g. management letter for §3(c)).
- Bulk Provided-By-Client list at engagement start — upload an Excel of expected documents; the client sees a single checklist.
Anatomy of a request#
- Title ("Payslip — Employee 0042 — Mar 2024") — kept short and unambiguous.
- Description with the evidence required and any anonymisation rules.
- Linked record (sampling row, AUP procedure, supplier ID) — opens automatically when reviewer accepts.
- Assignee — defaults to the section owner on the client side.
- Due date — the client gets reminders at -3d, -1d, +0d, +3d (configurable).
Lifecycle states#
| State | Meaning | Who acts next |
|---|---|---|
| Draft | Composed by CPA but not sent. | CPA — send. |
| Sent | Awaiting client upload. | Client. |
| In-progress | Client opened it; comments allowed. | Client. |
| Submitted | Client uploaded files. | CPA — accept or reject. |
| Accepted | Evidence cleared by CPA. | — |
| Rejected | Returned with a reason; loops back to client. | Client. |
Bulk reminders
From the Provided-By-Client view, multi-select overdue requests and click Remind. The client gets a single digest email instead of one per request.