Political Contributions
Written by Michelle Henley
Updated at January 22nd, 2024
Table of Contents
Use Case
- Political Contribution request type is used to seek pre-approval to provide a political contribution to an organization.
Key Features
-
Political Contributions request is separated into two sections:
- Recipient Details section to capture the details of the recipient and type of contribution requested for them.
- Contribution Details section to capture the type of political contribution that will be provided to the recipient.
Things to Note
• Submitting
- The questionnaire is designed to capture relevant information on the activity to be provided and the entity who will be the beneficiary of this activity .
- In Political Contribution requests, the recipient of the request is always an organization. An individual can not be added as the main beneficiary of the funding request.
- The entity that is receiving the contribution is the main focus of the request. The first step in creating a request uses the Recipient Search feature to select from an existing list of organizations to ensure duplicate organizations are not unnecessarily added.
- New entities can be added as part of request submission, if the Recipient Search yields no matching results.
- Different forms of political contributions can be specified in the request.
- Users are asked to provide details related to the entity first, followed by the activity details under which the contribution is being requested.
- Changes can be made after the request is approved. However, that will require the request to be re-approved by all approvers based on the workflow configuration.
- Initially selected approvers can not be changed at the time of re-submitting the activity or the consultants.
- Spend Amounts can be entered in any currency. However, the totals are calculated in the default currency set for the application.
• Approving
- Approvers take action on the entire request (unlike an Engage a Consultant request, where the Approvers take action on the activity and each recipient in separate steps).
- Approvers can approve or reject a request. Once the request is rejected, it moves into rejected status and can not be re-submitted.
- Approvers have the ability to request for more information from the submitter during the approval process. In such instances, the request needs to be re-submitted by the submitter after the updates have been made. Depending on the approval workflow configuration, the request will go back to the same approver for review or approval workflow can be initiated from the beginning.
• Spending
- Aggregate Spend and Count analysis at entity level.
- Allows Business Users to define one entity per funding request, giving approvers fully visibility into the spend amounts and flexibility to approve a specific entry.
• Oversight
- In-request screening using either Refintiv or RDC to compare individual and organization names against watchlist data.
• Request Features
Key Features
- Editor Collaboration allows different users to collaborate on filling details of the engagement.
- Approver Collaboration allows one of many approver collaborators to approve in any one approval step.
- Automated Approver Collaboration is used to automatically assign approver collaborators.
- Assign tasks to yourself, other users, or even third-parties.
- Easy-to-follow Request History tracks a complete audit trail of the changes and actions taken on the request throughout the approval process.
- Request Version Comparison allows for the ability to compare between different versions of the request if updates are made to the request before, during, and after the approval process.
- Business Owner configuration allows for requests to be submitted on behalf of someone else or to identify the actual business owner of the request.
Configurable Components
|
Request Configurations |