Provide Donations and Sponsorships
Written by Michelle Henley
Updated at January 22nd, 2024
Table of Contents
Use Case
- Provide Donations and Sponsorship requests are used to seek pre-approval to provide funding support (via sponsorship or donation) to an entity on behalf of the company.
- Used in scenarios where a funding request is initiated internally within the company.
- This request is designed to capture relevant information on the activity to be provided and the entity who will be the beneficiary of this activity.
Note: Currently, External Funding requests does not have an external facing module where organizations can submit requests to receive funding. We plan to offer an external portal in 2024.
Key Features
-
Providing Donations and Sponsorship requests are separated into two sections:
- Entity section to capture the details of the recipient entity and type of support requested for them.
- Activity section to capture the details related to the event.
Things to Note
• Submitting
- The recipient of a Donations and Sponsorship request is always an organization. An individual cannot be added as the main beneficiary of the funding request.
- The entity that is receiving the funding 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 funding is being requested for an entity for the first time.
- Allows Business Users to initiate funding requests internally by identifying the entity that will receive the funding.
- 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.
- 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 funding request (unlike an Engage a Consultant request, where the Approvers take action on the activity and each recipient in separate steps).
- Once a request is rejected, it moves into rejected status and can not be re-submitted.
- 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.
- Approvers have the ability to request for more information from the submitter of the request. 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 the approval workflow can be initiated from the beginning.
• Spending
- Aggregate Spend and Count analysis at entity level.
- Specify different forms of donation or sponsorship to be used while providing donation or sponsorship in a request.
• 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 |