External audit season has a rhythm every Australian accounting firm knows. Client files land in July after the 30 June year-end, the workpapers get built, and the pack goes to the auditor. Then the queries come back: a missing bank confirmation, a fixed asset register that does not tie to the ledger, a related-party note with no support. Each round of queries adds days, and days add cost. A pack that passes first review is the difference between a clean, profitable engagement and one that drags into September.
What passing first review actually means
Auditors do not expect perfection in a client pack. They expect completeness and traceability. When a senior opens your pack, they want every balance in the trial balance to point to something: a reconciliation, a confirmation, an invoice, or a signed agreement. First review fails when the reviewer has to stop and ask for the thing that should already be there. The goal is a pack where the first pass produces sign-off notes, not a query list.
In practice, a pack that clears first review usually carries the same building blocks:
A trial balance that agrees to the financial statements, with every material account cross-referenced to a workpaper.
Bank reconciliations for every account at balance date, with the closing statement attached.
A fixed asset register that reconciles to the ledger, including additions, disposals and depreciation.
Support for revenue: a sample of invoices, cut-off evidence, and a reconciliation to the BAS lodged with the ATO.
Related-party disclosures with the underlying agreements, consistent with the Australian Accounting Standards.
A clear index so the reviewer can find any item in under a minute.
Where firms lose the most time
The slow part is rarely the accounting judgement. It is the assembly. A junior spends hours renaming files, chasing the one bank statement the client forgot, and checking that the number in the note matches the number in the ledger. On a mid-sized engagement, pack preparation can run to 25 or 30 hours before the auditor sees anything. At a blended rate of $150 an hour, that is more than $4,500 of largely clerical work per client, and a busy firm carries dozens of these through winter. A practice running forty audits can spend upwards of $180,000 a season on pack assembly alone.
The rework is worse than the assembly. When a pack bounces on first review, the file has already moved on in the reviewer's mind. Reopening it, finding the gap, and re-submitting can cost another half day per query. Three or four queries per client, across a full book of work, is where audit margins quietly disappear.
How Claude helps assemble an audit-ready pack
Claude is well suited to the assembly and checking layer, which is exactly where the hours go. You can give Claude the trial balance, the ledger detail, and the draft financial statements, and ask it to flag every balance that has no supporting reference. It reads the documents, compares the figures, and returns a list of gaps before the auditor ever opens the file. That is the first-review query list, produced by your own team, a week early.
A few tasks Claude handles reliably:
Cross-checking that each figure in a note matches the ledger and the trial balance, then listing every mismatch.
Reading a stack of bank statements and confirming each reconciles to the recorded balance at 30 June.
Drafting the pack index and workpaper references so the reviewer can navigate without asking.
Turning messy client emails into a clean, dated schedule of outstanding items to request.
Rewriting file notes in plain, consistent language so every workpaper reads the same way.
None of this replaces professional judgement. The value is that your seniors spend their time on the calls that matter, not on confirming that page 14 agrees to page 3. Claude does the reconciling and the reading; the accountant decides what it means.
A realistic workflow for an Australian firm
A Sydney firm we work with runs pack preparation in three passes. First, the junior loads the client file and asks Claude to build the index and flag unsupported balances. Second, the manager reviews Claude's gap list, requests the missing items from the client, and drops them in as they arrive. Third, before the pack goes out, Claude runs a final completeness check against the audit request list. By the time the external auditor opens the file, the obvious queries are already closed, and their first review turns into sign-off rather than a query memo.
The security question comes up early, and it should. Client financial data is sensitive, and firms carry obligations under the Privacy Act and their own professional standards. Our guidance is to keep this work inside a controlled setup, with the right data handling in place, and to treat Claude as a team member that never takes the file home. We help firms configure that boundary before any client data goes near a model.
Start with one engagement
The lowest-risk way to test this is to pick one audit client this season and run the pack twice: once the way you always have, and once with Claude doing the assembly and the completeness checks. Compare the query list the auditor sends back. Most firms find the difference in the first engagement, then roll it across the book for next year.
If you want to see what this looks like against your own workpaper templates and audit clients, book a short brainstorm with us and we will map it to your process.
