Built from inside practice. Built by Mr H Hammad FCCA, ACA, ICAEW Chartered Accountant with over 20 years in practice.
ProductFor ClientsClient PortalResourcesWhy BalansixPricingAcademySupportFree practice guideBook a demoLogin
BalansixAcademy

Write client requests that get a usable answer

Practise clear requests, partial-response handling and thoughtful completion in Balansix Client Communications.

Foundation16 minute lessonClient Communications

What you will learn

A useful request tells the client exactly what is missing, why you need it and what a complete response looks like. Learn to keep the conversation focused, recognise partial answers and close it only when the information is usable.

By the end, you can

  • Choose a request type and write an actionable subject.
  • Respond to incomplete evidence without restarting the whole conversation.
  • Distinguish a client message from an internal task handover and a service-specific approval.

Before you begin

  • Know the selected client and the piece of work the request supports.
  • Use the fictional wording as a pattern, with real references checked before sending.
Use the example, then apply the method. The people, businesses and figures in this lesson are fictional. Work through the activity on paper before applying the method to authorised client work.

Choose the purpose before the wording

Client Communications offers Message, Missing information, Document request, Question and Approval. Choose the type that describes the response you need. A document request asks for a record; a question asks for an explanation. Combining unrelated requests can make it harder for the client to know when they have finished.

The “Send to client” action sends the conversation to the client portal. Draft it for the client to read. Keep internal preparation and reviewer instructions in the appropriate task context rather than adding them to a client-facing request.

For a service-specific approval, use its controlled workflow. For example, VAT approval belongs to the exact Full VAT Report in the portal, not simply to an informal “looks fine” message.

Worked example: replace a vague chase

Pine Workshop has supplied a supplier statement. It lists invoice PW-114 dated 6 March for £240 and PW-119 dated 19 March for £360. The underlying invoices are missing from the evidence you have reviewed.

A message saying “Please send your missing paperwork urgently” makes the client find the problem again. Use a document request with a specific subject and due date agreed for the work.

Subject: March purchase invoices PW-114 and PW-119

Please upload the invoices dated 6 March for £240 and 19 March for £360, references PW-114 and PW-119. We have the supplier statement, but need the individual invoices to review the purchases. Please include every page. If either invoice is unavailable, reply here and tell us which one so we can agree the next step.

The message identifies two records, explains why the statement did not finish the request and gives the client a useful response if they cannot supply everything.

Handle a partial response precisely

The client uploads PW-114 and says “done”. Check its reference, date, amount and pages. If it is usable, acknowledge that item and ask only for PW-119 in the existing thread.

Thank you, PW-114 is complete. We still need PW-119 dated 19 March for £360. Please upload that invoice, or reply here if you need help obtaining it.

This keeps the unresolved work visible without asking for the first invoice again. The thread history and attachments give another colleague the context if they take over.

When a reply raises a separate issue, decide whether it needs a new conversation with its own subject. Keep one thread focused enough that the completion decision is clear.

Make completion mean something

“Mark complete” closes the staff conversation’s reply area. Use it when the request has a usable outcome and the next workflow can proceed. A reply arriving is a reason to review the evidence, not an automatic reason to close.

For Pine, completion is appropriate once both invoices have been checked, or an authorised colleague has agreed and recorded a different resolution. Reflect any remaining accounting review in the task stage. Finishing the document request does not mean the accounts or VAT return are finished.

A final reply can confirm the outcome in plain words: “Both invoices have been received. We will now complete the purchase review.” The message tells the client what happens next without promising a result that still requires review.

Exercise: turn a reply into the next action

Your case. You requested a complete contract and its fee schedule. The client uploads the contract, but its last page says “Fees: see schedule A”; schedule A is absent. Write a reply and decide whether to complete the request.

Model answer. “Thank you for the contract. Its final page refers to schedule A for the fees, so please also upload that schedule, including all pages. Once it is available we can finish reviewing the agreement.” Leave the request open while the missing schedule remains unresolved.

The answer succeeds because it tells the client exactly which item remains and avoids suggesting that the first upload was wasted. It also gives a colleague a clear test for completion.

Check your understanding

A requested contract arrives without the fee schedule it refers to. When should you mark the document request complete?

Read the answer and explanation

After the missing schedule is usable or an authorised alternative resolution is recorded.

Completion follows a usable outcome. A precise follow-up identifies the missing schedule without duplicating the whole request.

Continue learning