1. Rejected Bill Notifications Beyond Workflow Participants
Currently, when a bill is rejected, Ramp only notifies the bill creator and approvers. This creates visibility issues when others—such as accounting staff, operations coordinators, or shared inbox monitors—need to know a bill has been rejected but aren’t part of the approval chain.
Feature Suggestion:
- Enable the ability to configure rejection-specific notifications to designated users, roles, or distribution lists outside of the workflow.
- Alternatively, add a global dashboard indicator or filter for “Rejected” bills to help teams proactively identify and address them.
This would prevent rejected items from falling through the cracks and allow for quicker resolution and resubmission. This creates a blackhole of rejected invoices that are not simple to monitor and people are not following-up.
2. “Send Back for Edits” Instead of Full Rejection
In Ramp’s corporate card transaction review, there’s a helpful feature that allows reviewers to send transactions back to employees with comments for corrections. However, Bill Pay currently lacks this functionality.
If an invoice is missing details or needs small edits, our only option is to reject the bill entirely—forcing the process to restart from scratch. This creates unnecessary back-and-forth and breaks workflow continuity.
Feature Suggestion:
- Introduce a “Send Back to Submitter” option in Bill Pay that lets reviewers return a bill for edits with comments, without rejecting it outright.
- This would mirror the corporate card experience and streamline collaboration between requesters and approvers.
Both of these enhancements would greatly improve the Ramp Bill Pay experience by adding flexibility and improving communication across teams. We’d love to see these added to your roadmap. Thanks for considering!
Note: We have moved our corp approval process to Ramp instead of our accounting system, the lack of this feature is causing concern.