Skip to content
  • There are no suggestions because the search field is empty.

Setting up POA and AKA signers

When one person has to sign under more than one name in the same signing, an attorney-in-fact under a power of attorney or an AKA name variation, you create a separate signer record for each required signature and then group those records together. This article covers the Snapdocs RON setup.

The signer name in Snapdocs RON must be the name the signature block requires. Not the person's legal name, not the name on their ID. Whatever the document expects them to sign as. Every step below follows from that rule.

1. Name the signer with the string the document uses

When a document requires an AKA vesting, type the full string into the signer's Name field. For example:

Jonathan A. Smith AKA John Smith

Do the same for a POA capacity: enter the name exactly as the signature block reads. There is no Snapdocs RON-side format rule for this. The signature field dictates the exact string, so match whatever the document uses.

2. Create one signer record per required signature

If one person is signing on behalf of several people, or under several vestings, in the same signing, create them as separate signers. One signer record per name that has to be signed.

Do not try to make a single signer record cover multiple names.

3. Group the records with Manage Joint Signers

Once the separate signer records exist, use Manage Joint Signers to put them in a group. Grouping is what lets the same person move through the ceremony once, in a single session, instead of receiving and running a separate signing for each name.

Email addresses do not matter here. The grouped records can share one email address or use different ones. Either works. The grouping ties the records together, not the email.

4. Turn identity verification on for one record only

If identity verification is required for the POA or AKA signer:

  1. Toggle KBA and IDV on for one of the records in the group.
  2. Skip KBA and IDV on every other record in that group.

Note: It is the same person behind every record in the group, so the verification performed on the one record applies across the whole group. Turning it on for each record forces that person through KBA and IDV twice for no additional assurance, and a second KBA attempt is a real failure risk, not just friction.

Quick checklist
  1. Read the signature blocks and list every name that must be signed.
  2. Add one signer per name, naming each with the exact required string (X AKA Y where that applies).
  3. Open Manage Joint Signers and group all records that belong to the same person.
  4. Set KBA and IDV to on for one record in the group, and skipped on the rest.