Scope & assertions
We lock the cycle, accounts, or controls in scope and list the assertions that need support — existence, completeness, valuation, and the rest that apply.
The evidence chain
A clear path from the assertion you must support to the document a reviewer can open without guessing.
How we move from question to filed support
Every engagement follows the same chain so finance owners and reviewers share one vocabulary for what “ready” means.
Collection checklist
Owners receive a concrete list of artefacts: extracts, approvals, reconciliations, confirmations, and exception clearances with due dates.
Index & provenance
Files are named, versioned, and linked back to the assertion map. Screenshots and exports carry system, period, and extractor notes.
Gap review
Missing or weak support is listed openly before handoff, so you decide what to chase rather than discovering holes mid-fieldwork.
Reviewer handoff
We brief the engagement owner on how to navigate the pack and how to log follow-ups if external or internal auditors ask for more.