Review process
How an Aiauto Cloud internal control review moves from first call to findings register — the sequence your team will recognise.
An engagement is a sequence of concrete steps, each with an owner and a visible output. The outline below matches our flagship internal control review.
Scoping conversation
We confirm entities, processes, reporting deadlines, and any prior findings. You receive a draft scope and fee range — not a binding letter yet.
Engagement letter & deposit
Scope, exclusions, timeline, confidentiality, and fees are fixed in writing. Fieldwork starts after the agreed deposit clears.
Information request
Policies, organisation charts, system access extracts, and sample populations land in a shared folder. We flag gaps early rather than discovering them mid-interview.
Walkthroughs
Process owners walk us through live steps — creating a vendor, approving a payment, completing a reconciliation — while we note where practice diverges from the binder.
Sample testing
We select items from agreed populations and test whether the control operated (evidence of review, dual approval, system block, or exception log) for those items.
Draft findings discussion
You see ranked issues before the final register. Factual corrections are welcome; disagreement on risk rating is recorded if it remains.
Final register & close-out
The findings register and supporting notes are issued. A short close-out call covers remediation ownership and optional follow-up testing dates.
What we need from your side
A sponsor who can open doors, a day-to-day contact who knows where files live, and honest answers when a control is skipped under deadline pressure. Hidden workarounds waste everyone’s calendar.
Ready to begin?
Request a review or browse other engagements if you need a narrower pass first.