Roles and Role Prefixes

What it is

A role prefix is the part of a Quik! field name that identifies the person (or entity) the field belongs to. In 1own.FName, the 1own is the role prefix. It tells Quik! that "FName" is the first name of the first owner on the form.

Quik! uses around 90 different role prefixes to cover every party that might appear on a financial form: owners, beneficiaries, trustees, advisors, witnesses, notaries, and more. The complete list is at the bottom of this page.

Why it matters

A form might ask for the first name of an owner, a beneficiary, a trustee, and a spouse. Without a way to tell them apart, "first name" would be ambiguous. Role prefixes make every field on every Quik! form unambiguous about who the data belongs to.

Three things depend on getting the role prefix right:

Prefilling the form correctly. Sending owner data to a beneficiary field is a common mistake. The prefix is how you make sure data lands in the right place.
The e-signature signing order. When a form goes out for e-signature, the order people sign in is based on the role prefixes of the signature fields.
Multi-party scenarios. When the same form needs to be filled out for more than one person or group (households, multiple beneficiaries), the role prefix is what keeps each person's data separate.

How it works

Reading a role prefix

A role prefix has two pieces: a number, and a short role name.

Field name	Means
`1own.FName`	Owner 1, first name
`2own.FName`	Owner 2, first name
`1ben.FullName`	Beneficiary 1, full name
`1rep.Email`	Representative (advisor) 1, email
`1spou.FName`	Spouse 1, first name

The number is the instance (first owner, second owner, third beneficiary, and so on). Numbers always start at 1. The short role name comes from Quik!'s standard list. After a dot comes the attribute being asked for (FName, Email, FullName).

Quik! tells you which roles a form needs

You don't decide which roles are on a form. Quik! reads the form when you ask for it and returns the list of roles present. If a form only has Owner 1 and Owner 2, those are the only two roles you can send data for. There is no third owner to prefill, and there is no beneficiary if the form does not include one.

Default signing order

When a form is sent for e-signature, the people who need to sign appear in a fixed order. Owners sign first. Trustees, insureds, annuitants, and other parties follow. Advisors and representatives sign last.

The default order is the same regardless of whether you use DocuSign, SIGNiX, or Native E-Sign. With DocuSign you can override the default if you need a custom order.

Complete role prefix reference

Roles are listed in default signing order. Owners sign first (signing order 1), reps and advisors sign last (signing orders 100 and above). Some signing orders are shared by multiple prefixes, which means those roles are treated as equivalent for ordering purposes.

Prefix	Role	Description	Signing order
`own`	Owner	Owner of account, contract, or policy (not the insured). Also: client, account owner, primary owner, account holder, owner, customer, individual, contract owner, shareholder, policy owner, applicant.	1
`ent`	Entity	Entity as the owner of an account, only when explicitly defined separately from Owner. Check the Owner definition first.	2
`trust`	Trust	Trust as an entity. The person name represents the trust executor or owner.	3
`ccown`	Credit Card Owner	Credit Card Owner or Signer.	4
`poa`	Power of Attorney	Power of Attorney.	5
`pown`	Prior Owner	Prior Owner.	6
`bown`	Beneficial Owner	Beneficial owner of account, contract, or policy.	7
`bown1`	Individual Beneficial Owner 1	Individual beneficial owner 1 of account, contract, or policy.	8
`bown2`	Individual Beneficial Owner 2	Individual beneficial owner 2 of account, contract, or policy.	9
`bown3`	Individual Beneficial Owner 3	Individual beneficial owner 3 of account, contract, or policy.	10
`bown4`	Individual Beneficial Owner 4	Individual beneficial owner 4 of account, contract, or policy.	11
`bown5`	Individual Beneficial Owner 5	Individual beneficial owner 5 of account, contract, or policy.	12
`bown6`	Individual Beneficial Owner 6	Individual beneficial owner 6 of account, contract, or policy.	13
`cown`	Contingent Owner	Contingent owner of account, contract, or policy (not the insured).	14
`ctrl`	Control Person	Person in control of account.	15
`tte`	Trustee	Trustee.	16
`ptte`	Prior Trustee	Prior Trustee.	17
`ctte`	Contingent Trustee	Contingent Trustee.	18
`plantte`	Plan Trustee	Plan Trustee.	19
`pplantte`	Prior Plan Trustee	Prior Plan Trustee.	20
`ins`	Insured	Insured.	21
`pins`	Prior Insured	Prior Insured.	22
`ann`	Annuitant	Annuitant.	23
`pann`	Prior Annuitant	Prior Annuitant.	24
`cann`	Contingent Annuitant	Contingent Annuitant.	25
`app`	Applicant	Applicant (when not the owner or insured).	26
`biz`	Business Profile	Business Profile.	26
`pbiz`	Previous Business Profile	Previous Business Profile.	26
`loc`	Business Location	Business Location.	26
`cus`	Custodian	Custodian (has the fiduciary responsibility for a minor child).	27
`pcus`	Prior Custodian	Prior Custodian (has the fiduciary responsibility for a minor child).	28
`guard`	Guardian	Guardian or responsible individual.	29
`pguard`	Prior Guardian	Prior Guardian or responsible individual.	30
`authind`	Authorized Individual	Authorized Individual, Employer, or Plan Sponsor who is authorized to manage the account.	31
`pauthind`	Prior Authorized Individual	The prior or existing Authorized Individual, Employer, or Plan Sponsor who is authorized to manage the account.	32
`stakeholder`	Stakeholder	Account stakeholder who has an interest in the account (can include authorized individuals).	33
`int`	Interested Party	Interested Party.	34
`planadm`	Plan Administrator	Plan Administrator for benefit plans.	35
`par`	Participant	Participant.	36
`fid`	Fiduciary	Fiduciary is the person with financial responsibility for the account.	37
`contact`	Contact	Contact person.	38
`petitioner`	Petitioner	Petitioner.	39
`petitionermom`	Petitioner Mother	Petitioner Mother.	40
`petitionerdad`	Petitioner Father	Petitioner Father.	41
`father`	Father	Father (dad).	42
`spou`	Spouse	Spouse to the account owner, when specifically called for (not a replacement for Owner 2).	43
`mother`	Mother	Mother (mom).	44
`prnt`	Parent	Parent to someone identified on the form, when specifically called for (not a replacement for Owner or Custodian).	45
`gprnt`	Grandparent	Grandparent to someone identified on the form, when specifically called for (not a replacement for Owner or Custodian).	46
`sib`	Sibling	Sibling: brother, sister, half-brother, half-sister, etc.	47
`fam`	Family	Family members including spouse, partner, and children.	48
`child`	Child	Child (son, daughter).	49
`ustaxpayer`	US Taxpayer	US Taxpayer who signed the document when different than the owner.	50
`dep`	Dependent	Dependent (not necessarily a minor).	51
`min`	Minor	Minor (for custodial accounts).	52
`wit`	Witness	Witness of client signature or actions.	53
`asn`	Assignee	Person who is being assigned to a policy or contract.	54
`grant`	Grantor	Person who is granting something to another.	55
`pay`	Payee	Person who is being paid.	56
`ben`	Beneficiary	Beneficiary.	57
`oben`	Original Beneficiary	Original Beneficiary.	58
`pben`	Prior Beneficiary	Prior Beneficiary.	59
`cben`	Contingent Beneficiary	Contingent Beneficiary.	60
`med`	Medical Examiner	Medical Examiner when qualifying a client for insurance.	61
`phy`	Physician	Client's physician.	62
`sec`	Corporate Secretary	A corporation's designated Secretary who is authorized to act in the role of secretary for the corporation.	63
`pres`	Corporate President	A corporation's designated President who is authorized to act in the role of president for the corporation.	64
`sig`	Signatory	Additional signatories for a document when no other persons on the form fit the signing role, and recipients who are not signing but receiving a copy (role number 11 and above).	65
`guar`	Guarantor	Person who guarantees an account or obligation.	66
`donor`	Donor	Person who is acting as a donor.	67
`rcpt`	Receipt Signer	Person who signed as in receipt of the document.	68
`ntry`	Notary Public	Notary Public who witnesses signatures.	69
`interp`	Interpreter	Interpreter or Translator.	70
`bnk`	Bank Account Information	Bank Account Information (depositor).	96
`newbnk`	New Bank Account Information	New Bank Account Information.	96
`fnd`	Fund Source	Fund Source for funding application.	97
`paralegal`	Paralegal	Paralegal.	97
`lawyer`	Lawyer	Lawyer or attorney.	98
`lawfirm`	Law Firm	Law firm name.	99
`prep`	Prior Rep	Prior Rep (representative, advisor, adviser, agent).	100
`rep`	Rep	Rep (representative, advisor, adviser, agent).	101
`ria`	RIA	Registered Investment Advisor.	102
`princ`	Principal	Principal.	103
`osj`	OSJ	OSJ.	104
`agent`	Agent	Authorized Agent.	105
`tpa`	TPA	Third-party administrator or TAMP (turnkey asset management program).	106
`cusbank`	Custodian Bank	Custodian bank responsible for safeguarding financial assets.	107
`ccequip`	Credit Card Equipment	Credit Card Equipment.	199
`dec`	Deceased	Deceased.	998

For developers: where this shows up in the API

This section is for the technical reader implementing the integration.

FieldName property inside the FormFields array uses the role prefix as the first segment, for example "FieldName": "1own.FName".
/forms/fields endpoint returns the field names (and therefore the role prefixes) present on a given set of forms. Call this when you need to know which roles a form supports before building your prefill logic.
TestDataMode property (set to TRUE) launches the form with every field labeled with its own name. Easiest way to confirm which role prefixes are on a form visually.

Pitfalls

Role numbers are 1-indexed. First owner is 1own, not 0own. Same for every other role.
Similar-looking prefixes are not the same role. own (Owner), cown (Contingent Owner), pown (Prior Owner), and bown (Beneficial Owner) are four different roles. Check the description in the full reference if you are not certain which one a form is asking for.
Do not substitute one role for another. Spouse and Owner 2 are different roles even if the same person fills both. A form was built expecting specific roles. Sending spouse data to an Owner 2 field, or vice versa, will not work.
The same role prefix refers to the same person across forms in a package by default. If you generate a package with three forms and all three ask for Owner 1's name, prefilling 1own.FName once fills all three. If you need different people on different forms (for example, two separate households on the same package), see Form Groups and Instances.

Continue with these articles to understand the related concepts and workflows:

Fields and Field Names — Learn how role prefixes fit into the full Quik! field-name structure.
Form Groups and Instances — Understand how roles behave when one package includes multiple transactions or data sets.
Field Mapping — See how to map the right customer data to the right role on a form.
Send Direct to DocuSign — Learn how roles connect to signer setup in a DocuSign workflow.

Fields and Field Names

Form Groups and Instances