LedgerOS
Open LedgerOS
Knowledge HubE-signaturesSend a document for signature
E-signatures

Send a document for signature

Place fields, add signers, choose the signing order, and pick the right identity check.

6 min readUpdated July 24, 2026Requires E-signatures

Upload a document, mark where people sign, say who signs it, send. The parts worth understanding are the signing order and which identity check to use.

Where to find it

SignaturesNew

Build the request

  1. Give it a Title — for example, Form 8879 — 2024. The title matters more than you'd think, and the next section explains why.
  2. Choose the Client.
  3. Add the Document, or pick a Template.
  4. Add your Signers, each with a Full name and email.
  5. Place the fields on the page.
  6. Set Expires.
  7. Add a Message (optional) for the signer.
  8. Send.

Placing fields

Choose a field type, then click the page to drop a field. Five types: Signature, Initials, Date, Text, and Checkbox.

Fields are assigned to a specific signer — the Place for: control decides whose field you're dropping. On a joint return this is the step to slow down on, because two signature blocks assigned to the same person means one spouse signs twice and the other never gets asked.

Using a Template means fields are already placed. You'll see Template fields are predefined — preview below rather than an editor.

Signing order

Sequential or Parallel.

Parallel sends to everyone at once. Fastest, and right for most joint returns where either spouse can go first.

Sequential sends to one signer at a time in the Order you set. Use it where somebody must see a signature before adding theirs — a preparer signing after the taxpayer, or a partner countersigning.

Sequential is slower by design. Each signer only hears about it when the person before them is done, so a slow first signer stalls everyone behind them.

Merge variables

Merge variables insert client-specific values into the document, so one template serves every client rather than one document per client.

Expiry

Set a sensible window. Too short generates "my link expired" emails during the exact week you're busiest. Too long leaves authorizations open indefinitely.

Notes and limits

  • A request belongs to one client, though it can carry several signers.
  • Signers don't need a portal account. They sign from the link.
  • A sent request can be voided but not edited. Fix a mistake by voiding and re-sending.
  • Adding a signer after sending isn't possible — that's a new request.
Was this article helpful?
Related articles