Loading running mileageLoading book count

Reimbursement Portal

From 20-page forms to one-click invoicing

CoachArt2 min read
  • FinTech
  • Education
  • UI/UX Designer
CoachArt Supply Request Form Review showing requested items, volunteer details, a total, and a Submit Request button.
Role
UI/UX Designer
Team
9 developers, 2 designers
Timeline
Jan–Jun 2024
Tools
Figma

The Challenge

20 Pages, 3 Channels, 1 Bottleneck

Teachers submitted reimbursement requests through a lengthy, rigid form and supply requests through a completely separate email channel. Admins juggled inputs from both channels and manually re-entered data into Bill.com to generate invoices.

Circular workflow diagram connecting volunteers and staff across the supply-request and billing process.

We asked: how might we build a scalable expense management system that simplified teacher submissions, unified both request types, and automated invoice generation on the admin side?

My Role & Process

As the UI/UX designer…

I partnered with another designer to sketch wireframes, iterate based on client feedback, and prepare detailed design documentation for engineering handoff, collaborating closely with developers across 3 sprints to validate technical feasibility throughout the build.

Discovery Research

From forms to frustration

Methods

  • 3 Staff interviews
  • User personas
  • Journey mapping
Volunteer journey map with Shop, Fill, Submit, and Receive phases, including pain points about the long form, finding totals, and creating an account.
Volunteer journey map
Admin journey map with Assess, Approve, Notify, and Send phases, including pain points around receipt handling, repeated data entry, and referrals.
Admin journey map

Key Insights

  • Teachers had to complete a rigid, 20-page Google Form with repetitive fields and no flexible editing.
  • Supply requests were submitted via email through a completely separate process, creating confusion for volunteers and admins alike.
  • Transferring data to and from Bill.com was manual, error-prone, and a major time sink for admins.

“I want to have a simpler and clear way to request supplies and submit reimbursements.”

— Volunteer

“I want to create bills within Bill.com with minimal manual effort.”

— Operations Specialist

Design Decisions

3 Constraints, 3 Trade-offs, 1 Platform

Reimbursement forms that flex

CoachArt initially used a fixed-length Google Form for users to submit their reimbursements. Through our own evaluation, we believed that the form was padded with unnecessary pages which made reviewing frustrating. Thus, we designed a preview layer so users could easily view all of their submissions and notice any inconsistencies at a glance.

However, early feedback said that editing an entry required too many clicks so we opted for a tabbed format that allowed users to easily edit and compare reimbursements.

Old CoachArt reimbursement portal showing two receipt previews and their reimbursement details in one long page.
Old reimbursement portal
New CoachArt reimbursement portal showing a receipt in an editable tabbed interface.
New reimbursement portal

02 Supply request that feel familiar

Volunteers emailed raw purchase links to admins, but the lack of visible confirmation often led to missing information or the wrong item being sent. Thus, we added link previews, quantity counts, and pricing, but without a clear layout hierarchy, the screen still felt cluttered and hard to parse.

Ultimately, I designed items to be displayed in a familiar e-commerce-style layout, aligning with existing mental models and user flows.

Old CoachArt supply portal showing supply requests as a grid of product cards.
Old supply portal
New CoachArt supply portal showing supply requests in a familiar e-commerce-style list.
New supply portal

Finding opportunities in the admin portal

In order to use Bill.com's API to automate invoice creation, submissions needed to be in a PDF format. Our first thought was to generate a PDF immediately after the volunteer’s submission so the admin needed to just review the PDF. However, I realized that the timing was wrong: admins needed to review submissions first, PDF generation was the final step.

Because the static PDF was the final step, we were able to build interactive, item-level check marks with streamlined feedback flows, letting admins flag issues precisely and invoice in a single pass.

Old CoachArt admin portal showing a generated reimbursement PDF for review.
Old admin portal
New CoachArt admin portal showing interactive item-level approval controls.
New admin portal

Final Product

Double-sided portal

Dynamic, receipt-by-receipt form with side-by-side preview and editing.

Impact

6 Steps to 1

  • 90% reduction in reimbursement submission time
  • Per-receipt processing cut from 6 manual steps to 1 — eliminating manual download/upload and re-entry of 5 associated form fields per receipt
  • Adopted by 450+ volunteers and teachers

Reflection

Looking back, I'd have spent more time researching how existing cloud ERP systems like Ramp or Oracle handle financial workflows before jumping into wireframes. In hindsight, I would’ve added features like bulk review or smart categorization into CoachArt’s reimbursement portal.