Engagement flow
How we move from your first call to a signed evidence index without rewriting your close calendar.
Custom to this practice
Your close calendar stays in charge
Every CloudNxtGen engagement is timed to a reporting period, a PBC deadline, or a named audit finding. We do not invent a parallel project plan that ignores payroll cut-off, inventory counts, or board pack dates.
Controllers remain the decision owners. We prepare trails, indexes, and residual risk notes; you approve what goes to auditors and group finance.
The four stages
Scope call
Entity, period, pressure point, and access constraints. You receive a one-page fee outline before any fieldwork.
Source map
We list journals, subledgers, warehouses, and approval routes that must appear in the trail for the scoped areas.
Evidence build
Reconciliations and attachments are indexed. Gaps are logged early so you can chase owners while time remains.
Controller handoff
Walkthrough of the pack, residual risk note, and clear end of engagement unless you extend in writing.
What we need from your side
- Named contact for each major subledger (AR, AP, inventory, fixed assets, cash)
- Read-only exports or secure folder access within three business days of kickoff
- Prior-period packs and the current PBC list, even if incomplete
- Decision on which findings are reconstruction vs. disclosure-only