Signatory Mandate
The Signatory Mandate Answer is used to specify the authorization arrangement for account operations, indicating who has signing authority and under what conditions.
Fields
| Field | Type | Required | Description |
|---|---|---|---|
fieldTypeId | string | Yes | Must be set to "SignatoryMandate" (from FieldTypeEnum) |
signatoryMandateId | string | Yes | ID of the selected signatory mandate |
Example Usage
{
"fieldId": "b8c9d0e1-2f3g-4h5i-6j7k-8l9m0n1o2p3q",
"answer": {
"fieldTypeId": "SignatoryMandate",
"signatoryMandateId": "a640b5fd-0b98-494a-a6ec-6f7f8e323ff72"
}
}
Lookup References
This answer model requires values from the following lookup source:
Signatory Mandate Types: For valid values for the signatoryMandateId field, please refer to the Lookup API documentation and use the "SignatoryMandateEnum" lookup source.
Notes
- The signatory mandate defines the rules for account operation and transaction authorization.
- Common signatory mandate types include single signatory, joint signatories (any two to sign), specific combination of signatories, tiered authorization based on transaction amount, etc.
- The signatory mandate is particularly important for corporate accounts and accounts with multiple authorized users.
- This information affects operational processes and may influence risk assessment.
- Changes to the signatory mandate typically require formal documentation and verification.
- The signatory mandate should be consistent with the entity's governance structure and organizational policy.
- Different types of mandates may have different security implications and may require different control measures.