Emburse / Product / Recurring Spend

Recurring Spend

Platform Web Tooling Figma Year 2023 Status Shipped
Recurring Spend — header image

Context

Emburse Spend’s mission is to help companies better manage their Card-Based Vendor Spend by automating the reconciliation of as many of these transactions as possible. Due to the predictable nature of subscriptions and other recurring spend, these are the simplest types of spend that we have an opportunity to make easier to manage.

This project aims to facilitate configuring automation for this type of spend while offering customers the ability to confirm or ignore suggestions our ML model picks up on based on transaction history and spending patterns.

Goals & Success Metrics

  • Provide proactive management of recurring spend
  • Enable automation for subscription/recurring transactions
  • Allow admins to quickly Identify Cost-Saving Opportunities wherever possible
  • Differentiate ourselves as a “Vendor Card-Spend” solution

Users

  • Admins

Inspiration Explored

Lofi Wireframes

Proposed Solution

Final Design & Key Screens

New Recurring Spend Page
Mark as Recurring
Create New Card
Track Recurring Spend Only

Research & Testing Methods

  • Usability Testing

Key Insights & Findings

  • Recurring spend icon intended purpose not clear
  • Creating a new card had a 100% success rate
  • Users easily found where to manage their recurring spend
  • Marking expenses as recurring and finding the next payment date were both highly successful

Recommendations For Next Iteration

  • More clearly indicate discoverability of recurring spend icon with hover effect, eg. Upon launch, utilize Pendo guide to point out the ability to click to confirm or deny.
  • Include a link to Transactions for the payments from the Recurring Spend page, indicating the status of the transaction.
  • Clarify the language of buttons. “Edit” should only say “Edit” if there is something that is truly editable.
  • Tool-tip to explain expectations around card chargeability, and ability to re-activate moving forward.

Reflection

  • What worked: Overall discoverability of this new feature. Admins were overall excited about the feature and would be comfortable using it today.
  • What didn’t: Some options seemed buried to users and didn't seem to have a clear path.