Signature templates and sets

Placing fields on the same form four hundred times is not a good use of March. Templates fix that, and sets take it further.

Templates

A template is a document with its fields already placed and its signature type already set. Build it once, then every request from that template arrives ready to send.

Templates carry their signature type, so an 8879 template always sends as a KBA request without anyone remembering to change a dropdown. That's the single best reason to template your authorization forms — it removes a per-request decision that has a bad failure mode.

Merge variables let one template serve every client, pulling names and values in at send time.

Sets

A set groups several forms that go out together. Season paperwork is rarely one document — it's an authorization, an engagement letter, and a consent, all needing the same signers.

Each form in a set is mapped so LedgerOS knows where its fields belong. Once mapped, the whole set sends as one action, and the client gets one coherent request rather than three separate emails they'll deal with in the wrong order.

Batches

Sets can be sent to many clients at once as a batch, with progress tracked per batch.

This is where the setup pays for itself. The work is in mapping the set properly, and the work happens once.

What to template

Worth templating:

• Anything you send more than a handful of times a season
• Every e-file authorization, for the signature-type reason above
• Engagement letters, which have their own dedicated flow

Not worth templating:

• One-off documents
• Anything whose fields move between clients

Notes and limits

• Editing a template doesn't change requests already sent from it.
• A set's mapping is per form. Adding a form to a set means mapping it.
• Templates are firm-wide.
• Sets are managed under their own permission, separate from sending individual requests.