Chasing Missing Receipts and Documents with AI-Drafted Messages

A message that chases a client works when it's specific, short and easy to act on. The tool can help with the tone. It can't help with the list, because it doesn't know what's missing.

Why the missing item matters to the client

Clients often hear a chase as nagging. A reason makes it sound less like that.

The Internal Revenue Service says records help support items reported on a tax return.¹ It also notes that purchases, sales, payroll and other transactions generate supporting documents.¹ The Australian Taxation Office says accurate and complete records help a business meet its tax, superannuation and employer obligations.²

Those are US and Australian sources. Rules differ elsewhere, so check your own tax authority's wording before you describe what a record is for. Keep the reason in the message to one plain sentence.

What a good chase message holds

• What's missing, named exactly: "the February statement for the business savings account", not "some paperwork"
• The date you need it by, in full
• Why you need it, in a single sentence
• The easiest way to send it, such as a photo of a receipt by reply
• What to do if they can't find it, such as asking the bank for a copy

Plain-language guidance from the US government says the first rule is to write for your audience.³ It also recommends active voice and lists.³ A shop owner reading on a phone between customers is your audience. Give them a short list and a clear ask.

How to ask the tool

A prompt is just the written instructions you give the tool. Wikipedia's page on prompt engineering frames it as arranging everyday-language inputs so a model gives the output you want.⁴ You don't need a technical method. You need to say who it's for, what's missing, and how it should sound.

Write a short, friendly email from a bookkeeper to a small business owner. The owner hasn't sent the following yet: [list items]. I need them by [date]. Say why in one sentence. Offer to take a phone photo by reply. Keep it under one hundred and twenty words. Don't sound cross. Don't add any facts I haven't given you.

The last sentence matters. Left alone, a tool may add a deadline, a fee or a legal warning of its own.

Keeping the tone kind

If the first draft sounds sharp, ask for changes in plain terms: "warmer", "shorter", "less formal". Then read the result against how you'd say it on the phone.

Words to watch for in a draft:

• "As previously requested" and "failure to provide", which read as blame.
• "Urgent" used when nothing is urgent.
• Threats about fees or deadlines you didn't write in.
• Hints about the client's tax position. That's a question for the tax authority or a registered adviser, so leave it out.

A gentle sequence

Plan the follow-ups before the first message goes out. A rough pattern:

• First message: the list, the date, how to send
• Second message, a few days later: the same list with whatever's still missing, nothing new
• Third message: offer a short call to go through it together

Ask the tool to draft all three at once, each shorter than the last. Then edit. Keep the dates in your own calendar. The reminder messages page covers using fixed dates.

Leave real details out of the chat

You rarely need a client's real name, account number or figures to get good wording. Write "[Client]" and "[Account]" in the prompt and fill the gaps in your email programme afterwards. The reasoning is on the data-care page.

Check before you send

• Does the list match your records?
• Is the date right, and does it include the year?
• Is anything promised that you can't deliver?
• Would you be happy to receive it?

If the answer to any is no, fix it before sending. Then save the version that worked, as a template with blanks, so next month's chase takes a minute.