Drafting Query Emails About Unclear Transactions

A good query email asks one thing, gives just enough to jog a memory and offers an easy way to answer. An AI tool can tighten the wording. It shouldn't guess what the payment was.

Why you ask at all

Transactions produce records. The Internal Revenue Service says those documents hold details you need to enter in your books.¹ If a bank line has no document and no clear description, the person who paid knows best.

So you ask. The skill is in making it quick for them.

What a query holds

• The date of the payment, as it appears on the statement
• The amount, with the currency
• The payee name, as the bank shows it
• One direct question: "What was this for?"
• A simple way to answer, such as a one-line reply
• A note that a photo of a receipt or invoice would help, if there is one

Skip the accounting talk. "Can you tell me what this was for?" works better than a question about categories or coding. US plain-language guidance names clear, easy-to-understand content as the aim.²

Don't let the tool guess the answer

It's tempting to paste a bank line and ask, "What is this likely to be?" Don't.

Wikipedia's word for an invented answer is hallucination.³ A tool asked to explain an unfamiliar payee may produce a neat, wrong story about it. The Australian privacy regulator also describes these tools as known to give inaccurate or false results.⁴

A made-up explanation can slip into a draft as a hint, such as "this looks like a personal expense". That plants an idea in the client's head and may be wrong. Tell the tool what to do and what not to do.

Write a short, polite email from a bookkeeper to a client asking what one payment was for. Details: date [date], amount [amount], payee [payee]. Ask one question only. Don't suggest what it might be. Don't mention tax. Offer a one-line reply or a photo of the receipt. Under seventy words.

Keep real details to a minimum

Bank lines can carry names, partial account numbers and references. Australia's privacy regulator says its obligations cover personal details typed into an AI product.⁴

You don't need those details to get good wording. Put "[payee]" and "[amount]" in the prompt and type the real values into your email afterwards. If you can write the question without the tool seeing the real line, do. The client data page goes into more detail.

Several queries at once

If you have a handful of unclear lines, one email with a numbered list beats five separate emails. Ask the tool to format a table or list from placeholders, then fill the real rows in yourself.

Write a short email asking a client to reply beside each item below. Use the layout: date, amount, payee, then a blank for their answer. Use [date], [amount] and [payee] as placeholders for each row. Keep the tone friendly.

Keep batches small. A long list tends to get a half answer.

What to do with the reply

Record the answer in your system the way you normally would. If the answer raises a question about tax treatment, don't have a chatbot decide it. That's a matter for the tax authority's published guidance or a registered adviser.

Read it as the client would

Before sending, check:

• Could someone with no accounting knowledge answer it?
• Is it free of jargon and shorthand?
• Does it avoid blame?
• Is it a single question, or a list clearly laid out?

The words "just checking" and "I was wondering" soften a message but also make it longer. Cut them if the email is already friendly.