Exploring the Close the Request Process

Objective

After completing this lesson, you will be able to identify key considerations for the Close the Request process.

Overview of the Close the Request Process

When managing budget requests, it’s important to properly close requests to release any unspent funds. You can do this using one of the following methods:

  • User defined closure - The user sets an end date on the request header, which acts as the automatic closure point for the request.

    Note

    If no date is provided by the user, the request will automatically close on the last date it was approved.
  • Administrator defined extension - The administrator can extend all requests beyond the user-defined end date by specifying a fixed number of additional days using the Request Active Days option in Request Policies. The requests are automatically closed after the specified duration.The image shows a screenshot of Modify Request Policy: Approve then Book settings. Several key options are listed including Request Active Days (highlighted in yellow).

In addition to extending a request, administrators have the flexibility to reopen the request as needed. To reopen a request, enable Allow Request administrator to re-open a Request in the Request Admin Site Settings.

The image shows a screenshot of the Site Settings page under Request Admin. The page includes a list of different options including Allow Request administrator to re-open a Request (highlighted in yellow) with checkboxes, some enabled. Save and Cancel buttons are located at the top of these options.

Summary

  • Close requests to return unspent funds to the budget.
  • Users can set a request end date for automatic closure.
  • Requests close automatically on the last approval date if no end date is set.
  • Administrators can extend request duration with the Request Active Days option.
  • Administrators can reopen closed requests when necessary.