Sample practice: 20 documents are requested from one client.
16 are accepted. 3 are missing and 1 covers the wrong period.
The 4 unresolved items go to the team. The pack stays on hold.
Automation moves the chase along; 4 of 20 items are still open, so the partner holds the pack.
Illustrative figures, not client data.
In short
Choose a workflow with a clear trigger and reviewer.
Check native features and plan limits before buying another tool.
Keep professional judgement and client release with accountable people.
A practice needs fewer unfinished handovers, not another tool list. I would start where missing information repeatedly holds up otherwise straightforward work.
I’m a Chartered Accountant who builds connected systems. These are proposed workflows, not claims about builds for an accounting client.
Exhibit 2
Of 20 requested documents, 4 are still open, so the pack stays on hold
Requested
20
Documents requested from one client
Sample practice, not client data.
Moves on
16
Accepted for the right entity and period
These can move on.
Release blocked
4
Not accepted: 3 missing and 1 for the wrong period
Routed to the team to resolve.
Illustrative figures, not client data.
Intake and document chasing
Exhibit 3
Correct intake prevents the wrong chase
Workflow and trigger
Inputs; native starting point
Exception; partner signs
Intake: engagement accepted
Entity, scope, access; Karbon templates and Dext client accounts
Duplicate entity or unclear scope; engagement and access
Document chasing: request due
Period, required list; Karbon reminders
Missing or wrong-period file; unresolved-information treatment
Capabilities as the vendors document them, read 31 October 2026. Triggers, exceptions and sign-offs are an illustrative control design, and ‘partner signs’ is a proposed approval, not a statutory signing requirement.
Exhibit 4
Three steps keep the chase aimed at the right document
01
Set the scope first
Set the entity, period and engagement scope before anything moves.
02
Start from native features
Karbon documents templates, requests and reminders. Dext provides client accounts and document collection.
03
Accept the right file
A received file may cover the wrong period. Stop chasing only when the right document is accepted.
Set the entity, period and engagement scope before anything moves. Karbon documents templates, requests and reminders. Dext provides separate client accounts and document collection. These native features are starting points, not proof that your whole workflow is configured.
Bank review and billing
Exhibit 5
Review gates separate preparation from release
Workflow and trigger
Inputs; native starting point
Exception; partner signs
Bank and coding review: data received
Statements, receipts; Dext extraction, Bank Match and coding rules
Missing evidence or unusual treatment; material judgements
WIP to invoice: job ready
Time, fees, cut-off; FYI draft-invoice automation, subject to eligibility
Future WIP or scope dispute; write-offs and invoice release
Capabilities as the vendors document them, read 31 October 2026. WIP means work in progress. Triggers, exceptions and review gates are illustrative recommendations.
Exhibit 6
The two billing routes differ, so do not assume identical controls
FYI Create Invoice
Requires Elite
Needs FYI as the practice-management source
Eligibility table excludes Xero Practice Manager
Xero Partner Hub
Documents time-to-invoice features
Check its controls separately
Capabilities as the vendors document them, read 31 October 2026.
Keep totals and matching in rules. Use AI for draft explanations and uncertain-item flags. A reviewer checks the underlying evidence.
FYI’s Create Invoice automation requires Elite with FYI as the practice-management source. Its eligibility table excludes Xero Practice Manager. Xero separately documents time-to-invoice features in Partner Hub. Do not assume the two routes have identical controls.
Month-end after the close
Exhibit 7
The pack waits for the closed period
01Close accepted
The period is closed and the ledger and comparatives are final.
02Ledger and comparatives
Inputs: the closed ledger, the period and the comparatives.
03Syft report template and draft insights
A report template and AI draft insights; each figure still needs a source.
04Reviewer resolves mapping or explanation gaps
An unexplained variance stays visible until a person explains it.
05Partner approves client pack
Nothing goes to the client before the partner approves it.
Syft’s reporting capability as documented, read 31 October 2026. The sequence and approvals are illustrative.
Syft documents report templates and exports with AI insights. A fluent explanation still needs a source. Tie figures to the closed ledger and ask what actually caused the movement.
Keep unexplained changes visible. A pack that hides uncertainty is harder for a partner to review.
Accountability stays with the practice
Exhibit 8
Preparation can move while judgement stays accountable
Rules and AI
Rules: dates, totals, matches, routing
AI: suggested wording and flags
Team and partner
Team: evidence, exceptions, corrections
Partner: material judgements and release
An illustrative division of responsibilities, informed by the TPB’s guidance and CPA Australia. No autonomous judgement or tested performance is claimed.
TPB(GS) 55/2026, issued 22 July 2026, keeps accuracy and competence with tax practitioners using AI. Review and document AI output throughout the workflow.
Check client permission before third-party disclosure, unless a legal duty applies. Map the actual data flow. OAIC guidance recommends due diligence and human oversight when selecting AI products. This is general information; get advice on your practice’s confidentiality, privacy and tax obligations.
CPA Australia, AI Hub, which says to confirm accounting and regulatory answers with primary sources.
What to do first
Exhibit 9
Test a small workflow before expanding access
01Choose one queue
One bounded workflow with a clear trigger and a named reviewer.
02Approve data access
Check client permission and the data flow before any sample data moves.
03Test exceptions
Include a missing file and a wrong-period file.
04Measure and review
Preparation, review and rework separately, with software, setup and support costs beside any payback.
Sample scorecard: requested 20; accepted 16; missing 3; wrong period 1; unresolved 4; release blocked. No client data or measured result.
Illustrative figures, not client data.
Test one bounded workflow using sample data. Measure preparation, review and rework separately. Record software, setup and ongoing support costs alongside any proposed payback. Time released does not automatically reduce payroll.
Common questions
Can you use AI as an accountant?
Yes, within the relevant professional and confidentiality obligations. The Tax Practitioners Board’s guidance keeps tax practitioners accountable when AI supports tax agent services.
Is Claude or ChatGPT better for accounting?
Test the same approved task, evidence and review criteria. Select for suitability, access controls and total cost rather than a general ranking.
Which AI is best for solving accounting problems?
Start with the workflow and its existing software features. CPA Australia advises checking accounting and regulatory answers against authoritative sources.
Chartered Accountant (CA ANZ) and finance executive, based in Canberra. Practical AI and automation for SMEs, and adviser to owners, CEOs and boards on integration and finance.
Work is stuck between systems and reviewers? I use the Diagnostic to identify the bottleneck and set priorities for change.
Renzo Demartini