Client document chasing for Irish accountants

Explore this guide with AI

Choose your assistant to open a new chat with a prompt about this guide.

Opens the provider's site; sign-in may be needed. For a local preview, or if the AI cannot read the page, copy the full guide below and paste it into the chat.

Copy guide for another AI

Talk it through in your preferred AI chat. Copy the guide and a ready-made prompt, then paste them into a new conversation.

The prompt asks about your business, explains unfamiliar terms and helps you choose a next step. It includes the guide text and source links, so the AI does not need to open this page.

Choosing a provider shares the guide address and explanation prompt with that service. Copying or downloading stays on your device until you paste or upload the briefing. Avoid adding confidential business information, and check the advice against the sources.

Your client sends the bank statement but not the purchase invoices. If your team sends “we are still waiting for your records”, the client may reasonably think nobody checked their upload. Meanwhile, the statement can sit in the portal without an owner reviewing it.

For an Irish accountancy practice, useful document chasing means seeing what is missing, what has arrived but still needs checking, and who owns the next action. Remind the client only about the missing item. Pause the statement’s reminder, assign its review and check the latest record before a person sends anything. You can start with the tracker you already use.

See what changes when only some records arrive

Here is a fictional example to try with your team, not a client result or a tax-document checklist. A practice has asked for a bank statement and purchase invoices covering an agreed period. The client uploads the statement. The invoices are still missing.

The practice’s view should now look like this:

Requested item	Status	Owner's next action
Requested itemBank statement, agreed period	StatusReceived, awaiting review	Owner's next actionReviewer checks the period and either accepts it or requests a correction. No missing-item reminder.
Requested itemPurchase invoices, agreed period	StatusMissing	Owner's next actionOwner prepares a reminder, rechecks the latest record and approves the message before sending.

If the invoices arrive while the reminder awaits approval, withdraw the draft. If the statement covers the wrong period, ask for a correction. A client-level hold, such as a complaint or changed contact, pauses both paths.

01 Still missing

1. Prepare a reminder for this item.
2. Recheck the latest record and any client hold.
3. The owner approves the final message before sending.

02 File received

1. Pause the missing-item reminder.
2. A person checks the file against the request.
3. Accept it, or flag what needs attention.

Whole-client hold: stop every outgoing reminder until the owner resolves it.

Give the team a tracker they can act on

One label saying “client outstanding” hides the distinction in that example. Track each requested item and its period in your existing practice system or tracker. Record the client reference, records date, status, owner, last contact, next action and a link to the file in approved storage. Do not duplicate the document in the tracker.

For a first trial, give each item one of these 4 statuses:

• Missing: the requested item has not arrived. A reminder can be prepared when due.
• Received, awaiting review: an upload has arrived. Pause the missing-item reminder and assign a reviewer.
• Accepted for this request: the reviewer has confirmed that this item meets the request. Close its reminder task.
• Needs attention: the period is wrong, the file is unreadable, records disagree or the client has raised a question. Hold the routine chase for a person to decide the next action.

Accepting an item for this request does not sign off the accounts or tax return.

Give received items a visible review queue and a next check date, so a paused reminder does not hide an unopened upload.

The document-chasing test checklist has a blank tracker and 6 cases to run with fictional records. Copy the rows into your existing system.

Send the right message for the item

For the missing invoices, a person could approve this draft after checking the latest record, recipient and agreed records date:

Thanks for sending the bank statement. We are checking it. We still need the purchase invoices for [agreed period]. Please upload them through the usual practice portal by [agreed records date]. If you have already sent them, tell us where so we can check before asking again.

If the statement is for the wrong period, that calls for a different message, after the reviewer confirms what arrived:

Thanks for sending the bank statement. It covers [period received], but we need [period requested] for this request. Could you upload that statement through the usual practice portal by [agreed records date]? If it is difficult to get, please let us know.

These are drafts for a person to check, not automatic messages. Do not invent a filing deadline or consequence. If the client asks to speak to the partner, stop the routine sequence.

Keep the records date separate from Revenue’s date

For Irish practices preparing 2025 Form 11 returns this autumn, Revenue states that the Pay and File deadline is 31 October 2026. Its extension to 18 November 2026 applies when both the return and the required payments are made through ROS. Check the conditions for the client concerned in Revenue’s 2026 eBrief.

Agree an earlier practice date for receiving records, leaving time to review and correct them. Do not present that date as Revenue’s deadline.

For a first trial, choose one type of work and have its owner agree the requested items, records date and wording.

When should a document reminder stop?

A missing-item reminder should stop when the item arrives, records conflict, delivery is uncertain or the client has a contact hold. An item awaiting review stays paused, not complete.

Recheck before sending. Compare the tracker with new uploads and contact holds. If the latest status is unclear, hold the draft for the owner.

Do not retry blindly. Record what was approved and sent. If delivery is uncertain, investigate before another attempt.

Give held work an owner. A conflict between inbox and tracker, an unreadable file or a contact hold needs a visible owner, review date and backup person. The owner resolves it before the routine chase resumes.

The Astraeus accountancy workflow service keeps a person approving outgoing work. Confirm the final message and latest status together; a change requires another review. Enforce approval in the sending tool’s permissions, not only in written instructions.

Do you need AI to chase client documents?

No. Dates, statuses and duplicate checks work with ordinary rules, and an approved template may cover a straightforward reminder. Check your existing practice software before adding another subscription.

AI can help adapt wording or summarise a reply for the owner. Give it the minimum approved information, then check its draft against the record. Do not approve an invented item, deadline or consequence.

Our guide to reusable AI skills shows how to prepare a reminder draft. Connecting that example to a live tracker, enforcing approval and recording sends are separate work.

Before sending personal data to an AI provider, check what it receives, where it goes and whether it is retained or reused. The Data Protection Commission’s guidance on AI and large language models sets out the questions to consider. A paid account or human review alone does not settle them.

Use fictional records for the first test. Keep any later access to live records within the practice’s approved data arrangements.

Test the awkward cases before using client records

The document-chasing test checklist covers partial uploads, arrivals after drafting, wrong-period files, conflicting records, duplicate sends and client-level holds. It gives each case an expected outcome and space to record what happened.

Run them with the person who normally does the chasing. Ask them to show where held items appear, who owns them and how to stop all sends.

Measure the work that remains

For a defined group of requests, count staff time spent checking status, preparing and reviewing messages, and correcting errors. Count reminders sent after receipt and items waiting too long for review.

Repeat for comparable work during the trial. Record request volume and unusual cases; include review time in the total. A tool can draft quickly while creating more checking.

Use the results to extend, simplify or leave the process manual. The example above does not claim a time saving.

Questions about client document chasing

Do I need AI to chase client documents?

No. Dates, statuses and duplicate checks work with ordinary rules, and an approved template may cover a straightforward reminder. AI can help adapt wording or summarise a reply for the owner, but a person should check its draft against the record.

When should a missing-item reminder stop?

A missing-item reminder should stop when the item arrives, records conflict, delivery is uncertain or the client has a contact hold. An item that has arrived but is awaiting review stays paused, not complete.

Is the practice records date the same as the Revenue deadline?

No. Agree an earlier practice date for receiving records, leaving time to review and correct them. For 2025 Form 11 returns, Revenue states that the Pay and File deadline is 31 October 2026, extended to 18 November 2026 when both the return and the required payments are made through ROS. Check the conditions for the client concerned.

Bring the records request to a consultation

Astraeus can implement the agreed workflow around your existing tools, with your team approving outgoing messages.