Home / Guides / E-signing for accounting firms

E-signing for accounting firms: the workflow that files itself

Elio · practising accountant, MC&S · 6 min read · July 2026

Every e-signing tool can collect a signature. The question that actually matters for an accounting firm is: what happens in the thirty minutes after the client signs? In most practices the answer is a staff member downloading PDFs, renaming them, filing them into SharePoint, updating the job in practice management and emailing the lodgment person. That's the part worth automating.

Where generic e-signing tools leave accounting firms

Generic e-signature platforms were built for one-off contracts, not for a tax practice sending a family group's entire year-end pack. Used off the shelf, they leave four gaps:

• One document, one envelope, one link. A family group with a trust return, two individual returns and financial statements becomes four separate signing requests — and four separate things for the client to lose in their inbox.
• The signed copy just sits there. Someone still downloads it, renames it to your convention, and files it to the right client-and-year folder.
• Practice management never hears about it. The job status doesn't change; the person who lodges doesn't find out until someone tells them.
• Per-envelope or per-user pricing that scales with exactly the thing you want to do more of.

What a good workflow looks like

This is the workflow that runs at MC&S today, built by us, inside our own practice:

1. Bundle everything into one link. All documents for a client — even across multiple jobs and entities — go out as a single bundle with a single signing link. The client gets one email, one guided walk-through, one "sign all" button, and can reopen the same link later. They can also decline with a note, which is feedback you want early, not after three follow-up calls.
2. The last signature triggers everything. The sealed documents file themselves to the correct client folder in SharePoint, into the right financial year and document-type subfolder, named to the firm's convention. Nobody downloads anything.
3. Job statuses move on their own. Every job in the bundle flips to Ready to Lodge the moment signing completes. The person who lodges gets notified; the accountant who sent it sees it in their feed.
4. The payment gate can hold it. If the job is flagged as payable and the invoice hasn't cleared, it waits — signed, filed, and parked — until payment lands. (Full detail in the payment-gated lodgment guide.)

What this saves in practice

For a firm sending a few hundred signing packs a year, the arithmetic is straightforward: if each signed pack takes 15–20 minutes of download-rename-file-update admin, that's multiple weeks of staff time annually spent on work a computer does perfectly and a human does resentfully. The subtler win is error rate — misfiled documents and jobs stuck in the wrong status simply stop happening, because the filing and the status change are the same event as the signature.

Buy, or build?

If a subscription tool covers your workflow, use it — genuinely. The case for a custom build is when your workflow doesn't fit the template: multi-entity family groups, your own filing conventions, integration with your practice management statuses, payment gating, or simply not wanting a per-envelope fee on every signature forever. We wrote up the general trade-off in custom vs off-the-shelf practice software; the short version is that you own a custom build outright, and it's shaped around your firm rather than the other way round.