Batching of Reimbursements Notifications

Ability to batch the notifications the reviewer of Employee Expense Reimbursements receives.

1 Like

Hi Nick, thank you for the helpful feedback! When you are referring to the notifications, do you mean batch email notifications with a certain cadence vs getting an email notification every time someone submits a reimbursement request that needs to be reviewed?

Hi Rehana, thank you for your reply and my apologies for my delayed answer! Yes, the ability to batch notifications with a certain cadence (i.e. once a week, twice a month) as opposed to getting an email notification every time someone submits a reimbursement request to be reviewed.

It’s important to note that I’m not the reviewer in our organization myself, so my answer above is to the best of my knowledge. But based on your response, I can definitely relay the information to our reviewer and will keep you posted if I was not providing the proper context.

Thank you!

I would be interested in batching not only the notifications, but the actual reimbursements also. Would allow the accounting department to do just one upload per batch (we prefer weekly), versus having to do multiple ramp exports and imports into our accounting software (for bank reconciliation purposes, each reimbursement debited from our company’s account needs to be a separate export).

2 Likes

Posting on this thread - I see its old but this still applies today. Our managers receiving 1 email per reimbursement transaction for users that may have 10 submitted per day is going to get frustrating fast.
Thank you Ramp team!

Hi @Rachel_Selkirk, Jerry from the Ramp engineering team here. Could it be potentially due to a “Notify” step in an approval policy workflow (example screenshot below)?

1 Like

Hey @Jerry_Tsui ! We do not have a notify step in our approval flows. Its just requiring approvals, and in doing so is sending 1 notification per receipt even when taking advantage of the reimbursement ‘groupings’.

@Jerry_Tsui — to further elaborate on @Rachel_Selkirk’s point:

Our leaders are finding it challenging that each reimbursement item (hotel, flight, per diem, Uber, etc.) triggers a separate Slack notification. For a single trip, this can result in multiple pings, which makes review and approval harder.

What they’re asking for is a more consolidated, trip-level view — similar to a traditional expense report — where a team lead can review all related expenses together and see the total spend for that trip in one place.

We understand we have some control over email notifications, but there appear to be limitations with Slack notifications today, which is where this becomes a pain point.

cc: @charlotte @Rehana

1 Like