Signing documents electronically

Some documents need a signature before they count, such as a loan agreement. When a document type needs signing, Save and send sends it for signature instead of as a plain letter. Each signer gets a link from your bank, signs on their phone or computer, and the signed copy comes back to the Documents tab.

What the Documents tab shows

The Signature column says where each document’s signing stands.

Shown What it means
Awaiting signature · N days left The signers have their links. N is the days before the request expires.
Signed Every signer has signed. The signed copy and its certificate are stored.
Signature declined Too few signers remain to complete it.
Signature expired The expiry date passed with signatures still missing.
Signing cancelled A clerk cancelled the request.

Once a document is signed, the File column shows the Signed PDF first. The unsigned Original and the signing Certificate sit beside it. The certificate is the signing provider’s record of who signed, when, and how they proved who they were.

stateDiagram-v2
    [*] --> Awaiting: Sent for signature
    Awaiting --> Signed: Every signer signs
    Awaiting --> Declined: Too few signers remain
    Awaiting --> Expired: Expiry date passes
    Awaiting --> Cancelled: A clerk cancels
    Expired --> Signed: A signature made in time is reported late

Reminding a signer

The signers are reminded on a schedule your organisation sets. To remind them now:

  1. Find the document on the client’s or account’s Documents tab.
  2. Select Send reminder.

The reminder goes to every signer who has not yet signed. It carries the same link as the first invitation.

Cancelling a request

Cancel a request when the document is wrong, or the client asks you to stop.

  1. Select Cancel signing on the document’s row.
  2. Enter the reason. It is kept on the request’s record.
  3. Select Cancel signing again to confirm.

The signers’ links stop working at once. Cancelling needs no second approval, because it stops a signature rather than creating one.

To send the same document again after it was cancelled, declined or expired, select Send for signature on its row.

Chasing unsigned documents

The Awaiting signature page lists every document still waiting for a signature, across the bank, oldest first. Find it under Back office. Each row shows the client, the document, when it was sent, the days left before it expires, and who has still to sign.

For example, read on 6 October 2026, an agreement sent on 1 October shows 9 days left. One sent on 5 October shows 13 days left, and is listed second.

Setting up signing

An administrator sets up signing on the Signing settings page, under Correspondence.

  1. Store the provider’s password on the Secrets page.
  2. On the Signing page, select Add gateway.
  3. Enter a name, choose the provider, and enter the provider’s address and the password’s secret name.
  4. For SigniFlow, enter the SigniFlow user the platform signs in as in Signs in as.
  5. Select Add.
  6. Give the provider the Webhook address the page shows, so it can report each signature.
  7. For SigniFlow, also enter the Event handler secret in SigniFlow’s event handler settings. SigniFlow sends it with every report, and the platform ignores a report without it.

Only one gateway is active. Adding a gateway retires the one before it, and adding the same name again issues a new webhook address. Documents cannot be sent for signature while no gateway is active.

The Test provider signs nothing. It exists for trying the flow out, and production refuses it.

Signing through SigniFlow

SigniFlow sends no emails of its own. Your bank sends every invitation and reminder, and SigniFlow only hosts the signing page. Each signer signs with a digital signature.

For now, SigniFlow signing has limits. If a document type breaks one, sending it is refused before anything reaches SigniFlow, and the message names the problem.

Not yet supported What to do instead
A one-time code to the signer’s mobile Use email link as the proof of identity.
“Any N” of a group of signers Name every signer.
Two signers with the same signing order Give each signer an order of their own.
Two signers with the same email address Give each signer their own email address.

Adding the same gateway name again issues a new webhook address and a new event handler secret. Enter both in SigniFlow again.

The page also lists each signed document type: who signs it, how they prove who they are, when the request expires and how often signers are reminded.

The platform records evidence of each signature: who signed, when, and how they proved who they were, with the provider’s certificate. It does not decide whether that signature satisfies a law. South African law accepts an electronic signature for most documents, but some may need an advanced electronic signature, and sales of land cannot be signed electronically. Your organisation’s legal team decides which documents need which kind. See the standards register rows for the Electronic Communications and Transactions Act and for PAdES; neither is claimed yet.

A worked example

Alex’s loan agreement needs Alex’s signature, by email link plus a one-time code to their mobile. Requests expire after 14 days.

When What happens
1 October 2026 The agreement is sent for signature. The tab shows Awaiting signature · 14 days left.
1 October 2026, 10:14 Alex signs with the code. The tab shows Signed, with the signed PDF first.
No signature by 15 October 2026 The request expires. The tab shows Signature expired.

Expiry counts calendar days from the trading date the document was sent.

What your organisation configures

From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.