All features/Clients & engagements
FoundationsOne client record. One audit file per year. Zero version chaos.
Everything in Audit Intelligence hangs off two objects: the client, and the engagement — one audit file per financial year. Set a client up once, and every year after that starts ahead of the last.
Client setup that takes minutes, not meetings.
A client record is deliberately light: legal name, ABN, year-end, contacts. AuditBot can search ASIC and the web to pre-fill the entity profile — you confirm what it found. The deeper classification work, like entity type and PIE status, happens later inside the audit file where the standards require it.
- Each client shows its full engagement history, year by year.
- Client contacts drive the client portal — who receives requests and questionnaires.
- For-profit and not-for-profit entities route to the right templates downstream.
| Client | ABN | Engagements |
|---|---|---|
| Acme Pty Ltd | 11 222 333 444 | FY2023 · FY2024 · FY2025 |
| Brightpath NFP | 55 666 777 888 | FY2024 · FY2025 |
| Coastal Holdings | 99 000 111 222 | FY2025 |
One audit file per year — eight phases, properly gated.
An engagement is the audit file for one financial year. It moves through eight phases — pre-engagement, trial balance, inherent risk, control risk, materiality, risk matrix, execution, completion — and each phase only unlocks when the partner signs off the gate before it. The file index always shows exactly where you are.
- First-year and continuance engagements get different pre-engagement programs.
- Every working paper, journal, request and note belongs to the engagement — no orphan data.
- An activity timeline records every action taken on the file.
Assignments with role-appropriate access.
The partner assigns the team to each engagement — preparers, reviewers, manager, partner, and where required an engagement quality reviewer. Each person's access reflects their role, and nobody touches the file until their independence declaration is signed.
- Independence questionnaires are emailed automatically on assignment.
- Issues block access and alert the partner immediately.
- Read-only QA reviewers can inspect without ever editing the file.
| Member | Role | Independence |
|---|---|---|
| Chanelle P. | Partner | Signed |
| James K. | Manager | Signed |
| Priya S. | Graduate | Pending |
| External QA | Read-only QA | N/A |
Next year starts ahead of this year.
When the new financial year begins, the file rolls forward: the trial-balance mapping is remembered per client, prior-year balances flow into the opening balance test and analytics, and the file structure carries across. Risk assessments deliberately do not roll — the standards expect them reassessed every year, so the platform makes you look again.
- Mapping memory is per client, so industry quirks stick.
- Continuance programs pull prior-year answers forward for review, not blind reuse.
See it on your own engagements.
Start your firm free, or book a demo and we will walk you through the platform on a real audit file.
No credit card to start · Australian-resident data · Cancel anytime