Nick Hallam
10 August 2026
An electronic signature is valid in Australia when the method identifies the signer, indicates their intention, and is as reliable as the transaction warrants. What decides a dispute is the trail behind it. MatterFirst, a legal practice management platform for Australian law firms, sends any matter PDF for signature and returns one file: signatures stamped into the pages, certificate appended.
That last part is the whole point. A signature is easy. Proving who made it, when, and that they meant to, is the part that has to survive being questioned two years later.
What the law actually asks of an electronic signature
The Electronic Transactions Act 1999 (Cth) sets the test at section 10, and each state and territory has an equivalent, such as the Electronic Transactions (Victoria) Act 2000. Where a law requires a signature, an electronic method satisfies it when three things hold:
- Identification and intention. The method identifies the person and indicates their intention in respect of the information communicated.
- Reliability. The method is as reliable as appropriate for the purpose, given the circumstances, or is proven in fact to have identified the person and indicated their intention.
- Consent. The person receiving the signature consents to it being given that way.
Notice what is absent. There is no prescribed technology, no mandated certificate authority, no minimum key length. The test is functional, which is why a typed name can satisfy it in one context and be plainly inadequate in another. Reliability is judged against the transaction, so the standard for a costs agreement is not the standard for a guarantee over a family home.
For companies, the position was settled by the Corporations Amendment (Meetings and Documents) Act 2022, Act No. 9 of 2022, which received assent on 22 February 2022. Its Schedule 1, headed "Signing and executing documents", made electronic execution under sections 126 and 127 of the Corporations Act 2001 permanent rather than a pandemic measure, and put beyond doubt that a document signed under those sections, including a deed, need not be on paper.
What still needs its own process
Electronic signing is the default for ordinary commercial and client documents. It is not universal, and a firm that treats it as universal will eventually execute something badly.
| Document | Usual position | What to check |
|---|---|---|
| Costs agreements, engagement letters, authorities | Electronic signing is ordinary practice | Client consent to electronic communication, and that the signer is the client |
| Commercial contracts and deeds signed by a company | Electronic execution available under Corporations Act ss 126 and 127 | Who is signing, and whether the section 127 assumption is being relied on |
| Deeds signed by individuals | Depends on the jurisdiction and the instrument | The state statute, and whether witnessing is required |
| Wills, affidavits, statutory declarations | Carry their own execution and witnessing requirements | The specific rule for the instrument, not the general electronic transactions Act |
| Land title dealings | Lodged electronically through a network operator, under the Electronic Conveyancing National Law framework | The participation rules and verification of identity requirements for the jurisdiction |
The pattern worth carrying: the Electronic Transactions Acts are a general permission that specific statutes can displace. When the instrument has its own execution rule, that rule wins. Anything requiring a witness needs the witnessing rule checked separately, because permission to sign electronically is not permission to witness remotely.
The evidence a dispute asks for
If a signature is challenged, the questions are predictable. A signing system is worth having in proportion to how many of them it answers without a person reconstructing anything.
| Question | What answers it | Why it matters |
|---|---|---|
| Who was asked to sign? | The request record: name and email address the link was sent to | Establishes the chain from your file to the person |
| Did they see it? | Timestamp when the document was opened | Distinguishes ignored from unseen |
| When did they sign? | Timestamp on each individual mark, not just on the finished document | Multi-party documents are signed at different times |
| From where? | IP address and device recorded per signature | Corroborates identity, or contradicts it |
| Did they consent? | A recorded consent to sign electronically | Goes directly to the third limb of section 10 |
| Was it drawn or typed? | Recorded per signature | Both are valid, and the difference is a fact about the document |
| Could someone else have signed it? | Server side enforcement that each signer completes only their own fields | A control on the page is not a control |
| Can the proof be separated from the document? | A certificate appended to the executed file rather than emailed alongside it | Separate files go missing; attached ones travel |
That last row is the one most often overlooked at purchase and most often regretted later. A signing certificate that arrives as a second attachment is proof only while somebody keeps filing it correctly.
Signing from the matter, or signing from another tool
Most firms already sign electronically. The question is where the signing sits.
A standalone signing tool works, and it costs you three things. First, a re-upload: the document leaves your system and the executed copy has to come back, usually by email, usually filed by hand. Second, a second address book, since signers are contacts in the practice management system and recipients in the signing tool, and the two drift. Third, a broken audit line, because the matter shows a document and the signing tool shows the evidence, and joining them is manual.
Signing inside the matter removes all three, and adds one risk worth naming: you are now depending on one vendor for both the document and its proof. The mitigation is export. If the executed copy is a standard PDF with the certificate inside it, the evidence survives leaving the platform, which is the test to apply.
How MatterFirst handles this
MatterFirst is a legal practice management platform for Australian law firms, built by North Cape Technology in Melbourne. E-signing is built into the matter rather than provided by a third party signing account.
Open any PDF on the matter, choose Send for signature, add the signers and drag boxes onto the page. There are five field types: signature and initials are drawn, while full name, date and text are typed. Every box belongs to a specific signer and is colour coded, so a two party contract stays legible, and the layout locks the moment the request goes out. Signing order is optional: everyone at once, or gated so the next signer is only emailed when the person before them finishes.
Signers do not need an account. A signer can be a portal client, a contact on the matter, or anyone named by email, and the emailed link is the credential. Portal clients can also sign from their documents list. Signatures can be drawn on a phone, tablet or trackpad, or typed, and a typed name is rendered and stamped through the identical path, which is also what makes signing workable with a keyboard or a screen reader.
The control sits on the server rather than the page: each signer can only complete their own fields, consent, timestamp, IP address and device are recorded on every signature, signing burns the emailed link so it cannot be reused, and a signer can decline with the reason recorded. Each signature is saved the moment it is given, so nothing already signed is lost to a dropped connection.
When the last signer finishes, every mark is burned into the page it was placed on and a signing certificate is appended: who was asked, when they opened it, when they signed, from what IP, and whether each mark was drawn or typed. One file, filed to the matter, with the source document marked signed. Documents are held in the AWS region the firm chooses, Sydney by default. Plan inclusions are on the pricing page, which starts at $199 per month per workspace with users included.
How the platforms compare on e-signing
Verified on 10 August 2026 from each vendor's own public pages and support material. "Not published" means the page checked does not state it.
| MatterFirst | LEAP | Clio | Smokeball | Actionstep | |
|---|---|---|---|---|---|
| How signing is provided | Built in | Via LawConnect, returning a DocuSign certificate | Via the Dropbox Sign integration, built into Clio Manage | Via InfoTrack: InfoSign or DocuSign | Via the DocuSign integration |
| Third party account required | No | Not published | No separate Dropbox Sign subscription needed | InfoTrack integration must be enabled | Yes, "Free + DocuSign Subscription" |
| Stated cost | Included | A cost recovery is saved to the matter and can be invoiced to the client | Included in the subscription, with monthly per-plan e-signature counts that do not roll over | InfoSign free and unlimited on Grow and Prosper+; DocuSign $5 per signature | Integration free, DocuSign subscription separate |
| Executed copy returned | Stamped PDF with certificate appended, filed to the matter | Signed document and DocuSign certificate saved back to the matter as a PDF | With DocuSign, the signed file arrives by email and replaces the version in Clio Manage | Signed copy sent to all parties on completion | Not published |
| Signing order control | Optional, all at once or gated | Not published | Not published | Not published | Not published |
| Where the firm's data sits | Chosen AWS region, Sydney by default | Not published | Not published | Not published | One of four AWS regions, including Australia |
Sources: MatterFirst e-signatures; LEAP's own eSignatures description and secure document sharing pages; Clio's help centre on e-signatures and DocuSign; Smokeball's support hub on InfoSign; Actionstep's DocuSign integration and security pages. Clio's plan names and e-signature counts are published for its United States and Canadian plans. LEAP's eSignature wording was read on a LEAP regional site rather than an Australian page, so confirm the Australian cost recovery treatment with LEAP directly.
Who this suits, and who it does not
Built in signing pays for itself in firms that send documents out weekly: costs agreements, authorities to act, deeds of release, settlement authorities and client instructions. If your firm is paying a separate signing subscription mainly to send engagement letters, that is the clearest case for consolidating.
It is worth less to a firm that rarely needs documents executed, and less again to one whose signing is dominated by instruments with their own rules, where the constraint is the witnessing requirement rather than the software. It does not change what must still be signed on paper or witnessed in person.
MatterFirst suits Australian firms of roughly two to twenty fee earners that want onshore hosting, state based trust accounting and document workflows in one system. Firms that depend on a connector outside Xero, Stripe, Microsoft 365 and Google Workspace should check first, because those four are the connectors available today and the rest of the catalogue, including DocuSign, PEXA and InfoTrack, is listed as coming soon. The evaluation checklist collects the questions worth putting to every vendor on your shortlist, including MatterFirst.
FAQ
Are electronic signatures legally valid in Australia? Yes, for most documents. The Electronic Transactions Act 1999 (Cth) and its state and territory equivalents ask that the method identify the signer, indicate their intention, and be as reliable as appropriate in the circumstances, with the recipient's consent. Some instruments carry their own execution or witnessing rules, so check the rule for the document in front of you rather than relying on the general position.
Do my clients need an account to sign? Not in MatterFirst. A signer can be a portal client, a contact on the matter, or anyone you name and give an email address to, and the emailed secure link is the credential. Links last fourteen days, and resending issues a fresh one while the superseded link keeps working briefly so a resend never kills a signature already in progress.
What if a signer cannot draw a signature? They type their name instead. The typed name is rendered into a signature image and follows the identical path: same validation, same stamp, same position on the page. The certificate records that the mark was typed rather than drawn, because that is a fact about how it was made. This is also what makes signing workable with a keyboard or a screen reader.
Can I control the order people sign in? Yes. Leave it open and everyone is emailed at once and can sign in any order, or switch on Sign in order, in which case the next signer is only emailed when the person before them finishes. Either way each signer can only complete their own fields, and that is enforced on the server.
What proof comes back with the signed document? A signing certificate appended to the executed PDF: who was asked, when they opened it, when they signed, from what IP address, and whether each mark was drawn or typed. It is part of the same file rather than a separate attachment, so the proof travels with the document.
Can I still use DocuSign with MatterFirst? MatterFirst's signing is built in, so a DocuSign subscription is not needed to send documents for signature. DocuSign appears in the MatterFirst integration catalogue as coming soon rather than as a connector available today, so a firm with an existing DocuSign workflow it must keep should raise that before switching.
Where is signing data stored? In the AWS region your firm chooses, with Sydney the default for Australian firms. The security page sets out which processing runs where.
The short version
The statute is functional, not technical: identify the signer, show their intention, be as reliable as the transaction warrants, get consent. Every serious signing product clears that bar. They separate on evidence and on filing.
So when you compare them, ask four questions. Does the proof attach to the document or arrive as a second file. Is the rule about who may sign which field enforced on the server or in the browser. Does the executed copy land on the matter without a person moving it. And can you take all of it with you if you leave. The signing is the easy half.