Give each recurring job an agreed required-item list and make received, missing, unusable and not-applicable status visible in one trusted place. Send approved reminders from that status, stop them when evidence arrives, and route sensitive, disputed or repeatedly missing items to a named person.
Document chasing becomes expensive when the firm has no reliable answer to a simple question: what exactly is still missing for this job to become ready? A spreadsheet may say statements are outstanding while files sit in an email thread. A client may receive a generic reminder after already sending the item. A bookkeeper may know the real status, but the manager and job record do not.
This is different from initial client onboarding. The client is already accepted. The problem repeats across BAS, month-end, annual accounts or advisory work, and the required items can vary by client, entity, service and period.
Make the checklist part of the job
Begin with one completed job and list the evidence the team actually needed. Distinguish required, conditional and not-applicable items. For each item, define what counts as received and usable. A file existing somewhere is not necessarily enough: it may be the wrong period, incomplete, unreadable or attached to the wrong client.
The list should inherit known facts from the client and job template, then allow an authorised person to adjust it. It should not make every client answer the maximum possible questionnaire. The source of truth needs to be accessible to the delivery team, not hidden in an individual's inbox or side spreadsheet.
Useful item states are plain:
- required and not requested
- requested and waiting
- received and awaiting review
- accepted as usable
- needs correction or explanation
- not applicable, with the reason
- escalated to a named person
Those states make the next action visible. They also prevent an uploaded file from silently turning a job into ready work before anyone confirms that it is the right evidence.
Send reminders from evidence, not a calendar alone
An approved reminder can be useful when it is tied to a specific missing item, job, period and due date. The message should tell the client what remains, where to provide it and who can help. It should stop when the item reaches the agreed received state.
A time-based sequence by itself is fragile. It can continue after a reply lands in another channel, treat every item as equally urgent and create unnecessary client frustration. Connect reminders to the trusted checklist, and keep a record of what was requested and when.
Use escalation rules rather than endless nudges. After an agreed number of attempts, or when the deadline or relationship needs judgement, route the job to the responsible accountant, bookkeeper or manager. They can decide whether to call, change the deadline, proceed with an explicit limitation or take another appropriate step.
Keep privacy and security in the design
Accounting documents can contain personal and financial information. The workflow should collect only what the practice needs, use approved channels, restrict access to the right roles and apply the firm's retention and security controls. The Australian Privacy Principles cover matters including collection, use, disclosure, security, access and correction of personal information. A convenient upload link does not remove those responsibilities.
Do not copy sensitive attachments through consumer tools simply because an integration exists. Map where a file is received, where the authoritative copy belongs, what metadata may be transferred and what should be deleted or retained. Record access and errors without exposing the contents in logs.
Define job-ready as a controlled state
A useful endpoint is not documents uploaded. It is job ready according to the practice's rule. That may require every mandatory item to be accepted, conditional items resolved, exceptions assigned and the due date still achievable.
The workflow can prepare that status and notify the owner. A person should retain responsibility where evidence is ambiguous, the client disputes the request, the work must proceed with limitations or professional judgement changes what is required.
Test the normal path and the awkward cases
Replay completed jobs before automating live reminders. Include a straightforward client, a file sent by email instead of the portal, the wrong period, a duplicate, a password-protected file, an item that is genuinely unavailable and a client who needs a different communication approach.
Confirm that the workflow recognises the normal case, stops safely on exceptions and records the final status in the system the team actually uses. If staff must still search an inbox to prove receipt, the handoff is not complete.
Measure less chasing and clearer readiness
Track time from first request to job-ready status, reminders per required item, items rejected after upload, jobs blocked by reason and manual touches needed to reconcile status. Review client complaints or corrections as well as speed. Fewer messages are useful only if the work becomes more reliable.
For the broader implementation pattern, see workflow automation for accounting firms in Sydney. The free Accounting Workflow Friction Check can test one document-collection workflow without booking a call. An on-site automation review is available if a completed case needs to be traced with the team.
This post has been automated so we can run lighter.