When to Stop Using Email for Client Approvals

You sent the VAT return for review on Monday. It is now Thursday, and you have no way to know whether the client approved it and forgot to reply, has a question and is composing a response, has not opened the email, or opened it and moved on without acting. What you do know is that the SARS submission deadline is tomorrow and you are going to call them — because that is what you always end up doing. Email was never built to be an approval system, and the fact that it has been used as one for twenty years does not mean it should be.

The Real Cost of the Current Approach

Email approval chains create three distinct problems for accounting firms, each more serious than it appears.

Timeline uncertainty. When an approval request goes into an email inbox, you lose control of the timeline. You have no visibility into whether the email has been read or reviewed. The only feedback mechanism is the absence of a response — which is meaningless because you cannot distinguish between "not yet read," "under consideration," and "approved but not replied to." The result is that approval timelines are always longer than necessary, and compression happens at the deadline.

For VAT submissions, provisional tax filings, and management account sign-offs — all of which have hard deadlines — this timeline uncertainty creates direct regulatory risk. The article on SARS provisional tax deadlines 2026 outlines the specific penalty exposure that comes from missed deadlines.

The audit trail. An email chain is a fragile, unstructured record. It can be deleted. It can exist in a personal inbox that is inaccessible if a staff member leaves the firm. The chain of "I sent it, they replied, they approved" is not a robust audit record — it is a sequence of messages that must be reconstructed manually if ever needed.

The revision trap. Email approvals invite revision by design. An open-ended approval request — "Please review the attached and let me know if you are happy to proceed" — invites a client to raise questions, loop in a third party, or request changes. The resulting thread can run for days. Structured approval systems that present specific items for sign-off produce faster, more decisive responses.

What a Better Operating Model Looks Like

A structured approval process presents the client with a specific, bounded decision: here is the item for approval, here is the context, here is what you are confirming, and here is the deadline. The response is a defined action — approve or decline with a comment — not an open-ended reply.

This produces several immediate improvements. The approval request requires an active action rather than a reply, making it harder to ignore passively. The timeline is visible to both the firm and the client. The outcome is clear at a glance. And the record of what was approved, by whom, and when is captured automatically.

Before committing to any new system, the VAT approval workflows article provides a useful structure for how sign-off should be managed for VAT specifically. The same principles apply across all approval types.

A Framework for Getting This Right

Define what requires formal approval. Not every client communication requires sign-off. The items that do are those carrying a regulatory submission, financial commitment, or professional liability: VAT returns, income tax returns, provisional tax calculations, management accounts issued to third parties, and payroll submissions.

Define who is authorised to approve. For corporate clients, this is often a specific director or financial manager. Knowing this in advance eliminates the pattern where an approval email is sent to a general address and sits unread because no one feels ownership.

Set deadline dates at the point of issuance. Every approval request should include the date by which approval is needed and a brief note on the consequences of not approving by that date. This is not pressure — it is professional clarity.

Automate reminders against the deadline. A reminder that fires one day before the approval deadline, without requiring a staff member to send it, is more consistent than a personal follow-up call. The call should be the exception.

Capture the approval in a system, not an inbox. The record of what was approved, by whom, and when must be stored in a system accessible to the firm — not in a personal email account.

What This Looks Like Inside a Purpose-Built Platform

The email-protocol approach requires no new technology but fails at the record-keeping level. Email remains an inbox, not an audit trail, and you still cannot see whether a client has read an approval request without calling them.

Evoke LedgerBridge treats approvals as a first-class workflow. Approval requests are issued as specific items within the platform, linked to the document or calculation they relate to. Clients see the approval request in their portal with the context they need and a clear deadline. When the client approves or declines, the action is timestamped and stored permanently as part of the engagement record.

This is where the audit-ready client communication logs requirement becomes concrete. An approval captured in a purpose-built system is an audit-ready record. An approval captured in an email thread is a reconstruction exercise.

Common Mistakes Firms Make When Addressing This

The first mistake is accepting email approvals for clients who "prefer it." Consistency is the only standard that produces a reliable audit trail. If some clients approve via portal and others via email, your records are split and neither is complete.

The second mistake is making the approval process more complicated than the thing being approved. Clients do not need a ten-field form to approve a VAT return. They need to see the relevant figure, understand what they are approving, and take one action.

The third mistake is not linking the approval to the specific document version. "Client approved the VAT return" is not useful if three versions were in circulation. The approval record must reference the exact document approved.

The risk of staying with email approvals is accumulative. Every month that approval chains run through email is a month of audit trail that does not meet the standard you would want if a client ever disputed a submission or if SARS ever queried the basis of an approval.

If your firm is ready to move past email approval chains, Evoke LedgerBridge was built for exactly this.

Book a demo or chat on WhatsApp to see how it fits your delivery model.