Two documents carry more legal and reputational weight in a professional services firm than almost anything else it produces: the engagement letter that defines what the firm agreed to do, and the client's approval of the finished accounts before they go anywhere near HMRC or Companies House. Both are, in most firms, still handled as an email attachment and a printed signature page, or routed through a third-party e-signature subscription bought and administered separately from the practice management system that actually holds the client relationship.
Running signing through a separate subscription creates a specific, recurring inconvenience that firms tend to underestimate until they have lived with it for a year: the signed PDF comes back to an inbox, and someone still has to remember to download it, rename it sensibly, and file it against the right client before it is genuinely part of the record. Skip that last step, which busy staff regularly do, and the firm ends up with a "signed" document that exists only as an email nobody can find eleven months later.
Accupe builds e-signing for both documents directly into the platform, from the Growth plan upward, so the signed result lands on the client record the instant it is completed rather than arriving as a PDF someone has to remember to file. This piece goes through the workflow for both document types in real detail: how a request is built, what the client experiences, what the resulting audit trail actually contains, and what a firm gains by not running this through a separate DocuSign or Adobe Sign subscription bought and administered on its own.
Why these two documents deserve more care than the rest
An engagement letter is the document a court, an insurer or an ICAEW practice assurance reviewer reads first when a dispute or a review reaches the firm. It sets the scope of what the firm promised, the fee basis, and the boundaries of professional liability. Get the scope clause wrong or leave a service undefined, and the firm may find itself performing work it never intended to include, or defending a claim over work it believed was explicitly excluded.
An accounts approval is the equivalent moment on the other end of the engagement: the client's formal acceptance of the figures the firm is about to submit on their behalf. Without it, a firm is filing a set of accounts the client has not actually agreed are correct, which is precisely the situation a regulator, an insurer, or a disgruntled client will ask about first if something later goes wrong with the figures. Both documents need to be unambiguous about who signed, when, and on what device, in a way that a scanned signature page rarely establishes with any rigour, because a photocopied signature proves almost nothing about the circumstances under which it was made.
Firms that have been through a practice assurance visit tend to describe the same experience: the reviewer does not ask to see the accounts themselves nearly as often as they ask to see the evidence that the engagement was properly scoped and that the client actually approved what was filed. Those two documents are disproportionately what a review is checking for, which is exactly why they are the two this workflow is built around rather than a general-purpose signing tool for anything the firm happens to need signed.
Building the request: two steps, not a template hunt
Sending either document starts the same way. The firm selects the client from the CRM, attaches the document itself, either a PDF or Word file or the platform's built-in engagement letter template, and enters the signer's name and email along with an optional personal note. From there, a full-screen document builder opens with a live preview of the file. The firm drags signature boxes, text input fields and date-signed fields onto the exact positions on the page where the client needs to act, so the client is never guessing where to click or scrolling past three pages of legal text hunting for a signature line.
- Client and document selected, with an optional cover message
- Signature boxes, text fields and date fields positioned on a live preview of the real document
- Signer identified by name and email, verified again at the point of signing
- Request dispatched with a branded portal notification and a direct signing link
- Automatic reminders if the client has not opened or completed it after a few days
A worked scenario: the accounts approval that closes the year
A manager finishes a set of annual accounts for a small limited company client in late October, and the partner signs off the draft the same week. The manager opens the client record, attaches the finished accounts pack, drops a signature field on the approval page and a date field beside it, and sends. The client receives a portal notification the same afternoon, opens the document on their phone during a coffee break, reads the summary page, and signs with a finger on the touchscreen. The signed PDF appears back on the client record within seconds, the Smart Board card moves from "Awaiting Approval" to "Approved, Ready to File," and the firm proceeds to submit through whichever filing software it actually uses.
No one downloaded anything, forwarded anything, or manually updated a tracker to record that the approval had come in, and if the same partner is asked in eighteen months' time whether this particular client actually approved these specific figures, the answer is a document, not a memory. Compare this to the more familiar version of the same moment: a PDF attached to an outbound email, a printed page waiting for a client visit that keeps getting postponed, and a manager who has to interrupt the client with a phone call simply to confirm the pack arrived at all, only to discover three days later that it was sitting unread.
What the audit trail contains, and how outstanding requests are managed
The part of this workflow that firms underestimate until they need it is the evidence it leaves behind. Every signed document is hashed for integrity verification, so any later tampering with the file would be detectable. The signer is verified at the point of signature, and the full event, including timestamp, IP address and verification method, is written to a tamper-evident audit log. A certificate of completion is generated and permanently linked to the signed document, giving the firm a self-contained package it can hand to a practice assurance reviewer, an insurer, or a client's solicitor without having to reconstruct anything from memory or from a scattered email chain.
Requests that are still outstanding are just as visible. A dashboard tracks Awaiting, Expiring Soon, and Signed in the last 30 days at a glance, and a single click resends the signing email to a client who has gone quiet rather than requiring a staff member to remember which of forty pending requests needs chasing this week. If a request needs to be pulled entirely, whether because the figures changed after sending or the wrong document was attached, voiding it permanently invalidates the signing link so the client can no longer access the outdated version, closing off a real risk that a stale copy of an engagement letter or an accounts pack gets signed by mistake.
A direct signing link can also be copied and shared through WhatsApp or SMS as an alternative to the email notification, which matters for the client who reliably answers a text within the hour but lets firm emails sit unread for a week. The same audit trail is captured regardless of which channel carried the link, because what the platform records is the act of signing, not the route by which the client got there, so a firm is never choosing between convenience and evidential rigour.
The legal footing under both documents
For UK firms, electronic signatures on documents like these rest on the Electronic Communications Act 2000 and the UK eIDAS regime, and the Law Commission's 2019 statement of the law confirmed that an electronic signature is capable of executing a document provided the signer intends to authenticate it and any formalities attached to that document are met. For UAE firms, the equivalent footing is Federal Decree-Law No. 46 of 2021 on Electronic Transactions and Trust Services, which gives an electronic signature the same legal weight as a handwritten one where it meets the conditions set out in the law and its executive regulations.
In practice, this means an engagement letter or an accounts approval signed through Accupe is not a lesser or provisional version of a "real" signature; it is the real signature, with a stronger evidential trail, timestamped, IP-logged and hash-verified, than most paper equivalents ever had. A signature on a printed page proves someone held a pen; it says almost nothing about when, from where, or whether the page was altered afterwards, whereas the digital record answers all three questions by default rather than requiring the firm to reconstruct them if it is ever challenged, whether by a regulator years later, by an insurer assessing a claim, or by the client themselves in a dispute over what they actually agreed to.
What it does not do
The workflow drafts, sends, tracks and evidences a signature. It does not decide what the engagement letter should say, or whether the accounts are ready to go to the client at all; those remain the partner's professional judgement, exercised before the document is ever sent. It also does not submit anything to HMRC, Companies House or the FTA. A signed accounts approval is the client's consent to file, not the filing itself, and the firm still submits through TaxCalc, Iris, Companies House WebFiling, the FTA portal or whichever tool it uses for that step. Accupe holds the signed evidence that the client agreed; the firm does the filing, exactly as it always has.
It is also worth noting what the workflow does not attempt to be a substitute for: a genuine conversation about scope before the engagement letter is drafted in the first place. A well-evidenced signature on a poorly scoped letter is still a poorly scoped letter, just one the firm can now prove the client agreed to. The quality of the underlying document remains entirely the firm's responsibility.
What changes for the firm
Firms moving engagement letters and accounts approvals onto native e-signing describe the same shift regardless of size. Turnaround from "document ready" to "signed" drops from days to hours because the client can act from a phone rather than needing to be at a desk with a printer and a scanner. The administrative cost of tracking who has and has not signed largely disappears, replaced by a dashboard that already knows. And the firm stops discovering, at the worst possible moment, usually when a regulator or an insurer asks, that a signed copy of an important document cannot actually be located.
There is also a knock-on effect on how the firm plans its own busiest weeks. A December accounts-approval push that used to depend on staff physically printing, posting or personally handing over documents can instead be dispatched from a desk in an afternoon, with the follow-up handled by reminders rather than a member of staff working through a phone list. The bottleneck moves from "can we physically get this in front of the client" to "has the client actually opened it," which is a far easier problem to monitor and solve.
Closing
An engagement letter and a set of approved accounts are two of the highest-stakes documents a firm produces, and neither should depend on a scanner working correctly or an email not getting lost. Accupe's native e-signature workflow gives both a defensible, self-evidencing path from draft to signed, without adding a separate vendor, a separate login, or a separate place the record can go missing. The two documents are different in purpose, one opens a relationship and one closes a year, but they share the same requirement: proof, not just a promise, that the client actually agreed, recorded in a form the firm can still produce with confidence years after the moment itself has been forgotten by everyone involved, whether the question comes from a reviewer, an insurer, or the client themselves.
