The Request selector appears in the Expenses app for certain expenses when specific conditions are met. It allows you to link an expense to an existing request when the criteria below apply.
Request selector visibility
The expense must be in Draft status.
For bank expenses, at least one enabled request type must have an allowed payment method of Bill.
For card expenses, at least one enabled request type must have an allowed payment method of Card.
Only requests with the status Open appear in the drop-down list.
Supplier filtering
If the expense has a Supplier ID, only requests with either a matching supplier ID or no supplier are shown.
If the expense has no Supplier ID, supplier-based filtering is skipped.
Requests with inactive suppliers are always excluded.
A suggested supplier (a name only, without an ID) is treated as having no Supplier ID.
Who can link an expense to a request
A user can link an expense to a request if any of the following conditions is met:
Their role includes the policy Link expenses to any request.
They are a team manager of the request.
They act as a reviewer within the workflow for that request type.
They are both the owner of the expense and the owner of the request.
Expense types
Bank expenses can be linked to requests with a Bill payment method.
Card expenses can be linked to requests with a Card payment method.
Both bank and card expenses can be linked to requests with a None payment method if the request type allows the relevant outcome type.
Expenses cannot be linked to requests with the No payment needed payment method.