Disclosing the Receipt of Gifts, Travel or Hospitality
Table of Contents
Use Case
- Disclosing the Receipt of Gifts, Travel or Hospitality (RGTH) requests are used by employees to disclose the receipt or request approval to accept an upcoming gift, travel or hospitality from an individual or entity.
- The gift, travel or hospitality received is typically associated with the submitter’s employment.
- This request types helps the Business User identify the details on what is being offered to the employee as part of this gift, travel and hospitality request.
- This workflow differs from the GTH-Provide workflow as the offer of a gift or other benefit should still be tracked and logged even if rejected, while for a planned giving, the submitter can simply remove the planned item if the approver does not agree to its provision.
Key Features
- Disclosing the Receipt of Gifts, Travel or Hospitality requests consists of one section for Disclosure Details.
Things to Note
• Submitting
- Disclosure categories can be updated from the standard list configured by Lextegrity.
- The three main support categories of gift, travel, and hospitality received can be broken down further in order to track specific types of benefit (i.e. Hospitality is typically separated into Food & Beverage, Travel & Lodging, and Other)
-
The submitter can disclose one benefit for each request. This is done to ensure that each disclosure specifically contains details related to the benefit being accepted and also gives the reviewer or approver a chance to take action on different disclosures separately.
- If two gifts have been received, there should be two disclosures submitted – one for each benefit.
- If one hospitality and one entertainment benefits have been provided, there should be a disclosure submitted for each benefit.
- After submission, the request can be canceled but not deleted.
• Approving
- 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.
- 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
- Spend amounts can be entered in any currency.
- Specify local and regional limits for each category of support.
• 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 |
Useful Links
- How to Disclose the Receipt of Gifts, Travel or Hospitality
- Approving a Disclosure for the Receipt of Gifts, Travel, or Hospitality
- Email Templates
- Email Reminders