It would be nice, if as part of the workflow there was an option to auto reject requests if an incorrect vendor is selected. For instance, if you have spend program with contracts for “cups” and they can only be purchased from XYZ and ABC; if a request comes in from 123, the system should auto-reject the request.
3 Likes
Thank you, Calvin! Option 1 works perfectly.
1 Like
bumping this request. we just added a ramp-only field “Is this an itemized receipt?” and I would like reimbursement requests to be AUTO REJECTED if the user selects “No”.
1 Like
Is it possible to train the AI policy to review the receipts? just saying that it has seemed to us that Ramp AI is looking at the attached receipts to help better code transactions than hard rules - like 7-Eleven can be Fuel or Food/other and Ramp has been properly suggesting the codes detecting when it is Fuel. Just a thought as it is more flexible than hard coded rules
Hi all! Calvin from the Product team here.
For procurement requests (Ro): for your cups example, you have a couple of options. My recommendation would be to prevent requests for unapproved vendors before submission, rather than rejecting them afterward.
-
Option 1 (recommended): Restrict vendors on the request form. Where vendor custom groups are enabled, create a group containing only XYZ and ABC. In Manage spend → Programs, edit the program’s Vendor question, check Always required, enable Restrict available vendors, and select that group. Leave Allow adding new vendors to group off. Requesters must then choose an allowed vendor before submitting. See Vendor custom groups.
-
Option 2: Send requests back for corrections. If the Send back node is enabled for your account, you can place it on a conditional workflow path and assign it to the requester with instructions explaining what to change. This pauses that path for follow-up—it does not reject the request. See Configuring Procurement Workflows for building conditional paths. Reviewers can also send requests back from a pending approval or form step using Request changes.
For auto-reject on card transaction and reimbursements (Tyler, Stuart) : we support this capability and are rolling it out gradually! It is available in early access if you are a Plus Customer using the Policy Agent. Head to What’s New and look for “Policy Agent send-backs and repayments”. All you need to do is add a rule to the “send back” section of the policy document for unitemized receipts. No custom field needed.
1 Like